The MPLS WG Archive

Cell Relay Retreat>MPLS WG Archive>month:2003-Apr> msg00085



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

[PWE3] I-D ACTION:draft-allan-mpls-pid-00.txt

  • From: "David Allan" <dallan@nortelnetworks.com>
  • Date: Fri, 4 Apr 2003 15:54:04 -0500
  • Cc: "'pwe3@ietf.org'" <pwe3@ietf.org>, "'mpls@uu.net'" <mpls@UU.NET>

Title: RE: [PWE3] I-D ACTION:draft-allan-mpls-pid-00.txt

Actually I suspect someone will suggest that 0000 will collide with deployed stuff ;-)

1000 was chosen not to collide with stuff that after writing I found may not be an issue. If we accept that existing PHP may lead to somthing trying to interpret this stuff, then avoiding all assigned IP version numbers is probably the best choice, which leaves 1-3 and 10-14, or 0 and 15 (the explicitly reserved values). IMO I would lean towards 15, which cannot be interpreted as a protocol at all and does not collide with IANA space.

Dave

> -----Original Message-----
> From: Shahram Davari [mailto:Shahram_Davari@pmc-sierra.com]
> Sent: Friday, April 04, 2003 3:28 PM
> To: Shahram Davari; Allan, David [CAR:NS00:EXCH]
> Cc: 'pwe3@ietf.org'; 'mpls@uu.net'
> Subject: RE: [PWE3] I-D ACTION:draft-allan-mpls-pid-00.txt
>
>
> Dave,
>
> Also isn't it better to use '0000' instead of '1000' for the
> first nibble. This way it won't interfere with any implementation.
>
> -Shahram
>
> >-----Original Message-----
> >From: Shahram Davari
> >Sent: Friday, April 04, 2003 3:25 PM
> >To: David Allan (E-mail)
> >Cc: pwe3@ietf.org; mpls@uu.net
> >Subject: RE: [PWE3] I-D ACTION:draft-allan-mpls-pid-00.txt
> >
> >
> >Hi Dave,
> >
> >I have a few questions/comments:
> >
> >1) Last sentence of section 2: It is not clear what the
> >loopback address is. I assume it is not a 127/8 address.
> >
> >2) Could you please explain bullet 2 of section 4 a bit more.
> >
> >3) Section 6: I assume by no PHP you mean when there is only
> >one label to be poped. right?
> >Also it might be possible to get a PPP PID for the extended
> >Payload ID control-word.
> >
> >Yours,
> >Shahram
> >
> >>-----Original Message-----
> >>From: Internet-Drafts@ietf.org [mailto:Internet-Drafts@ietf.org]
> >>Sent: Friday, April 04, 2003 6:44 AM
> >>Cc: mpls@uu.net; pwe3@ietf.org
> >>Subject: [PWE3] I-D ACTION:draft-allan-mpls-pid-00.txt
> >>
> >>
> >>A New Internet-Draft is available from the on-line
> >>Internet-Drafts directories.
> >>
> >>
> >>    Title           : MPLS and IP PW Payload ID
> >>    Author(s)       : D. Allan
> >>    Filename        : draft-allan-mpls-pid-00.txt
> >>    Pages           : 0
> >>    Date            : 2003-4-3
> >>   
> >>This memo defines an MPLS and PW payload ID. It describes
> how an MPLS
> >>payload ID may be used to address a number of issues
> associated with
> >>proprietary ECMP deployments. It describes how when used with PWs
> >>permits OAM and control protocols to be multiplexed with a PW.
> >>
> >>A URL for this Internet-Draft is:
> >>http://www.ietf.org/internet-drafts/draft-allan-mpls-pid-00.txt
> >>
> >>To remove yourself from the IETF Announcement list, send a
> message to
> >>ietf-announce-request with the word unsubscribe in the body of
> >>the message.
> >>
> >>Internet-Drafts are also available by anonymous FTP. Login
> >>with the username
> >>"anonymous" and a password of your e-mail address. After logging in,
> >>type "cd internet-drafts" and then
> >>    "get draft-allan-mpls-pid-00.txt".
> >>
> >>A list of Internet-Drafts directories can be found in
> >>http://www.ietf.org/shadow.html or
> >>ftp://ftp.ietf.org/ietf/1shadow-sites.txt
> >>
> >>
> >>Internet-Drafts can also be obtained by e-mail.
> >>
> >>Send a message to:
> >>    mailserv@ietf.org.
> >>In the body type:
> >>    "FILE /internet-drafts/draft-allan-mpls-pid-00.txt".
> >>   
> >>NOTE:       The mail server at ietf.org can return the document in
> >>    MIME-encoded form by using the "mpack" utility.  To use this
> >>    feature, insert the command "ENCODING mime" before the "FILE"
> >>    command.  To decode the response(s), you will need "munpack" or
> >>    a MIME-compliant mail reader.  Different MIME-compliant
> >>mail readers
> >>    exhibit different behavior, especially when dealing with
> >>    "multipart" MIME messages (i.e. documents which have been split
> >>    up into multiple messages), so check your local documentation on
> >>    how to manipulate these messages.
> >>           
> >>           
> >>Below is the data which will enable a MIME compliant mail reader
> >>implementation to automatically retrieve the ASCII version of the
> >>Internet-Draft.
> >>
> >
>