Hello working group,
We've received a heads up from Joel Halpern as LISP WG co-chair related
to draft-ietf-lisp-lcaf.
Please provide any comment that you think can help answer Joel's request
on whether or not the WG sees issue in the referenced work done by the
LISP WG.
Thank you,
-Thomas, as l3vpn co-chair
_________________________________________________________________________________________________________________________
Ce message et ses pieces jointes peuvent contenir des informations
confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce
message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages
electroniques etant susceptibles d'alteration,
France Telecom - Orange decline toute responsabilite si ce message a ete
altere, deforme ou falsifie. Merci.
This message and its attachments may contain confidential or privileged
information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete
this message and its attachments.
As emails may be altered, France Telecom - Orange is not liable for messages
that have been modified, changed or falsified.
Thank you.
--- Begin Message ---
My apologize for bothering so many of you.
The LISP Working group has adopted a draft which defines "LISP Canonical
Address Formats". These are type based encodings of different kinds of
addresses.
LISP is an experimental protocol which the working group is working on
revising (having completed the 7 base specs last spring.)
In order to lay groundwork for the many ideas that people have, and to
show how this canonical address format can be used, there are a numbwer
of type codes reserved for specific uses that impinge on other working
groups. If the LISP working were to decide to do more than define the
code point, this would require close involvement with one or more of the
working groups whose chairs are copied above. In fact, it is expected
that core work on using LISP in those spaces would belong in those
working groups.
In the interest of clarity, I and my co-chair are calling your attention
to these code point reservations now. Please let us know if you see any
issues. (I leave it to your judgment whether it is worth bothering your
working group with this heads up.)
Yours,
Joel (and Terry)
PS1: I am sorry if I missed anyone who should have gotten this.
PS2: Security ADs, I could not figure out who should get the heads up
for the Security data LCAF type.
--- End Message ---
