The MPLS-OPS Archive[Date Prev][Date Next][Thread Prev][Thread Next] [Date Index][Thread Index][Author Index][Subject Index] Fwd: RE: Fwd: Explicit Null Configuration
Thanks to both for the clarifications. I had a feeling I might not be getting it quite right... Roger Williams >X-SpamCatcher-Score: 1 [X] >X-Real-To: rogerw@nordlink.com >Resent-Date: Sun, 22 Feb 2004 06:05:45 -0500 >X-Authentication-Warning: host.secure4-hosting.net: mplsrc12 set sender to >mpls-ops-request@mplsrc.com using -f >To: elkou141061@hotmail.com >Cc: mpls-ops@mplsrc.com >Subject: RE: Fwd: [MPLS-OPS]: Explicit Null Configuration >From: sthaug@nethelp.no >X-Mailer: Mew version 1.05+ on Emacs 19.34.1 >Date: Sun, 22 Feb 2004 11:53:32 +0100 >Resent-From: mpls-ops@mplsrc.com >X-Mailing-List: <mpls-ops@mplsrc.com> archive/latest/6797 >X-Loop: mpls-ops@mplsrc.com >Resent-Sender: mpls-ops-request@mplsrc.com > > > The above conflict with the (current) definition of explicit null ie: > > "This label value is only legal at the bottom of the label stack" . > > > > but in accordance with the (new/draft) definition which will remove the > > restriction of > > being at the bottom of the stack . their is a draft addressing this point > > but can not recall > > it's name . > >draft-rosen-mpls-explicit-null-01.txt: > > RFC 3032 defines a reserved label value known as "IPv4 Explicit NULL" > and a reserved label value known as "IPv6 Explicit NULL". It states > that these label values are only legal at the bottom of the MPLS > label stack. This restriction is now removed, so that those label > values are legal anywhere in the stack. > >Steinar Haug, Nethelp consulting, sthaug@nethelp.no > >------- >The MPLS-OPS Mailing List >Subscribe/Unsubscribe: http://www.mplsrc.com/mplsops.shtml >Archive: http://www.mplsrc.com/mpls-ops_archive.shtml ------- The MPLS-OPS Mailing List Subscribe/Unsubscribe: http://www.mplsrc.com/mplsops.shtml Archive: http://www.mplsrc.com/mpls-ops_archive.shtml |
|