[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: IANA Considerations for RSVP
- To: Kireeti Kompella <kireeti@juniper.net>
- Subject: Re: IANA Considerations for RSVP
- From: Yangguang Xu <xuyg@lucent.com>
- Date: Thu, 23 Jan 2003 14:20:22 -0500
- Cc: "Lin, Zhi-Wei (Zhi)" <zwlin@lucent.com>, David Charlap <David.Charlap@marconi.com>, Bob Braden <braden@ISI.EDU>, rsvp@ISI.EDU, ccamp@ops.ietf.org, mpls@UU.NET, iana@ISI.EDU, sob@harvard.edu, mankin@psg.com, bwijnen@lucent.com
- Organization: Lucent Technologies, Inc.
- References: <20030123104246.W83975-100000@kummer.juniper.net>
Kireeti,
> > 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...
>
> Do you consider deprecating ResvErr and ResvTear not "forcibly changing
> RSVP or major change in direction"?
>
Well, it's my turn to beg to differ :) If you read the document && understand it
&& don't take any prejudice, then it may be more like specifying rules for using
a protocol for an application with some hard requirements.
Regards,
Yangguang