Re: [mpls] AD review of draft-ietf-mpls-entropy-label

John E Drake <jdrake@juniper.net> Mon, 20 August 2012 18:56 UTC

Return-Path: <jdrake@juniper.net>
X-Original-To: mpls@ietfa.amsl.com
Delivered-To: mpls@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1BF4421F84F5 for <mpls@ietfa.amsl.com>; Mon, 20 Aug 2012 11:56:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.757
X-Spam-Level:
X-Spam-Status: No, score=-5.757 tagged_above=-999 required=5 tests=[AWL=0.842, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BEoEudltCU9D for <mpls@ietfa.amsl.com>; Mon, 20 Aug 2012 11:56:43 -0700 (PDT)
Received: from exprod7og117.obsmtp.com (exprod7og117.obsmtp.com [64.18.2.6]) by ietfa.amsl.com (Postfix) with ESMTP id 85D2F21F855B for <mpls@ietf.org>; Mon, 20 Aug 2012 11:56:43 -0700 (PDT)
Received: from P-EMHUB01-HQ.jnpr.net ([66.129.224.36]) (using TLSv1) by exprod7ob117.postini.com ([64.18.6.12]) with SMTP ID DSNKUDKIZN+s4e+KD4u7Gtsq0nQnc6+T/E4Q@postini.com; Mon, 20 Aug 2012 11:56:43 PDT
Received: from EMBX01-HQ.jnpr.net ([fe80::c821:7c81:f21f:8bc7]) by P-EMHUB01-HQ.jnpr.net ([fe80::fc92:eb1:759:2c72%11]) with mapi; Mon, 20 Aug 2012 11:55:48 -0700
From: John E Drake <jdrake@juniper.net>
To: Kireeti Kompella <kireeti@juniper.net>, "adrian@olddog.co.uk" <adrian@olddog.co.uk>
Date: Mon, 20 Aug 2012 11:55:46 -0700
Thread-Topic: AD review of draft-ietf-mpls-entropy-label
Thread-Index: Ac1/AuBrt4NG4vEBTYKWZ3r4WaNOuwAAdTPA
Message-ID: <5E893DB832F57341992548CDBB333163A632037585@EMBX01-HQ.jnpr.net>
References: <0dc501cd7bb1$d318ad10$794a0730$@olddog.co.uk> <C1AFAC36-95CE-47AE-8FA3-633288144AB4@juniper.net> <0edf01cd7c43$94feec00$befcc400$@olddog.co.uk> <3E2B22DB-9FF6-41D0-92C3-85E25FF57ECF@juniper.net> <10c101cd7d65$7bd332e0$737998a0$@olddog.co.uk> <A151C7AC-E538-4800-99C0-85516FBF1E66@juniper.net>
In-Reply-To: <A151C7AC-E538-4800-99C0-85516FBF1E66@juniper.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "mpls@ietf.org" <mpls@ietf.org>, "draft-ietf-mpls-entropy-label@tools.ietf.org" <draft-ietf-mpls-entropy-label@tools.ietf.org>
Subject: Re: [mpls] AD review of draft-ietf-mpls-entropy-label
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 20 Aug 2012 18:56:44 -0000

Kireeti,

In the last sentence of your proposed text, I think it would be clearer if we changed "In any case" to "Irregardless", which, according to Webster's Third New International, is a blend of 'irrespective' and 'regardless'.

Thanks,

John

Sent from my iPhone


> -----Original Message-----
> From: Kireeti Kompella
> Sent: Monday, August 20, 2012 11:38 AM
> To: adrian@olddog.co.uk
> Cc: Kireeti Kompella; draft-ietf-mpls-entropy-label@tools.ietf.org;
> mpls@ietf.org
> Subject: Re: AD review of draft-ietf-mpls-entropy-label
> 
> While we're on the subject, I'd like to make another change -- a
> clarification.
> 
> section 4.3:
> 
> OLD:
> 
>    If a transit LSR recognizes the ELI, it MAY choose to load balance
>    solely on the following label (the EL); otherwise, it SHOULD use as
>    much of the whole label stack as feasible as keys for the load
>    balancing function, with the exception that reserved labels MUST NOT
>    be used.
> 
> NEW:
> 
>    If a transit LSR recognizes the ELI, it MAY choose to load balance
>    solely on the following label (the EL); otherwise, it SHOULD use as
>    much of the whole label stack as feasible as keys for the load
>    balancing function.  In any case, reserved labels MUST NOT be used
>    as keys for the load balancing function.
> 
> Kireeti.
> 
> PS: there, you see, I do (sometimes) use MUST/MUST NOT.