![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
Hello Jukka, On 6 Nov 2009, at 09:34, Jukka MJ Manner wrote:
My WG having been a victim of a long debate on router alert, I believe there is value in documenting if or when RAO should or should not be used.
Good.
Yet, there are already several RFCs that discuss/present RAO (2113, 2711, 5350). I have thought about the RAO lately and how to go forward, and it might make sense to merge these existing specs together, add recent views on RAO, and obsolete the previous RFCs.
There has been quite a bit of discussion about obsoleting (or not) RFC 2113 & RFC 2711. Our conclusions from that discussion was that the most effective approach was to :
break down the RAO discussions into two different "tracks":* one track that assumes current RAO definition (RFC2113 & 2711) and router implementation. The aim there is to define a BCP discussing if/ where/how RAO should/should not be used in the current IP world. This can be done in a short time frame. This is the scope of draft-rahman- rtg-router-alert-considerations * one track that investigates potential changes to RAO definition. This is the scope of draft-narayanan-rtg-router-alert-extensions. This is much more exploratory and with longer term implications since it would depend on deployment of routers supporting the "new" RAO. This would be a Standards Track document.
Could we agree to:* "add recent views on RAO" (including pointers to relevant parts of RFC5350 such as discussion on Experimental RAO values, and as already done including pointers to relevant text of RFC2113/2711) into draft-rahman-rtg-router-alert-considerations, and * "merge RFC 2113/2711 and obsolete/update/work-along these previous RFCs" in draft-narayanan-rtg-router-alert-extensions if/when the work on changing RAO definition progresses
?I believe it is really important to provide a BCP asap on use of RAO in the current situation and the above proposal would help us get there in a reasonable timeframe.
Thanks Francois
I will arrive too late on Monday to take part in the int are meeting and hear the discussion, unless it would happen as the last item on the agenda.cheers, Jukka Francois Le Faucheur wrote:FYI. Francois Begin forwarded message:*From: *Internet-Drafts at ietf.org <mailto:Internet-Drafts at ietf.org> *Date: *26 October 2009 15:15:02 CET *To: *i-d-announce at ietf.org <mailto:i-d-announce at ietf.org>*Subject: **I-D Action:draft-rahman-rtg-router-alert- considerations-03.txt * *Reply-To: *internet-drafts at ietf.org <mailto:internet-drafts at ietf.org >A New Internet-Draft is available from the on-line Internet-Drafts directories.Title : IP Router Alert Considerations and Usage Author(s) : F. Le FaucheurFilename : draft-rahman-rtg-router-alert- considerations-03.txtPages : 25 Date : 2009-10-26 The IP Router Alert Option is an IP option that alerts transit routers to more closely examine the contents of an IP packet. RSVP, PGM, IGMP/MLD, MRD and GIST are some of the protocols that make use of the IP Router Alert option. This document discusses security aspects and usage guidelines around the use of the current IP RouterAlert option. Specifically, it provides recommendation against usingthe Router Alert in the end-to-end open Internet as well as identifycontrolled environments where protocols depending on Router Alert canbe used safely. It also provides recommendation about protection approaches for Service Providers. Finally it provides brief guidelines for Router Alert implementation on routers. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-rahman-rtg-router-alert-considerations-03.txt Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft.------------------------------------------------------------------------_______________________________________________ I-D-Announce mailing list I-D-Announce at ietf.org https://www.ietf.org/mailman/listinfo/i-d-announce Internet-Draft directories: http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt------------------------------------------------------------------------ _______________________________________________ Int-area mailing list Int-area at ietf.org https://www.ietf.org/mailman/listinfo/int-area-- Jukka MJ Manner, Professor, PhD. Phone: +358+(0)9+451 2481 Helsinki University of Technology Mobile: +358+(0)50+5112973 Department of Communications Fax: +358+(0)9+451 2474 and Networking (Comnet) Office: G320 (Otakaari 5A) P.O. Box 3000, FIN-02015 TKK E-mail: jukka.manner at tkk.fi Finland WWW: www.comnet.tkk.fi <jukka_manner.vcf>