Re: [mpls] AD review of draft-ietf-mpls-forwarding
Curtis Villamizar <curtis@ipv6.occnc.com> Tue, 28 January 2014 02:17 UTC
Return-Path: <curtis@ipv6.occnc.com>
X-Original-To: mpls@ietfa.amsl.com
Delivered-To: mpls@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7B1B61A0176 for <mpls@ietfa.amsl.com>; Mon, 27 Jan 2014 18:17:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.437
X-Spam-Level:
X-Spam-Status: No, score=-2.437 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.535, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mjEWPxK-Mela for <mpls@ietfa.amsl.com>; Mon, 27 Jan 2014 18:17:07 -0800 (PST)
Received: from maildrop2.v6ds.occnc.com (maildrop2.v6ds.occnc.com [IPv6:2001:470:88e6:3::232]) by ietfa.amsl.com (Postfix) with ESMTP id E58401A00A7 for <mpls@ietf.org>; Mon, 27 Jan 2014 18:17:06 -0800 (PST)
Received: from harbor3.ipv6.occnc.com (harbor3.v6ds.occnc.com [IPv6:2001:470:88e6:3::239]) (authenticated bits=128) by maildrop2.v6ds.occnc.com (8.14.7/8.14.7) with ESMTP id s0S2H151000639; Mon, 27 Jan 2014 21:17:01 -0500 (EST) (envelope-from curtis@ipv6.occnc.com)
Message-Id: <201401280217.s0S2H151000639@maildrop2.v6ds.occnc.com>
To: l.wood@surrey.ac.uk
From: Curtis Villamizar <curtis@ipv6.occnc.com>
In-reply-to: Your message of "Tue, 28 Jan 2014 01:11:27 +0000." <290E20B455C66743BE178C5C84F1240847E63346F9@EXMB01CMS.surrey.ac.uk>
Date: Mon, 27 Jan 2014 21:17:01 -0500
Cc: mpls@ietf.org, draft-ietf-mpls-forwarding.all@tools.ietf.org
Subject: Re: [mpls] AD review of draft-ietf-mpls-forwarding
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: curtis@ipv6.occnc.com
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: Tue, 28 Jan 2014 02:17:10 -0000
In message <290E20B455C66743BE178C5C84F1240847E63346F9@EXMB01CMS.surrey.ac.uk> l.wood@surrey.ac.uk writes: > Curtis, > > my mistake. I hadn't realised that RFCs and internet-drafts were > written solely for an American audience, and that the preferences of > US readers takes priority over the ease of reading of the other 6.5 > billion+ people on the planet. > > Lloyd Wood > http://about.me/lloydwood Well now you know. :-) See for example RFC-Editor's FAQ #40. 40. I used British English. Why did you change it to American English? If there is a mix of British and American English within the Internet-Draft, the document is updated to use American English for consistency. The default has always been American English. Perhaps since a DARPA funded project started the RFC series and Jon Postel was not a Brit. Even though RFC 6949 says "The official language of the RFC Series is English" and otherwise stays out of the fight. :-) Cherio old chap, Curtis > ________________________________________ > From: Curtis Villamizar [curtis@ipv6.occnc.com] > Sent: 28 January 2014 00:09 > To: Wood L Dr (Electronic Eng) > Cc: adrian@olddog.co.uk; curtis@ipv6.occnc.com; mpls@ietf.org; draft-ietf-mpls-forwarding.all@tools.ietf.org > Subject: Re: [mpls] AD review of draft-ietf-mpls-forwarding > > In message <290E20B455C66743BE178C5C84F1240847E63346F5@EXMB01CMS.surrey.ac.uk> > l.wood@surrey.ac.uk writes: > > > >> > I think Curtis may have heard this before :-) > > >> > The "preferred" (by the RFC editor) expansion of ECMP is > > >> > "Equal-Cost Multipath" > > >> > > >> The form without the hyphen is more common, even among recent > > >> documents. I prefer to keep it without the hyphen. > > > > >> A discussion for a rainy day with the RFC Editor. > > >> Leave as is. > > > > Basic English grammar. Hyphenate related adjectives. > > http://www.grammar-monster.com/lessons/hyphens_in_compound_adjectives.htm > > > > Lloyd Wood > > http://about.me/lloydwood > > > Hi Lloyd, > > Monster.com lists this as a "should". They don't seem to be using RFC > 2119 keywords since its lower case. :-) > > In the UK, your readers will expect you to use hyphens in compound > adjectives. > > Americans are more lenient. The US ruling is: Use a hyphen if it > eliminates ambiguity or helps your reader, else don't bother. If > you're unsure, use hyphens. You won't be marked down for using > hyphens. > > Good thing we use US English in IETF and don't have to stick with > those pesky British rules. They don't even know how to pronounce > router over there. :-) > > There is no ambiguity caused by leaving out the hyphen. My reasoning > is that The form without the hyphen is more common, even among recent > documents - and it looks better to a US English reader. We have given > the matter due consideration and are going against the monster.com > "should". > > Curtis
- Re: [mpls] draft-ietf-mpls-forwarding t.petch
- Re: [mpls] AD review of draft-ietf-mpls-forwarding Curtis Villamizar
- [mpls] AD review of draft-ietf-mpls-forwarding Adrian Farrel
- Re: [mpls] AD review of draft-ietf-mpls-forwarding Curtis Villamizar
- Re: [mpls] AD review of draft-ietf-mpls-forwarding Carlos Pignataro (cpignata)
- Re: [mpls] AD review of draft-ietf-mpls-forwarding Curtis Villamizar
- Re: [mpls] AD review of draft-ietf-mpls-forwarding Carlos Pignataro (cpignata)
- Re: [mpls] AD review of draft-ietf-mpls-forwarding Adrian Farrel
- Re: [mpls] AD review of draft-ietf-mpls-forwarding l.wood
- Re: [mpls] AD review of draft-ietf-mpls-forwarding Curtis Villamizar
- Re: [mpls] AD review of draft-ietf-mpls-forwarding l.wood
- Re: [mpls] AD review of draft-ietf-mpls-forwarding Curtis Villamizar
- Re: [mpls] AD review of draft-ietf-mpls-forwarding Curtis Villamizar
- Re: [mpls] AD review of draft-ietf-mpls-forwarding Curtis Villamizar
- Re: [mpls] AD review of draft-ietf-mpls-forwarding Adrian Farrel
- Re: [mpls] AD review of draft-ietf-mpls-forwarding Adrian Farrel
- Re: [mpls] AD review of draft-ietf-mpls-forwarding Curtis Villamizar
- Re: [mpls] draft-ietf-mpls-forwarding t.petch
- Re: [mpls] draft-ietf-mpls-forwarding Curtis Villamizar
- Re: [mpls] draft-ietf-mpls-forwarding Curtis Villamizar