Re: [mpls] [mpls-tp] [PWE3] FW: Changes to PW ACH Channel Type allocation policy]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [mpls] [mpls-tp] [PWE3] FW: Changes to PW ACH Channel Type allocation policy]



Hi Stewart,

On Thu, Oct 2, 2008 at 8:39 PM, Stewart Bryant <stbryant at cisco.com> wrote:
> Since a reference was made to extension mechanisms proposed to
> the ISIS WG, and since there seemed to be some enthusiasm
> for it, to the point where there was a suggestion that we
> might follow the same model, I asked my college Mike Shand
> for some history and background and what happened next.

[cut]

> However, despite all this, the draft expired in November 2005 and there has
> been no subsequent desire to resurrect it.
>
> 	Mike

Ok, let me talk about something that is not dead :-)

in RSVP context class numbers 124..127 and 188..191 and 252..255
are "reserved for Vendor Private Use".
(http://www.iana.org/assignments/rsvp-parameters)
Definition of "Organization/Vendor Private" is in RFC 3936:

---
"Organization/Vendor Private" ranges refer to values that are
enterprise-specific; these MUST NOT be registered with IANA.  For
Vendor Private values, the first 4-octet word of the data field
MUST be an enterprise code [ENT] as registered with the IANA
SMI Network Management Private Enterprise Codes, and the rest
of the data thereafter is for the private use of the
registered enterprise.  (For each RSVP entity that has a
Vendor Private range, it must be specified where exactly the
data field starts; see below for examples.)  In this way,
different enterprises, vendors, or Standards Development
Organizations (SDOs) can use the same code point
without fear of collision.
---

I did implement some vendor-private-application-specific extensions
to RSVP following rules above and rules of RFC 2205 Section 3.10
(obj with Class-Num 0bbbbbbb rejected, 10bbbbbb ignored, 11bbbbbb
opaquely forwarded).

Never had an interoperability problem.

Is such a policy/mechanism applicable to "PW ACH Channel Type"?

Dunno, I just wanted to compensate the IS-IS history :-))

What do you think?

Ciao
FF

ps
obviously IANA doesn't charge you for a Private Eterprise Number
(PEN) http://pen.iana.org/pen/PenApplication.page
_______________________________________________
mpls mailing list
mpls at ietf.org
https://www.ietf.org/mailman/listinfo/mpls



Note: Messages sent to this list are the opinions of the senders and do not imply endorsement by the IETF.