[FW: [DNA] Document Action: 'Link-layer Event Notifications for Detecting Network Attachments' to Informational RFC]
FYI.
----- Forwarded message from The IESG <iesg-secretary@ietf.org> -----
X-VirusChecked: Checked
X-Env-Sender: dna-owner@webcamserver.eng.monash.edu.au
X-Msg-Ref: server-3.tower-74.messagelabs.com!1176157639!63844706!1
X-StarScan-Version: 5.5.10.7.1; banners=-,-,-
X-Originating-IP: [130.194.13.164]
X-SpamReason: No, hits=0.0 required=7.0 tests=
From: The IESG <iesg-secretary@ietf.org>
Subject: [DNA] Document Action: 'Link-layer Event Notifications for
Detecting Network Attachments' to Informational RFC
To: IETF-Announce <ietf-announce@ietf.org>
Cc: Internet Architecture Board <iab@iab.org>,
RFC Editor <rfc-editor@rfc-editor.org>,
dna mailing list <dna@eng.monash.edu.au>,
dna chair <dna-chairs@tools.ietf.org>
X-Spam-Checker-Version: SpamAssassin 3.1.8 (2007-02-13)
X-test-idtracker: no
X-Spam-Level:
X-UIDL: <&^"!LQj!!l4B"!kOY"!
The IESG has approved the following document:
- 'Link-layer Event Notifications for Detecting Network Attachments '
<draft-ietf-dna-link-information-06.txt> as an Informational RFC
This document is the product of the Detecting Network Attachment Working
Group.
The IESG contact persons are Jari Arkko and Mark Townsley.
A URL of this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-dna-link-information-06.txt
Technical Summary
Certain network access technologies are capable
of providing various link-layer status information
to IP. Link-layer event notifications can help
IP expeditiously detect configuration changes. This
document provides a non-exhaustive catalogue of
information available from well-known access technologies.
Working Group Summary
The dna working group reached consensus on this document on the DNA
mailing list. There was strong support for the document from key
contributors to the WG and no opposition.
One contentious issue in this draft has been whether
it should document just Link Up or also Link Down
events. Based on reviews from the designer of DNAv4
and the AD review, it was finally decided to focus
only on the Link Up event.
Protocol Quality
This document and has been reviewed by the dna working group
and the required changes have been incorporated into the document.
The document has also been reviewed by a member of the IAB
(Bernard Aboba) and wg chairs of the bridgeand hubmib working
groups (Dan Romascanu and David Harrington). Some of the
information contained within has been derived from documents
reviewed by other standards bodies.
A significant amount of review was also received during
IETF Last Call, and the suggested changes are either in
the -06 version or in the below RFC Editor notes.
Note to RFC Editor
Please insert a new paragraph between the 2nd and 3rd paragraph of
Section 1:
OLD:
NEW:
Link-layer event notifications can help IP expeditiously detect
configuration changes. This document provides a non-exhaustive
catalog of information available from some access technologies, and
discusses the interpretation of this information at the IP layer. This
document is not intended to specify or change the behaviour of these
access technologies in any manner.
Also, please change the following. In Section 3:
OLD:
notification must be delivered
NEW:
notification is delivered
OLD:
notification must be generated and what information must be included in
it
NEW:
notification is generated and what information is included in it
Section 3.1:
OLD:
must generate a link up
NEW:
generates a link up
OLD:
notification must be the IPv4
NEW:
notification is the IPv4
Section 3.2:
OLD:
notification must be delivered
NEW:
notification is delivered
OLD:
address must be provided
NEW:
address is provided
Section 3.3:
OLD:
must be generated
NEW:
is generated
OLD:
must cause a link up
NEW:
causes a link up
OLD:
notification must be generated, if one
NEW:
notification is generated, if one
OLD:
notification must be generated.
NEW:
notification is generated.
----- End forwarded message -----