IETF Logo Mail Archive

[mpls] (no subject)

"Bert Wijnen \(IETF\)" <bertietf@bwijnen.net> Mon, 18 October 2010 05:34 UTC

Return-Path: <bertietf@bwijnen.net>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1D4AB3A6ADB for <mpls@core3.amsl.com>; Sun, 17 Oct 2010 22:34:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -98.431
X-Spam-Level:
X-Spam-Status: No, score=-98.431 tagged_above=-999 required=5 tests=[AWL=-1.609, BAYES_20=-0.74, HELO_MISMATCH_NET=0.611, HOST_EQ_NL=1.545, MISSING_SUBJECT=1.762, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Myqow+xKyHxE for <mpls@core3.amsl.com>; Sun, 17 Oct 2010 22:33:58 -0700 (PDT)
Received: from relay.versatel.net (relay60.tele2.vuurwerk.nl [62.250.3.60]) by core3.amsl.com (Postfix) with ESMTP id B011A3A6A87 for <mpls@ietf.org>; Sun, 17 Oct 2010 22:33:56 -0700 (PDT)
Received: from [87.215.199.34] (helo=BertLaptop) by relay.versatel.net with smtp (Exim 4.69) (envelope-from <bertietf@bwijnen.net>) id 1P7iNW-0002wf-To for mpls@ietf.org; Mon, 18 Oct 2010 07:35:23 +0200
Message-ID: <B56AB926341D409F81D2154390D0ED26@BertLaptop>
From: "Bert Wijnen (IETF)" <bertietf@bwijnen.net>
To: mpls@ietf.org
Date: Mon, 18 Oct 2010 07:32:52 +0200
Organization: Consultant
MIME-Version: 1.0
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Windows Mail 6.0.6002.18197
X-MimeOLE: Produced By Microsoft MimeOLE V6.0.6002.18263
X-Mailman-Approved-At: Tue, 19 Oct 2010 13:55:46 -0700
Subject: [mpls] (no subject)
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 18 Oct 2010 05:34:00 -0000

As a member of the Operations Directorate I was  asked to review
the following draft which is in IETF last call for it's operational  
impact.

IETF Last Call:
The file can be obtained via
http://www.ietf.org/internet-drafts/draft-ietf-mpls-ldp-upstream-08.txt


- As far as I can tell, I see no speical operational impact.
  I think that an operator does not have to configure anything for this
  new protocol. If an operator does have to configure anything, then 
  such is not clear from the document.

- Editorial nit, Bottom of page 4:

   transmission and ignored on receipt. The Upstream Label Assignment
   Capability Parameter MUST be carried only LDP initialization messages
   and MUST be ignored if received in LDP Capability messages.

   s/only LDP/only by LPD/    or maybe   s/only LDP/only in LDP/

Bert Wijnen
p.s. I am not subscribed to the mpls mailing list

v2.39.1 | Report a Bug | By Email | System Status