Re: [AVT] Outstanding issues on the HDREXT draft

[Dave Singer <singer at apple.com>]

At 22:04  -0500 17/02/08, Tom Taylor wrote:
>The basic point is that the IETF insists that the standards it 
>creates should result in interoperable implementations. Thus the 
>standards address not only implementation issues, but also process 
>issues that have to be resolved to achieve this result.
>
>Having taken this hard line, I will note that some IANA registries 
>also provide for a private namespace in addition to the public one. 
>The intent is to allow for vendor-specific implementations, but 
>other SDOs have sometimes taken advantage of this feature to modify 
>IETF protocols without going through IETF process. The Diameter 
>protocol is an example in many respects. Note, however, that the 
>process is not totally uncontrolled -- there is still an IANA 
>registry, even though no publicly available specification is 
>necessarily required.

I don't know Diameter, sorry.

But there are lots of places in IETF specs where X- names are 
allowed, and they are unregistered and *also subject to collision*. 
One of the points of using URIs was to sharply reduce the risk of 
collision, if properly used, even if they are not registered.

I mean, we have unregistered collision-sensitive payload names, for 
example.  The payload is probably the whole point of the RTP 
protocol, whereas header extensions are *defined* to be ignorable...

>
>So the question we have to resolve here is the degree to which the 
>IETF wishes to track (in the first instance) and review the 
>specification of RTP header extensions.

An absolute hard line on "if you want to register, then you are 
subject to review" is appropriate, and the intent is that it's in the 
draft.  I have no trouble adding  "and if your practice is public or 
likely to encounter other implementations, then you SHOULD register", 
as well.  That's appropriate.



-- 
David Singer
Apple/QuickTime
_______________________________________________
Audio/Video Transport Working Group
avt at ietf.org
http://www.ietf.org/mailman/listinfo/avt