Hi Jonathan,
You've pointed out what I see as a problem with many experimental and
private IANA ranges. I agree with the solution you suggest is what
should be done - the vendor code should be required as the first 4
octets of the value field in TLVs in the experimental/vendor range.
This is also consistent with other OSPF IANA ranges defined in RFC 4940.
Thanks,
Acee
On Feb 15, 2008, at 1:41 PM, Sadler, Jonathan B. wrote:
Hi Acee,
Generally, the draft looks useful/good. One question: TLVs
32768-65535 are marked for Private Use -- what is the method for
distinguishing the meaning for these TLVs when two different
implementations utilize the same Private Use TLV? Should OUI be
placed in the first 3 octets? If so, can the I-D capture this?
Thanks,
Jonathan Sadler
From: [EMAIL PROTECTED] on behalf of Acee Lindem
Sent: Fri 2/15/2008 11:15 AM
To: OSPF List
Subject: [OSPF] WG Last Call for OSPF Link-local Signaling -draft-
ietf-ospf-lls-04.txt
This starts the WG last call for the subject document. The target
status is Proposed Standard.
The WG last call will begin today and will end March 1st, 2008 at
12:00 AM EST. Note that a previous revision (not including OSPFv3) of
this protocol extension was published as an experimental RFC 4813.
Thanks,
Acee
_______________________________________________
OSPF mailing list
[email protected]
http://www.ietf.org/mailman/listinfo/ospf
============================================================
The information contained in this message may be privileged
and confidential and protected from disclosure. If the reader
of this message is not the intended recipient, or an employee
or agent responsible for delivering this message to the
intended recipient, you are hereby notified that any reproduction,
dissemination or distribution of this communication is strictly
prohibited. If you have received this communication in error,
please notify us immediately by replying to the message and
deleting it from your computer. Thank you. Tellabs
============================================================
_______________________________________________
OSPF mailing list
[email protected]
http://www.ietf.org/mailman/listinfo/ospf
