The MPLS WG Archive

Cell Relay Retreat>MPLS WG Archive>month:2001-Feb> msg00339



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

New TTL Draft

  • From: Shahram Davari <Shahram_Davari@pmc-sierra.com>
  • Date: Tue, 27 Feb 2001 11:18:51 -0800
  • Cc: "'mpls@uu.net'" <mpls@UU.NET>, "'flefauch@cisco.com'" <flefauch@cisco.com>, "'liwwu@cisco.com'" <liwwu@cisco.com>, "'bsd@cisco.com'" <bsd@cisco.com>, Bora Akyol <akyol@pluris.com>

Hi Puneet,

Thanks for your reply. Please see my comments in-line:

> >2) Section 2.4 does not discuss an important case that is: 
> >egress processing of tunnels, i.e. pop and forwarding the 
> >packet as MPLS. 
> 
> Pop (or Egress Pop to distinguish from PHP) is actually 
> covered in section
> 2.3. The possibly operation when forwarding the packet as 
> MPLS are covered
> in the 3 bullets  of section 2.4. Combine section 2.3 and the relevant
> section of 2.4 and I think your concern about the missing 
> case should be
> answered. Hence as far as I can see the case is convered, but 
> please let me
> know if you still think that it is not addressed.
> >

As you know there are at least 2 distinct operations that are needed 
for TTL processing:

1) Determining iTTL
2) Determining oTTL

Section 2.3 describes the iTTL determination for both PHP and non-PHP case.
Section 2.4 however describes the oTTL determination for PHP case only. I 
can't see anywhere in the draft that talks about oTTL determination for non-PHP
case. Do you see any?
 

Yours,
Shahram