[Hubmib] FYI: FW: Informational RFC to be: draft-foschiano-udld-03.txt
"Wijnen, Bert \(Bert\)" <bwijnen@alcatel-lucent.com> Tue, 24 July 2007 15:39 UTC
Return-path: <hubmib-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IDMUD-00029R-Qm; Tue, 24 Jul 2007 11:39:45 -0400
Received: from hubmib by megatron.ietf.org with local (Exim 4.43) id 1IDMUC-00029J-Op for hubmib-confirm+ok@megatron.ietf.org; Tue, 24 Jul 2007 11:39:44 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IDMUC-000299-CR for hubmib@ietf.org; Tue, 24 Jul 2007 11:39:44 -0400
Received: from ihemail1.lucent.com ([135.245.0.33]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IDMUB-0005g9-Fa for hubmib@ietf.org; Tue, 24 Jul 2007 11:39:43 -0400
Received: from ilexp02.ndc.lucent.com (h135-3-39-2.lucent.com [135.3.39.2]) by ihemail1.lucent.com (8.13.8/IER-o) with ESMTP id l6OFdNWh024969; Tue, 24 Jul 2007 10:39:42 -0500 (CDT)
Received: from DEEXP01.de.lucent.com ([135.248.187.65]) by ilexp02.ndc.lucent.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 24 Jul 2007 10:39:35 -0500
Received: from DEEXC1U02.de.lucent.com ([135.248.187.30]) by DEEXP01.de.lucent.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 24 Jul 2007 17:39:30 +0200
x-mimeole: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 24 Jul 2007 17:39:11 +0200
Message-ID: <D4D321F6118846429CD792F0B5AF471F7E5920@DEEXC1U02.de.lucent.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: FYI: FW: Informational RFC to be: draft-foschiano-udld-03.txt
Thread-Index: AcfNk01mqZiexPlUSWuHBuqoll9CmwAdUySA
From: "Wijnen, Bert (Bert)" <bwijnen@alcatel-lucent.com>
To: hubmib@ietf.org, STDS-802-1-L@LISTSERV.IEEE.ORG, STDS-802-3@LISTSERV.IEEE.ORG
X-OriginalArrivalTime: 24 Jul 2007 15:39:30.0821 (UTC) FILETIME=[D395AB50:01C7CE08]
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.33
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cd26b070c2577ac175cd3a6d878c6248
Cc:
Subject: [Hubmib] FYI: FW: Informational RFC to be: draft-foschiano-udld-03.txt
X-BeenThere: hubmib@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Ethernet Interfaces an Hub MIB WG <hubmib.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/hubmib>, <mailto:hubmib-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:hubmib@ietf.org>
List-Help: <mailto:hubmib-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/hubmib>, <mailto:hubmib-request@ietf.org?subject=subscribe>
Errors-To: hubmib-bounces@ietf.org
FYI Bert Wijnen -----Original Message----- From: The IESG [mailto:iesg-secretary@ietf.org] Sent: Monday, July 23, 2007 6:36 PM To: RFC Editor Cc: iana@iana.org; The IESG; ietf-announce@ietf.org Subject: Re: Informational RFC to be: draft-foschiano-udld-03.txt The IESG has no problem with the publication of 'Cisco Systems UniDirectional Link Detection (UDLD) Protocol' <draft-foschiano-udld-03.txt> as an Informational RFC. The IESG would also like the RFC-Editor to review the comments in the datatracker (https://datatracker.ietf.org/public/pidtracker.cgi?command=view_id&dTag =13566&rfc_flag=0) related to this document and determine whether or not they merit incorporation into the document. Comments may exist in both the ballot and the comment log. The IESG contact person is Russ Housley. A URL of this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-foschiano-udld-03.txt The process for such documents is described at http://www.rfc-editor.org/indsubs.html. Thank you, The IESG Secretary Technical Summary This document describes a Cisco Systems protocol that can be used to detect and disable unidirectional Ethernet fiber or copper links caused for instance by mis-wiring of fiber strands, interface malfunctions, media converters' faults, etc. It operates at Layer 2 in conjunction with IEEE 802.3's existing Layer 1 fault detection mechanisms. This document explains the protocol objectives and applications, illustrates the specific premises the protocol was based upon and describes the protocol architecture and related deployment issues, to serve as a possible base for future standardization. Working Group Summary This document is not the product of any IETF Working Group. It was submitted directly to the RFC Editor by the authors. Protocol Quality This document was reviewed by Joel Halpern and by the RFC Editor. At the request of the RFC Editor, the author changed the title and Abstract to make clear that this is a Cisco protocol, not an IETF product. IESG Note This RFC is not a candidate for any level of Internet Standard. The IETF disclaims any knowledge of the fitness of this RFC for any purpose and in particular notes that the decision to publish is not based on IETF review for such things as security, congestion control, or inappropriate interaction with deployed protocols. The RFC Editor has chosen to publish this document at its discretion. Readers of this document should exercise caution in evaluating its value for implementation and deployment. See RFC 3932 for more information. _______________________________________________ IETF-Announce mailing list IETF-Announce@ietf.org https://www1.ietf.org/mailman/listinfo/ietf-announce _______________________________________________ Hubmib mailing list Hubmib@ietf.org https://www1.ietf.org/mailman/listinfo/hubmib
- [Hubmib] FYI: FW: Informational RFC to be: draft-… Wijnen, Bert (Bert)