[16NG] FW: RFC 4840 on Multiple Encapsulation Methods Considered Harmful

FYI
> A new Request for Comments is now available in online RFC libraries.
>
>         
>         RFC 4840
>
>         Title:      Multiple Encapsulation Methods Considered Harmful 
>         Author:     B. Aboba, Ed.,
>                     E. Davies, D. Thaler
>         Status:     Informational
>         Date:       April 2007
>         Mailbox:    bernarda@microsoft.com, 
>                     elwynd@dial.pipex.com, 
>                     dthaler@microsoft.com
>         Pages:      27
>         Characters: 65287
>         Updates/Obsoletes/SeeAlso:   None
>
>         I-D Tag:    draft-iab-link-encaps-08.txt
>
>         URL:        http://www.rfc-editor.org/rfc/rfc4840.txt
>
> This document describes architectural and operational issues that arise 
> from link-layer protocols supporting multiple Internet Protocol 
> encapsulation methods.  This memo provides information for the Internet 
> community.
>
> This document is a product of the Internet Architecture Board.
>
>
> INFORMATIONAL: This memo provides information for the Internet community. 
> It does not specify an Internet standard of any kind. Distribution
> of this memo is unlimited.
>
> This announcement is sent to the IETF list and the RFC-DIST list.
> Requests to be added to or deleted from the IETF distribution list
> should be sent to IETF-REQUEST@IETF.ORG.  Requests to be
> added to or deleted from the RFC-DIST distribution list should
> be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.
>
> Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
> an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 
>
> help: ways_to_get_rfcs. For example:
>
>         To: rfc-info@RFC-EDITOR.ORG
>         Subject: getting rfcs
>
>         help: ways_to_get_rfcs
>
> Requests for special distribution should be addressed to either the
> author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG.  Unless
> specifically noted otherwise on the RFC itself, all RFCs are for
> unlimited distribution.
>
> Submissions for Requests for Comments should be sent to
> RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
> Authors, for further information.
>
>
> The RFC Editor Team
> USC/Information Sciences Institute
>
> ...
>
>
>
> _______________________________________________
> IETF-Announce mailing list
> IETF-Announce@ietf.org
> https://www1.ietf.org/mailman/listinfo/ietf-announce
>
>
>   


_______________________________________________
16NG mailing list
16NG@ietf.org
https://www1.ietf.org/mailman/listinfo/16ng