[LINK] McCrann calls on Latham to gazump Howard on Telstra

[Frank O'Connor]

Yes and No,

I believe I did specify that the network would be controlled by the 
telco (who would also be the dedicated service provider of its own 
multi-casted material). In that respect QOS would be guaranteed 
because both the QOS header and the multicast header could be used in 
combo with the router configuration to guarantee service quality.

For stuff posted from other providers/networks however the router 
configured controls would be ineffective - because router 
configurations differ according to users.

As Geoff says below there was 'no practical application' for the 20 
bit header in IPv6 ... but in an IPv6 only world this would in all 
likelihood change. The traffic class bits in IPv4 and IPv6 are 
devoted to the transport layer headers from memory ... which is 
useful for differentiating between services/applications at a header 
level, but given that other packet header items like the port number 
specifier in the header is also indicative of same, isn't really a 
QOS indicator as I'd understand it. (Most of the QOS in such 
circumstances would be configureable in-router rather than set by the 
header ... and serious QOS - IMHO - requires established standards 
and a hard wired approach to traffic management that doesn't depend 
on the individual router/switch configuration.)

Just my 2 cents worth ...

					Regards,

At 3:53 PM +1100 on 23/2/04 you wrote:
>  > That's (QOS I mean) a network layer problem ... which I
>>  believe IPv6 addresses quite well.
>
>This seems to be a pretty widely-held misconception about IPv6. As Geoff
>Huston explains:
>
>"Another consistent assertion is that V6 offers "bundled" support for
>differentiated Quality of Service (QoS), whereas V4 does not. The
>justification for this claim often points to the 20-bit flow label in the
>IPv6 header as some kind of instant solution to QoS. This conveniently omits
>to note that the flow identification field in the V6 header still has no
>practical application in large scale network environments. Both IPv4 and
>IPv6 support an 8 bit traffic class field, which includes the same 6 bit
>field for differentiated service code points, and both protocols offer the
>same fields to an Integrated Services packet classifier. From this
>perspective QoS deployment issues are neither helped nor hindered by the use
>of IPv4 or IPv6. Here, again, it's a case of nothing has changed."
>
>full article at: http://www.potaroo.net/papers/isoc/2003-01/Waiting.html
>
>Content-Type: application/x-pkcs7-signature;
>	name="smime.p7s"
>Content-Disposition: attachment;
>	filename="smime.p7s"
>
>Attachment converted: Macintosh HD:smime 2.p7s (????/----) (00121929)