The MPLS-OPS Archive

Cell Relay Retreat>MPLS-OPS Archive>month:2005-May> msg00000



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

Fragmented LSP Echo Request

  • From: "M. elk" <elkou141061@hotmail.com>
  • Date: Wed, 4 May 2005 22:25:50 +0300
  • Resent-Date: Wed, 4 May 2005 14:16:47 -0400
  • X-OriginalArrivalTime: 04 May 2005 18:16:55.0841 (UTC) FILETIME=[743E1910:01C550D5]
  • X-Originating-Email: [elkou141061@hotmail.com]
  • X-Originating-IP: [57.250.229.136]
  • X-Scanned-By: MIMEDefang 2.45

Hi
 
1) LSP PING draft , did not specify if the DF bit to be set or clear in the IP header
    of the LSP Echo request . One implementation  always set DF bit .
    Any reason the draft opted to leave it unspecified ???
 
2) Case :DF not set
     For a Transient LSR , If the LSP Echo request is "TOO-Big" to be forwarded .
     the LSP Echo request will be fragmented as per section 3.4 in RFC 3032
     (Label Stack Encoding ) .   
 
    is it correct
 
3) Case : DF set .
 
    3a) Transient LSR send ICMP as per RFC 3032 .
 
    or
 
   3b) Transient LSR notice that the packet is LSP echo request and send echo reply
         directly to the Head-end (the source IP address in the echo request) with
         return code which indicate that fragmentation is needed .  
         If yes: Their is no return code defined for fragmentation error ??
 
  is it 3a or 3b .
 
Brgds