Subject: RE: RFC3209

From: "Feng, Mark" <[email-masked]>
Date: Wed, 1 May 2002 13:39:33 -0700

Please see comments below.

- Mark

> -----Original Message-----
> From: Shahram Davari [mailto:[email-masked]]
> Sent: Wednesday, May 01, 2002 10:10 AM
> To: 'No name'; [email-masked]
> Subject: RE: RFC3209
> 
> 
> Hi,
> 
> A related question:
> 
> Is the RESV RRO appended to the Path RRO or the PATH RRO is 
> stripped off 
> in the RESV message?
> 

The Resv RROs specifies the reverse path. The Path RRO shouldn't be
appended.

> My reading of RFC3209 is that the PATH RRO is stripped off, 
> before sending RESV message. 
> If this is the case then the Egress never adds its address to 
> the PATH RRO. It only adds its
> address to the RESV RRO, and therefore the Notify message 
> should be sent to the EGRESS.
> 
> However, any such Notify sent to Egress will be converted to 
> Path Error message which will then be
> sent to the ingress. So practically it should not make any 
> difference to generate the PathError
> at the egress or to sent Notify to the egress which then 
> converts it to PathErorr.
>
> -Shahram
> 
> > -----Original Message-----
> > From: No name [mailto:[email-masked]]
> > Sent: Tuesday, April 30, 2002 2:57 PM
> > To: [email-masked]
> > Subject: RFC3209
> > 
> > 
> > Hi
> > 
> > This questions is about the handling of "RRO too large for 
> MTU" cases.
> > 
> > "If the newly added subobject causes the RRO to be too big 
> to fit in a
> > Path (or Resv) message, the RRO object SHALL be dropped from 
> > the   message 
> > and message processing continues as normal.  A PathErr (or  
>  ResvErr) 
> > message SHOULD be sent back to the sender (or receiver).  An
> > error code of "Notify" and an error value of "RRO too large for MTU"
> > is used.  If the receiver receives such a ResvErr, it SHOULD send a
> > PathErr message with error code of "Notify" and an error value of
> > "RRO notification". "
> > 
> > 
> > IF adding the EGRESS's IPv4 subobject to the RRO makes the 
> > RRO too large for 
> > MTU, will it send a RESVERR or PATHERR,
> > my guess is it should send a Patherror upstream.
> >

The egress cannot send ResvErr. Where would that go? It should send a
PathErr, so that the ingress node can take action. But I am not sure the
possibility of such error in the egress node, considering the limiting size
is the IP packet size.
 
> > I apologize if this has been answered before, but i put this 
> > question up 
> > since i couldnt find any specific discussion that answers 
> my question.
> > 
> > regards
> > 
> > Manish
> > 
> > 
> > 
> > 
> > 
> > 
> > _________________________________________________________________
> > Chat with friends online, try MSN Messenger: 
> http://messenger.msn.com
> > 
>