RE: [dccp] I-D ACTION:draft-ietf-dccp-spec-13.txt

["Phelan, Tom" <tphelan at sonusnet.com>]

Hi All,

Well, I guess this one was my fault (sorry, Eddie) :-(.  I had seen discussions on other lists that said if you say SHOULD instead of MUST, you need to supply some reasons under which you could violate the SHOULD.  I can certainly live without the sentence.

Tom P.

> -----Original Message-----
> From: dccp-bounces at ietf.org [mailto:dccp-bounces at ietf.org]On Behalf Of
> Eddie Kohler
> Sent: Friday, December 09, 2005 11:43 AM
> To: Allison Mankin
> Cc: dccp group; Colin Perkins
> Subject: Re: [dccp] I-D ACTION:draft-ietf-dccp-spec-13.txt
> 
> 
> Guys,
> 
> I am happy to remove that sentence.  Of course I wish there 
> had been a comment 
> when that sentence was added; it was discussed on the list! :)
> 
> I had imagined the "discretion" would involve IANA 
> communicating with someone 
> else (dccp-wg or ADs), much as IANA is currently going to 
> contact me on every 
> Service Code request.
> 
> If you think this needs a new draft I'm happy to make one of 
> course, otherwise 
> just consider it removed.
> 
> Eddie
> 
> 
> Allison Mankin wrote:
> > Colin, DCCP,
> > 
> >    The guidelines may be violated at IANA's discretion.
> > 
> > Hmm, I missed that line there.  It's a sweet idea, but
> > IANA has already been given plenty of leeway because there's
> > nothing but SHOULD/SHOULD NOTs in here.  I'll ask
> > for this line to be removed.  (with AD hat on).
> > 
> > IANA is not in the position to have further discretion about
> > instructions - they register several hundred of our 
> protoocols and it
> > is not in their functional description to be even mildly 
> knowledgeable
> > about protocols in doing so.  They request clear instructions which
> > can be carried out efficiently.
> > 
> > Telling them that the instructions can involve any back-and-forth
> > email discussion with the requestors will be bad news to them.
> > 
> > I say this based on nearly a hundred IANA registry actions
> > I've worked with this year,  and sitting on the IETF-IANA committee,
> > which discusses its function and relation to the IETF.
> > 
> > Long response to one sentence :)  Sorry, Eddie.
> > 
> > Allison
> > 
> 
>