RFC 4907 on Architectural Implications of Link Indications

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



A new Request for Comments is now available in online RFC libraries.

        
        RFC 4907

        Title:      Architectural Implications of Link Indications 
        Author:     B. Aboba, Ed.
        Status:     Informational
        Date:       June 2007
        Mailbox:    bernarda@microsoft.com
        Pages:      62
        Characters: 160604
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-iab-link-indications-10.txt

        URL:        http://www.rfc-editor.org/rfc/rfc4907.txt

A link indication represents information provided by the link layer to
higher layers regarding the state of the link.  This document
describes the role of link indications within the Internet
architecture.  While the judicious use of link indications can provide
performance benefits, inappropriate use can degrade both robustness
and performance.  This document summarizes current proposals, describes
the architectural issues, and provides examples of appropriate and
inappropriate uses of link indications.  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@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf-announce

[Index of Archives]     [IETF]     [IETF Discussion]     [Linux Kernel]

  Powered by Linux