The MPLS WG Archive

Cell Relay Retreat>MPLS WG Archive>month:2003-Jan> msg00096



[Date Prev][Date Next][Thread Prev][Thread Next]  
  [Date Index][Thread Index][Author Index][Subject Index]

IANA Considerations for RSVP

  • From: David Charlap <David.Charlap@marconi.com>
  • Date: Thu, 23 Jan 2003 12:01:37 -0500
  • CC: Bob Braden <braden@ISI.EDU>, rsvp@ISI.EDU, ccamp@ops.ietf.org, mpls@UU.NET, kireeti@juniper.net, iana@ISI.EDU, sob@harvard.edu, mankin@psg.com, bwijnen@lucent.com
  • Organization: Marconi, Vienna VA
  • User-Agent: Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:1.1) Gecko/20020826

Lin, Zhi-Wei (Zhi) wrote:
 >
 > The GMPLS RSVP-TE, which is done in IETF, makes major modifications
 > to RFC3209 and RFC2205 version of RSVP. The rest of the changes been
 > requested are three new objects, new error codes to support these
 > objects. This can hardly be characterized as forcibly changing RSVP
 > or major change in direction...

I am not criticizing the existance of GMPLS or the CCAMP work that's 
being done.  All of the IETF people involved in RSVP are aware of this 
and contribute to it as they feel necessary.

I'm far more concerned with non-IETF groups (like ITU, ATM Forum and 
others) deciding to develop their own incompatible extensions without 
even informing any IETF groups of their actions.

Groups like these should not be extending IETF protocols without 
consulting with the relevant IETF working groups.  Otherwise we end up 
with extensions that duplicate existing IETF functionality, don't 
coexist gracefully, and/or break interoperability.  And if these 
extensions become popular in products, the IETF will be forced to 
include them in the standards in order to prevent future IETF work from 
breaking them.

 > The extensions that's been requested were derived as a result of
 > discussions and efforts involving many IETF people as well (e.g.,
 > please look at the author list of the OIF UNI document). Your comment
 > seems to suggest that the work appear out of nowhere with no
 > participation from the IETF RSVP experts...this is clearly not
 > true...

I am not referring to OIF UNI.  They are doing consulting with relevant 
IETF groups as a part of their work.

I must have struck a nerve here, because yours is the second response 
I've gotten from somebody who thinks I'm referring to their specific 
IETF-approved RSVP extension, even though I specifically said I'm 
referring to extensions developed without IETF involvement.  And I think 
that was Bob's original issue as well - since he explicitly mentioned 
IANA RSVP requests coming from non-IETF sources.

-- David