
From abdussalambaryun@gmail.com  Tue Jan  1 00:22:09 2013
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3F12521F8BA1; Tue,  1 Jan 2013 00:22:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.586
X-Spam-Level: 
X-Spam-Status: No, score=-3.586 tagged_above=-999 required=5 tests=[AWL=0.013,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 nN6MjGcFvvDA; Tue,  1 Jan 2013 00:22:08 -0800 (PST)
Received: from mail-vc0-f181.google.com (mail-vc0-f181.google.com [209.85.220.181]) by ietfa.amsl.com (Postfix) with ESMTP id 6F2C921F8B94; Tue,  1 Jan 2013 00:22:08 -0800 (PST)
Received: by mail-vc0-f181.google.com with SMTP id gb30so13142647vcb.26 for <multiple recipients>; Tue, 01 Jan 2013 00:22:07 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=C90l7fLlEl+rguX2yL7S8fj3C999ZF5MHG8XJWtrGKI=; b=TkQZahDnv6p7atbyfSVGyD02mLLGDl3kCT/Tu+wDiraiQ+83rF76qKuAMyDu70NGCu bWsXNOoJ8mQDEZ11pCKaU7r6d8jYK5+T0WEEf0WJH/UGwfIAnvuNqC9ZAJJjdZc8kZ3Q 0QRtQJarMdh5jd5sfmjbCgyg6uwt4hVNNECoT7XTj91eGSPwnaow0l/vHbBTeLJCm0s2 DEBGjgcbPciXXDhYd9a+0TH5Y2y0lrcsvoAQ4GY2ptOCmvqy+PSxHlrhOSnxfyKGWfEu cUvejyFFlWhQZ5HBeDALIAD6udoeyYttVEtQdQqsePUza9ABPTYZoUGsEK1HhFa0cJBR AbWA==
MIME-Version: 1.0
Received: by 10.220.149.69 with SMTP id s5mr67661460vcv.23.1357028527626; Tue, 01 Jan 2013 00:22:07 -0800 (PST)
Received: by 10.220.145.5 with HTTP; Tue, 1 Jan 2013 00:22:07 -0800 (PST)
In-Reply-To: <B2E21F96-6487-437C-826E-00F610729D22@ietf.org>
References: <9DA543CE-5AE0-41B9-B0B9-49C6B208CCEE@vigilsec.com> <B2E21F96-6487-437C-826E-00F610729D22@ietf.org>
Date: Tue, 1 Jan 2013 09:22:07 +0100
Message-ID: <CADnDZ89=vhhQaHfPR=0cxvBb2S7i=EdmHPF7i-94hm0tjD-mig@mail.gmail.com>
Subject: Re: 30th Anniversary of Transition to TCP/IP
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: IETF Chair <chair@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1
Cc: IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 Jan 2013 08:22:09 -0000

Happy new year to you and anniversary to IETF, thanks,
It is interesting to see the transition plan, but do we have a future
plan in an ID, not sure, I think the IETF future plans are noted the
IETF reports of meetings not in an ID discussed (which can be historic
after done).

AB

 On 12/31/12, IETF Chair <chair@ietf.org> wrote:
> Happy New Year.  It is already 2013 in some part of the world.
>
> The ARPANET transitioned to TCP/IP on 1 January 1983.  That was 30 years
> ago, and it was a huge milestone in the journey toward the Internet as we
> know it.
>
> You can see the transition plan.  Like so many other historic networking
> documents, it is an RFC.  See http://www.rfc-editor.org/rfc/rfc801.txt
>
> Happy New Year,
>   Russ
>
>

From brian.e.carpenter@gmail.com  Tue Jan  1 00:31:10 2013
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5DAD221F8548 for <ietf@ietfa.amsl.com>; Tue,  1 Jan 2013 00:31:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.586
X-Spam-Level: 
X-Spam-Status: No, score=-101.586 tagged_above=-999 required=5 tests=[AWL=0.105, BAYES_00=-2.599, RCVD_ILLEGAL_IP=1.908, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
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 UdwLWDNmllvr for <ietf@ietfa.amsl.com>; Tue,  1 Jan 2013 00:31:09 -0800 (PST)
Received: from mail-we0-f176.google.com (mail-we0-f176.google.com [74.125.82.176]) by ietfa.amsl.com (Postfix) with ESMTP id 3C5F321F8546 for <ietf@ietf.org>; Tue,  1 Jan 2013 00:31:09 -0800 (PST)
Received: by mail-we0-f176.google.com with SMTP id r5so6048366wey.7 for <ietf@ietf.org>; Tue, 01 Jan 2013 00:31:08 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:organization:user-agent :mime-version:to:cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=J8Kmn66fQc9OTJLAAhCqEVHBVKnkMT5jQPAUTRXDWo0=; b=E0yOoxT8y1BJinw7wHQ+U0Q9chLQc7FQTEE4YXpPYpEjoBz+is6bgDbSIJX8nUtinM 5KcmJo58qC7EflM1FnisTNIeFmGEQdyhidO7p2TFx4u5HsVkIoKpVXbahFQZG0erkwFF t4Ko3zBrhLeNhvwQu+C80iVe24f2PcrBxmoHvYSII3OIoUYUHOhoB3bjlpZHsEh9h5bv /B4AYnvrAqpI4E1EDYdnVxGKW2yvUuT2SFqagqTLibNMghNsTbWyj/O4DsE1q5mR07PV UuJi3LBnYsF+r1ftmdmgIqShneQj7dwIy53wRZpT1RqAuDbDTSv0Y4v3ssqQ5BBkcsRI N8Uw==
X-Received: by 10.194.58.13 with SMTP id m13mr49136853wjq.18.1357029068317; Tue, 01 Jan 2013 00:31:08 -0800 (PST)
Received: from [192.168.1.65] (host-2-102-217-142.as13285.net. [2.102.217.142]) by mx.google.com with ESMTPS id h19sm79276008wiv.7.2013.01.01.00.31.06 (version=SSLv3 cipher=OTHER); Tue, 01 Jan 2013 00:31:07 -0800 (PST)
Message-ID: <50E29EE0.1080107@gmail.com>
Date: Tue, 01 Jan 2013 08:31:28 +0000
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: John Day <jeanjour@comcast.net>
Subject: Re: WCIT outcome?
References: <CAMm+Lwh2cHRY+Dk2_SDtZZmUbPcgRpP89u3DHUcniJDrKrX_pw@mail.gmail.com>	<CAMzo+1a0-90dnjnvs48a9DcNN9DY_edF5hH0__4XRuCaLHtL6Q@mail.gmail.com>	<CAMm+LwjzjLc2-=4EdxwHOi21B3dOBUohYc5hhXZHL_Pk+iBBmQ@mail.gmail.com>	<6.2.5.6.2.20121229192941.0aae33e8@resistor.net>	<CAMm+LwiC0xtJU4vnGFPvAG4VKZdj7Tf3LfW0+pzwxKWTegRREw@mail.gmail.com>	<a06240800cd074efd45b8@10.0.1.3>	<CAMm+Lwiq+DCzXw572wKs78DG+XzYsJtwCVSPvNuVHSrT=Cr2nA@mail.gmail.com> <a06240809cd0799fee029@[10.0.1.3]>
In-Reply-To: <a06240809cd0799fee029@[10.0.1.3]>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: Phillip Hallam-Baker <hallam@gmail.com>, IETF Discussion Mailing List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 Jan 2013 08:31:10 -0000

I'v been hesitating to join in here because this seems distinctly OT
to me, but there are some basics that need to be understood:

On 31/12/2012 21:08, John Day wrote:
> At 1:05 PM -0500 12/31/12, Phillip Hallam-Baker wrote:
>> On Mon, Dec 31, 2012 at 9:51 AM, John Day
>> <<mailto:jeanjour@comcast.net>jeanjour@comcast.net> wrote:

...
>> MPs and Congressmen are elected decision makers. ITU participants can
>> make decisions but they are not binding on anyone and only have effect
>> if people like me choose to implement them.
> 
> This was my point. The standards part of ITU is just like any other
> standards organization. But there are other things it does which are not
> like this, e.g. spectrum allocation.  There are other aspects with
> respect to tariffs that are binding on signatories.

Not only tariffs. Historically, it was national enforcement of international
regulations set by CCITT (now known as ITU-T) that prevented interconnection
of leased lines**. This is an arcane point today, but if CERN hadn't been
able to use its status as an international organization to bypass that
restriction in the 1980s, it's unlikely that TBL and Robert Cailliau would
ever have been able to propagate the web. It's even unlikely that Phill
would have been able to access Usenet newsgroups while on shift as a grad
student on a CERN experiment.

Also, it is exactly because ITU was in charge of resource allocations
such as radio spectrum and top-level POTS dialling codes that it was
a very plausible potential home for IANA in 1997-8, before ICANN was
created. Some of the ITU people who were active in that debate were just
as active in the preparation for WCIT in 2012.

** CCITT document D.1. The 1988 version includes the restrictions on
use of leased lines:
http://www.itu.int/rec/dologin_pub.asp?lang=e&id=T-REC-D.1-198811-S!!PDF-E&type=items

The 1991 version is much less restrictive, but it remains the case that
interconnections are all "subject to national laws" and that is the basis
for all national limitations on the Internet today. Nevertheless, the 1991
revision of D.1 was absolutely essential for the Internet to grow
internationally.

It would be foolish to imagine that the Internet is in some way immune
to ITU-T regulations, which is why the effort to defeat the more radical
WCIT proposals was so important.

   Brian

From jeanjour@comcast.net  Tue Jan  1 10:34:08 2013
Return-Path: <jeanjour@comcast.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EF7D01F0CE7 for <ietf@ietfa.amsl.com>; Tue,  1 Jan 2013 10:34:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.404
X-Spam-Level: 
X-Spam-Status: No, score=-100.404 tagged_above=-999 required=5 tests=[AWL=0.033, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_NET=0.611, RDNS_NONE=0.1, USER_IN_WHITELIST=-100]
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 dvkgOMLwD8zn for <ietf@ietfa.amsl.com>; Tue,  1 Jan 2013 10:34:08 -0800 (PST)
Received: from qmta15.westchester.pa.mail.comcast.net (qmta15.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:44:76:96:59:228]) by ietfa.amsl.com (Postfix) with ESMTP id DAA811F0C3E for <ietf@ietf.org>; Tue,  1 Jan 2013 10:34:07 -0800 (PST)
Received: from omta15.westchester.pa.mail.comcast.net ([76.96.62.87]) by qmta15.westchester.pa.mail.comcast.net with comcast id ihP21k0011swQuc5Fia7ie; Tue, 01 Jan 2013 18:34:07 +0000
Received: from [10.0.1.3] ([98.229.211.49]) by omta15.westchester.pa.mail.comcast.net with comcast id iia61k00814WE023bia6bC; Tue, 01 Jan 2013 18:34:07 +0000
Mime-Version: 1.0
Message-Id: <a06240815cd08da399dc6@[10.0.1.3]>
In-Reply-To: <50E29EE0.1080107@gmail.com>
References: <CAMm+Lwh2cHRY+Dk2_SDtZZmUbPcgRpP89u3DHUcniJDrKrX_pw@mail.gmail.com> <CAMzo+1a0-90dnjnvs48a9DcNN9DY_edF5hH0__4XRuCaLHtL6Q@mail.gmail.com> <CAMm+LwjzjLc2-=4EdxwHOi21B3dOBUohYc5hhXZHL_Pk+iBBmQ@mail.gmail.com> <6.2.5.6.2.20121229192941.0aae33e8@resistor.net> <CAMm+LwiC0xtJU4vnGFPvAG4VKZdj7Tf3LfW0+pzwxKWTegRREw@mail.gmail.com> <a06240800cd074efd45b8@10.0.1.3> <CAMm+Lwiq+DCzXw572wKs78DG+XzYsJtwCVSPvNuVHSrT=Cr2nA@mail.gmail.com> <a06240809cd0799fee029@[10.0.1.3]> <50E29EE0.1080107@gmail.com>
Date: Tue, 1 Jan 2013 13:32:50 -0500
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, John Day <jeanjour@comcast.net>
From: John Day <jeanjour@comcast.net>
Subject: Re: WCIT outcome?
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20121106; t=1357065247; bh=fpy5G9kI7WMhoI5gaKp5cU4U1B+vpFnnwLOsH2wkLO4=; h=Received:Received:Mime-Version:Message-Id:Date:To:From:Subject: Content-Type; b=AdDpbW6B7n7L1zj6nrFZJ3FiCI2RvszX6NOovdXi2ro/gn1fKSYQJfRe23PGifxYb B9p2NhmvnmWgAUMkNLyfJIn7EpQrCr40187ia2um4t3bOoUNxCYNVZmVqGFhh5nvyK CfxWzhIBbDgmfReiAcsM+mpRYczhqEhMh3wFzXKIjPnmlXk+V+KXHuo6wVZ5cwcgif LoFQKo60rDhWQtD2crIdG1YNhlVKGAasSAhvC9uM156AJgeUtqx43/ETx7kRjodt7W s6uWZtt17wfHOI2gsThYfbbNr+xEeO2jEK/DnSvuxTEx+dqzjnwXVBEARUjJV143/N UGY8pcH29KA/g==
Cc: Phillip Hallam-Baker <hallam@gmail.com>, IETF Discussion Mailing List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 Jan 2013 18:34:09 -0000

Thanks Brian, That helps clear up a few things.  See below for a 
couple of questions:

At 8:31 AM +0000 1/1/13, Brian E Carpenter wrote:
>I'v been hesitating to join in here because this seems distinctly OT
>to me, but there are some basics that need to be understood:
>
>On 31/12/2012 21:08, John Day wrote:
>>  At 1:05 PM -0500 12/31/12, Phillip Hallam-Baker wrote:
>>>  On Mon, Dec 31, 2012 at 9:51 AM, John Day
>>>  <<mailto:jeanjour@comcast.net>jeanjour@comcast.net> wrote:
>
>...
>>>  MPs and Congressmen are elected decision makers. ITU participants can
>>>  make decisions but they are not binding on anyone and only have effect
>>>  if people like me choose to implement them.
>>
>>  This was my point. The standards part of ITU is just like any other
>>  standards organization. But there are other things it does which are not
>>  like this, e.g. spectrum allocation.  There are other aspects with
>>  respect to tariffs that are binding on signatories.
>
>Not only tariffs. Historically, it was national enforcement of international
>regulations set by CCITT (now known as ITU-T) that prevented interconnection
>of leased lines**.

But creating a VPN with in an international carrier that crossed 
national boundaries would not fall under that rule?  Actually neither 
would a VPN operating over a couple of carriers that crossed national 
boundaries, would it?

>This is an arcane point today, but if CERN hadn't been
>able to use its status as an international organization to bypass that
>restriction in the 1980s, it's unlikely that TBL and Robert Cailliau would
>ever have been able to propagate the web. It's even unlikely that Phill
>would have been able to access Usenet newsgroups while on shift as a grad
>student on a CERN experiment.

;-) Actually what they don't know won't hurt them.  ;-) We were 
moving files from CERN to Argonne in the 70s through the 360/95 at 
Rutherford over the ARPANET.   Not exactly the way you want to do it 
but 15 years later I am sure it was upgraded a bit.

>
>Also, it is exactly because ITU was in charge of resource allocations
>such as radio spectrum and top-level POTS dialling codes that it was
>a very plausible potential home for IANA in 1997-8, before ICANN was
>created. Some of the ITU people who were active in that debate were just
>as active in the preparation for WCIT in 2012.

Yea, this one is more dicey.  Although I think there is an argument 
that says that you need ccoperation among providers about assignment, 
but I don't see why governments need to be involved.  When phone 
companies were owned by governments, then it made sense.  But phone 
companies are owned by governments any more.

That doesn't leave much does it?  (Not a facetious question, I am asking!)

Take care,
John

>
>** CCITT document D.1. The 1988 version includes the restrictions on
>use of leased lines:
>http://www.itu.int/rec/dologin_pub.asp?lang=e&id=T-REC-D.1-198811-S!!PDF-E&type=items
>
>The 1991 version is much less restrictive, but it remains the case that
>interconnections are all "subject to national laws" and that is the basis
>for all national limitations on the Internet today. Nevertheless, the 1991
>revision of D.1 was absolutely essential for the Internet to grow
>internationally.
>
>It would be foolish to imagine that the Internet is in some way immune
>to ITU-T regulations, which is why the effort to defeat the more radical
>WCIT proposals was so important.
>
>    Brian


From vesely@tana.it  Tue Jan  1 10:36:30 2013
Return-Path: <vesely@tana.it>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D34D11F0CF7 for <ietf@ietfa.amsl.com>; Tue,  1 Jan 2013 10:36:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.719
X-Spam-Level: 
X-Spam-Status: No, score=-4.719 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245, 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 vDkayBHmVI7I for <ietf@ietfa.amsl.com>; Tue,  1 Jan 2013 10:36:30 -0800 (PST)
Received: from wmail.tana.it (wmail.tana.it [62.94.243.226]) by ietfa.amsl.com (Postfix) with ESMTP id DB2451F0C3E for <ietf@ietf.org>; Tue,  1 Jan 2013 10:36:29 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=beta; t=1357065387; bh=MgnBAQ56cK4guvpvid++6zoM5jwx7FXVtueIoraiYYM=; l=1605; h=Date:From:To:References:In-Reply-To; b=Z/nj3RjDbzq03I5LHR7sugnLT5xIYd3PolFyyV7lbr8QFcQetlFlG03amXRu+FWDF MERCvd258JWrx9Dh6zzsWb8FjZZdyJJJhFM5LiZjHw3IQrO8zvyKLazKSS6Gxblwx0 g84v/YMeHtzsse34PiSDissGESmWMBm44jG0QlVw=
Received: from [37.183.113.166] ([37.183.113.166]) (AUTH: CRAM-MD5 uXDGrn@SYT0/k, TLS: TLSv1/SSLv3,256bits,AES256-SHA) by wmail.tana.it with ESMTPSA; Tue, 01 Jan 2013 19:36:27 +0100 id 00000000005DC039.0000000050E32CAB.000011BF
Message-ID: <50E32CAA.4040507@tana.it>
Date: Tue, 01 Jan 2013 19:36:26 +0100
From: Alessandro Vesely <vesely@tana.it>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: WCIT outcome?
References: <CAMm+Lwh2cHRY+Dk2_SDtZZmUbPcgRpP89u3DHUcniJDrKrX_pw@mail.gmail.com>	<CAMzo+1a0-90dnjnvs48a9DcNN9DY_edF5hH0__4XRuCaLHtL6Q@mail.gmail.com>	<CAMm+LwjzjLc2-=4EdxwHOi21B3dOBUohYc5hhXZHL_Pk+iBBmQ@mail.gmail.com>	<6.2.5.6.2.20121229192941.0aae33e8@resistor.net>	<CAMm+LwiC0xtJU4vnGFPvAG4VKZdj7Tf3LfW0+pzwxKWTegRREw@mail.gmail.com>	<a06240800cd074efd45b8@10.0.1.3>	<CAMm+Lwiq+DCzXw572wKs78DG+XzYsJtwCVSPvNuVHSrT=Cr2nA@mail.gmail.com> <a06240809cd0799fee029@[10.0.1.3]> <50E29EE0.1080107@gmail.com>
In-Reply-To: <50E29EE0.1080107@gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 Jan 2013 18:36:30 -0000

On Tue 01/Jan/2013 09:31:28 +0100 Brian E Carpenter wrote:
> 
> ** CCITT document D.1. The 1988 version includes the restrictions on
> use of leased lines:
> http://www.itu.int/rec/dologin_pub.asp?lang=e&id=T-REC-D.1-198811-S!!PDF-E&type=items
> 
> The 1991 version is much less restrictive, but it remains the case that
> interconnections are all "subject to national laws" and that is the basis
> for all national limitations on the Internet today. Nevertheless, the 1991
> revision of D.1 was absolutely essential for the Internet to grow
> internationally.

Was D.1 to ease wire tapping?  By example, I, as a mail server operator
who is not a telecom, am not required by my country's laws to provide an
instrumentation whereby authorized investigators can obtain a list of a
user's correspondents on the fly.  Yet that kind of data is said to be
essential for police operations.  OTOH, SMTP doesn't consider that kind
of facilities, and fashionable implementations don't provide them.  What
am I missing?

Perhaps, as the old telephone system is fading away, the institutions
that founded it --local governments' branches-- should change their
mindset or just fade away as well...  Should the IETF or other SDOs help
such transition?

On Sat 29/Dec/2012 07:26:56 +0100 Phillip Hallam-Baker wrote:
> The old telephone system is fading away. It is becoming an Internet
> application just as the pocket calculator has become a desktop
> application. And as it passes, the institutions it founded are
> looking for new roles. There is no particular reason that this must
> happen.

From dhc@dcrocker.net  Tue Jan  1 10:46:50 2013
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7864621F86CC for <ietf@ietfa.amsl.com>; Tue,  1 Jan 2013 10:46:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.995
X-Spam-Level: 
X-Spam-Status: No, score=-5.995 tagged_above=-999 required=5 tests=[AWL=0.603,  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 rfNr7ZLucB74 for <ietf@ietfa.amsl.com>; Tue,  1 Jan 2013 10:46:49 -0800 (PST)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id DADDE21F86CB for <ietf@ietf.org>; Tue,  1 Jan 2013 10:46:49 -0800 (PST)
Received: from [192.168.1.66] (76-218-9-215.lightspeed.sntcca.sbcglobal.net [76.218.9.215]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id r01Ikk8E002406 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 1 Jan 2013 10:46:47 -0800
Message-ID: <50E32F14.3090409@dcrocker.net>
Date: Tue, 01 Jan 2013 10:46:44 -0800
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: WCIT outcome?
References: <CAMm+Lwh2cHRY+Dk2_SDtZZmUbPcgRpP89u3DHUcniJDrKrX_pw@mail.gmail.com>	<CAMzo+1a0-90dnjnvs48a9DcNN9DY_edF5hH0__4XRuCaLHtL6Q@mail.gmail.com>	<CAMm+LwjzjLc2-=4EdxwHOi21B3dOBUohYc5hhXZHL_Pk+iBBmQ@mail.gmail.com>	<6.2.5.6.2.20121229192941.0aae33e8@resistor.net>	<CAMm+LwiC0xtJU4vnGFPvAG4VKZdj7Tf3LfW0+pzwxKWTegRREw@mail.gmail.com>	<a06240800cd074efd45b8@10.0.1.3>	<CAMm+Lwiq+DCzXw572wKs78DG+XzYsJtwCVSPvNuVHSrT=Cr2nA@mail.gmail.com> <a06240809cd0799fee029@[10.0.1.3]> <50E29EE0.1080107@gmail.com>
In-Reply-To: <50E29EE0.1080107@gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Tue, 01 Jan 2013 10:46:47 -0800 (PST)
Cc: IETF Discussion Mailing List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 Jan 2013 18:46:50 -0000

On 1/1/2013 12:31 AM, Brian E Carpenter wrote:
> Also, it is exactly because ITU was in charge of resource allocations
> such as radio spectrum and top-level POTS dialling codes that it was
> a very plausible potential home for IANA in 1997-8, before ICANN was
> created. Some of the ITU people who were active in that debate were just
> as active in the preparation for WCIT in 2012.


Just to avoid any misconstruction here:

      While there might have been a plausible case to be made, for 
having the ITU house the IANA functions, I believe there was no 
(serious) pursuit of that alternative at the time.

Around that time, the ITU did have a representative who participated in 
the ill-fated pre-ICANN IAHC effort (of which I was a part, including 
editor of its proposal).

But the IAHC only had the very narrow scope of suggesting a few gTLDs to 
add.  It had no formal part in the much larger question of finding a 
home for IANA.

d/
-- 
  Dave Crocker
  Brandenburg InternetWorking
  bbiw.net

From jeanjour@comcast.net  Tue Jan  1 10:52:33 2013
Return-Path: <jeanjour@comcast.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 917E721F885E for <ietf@ietfa.amsl.com>; Tue,  1 Jan 2013 10:52:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.415
X-Spam-Level: 
X-Spam-Status: No, score=-100.415 tagged_above=-999 required=5 tests=[AWL=0.022, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_NET=0.611, RDNS_NONE=0.1, USER_IN_WHITELIST=-100]
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 kVjaDPMWMbek for <ietf@ietfa.amsl.com>; Tue,  1 Jan 2013 10:52:32 -0800 (PST)
Received: from qmta05.westchester.pa.mail.comcast.net (qmta05.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:43:76:96:62:48]) by ietfa.amsl.com (Postfix) with ESMTP id 7D69921F8858 for <ietf@ietf.org>; Tue,  1 Jan 2013 10:52:26 -0800 (PST)
Received: from omta14.westchester.pa.mail.comcast.net ([76.96.62.60]) by qmta05.westchester.pa.mail.comcast.net with comcast id ifWD1k0031HzFnQ55isRly; Tue, 01 Jan 2013 18:52:25 +0000
Received: from [10.0.1.3] ([98.229.211.49]) by omta14.westchester.pa.mail.comcast.net with comcast id iisQ1k00Y14WE023aisRsB; Tue, 01 Jan 2013 18:52:25 +0000
Mime-Version: 1.0
Message-Id: <a06240818cd08dffff813@[10.0.1.3]>
In-Reply-To: <50E32F14.3090409@dcrocker.net>
References: <CAMm+Lwh2cHRY+Dk2_SDtZZmUbPcgRpP89u3DHUcniJDrKrX_pw@mail.gmail.com> <CAMzo+1a0-90dnjnvs48a9DcNN9DY_edF5hH0__4XRuCaLHtL6Q@mail.gmail.com> <CAMm+LwjzjLc2-=4EdxwHOi21B3dOBUohYc5hhXZHL_Pk+iBBmQ@mail.gmail.com> <6.2.5.6.2.20121229192941.0aae33e8@resistor.net> <CAMm+LwiC0xtJU4vnGFPvAG4VKZdj7Tf3LfW0+pzwxKWTegRREw@mail.gmail.com> <a06240800cd074efd45b8@10.0.1.3> <CAMm+Lwiq+DCzXw572wKs78DG+XzYsJtwCVSPvNuVHSrT=Cr2nA@mail.gmail.com> <a06240809cd0799fee029@[10.0.1.3]> <50E29EE0.1080107@gmail.com> <50E32F14.3090409@dcrocker.net>
Date: Tue, 1 Jan 2013 13:52:20 -0500
To: dcrocker@bbiw.net, Brian E Carpenter <brian.e.carpenter@gmail.com>
From: John Day <jeanjour@comcast.net>
Subject: Re: WCIT outcome?
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20121106; t=1357066345; bh=kqJEZDUVN6BJpUMYyXdS3d7f0y4qcNbisGwTjuHgtPI=; h=Received:Received:Mime-Version:Message-Id:Date:To:From:Subject: Content-Type; b=IaTB6rnMEIEKIQZ4ju0/QL5ScPN7OHhejaRQuHL8KWpowX9XiSuVg3t+xkomTLNJT uCym1xhONrqB1fSTNc14MICCHKMy9kjgOfWIDoXKeMEy7rNrhMdcRhO/l1zSgS7Let KkRnCWq+wO8i022+QnPBQgp9ZofzH8ZuRPGsCg7fFOtxoH/nn9v5wh7xhHdpsq0INH j9O/TpIVEkIFSR1Qcas/fymBl58EH/w8CuZ3M3+zPb8QkYiOGFerSbehOFtvKjmjEM WraaHJcIzDr2DEedFaRmx57SKS0jrdDa6c6ORYvdf5NNI1WTh4yV8TLtCWcxXeFdDm 9cyIh11wvaeEg==
Cc: IETF Discussion Mailing List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 Jan 2013 18:52:33 -0000

Dave,

I was thinking about that after I sent my email.  I actually don't 
think there is an argument for ITU holding the IANA function.  The 
assignment of addresses should be done in such a way as to facilitate 
routing.  This requires agreements among providers, but not 
governments.  Going back to governments no longer own the networks, 
then there is no reason for it be in the purview.

Domain names I guess would follow since there are merely macro 
strings for network addresses.

So I see no argument for ITU to be involved.

Take care,
John

At 10:46 AM -0800 1/1/13, Dave Crocker wrote:
>On 1/1/2013 12:31 AM, Brian E Carpenter wrote:
>>Also, it is exactly because ITU was in charge of resource allocations
>>such as radio spectrum and top-level POTS dialling codes that it was
>>a very plausible potential home for IANA in 1997-8, before ICANN was
>>created. Some of the ITU people who were active in that debate were just
>>as active in the preparation for WCIT in 2012.
>
>
>Just to avoid any misconstruction here:
>
>      While there might have been a plausible case to be made, for 
>having the ITU house the IANA functions, I believe there was no 
>(serious) pursuit of that alternative at the time.
>
>Around that time, the ITU did have a representative who participated 
>in the ill-fated pre-ICANN IAHC effort (of which I was a part, 
>including editor of its proposal).
>
>But the IAHC only had the very narrow scope of suggesting a few 
>gTLDs to add.  It had no formal part in the much larger question of 
>finding a home for IANA.
>
>d/
>--
>  Dave Crocker
>  Brandenburg InternetWorking
>  bbiw.net


From dhc@dcrocker.net  Tue Jan  1 11:08:28 2013
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8068221E803F for <ietf@ietfa.amsl.com>; Tue,  1 Jan 2013 11:08:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.197
X-Spam-Level: 
X-Spam-Status: No, score=-6.197 tagged_above=-999 required=5 tests=[AWL=0.402,  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 IjXCKpnCoPTz for <ietf@ietfa.amsl.com>; Tue,  1 Jan 2013 11:08:22 -0800 (PST)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 971E421E8044 for <ietf@ietf.org>; Tue,  1 Jan 2013 11:08:22 -0800 (PST)
Received: from [192.168.1.66] (76-218-9-215.lightspeed.sntcca.sbcglobal.net [76.218.9.215]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id r01J8Kkt002618 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 1 Jan 2013 11:08:21 -0800
Message-ID: <50E33423.6050800@dcrocker.net>
Date: Tue, 01 Jan 2013 11:08:19 -0800
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: John Day <jeanjour@comcast.net>
Subject: Re: WCIT outcome?
References: <CAMm+Lwh2cHRY+Dk2_SDtZZmUbPcgRpP89u3DHUcniJDrKrX_pw@mail.gmail.com> <CAMzo+1a0-90dnjnvs48a9DcNN9DY_edF5hH0__4XRuCaLHtL6Q@mail.gmail.com> <CAMm+LwjzjLc2-=4EdxwHOi21B3dOBUohYc5hhXZHL_Pk+iBBmQ@mail.gmail.com> <6.2.5.6.2.20121229192941.0aae33e8@resistor.net> <CAMm+LwiC0xtJU4vnGFPvAG4VKZdj7Tf3LfW0+pzwxKWTegRREw@mail.gmail.com> <a06240800cd074efd45b8@10.0.1.3> <CAMm+Lwiq+DCzXw572wKs78DG+XzYsJtwCVSPvNuVHSrT=Cr2nA@mail.gmail.com> <a06240809cd0799fee029@[10.0.1.3]> <50E29EE0.1080107@gmail.com> <50E32F14.3090409@dcrocker.net> <a06240818cd08dffff813@[10.0.1.3]>
In-Reply-To: <a06240818cd08dffff813@[10.0.1.3]>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Tue, 01 Jan 2013 11:08:21 -0800 (PST)
Cc: IETF Discussion Mailing List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 Jan 2013 19:08:28 -0000

On 1/1/2013 10:52 AM, John Day wrote:
> I was thinking about that after I sent my email.  I actually don't think
> there is an argument for ITU holding the IANA function.

And just to make sure my own message was clear:  I wasn't commenting on 
the merits of the view, but merely trying to report the facts of what I 
recall taking place at the time.


> Domain names I guess would follow since there are merely macro strings
> for network addresses.

While this is a topic serving more as a discussion black hole than 
likely to engender intellectual opportunity, I'll point out that domain 
names are -- and I think always have been -- quite a bit more than 
merely being macros for network addresses.

The mapping to network addresses has (always?) been the primary use, but 
they are a discrete name space with social as well as operational uses. 
  That is, the social aspects serve as distinct from the mapping aspects.

For that matter, the operational uses have extended considerably beyond 
mapping to addresses.  Given my own activities with DKIM, the obvious 
exemplar is mapping to security parameters.

d/
-- 
  Dave Crocker
  Brandenburg InternetWorking
  bbiw.net

From Jeff.Hodges@KingsMountain.com  Tue Jan  1 13:50:57 2013
Return-Path: <Jeff.Hodges@KingsMountain.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0A49D1F0C3E for <ietf@ietfa.amsl.com>; Tue,  1 Jan 2013 13:50:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.774
X-Spam-Level: 
X-Spam-Status: No, score=-100.774 tagged_above=-999 required=5 tests=[AWL=-1.109, BAYES_50=0.001, IP_NOT_FRIENDLY=0.334, USER_IN_WHITELIST=-100]
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 1drOoEiwFxkO for <ietf@ietfa.amsl.com>; Tue,  1 Jan 2013 13:50:55 -0800 (PST)
Received: from oproxy6-pub.bluehost.com (oproxy6-pub.bluehost.com [67.222.54.6]) by ietfa.amsl.com (Postfix) with SMTP id 0FC4A1F0CE4 for <ietf@ietf.org>; Tue,  1 Jan 2013 13:50:54 -0800 (PST)
Received: (qmail 7143 invoked by uid 0); 1 Jan 2013 21:50:31 -0000
Received: from unknown (HELO box514.bluehost.com) (74.220.219.114) by cpoproxy3.bluehost.com with SMTP; 1 Jan 2013 21:50:31 -0000
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=kingsmountain.com; s=default;  h=Content-Transfer-Encoding:Content-Type:Subject:CC:To:MIME-Version:From:Date:Message-ID; bh=k28ZxOMVbmKh9wzSH4GhvwSw/wJDPo9m8OU1IT4Y9tc=;  b=3BwsQhUR1KAd7OWpVdeBgYHSckcRxbzusGEQf1J57BGoKxpOg7bdUffVpGjmQXmQDqFWXDFeCa6uGj9Xmpg3IRQ9L92RzQBA9Air1UDB0NuS4z6NLkTX6VOipJMM9x4C;
Received: from [24.4.122.173] (port=60450 helo=[192.168.11.12]) by box514.bluehost.com with esmtpsa (TLSv1:CAMELLIA256-SHA:256) (Exim 4.76) (envelope-from <Jeff.Hodges@KingsMountain.com>) id 1Tq9jB-0003uF-QU; Tue, 01 Jan 2013 14:50:30 -0700
Message-ID: <50E35A23.9060003@KingsMountain.com>
Date: Tue, 01 Jan 2013 13:50:27 -0800
From: =JeffH <Jeff.Hodges@KingsMountain.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: therightkey@ietf.org, IETF Discussion List <ietf@ietf.org>
Subject: LC comments on draft-laurie-pki-sunlight-05
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Identified-User: {11025:box514.bluehost.com:kingsmou:kingsmountain.com} {sentby:smtp auth 24.4.122.173 authed with jeff.hodges+kingsmountain.com}
Cc: Emilia Kasper <ekasper@google.com>, Ben Laurie <benl@google.com>, Adam Langley <agl@google.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 Jan 2013 21:50:57 -0000

Hi,

Here are some last call comments on draft-laurie-pki-sunlight-05.

Overall the spec is in basically overall reasonable shape but I do have some 
substantive comments that if I'm not totally misunderstanding things (which 
could be the case) ought to be discussed and addressed in some fashion.

The plain overall comments are to some degree "take 'em or leave 'em" depending 
upon folks' sense of urgency to get the spec through the IETF pipeline, but the 
degree likely depends upon the observer.

I hope this is helpful,

=JeffH
------

comments on draft-laurie-pki-sunlight-05

substantive comments (in somewhat arbitrary order)
--------------------------------------------------

1. The client messages S4 don't explicitly lay out the syntax for request 
messages or responses. E.g., for S4.1 "Add Chain to Log", is the input a 
stand-alone JSON text array, or a JSON text object containing a JSON text array?

The term "JSON object" as used in the first paragraph is ambiguous and perhaps 
what is mean is simply "JSON texts" or "JSON text objects or JSON text arrays". 
RFC4627 clearly defines "JSON text", and should be cited. But RFC4627 is a 
little ambiguous itself regarding "JSON object" and so I suggest these definitions:

     JSON text object:   A JSON text matching the "object" ABNF production
        in Section 2.2 of [RFC4627].

     JSON text array:   A JSON text matching the "array" ABNF production
        in Section 2.3 of [RFC4627].

Also, the syntax for GETS isn't fully specified. Are the URL parameters to be 
encoded as (order independent) key-value pairs, or just as order-dependent 
values?  Which separator character is to be used between parameters? RFC3986 
should be cited.

Examples for both JSON text inputs and outputs, as well as URL parameters would 
be helpful.


2. "4. Client Messages" doesn't define error handling, i.e., responses to inputs 
the log service doesn't understand and/or is unable to parse, and/or have other 
errors. If the log service is to simply return a 4xx or 5xx error code, this 
should at least be mentioned.


3. There appear to be three defined methods for TLS servers to provide TLS 
clients with CT data, in S3.2.  For this experiment, which approach is mandatory 
to implement for servers and clients?  Or, is it the case that participating TLS 
clients (ie web browsers etc) implement all three methods, and TLS servers can 
choose any of them?

Also, S3.2 probably doesn't belong in S3 and perhaps should be a separate 
top-level section on its own, and have three subsections, one for each method.


4. "Leaf Hash" as used in S4.5 appears to be formally undefined. It apparently 
would be:

       SHA-256(0x00 || MerkleTreeLeaf)

..it should also be noted in S3.3.


5. The recursive equations in S2.1 describe how to calculate a Merkle Tree Hash 
(MTH) (aka "root hash"), and thus as a side effect generate a Merkle Tree, for a 
given set of input data. However, there doesn't seem to be a defined algorithm 
(or even hints, really) for adding further inputs to an existing tree. Even 
though this may be reasonably left as an exercise for implementers, it should 
probably be discussed to some degree in the spec. E.g., note that leaf hashes 
are "frozen" and various interior tree node hashes become "frozen" as the tree 
grows. Is it not sub-optimal to employ the obvious default brute-force mechanism 
of rebuilding a tree entirely from scratch when new inputs are available?  Would 
not a recursive algorithm for adding new inputs to an existing tree be 
straightforward to provide?


6. Signed tree heads (STHs) are denoted in terms of "tree size" (number of 
entries), but SCTs are denoted in terms of a timestamp.  Should there be a log 
client message supporting the return of the nearest STH (and thus tree size) to 
a given timestamp?


7. S3 paragraph 2 states that "TLS clients MUST reject certificates that do not 
have a valid SCT for the end-entity certificate" (i.e., hard-fail).  Presummably 
this requirement is only for TLS clients participating in the CT experiment and 
that understand this protocol. This, or whatever the requirement actually is, 
should be further explained.

For example, does the simple presence of SCT(s) in the TLS handshake serve to 
signal to participating TLS clients that hard-fail is expected if there are any 
issues with CT validation?


8. The spec implies, but doesn't clearly describe, especially in S3.1, that the 
hashes are "labels" for tree entries, and that given a leaf hash, the log 
implementation should be able to look up and present the LogEntry data defined 
in that section.


9. Validating an SCT presummably requires having the Log Service's public key, 
yes?  This isn't clearly discussed, and also the mention of how one obtains a 
log service's public key is out of scope is buried in 2nd para of S4 -- it 
should be discussed in a separate clearly entitled subsection.


10. Unless I'm totally missing it, there isn't an explicit description of how 
one (eg a TLS client) goes about validating/verifying an SCT.




Various overall comments:
--------------------------

O-1. The phrase "this experiment" is used in S2.1 -- should describing this as 
an experiment be more explicitly done in the abstract and introduction sections? 
  What about the document title?


O-2. Should explicitly say in abstract and introduction that operationally, the 
logs are to be materialized as (experimental?) network services having the 
protocol operations for submissions and queries that are defined in this spec.


O-3. The bare term "client" is used in various places where either the term "log 
client" or "TLS client" is being implied -- these should be made explicit. Also 
the roles of log clients and TLS clients should be more thoroughly 
presented/explored, in part because they can intersect.


O-4. These things seem to be duplicate names:

      "root hash" and "Merkle Tree Hash (MTH)"

      "Tree Head Signature" and "Signed Tree Head (STH)"

..which makes parsing the spec more difficult than if one name is used 
consistently for each.


O-5. The terms "leaf certificate" and "final certificate" appear to be used where..

   End Entity certificate

   final End Entity certificate

..would be clearer and more consistent with TLS and PKIX terminology, and 
perhaps less confusing with the terms "leaf" and "leaf node" which are used when 
discussing the Merkle trees and their components.


O-6. I found the "history tree" paper (aka "[1]", cited here as [CrosbyWallach]) 
helpful in understanding how such trees are constructed, perhaps it should be 
more prominently mentioned. Plus the differences between the two algorithms 
should perhaps be more explicitly mentioned. E.g. in [CrosbyWallach] version-n 
tree stores n+1 inputs, while in CT a version-n tree (D[n]) stores n inputs.

[CrosbyWallach]  <http://tamperevident.cs.rice.edu/Logging.html>


O-7. The note mentioning "dummy leaves" in [CrosbyWallach] seems misleading. The 
difference is AFAICT that in [CrosbyWallach] all nodes at layer 1 and above 
(leaf entries are at layer 0), are "interior nodes", and have hashes created 
using 0x01. Thus in a tree with an odd number of entries (ie leaf nodes at layer 
0), there will be one leaf node under an interior node having only that one 
child. It's not that there is a "dummy leaf", it's that such an interior node's 
hash is constructed from just one child rather than two.

While in CT, if the input set is an odd number of entries, then the hash of the 
final single leaf is at layer 1, and is calculated as a leaf hash using 0x00. 
Thus CT "interior nodes" always have two children, but if the tree has an odd 
number of entries, the rightmost hash at layer 1 ("j" in the "binary Merkle tree 
with 7 leaves" figure) is a leaf node hash rather than an interior node hash.


O-8. [CrosbyWallach] discusses auditing and gossiping and could be cited as a 
source for further discussion on those topics.


O-9. The notion of "commitments" isn't well defined, and where "add a commitment 
to D[k:n]"  couldn't  "add an interior/intermediate node to D[k:n}"  be used?

Is not the term "commitment" used in [CrosbyWallach] equivalent to the 
sha256_root_hash (an STH component) in the spec?

[CrosbyWallach] uses the term "interior node(s)" while the spec uses 
"intermediate nodes" (in one place).


O-10. The recursive algorithms in S2 are dense and take effort to work through, 
perhaps adding simplistic example code (in an appendix) which implements, and/or 
actually working through the algorithms to arrive at some of the audit paths and 
consistency proofs in S2.1.3, would be helpful.

I desk-checked S2.1, and it seems correct, but didn't do S2.1.1 or S2.1.2.  The 
examples in S2.1.3 appear nominally correct but I didn't desk check them.

Should there be a reference to 
<https://code.google.com/p/certificate-transparency/> ?   And/or a note 
regarding available code and to contact the authors for more information? (as is 
done in RFC 2154)


O-11. S3.3 should mention the Maximum Merge Delay MMD where it says 
"periodically append". Also, in S3.3, "Signed Merkle Tree Update" should be a 
"Tree Head Signature" aka "signed tree head (STH)"?


O-12. S3.3, S3.4, S4.4, S4.5, and S4.7 mention the notion of logs "publishing" 
STHs, but no mechanism is described for explicitly "publishing". Is this meant 
to mean only that a "published" STH is available for retrieval by clients using 
the "Retrieve Latest Signed Tree Head" log client message?

Or, would there be a use case, eg introducing an existing log service to a log 
monitor, for requesting (or being able to enumerate) all published STHs from the 
log?


O-13. signed tree heads (STHs) are denoted in terms of "tree size" (number of 
entries), but SCTs are denoted in terms of a timestamp.  Should there be a log 
client message supporting the return of the nearest STH (and thus tree size) to 
a given timestamp?



O-14. Detailed comments on S2...
------------------------------

> 2. Cryptographic components
>
>
> 2.1. Merkle Hash Trees
>
>
>    Logs use a binary Merkle hash tree for efficient auditing.  The
>    hashing algorithm is SHA-256 (note that this is fixed for this
>    experiment but it is anticipated that each log would be able to
>    specify a hash algorithm).  The input to the Merkle tree hash is a
>    list of data entries; these entries will be hashed to form the leaves
>    of the Merkle hash tree.  The output is a single 32-byte root hash.
>    Given an ordered list of n inputs, D[n] = {d(0), d(1), ..., d(n-1)},
>    the Merkle Tree Hash (MTH) is thus defined as follows:
>
>    The hash of an empty list is the hash of an empty string:
>
>    MTH({}) = SHA-256().

This MTH({}) construct doesn't appear to be used anywhere else in the spec 
(yes?), and so does it really need mentioning?



>    The hash of a list with one entry is:
>
>    MTH({d(0)}) = SHA-256(0x00 || d(0)).

The immediately above equation is for leaf entries (yes?), where in this 
notation n = 1, perhaps it should be stated explicitly:

     When n = 1, a leaf entry is denoted, and D[1] = {d(0)}. The leaf hash
     (LH) for a leaf entry is calculated as:

     MTH(D[1]) = LH(D[1]) = SHA-256( 0x00 || d(0) )



>    For n > 1, let k be the largest power of two smaller than n.

The unqualified "power of two" phrase is arguably ambiguous.
Suggested rephrase for this where it occurs throughout section 2..

     For n > 1, let k be a number which is the largest power of two
     such that k = 2^i, 0 <= i < n, and k < n.



>    The Merkle Tree Hash of an n-element list D[n] is then defined
>    recursively as

The above statement applies to the combination of the n = 1 equation above and 
the equation below, and so should perhaps be moved up above the n = 1 equation.



>    MTH(D[n]) = SHA-256(0x01 || MTH(D[0:k]) || MTH(D[k:n])),
>
>    where || is concatenation and D[k1:k2] denotes the length (k2 - k1)
>    list {d(k1), d(k1+1),..., d(k2-1)}.

The above phrase doesn't parse well and is somewhat ambiguous, here it is 
extracted for clarity:

  "D[k1:k2] denotes the length (k2 - k1) list {d(k1), d(k1+1),..., d(k2-1)}"


How about rephrasing it along the lines of this:

     D[k1:k2] denotes a sublist {d(k1), d(k1+1),..., d(k2-1)}, having
     (k2 - k1) elements, of the original input list D[n]. When (k2 - k1)
     is 1, a leaf hash is calculated.


                                          (Note that the hash calculation
>    for leaves and nodes differ.  This domain separation is required to
>    give second preimage resistance.)
>
>    Note that we do not require the length of the input list to be a
>    power of two.  The resulting Merkle tree may thus not be balanced,
>    however, its shape is uniquely determined by the number of leaves.
>    [This Merkle tree is essentially the same as the history tree [1]
>    proposal, except our definition omits dummy leaves.]

I suggest re-writing the first above Note along with the next paragraph in light 
of all above comments on S2 and [CrosbyWallach].





O-15.  Some comments on S3:
------------------------------------

> 3. Log Format

this section isn't just about "format" of log - it's also about log 
behavior/operation


>    Anyone can submit certificates to certificate logs for public
>    auditing, however, since certificates will not be accepted by clients
>    unless logged, it is expected that certificate owners or their CAs
>    will usually submit them.  A log is a single, ever-growing, append-
>    only Merkle Tree of such certificates.
>
>    When a valid certificate is submitted to a log, the log MUST
>    immediately return a Signed Certificate Timestamp (SCT).  The SCT is
>    the log's promise to incorporate the certificate in the Merkle Tree
>    within a fixed amount of time known as the Maximum Merge Delay (MMD).
>    If the log has previously seen the certificate, it MAY return the
>    same SCT as it returned before.

What if the submitted end entity cert is the same, but the certificate chain is 
different (yet valid)?


>                                     TLS servers MUST present an SCT from
>    one or more logs to the client together with the certificate.  TLS
>    clients MUST reject certificates that do not have a valid SCT for the
>    end-entity certificate.

[ see comment (7) above ]


>    Periodically, each log appends all its new entries to the Merkle
>    Tree, and signs the root of the tree.  Clients and auditors can thus

Should "Clients and auditors" actually be "TLS Clients, log monitors, and log 
auditors" ?


>    verify that each certificate for which an SCT has been issued indeed
>    appears in the log.

Add forward reference here to S4 and S5 ?



>                         The log MUST incorporate a certificate in its
>    Merkle Tree within the Maximum Merge Delay period after the issuance
>    of the SCT.
>
>    Logs MUST NOT impose any conditions on copying data retrieved from
>    the log.

s/copying data retrieved/retrieving or sharing data/



> 3.1. Log Entries
>
>
>    Anyone can submit a certificate to any log.  In order to enable
>    attribution of each logged certificate to its issuer, the log SHALL
>    publish a list of acceptable root certificates (this list might
>    usefully be the union of root certificates trusted by major browser
>    vendors).  Each submitted certificate MUST be accompanied by all
>    additional certificates required to verify the certificate chain up
>    to an accepted root certificate.  The root certificate itself MAY be
>    omitted from this list.
>
>    Alternatively, (root as well as intermediate) Certificate Authorities

Additionally?  which manner is the experiment going to operate, or is it TBD ?


>    may submit a certificate to logs prior to issuance.  To do so, a
>    Certificate Authority constructs a Precertificate by adding a special
>    critical poison extension (OID 1.3.6.1.4.1.11129.2.4.3, whose
>    extnValue OCTET STRING contains ASN.1 NULL data (0x05 0x00)) to the
>    leaf TBSCertificate (this extension is to ensure that the

leaf == end entity ?

s/leaf certificate/end entity certificate/g   ?

>    Precertificate cannot be validated by a standard X.509v3 client), and
>    signing the resulting TBSCertificate [RFC5280] with either


>    o  a special-purpose (Extended Key Usage: Certificate Transparency,
>       OID 1.3.6.1.4.1.11129.2.4.4) Precertificate Signing Certificate.
>       The Precertificate Signing Certificate MUST be certified by the CA
>       certificate that will ultimately sign the leaf TBSCertificate

"sign the leaf TBSCertificate"  means to say "sign the actual 
issued-to-the-customer TBSCertificate component of the End Entity certificate" ?

>       (note that the log may relax standard validation rules to allow
>       this, so long as the final signed certificate will be valid),
>
>    o  or, the CA certificate that will sign the final certificate.

"final certificate" is the "issued-to-the-customer End Entity certificate" ?


>    Structure of the Signed Certificate Timestamp:

The SCT discussion here should probably be its own subsection.


>
>        enum { certificate_timestamp(0), tree_hash(1), 255 }
>          SignatureType;
>
>        enum { v1(0), 255 }
>          Version;
 >
>          struct {
>              opaque key_id[32];
>          } LogID;
>
>          opaque CtExtensions<0..2^16-1>;
>
>    "key_id" is the SHA-256 hash of the log's public key, calculated over
>    the DER encoding of the key represented as SubjectPublicKeyInfo.

I'd place the above paragraph regarding "key_id" down below the 
SignedCertificateTimestamp definition.


>        struct {
>            Version sct_version;
>            LogID id;
>            uint64 timestamp;
>            CtExtensions extensions;
>            digitally-signed struct {
>                Version sct_version;
>                SignatureType signature_type = certificate_timestamp;
>                uint64 timestamp;
>                LogEntryType entry_type;
>                select(entry_type) {
>                    case x509_entry: ASN.1Cert;
>                    case precert_entry: ASN.1Cert;
>                } signed_entry;
>               CtExtensions extensions;
>            };
>        } SignedCertificateTimestamp;
>
>    The encoding of the digitally-signed element is defined in [RFC5246].

I would add a few words here summarizing that what happens here is that the 
digitally-signed struct here is replaced in the actual serialized binary 
structure by a struct DigitallySigned and cross-ref to S4.7 of RFC5246.


> 3.2. Including the Signed Certificate Timestamp in the TLS Handshake

This should be it's own top-level section as mentioned in comment (3).


>    The SCT data from at least one log must be included in the TLS
>    handshake, either by using an Authorization Extension [RFC5878] with
>    type 182, or by using OCSP Stapling (section 8 of [RFC6066]),

add to above sentence:

   or by embedding the the SCT(s) in the presented End Entity cert,


>                                                                  where
>    the response includes an OCSP extension with OID
>    1.3.6.1.4.1.11129.2.4.5 (see [RFC2560]) and body:
>
>        SignedCertificateTimestampList ::= OCTET STRING
>
>    At least one SCT MUST be included.  Server operators MAY include more
>    than one SCT.
>
>    Similarly, a Certificate Authority MAY submit the precertificate to

s/the precertificate/a precertificate/


>    more than one log, and all obtained SCTs can be directly embedded in
>    the final certificate, by encoding the SignedCertificateTimestampList

s/final certificate/actual End Entity certificate/   ?


>    structure as an ASN.1 OCTET STRING and inserting the resulting data
>    in the TBSCertificate as an X.509v3 certificate extension (OID
>    1.3.6.1.4.1.11129.2.4.2).  Upon receiving the certificate, clients
>    can reconstruct the original TBSCertificate to verify the SCT
>    signature.

This last step of "clients can reconstruct the original TBSCertificate" probably 
should be more thoroughly explained.




O-15.  Some comments on S4:
---------------------------


> 4. Client Messages

title should be "Log Client Messages" ?


>    Messages are sent as HTTPS GET or POST requests.  Parameters for
>    POSTs and all responses are encoded as JSON objects.  Parameters for

s/JSON objects/JSON texts/

see <https://tools.ietf.org/html/rfc4627>  (it should be cited)

>    GETs are encoded as URL parameters.  Binary data is base64 encoded as
>    specified in the individual messages.
>
>    The <log server> prefix can include a path as well as a server name
>    and a port.  It must map one-to-one to a known public key (how this
>    mapping is distributed is out of scope for this document).

s/distributed/constructed and distributed/  ?


>    In general, where needed, the "version" is v1 and the "id" is the log
>    id for the log server queried.




> 4.1. Add Chain to Log
>
>
>    POST https://<log server>/ct/v1/add-chain
>
>    Inputs
>
>    chain  An array of base64 encoded certificates.  The first element is

a JSON text array?


>       the leaf certificate, the second chains to the first and so on to
>       the last, which is either the root certificate or a certificate
>       that chains to a known root certificate.
>
>    Outputs
>
>    sct_version  The version of the SignedCertificateTimestamp structure,
>       in decimal.  A compliant v1 implementation MUST NOT expect this to
>       be 0 (i.e. v1).
>
>    id The log ID, base64 encoded.  Since clients who request an SCT for

s/clients/log clients/  ?

>       inclusion in the TLS handshake are not required to verify it, we

s/the TLS handshake/subsequent TLS handshakes/   ?



>       do not assume they know the ID of the log.
>
>    timestamp  The SCT timestamp, in decimal.
>
>    extensions  An opaque type for future expansion.  It is likely that
>       not all participants will need to understand data in this field.
>       Logs should set this to the empty string.  Clients should decode
>       the base64 encoded data and include it in the SCT.
>
>    signature  The SCT signature, base64 encoded.

"The SCT signature" means a SignedCertificateTimestamp structure ?


>
>    If the "sct_version" is not v1, then a v1 client may be unable to
>    verify the signature.  It MUST NOT construe this as an error.  [Note:
>    log clients don't need to be able to verify this structure, only TLS
>    clients do - if we were to serve the structure binary, then we could
>    completely change it without requiring an upgrade to v1 clients].

Does this "if we were to serve the structure binary...."  statement mean to say 
that since v1 log clients don't need to be able to verify the SCT signature over 
the various returned data items, that this operation could instead return an 
opaque binary blob?


O-16.  Some comments on S5:
---------------------------


> 5. Clients
>
>
>    There are various different functions clients of logs might perform.

Perhaps this section should be entitled "Log Client Roles" ?

this section doesn't mention the role of a (CA) log client that submits "certs 
and cert chains" to logs. Even though the latter role is mentioned elsewhere in 
the spec it should perhaps be mentioned here also.


> 5.1. Monitor
>
>
>    Monitors watch logs and check that they behave correctly.  They also
>    watch for certificates of interest.

"Monitor" should be "Log Monitor" ?

>
> 5.2. Auditor
>
>
>    Auditors take partial information about a log as input and verify
>    that this information is consistent with other partial information
>    they have.  An auditor might be an integral component of a TLS
>    client, it might be a standalone service or it might be a secondary
>    function of a monitor.

"Auditor" should be "Log Auditor" ?



> 8. Efficiency Considerations
>
>
>    The Merkle tree design serves the purpose of keeping communication
>    overhead low.
>
>    Auditing logs for integrity does not require third parties to
>    maintain a copy of each entire log.  The Signed Tree Heads can be
>    updated as new entries become available, without recomputing entire
>    trees.  Third party auditors need only fetch the Merkle consistency
>    proofs against a log's existing STH to efficiently verify the append-
>    only property of updates to their Merkle Trees, without auditing the
>    entire tree.

The above could be explained in more detail, and S5.1 should be 
cross-referenced. Is the last sentence above essentially a summary of step #8 in 
S5.1? Or are there differences?


---
end



From jaap@NLnetLabs.nl  Tue Jan  1 14:14:08 2013
Return-Path: <jaap@NLnetLabs.nl>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9069C1F0CF7 for <ietf@ietfa.amsl.com>; Tue,  1 Jan 2013 14:14:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 Ro6GAzlbs39N for <ietf@ietfa.amsl.com>; Tue,  1 Jan 2013 14:14:07 -0800 (PST)
Received: from bela.nlnetlabs.nl (bela.nlnetlabs.nl [IPv6:2001:7b8:206:1:222:4dff:fe55:4ccb]) by ietfa.amsl.com (Postfix) with ESMTP id 921791F0C3E for <ietf@ietf.org>; Tue,  1 Jan 2013 14:13:54 -0800 (PST)
Received: from NLnetLabs.nl (localhost [127.0.0.1]) by bela.nlnetlabs.nl (8.14.5/8.14.5) with ESMTP id r01MDgPM066363; Tue, 1 Jan 2013 23:13:42 +0100 (CET) (envelope-from jaap@NLnetLabs.nl)
Message-Id: <201301012213.r01MDgPM066363@bela.nlnetlabs.nl>
To: John Day <jeanjour@comcast.net>
Subject: Re: WCIT outcome?
In-reply-to: <a06240815cd08da399dc6@[10.0.1.3]>
References: <CAMm+Lwh2cHRY+Dk2_SDtZZmUbPcgRpP89u3DHUcniJDrKrX_pw@mail.gmail.com> <CAMzo+1a0-90dnjnvs48a9DcNN9DY_edF5hH0__4XRuCaLHtL6Q@mail.gmail.com> <CAMm+LwjzjLc2-=4EdxwHOi21B3dOBUohYc5hhXZHL_Pk+iBBmQ@mail.gmail.com> <6.2.5.6.2.20121229192941.0aae33e8@resistor.net> <CAMm+LwiC0xtJU4vnGFPvAG4VKZdj7Tf3LfW0+pzwxKWTegRREw@mail.gmail.com> <a06240800cd074efd45b8@10.0.1.3> <CAMm+Lwiq+DCzXw572wKs78DG+XzYsJtwCVSPvNuVHSrT=Cr2nA@mail.gmail.com> <a06240809cd0799fee029@[10.0.1.3]> <50E29EE0.1080107@gmail.com> <a06240815cd08da399dc6@[10.0.1.3]>
Comments: In-reply-to John Day <jeanjour@comcast.net> message dated "Tue, 01 Jan 2013 13:32:50 -0500."
Date: Tue, 01 Jan 2013 23:13:42 +0100
From: Jaap Akkerhuis <jaap@NLnetLabs.nl>
X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.2.7 (bela.nlnetlabs.nl [127.0.0.1]); Tue, 01 Jan 2013 23:13:45 +0100 (CET)
Cc: Phillip Hallam-Baker <hallam@gmail.com>, IETF Discussion Mailing List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 Jan 2013 22:14:08 -0000

It is of course all history, but allow me some remarks (in line).

    Thanks Brian, That helps clear up a few things.  See below for a 
    couple of questions:
    
    At 8:31 AM +0000 1/1/13, Brian E Carpenter wrote:
    >I'v been hesitating to join in here because this seems distinctly OT
    >to me, but there are some basics that need to be understood:
    >
    >On 31/12/2012 21:08, John Day wrote:
    >>  At 1:05 PM -0500 12/31/12, Phillip Hallam-Baker wrote:
    >>>  On Mon, Dec 31, 2012 at 9:51 AM, John Day
    >>>  <<mailto:jeanjour@comcast.net>jeanjour@comcast.net> wrote:
    >
    >...
    >>>  MPs and Congressmen are elected decision makers. ITU participants can
    >>>  make decisions but they are not binding on anyone and only have effect
    >>>  if people like me choose to implement them.
    >>
    >>  This was my point. The standards part of ITU is just like any other
    >>  standards organization. But there are other things it does which are not
    >>  like this, e.g. spectrum allocation.  There are other aspects with
    >>  respect to tariffs that are binding on signatories.
    >
    >Not only tariffs. Historically, it was national enforcement of international
    >regulations set by CCITT (now known as ITU-T) that prevented interconnection
    >of leased lines**.
    
    But creating a VPN with in an international carrier that crossed 
    national boundaries would not fall under that rule?  Actually neither 
    would a VPN operating over a couple of carriers that crossed national 
    boundaries, would it?

In the early eigthies, after consulting with the telecom authorithy
in the Netherlands we got the green light to move data for third
parties, and thus the (then uucp based) EUnet was born. The green
light was given in the anticipation of the libiralization of the
EU telcom market. And yes, first this was indeed first using (nearly
only) dial-up connections but soon some leased lines and of course
TCP/IP etc. game into play.
    
    >This is an arcane point today, but if CERN hadn't been
    >able to use its status as an international organization to bypass that
    >restriction in the 1980s, it's unlikely that TBL and Robert Cailliau would
    >ever have been able to propagate the web. It's even unlikely that Phill
    >would have been able to access Usenet newsgroups while on shift as a grad
    >student on a CERN experiment.
    
    ;-) Actually what they don't know won't hurt them.  ;-) We were 
    moving files from CERN to Argonne in the 70s through the 360/95 at 
    Rutherford over the ARPANET.   Not exactly the way you want to do it 
    but 15 years later I am sure it was upgraded a bit.
    
    >
    >Also, it is exactly because ITU was in charge of resource allocations
    >such as radio spectrum and top-level POTS dialling codes that it was
    >a very plausible potential home for IANA in 1997-8, before ICANN was
    >created. Some of the ITU people who were active in that debate were just
    >as active in the preparation for WCIT in 2012.
    
    Yea, this one is more dicey.  Although I think there is an argument 
    that says that you need ccoperation among providers about assignment, 
    but I don't see why governments need to be involved.  When phone 
    companies were owned by governments, then it made sense.  But phone 
    companies are owned by governments any more.

[The RIPE was born out of necessity for coordination of the IP number space].
    
    That doesn't leave much does it?  (Not a facetious question, I am asking!)
    
    Take care,
    John
    
    >
    >** CCITT document D.1. The 1988 version includes the restrictions on
    >use of leased lines:
    >http://www.itu.int/rec/dologin_pub.asp?lang=e&id=T-REC-D.1-198811-S!!PDF-E&type=items
    >
    >The 1991 version is much less restrictive, but it remains the case that
    >interconnections are all "subject to national laws" and that is the basis
    >for all national limitations on the Internet today. Nevertheless, the 1991
    >revision of D.1 was absolutely essential for the Internet to grow
    >internationally.
    >
    >It would be foolish to imagine that the Internet is in some way immune
    >to ITU-T regulations, which is why the effort to defeat the more radical
    >WCIT proposals was so important.
    >
    >    Brian


It seems that this document was already unaware about what was really happening
in practice.

	jaap

From hallam@gmail.com  Tue Jan  1 16:29:14 2013
Return-Path: <hallam@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D533921F8DEF for <ietf@ietfa.amsl.com>; Tue,  1 Jan 2013 16:29:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.561
X-Spam-Level: 
X-Spam-Status: No, score=-3.561 tagged_above=-999 required=5 tests=[AWL=0.037,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
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 XSfZUWjt3+dQ for <ietf@ietfa.amsl.com>; Tue,  1 Jan 2013 16:29:12 -0800 (PST)
Received: from mail-oa0-f46.google.com (mail-oa0-f46.google.com [209.85.219.46]) by ietfa.amsl.com (Postfix) with ESMTP id 62E3E21F8DEE for <ietf@ietf.org>; Tue,  1 Jan 2013 16:29:12 -0800 (PST)
Received: by mail-oa0-f46.google.com with SMTP id h16so12578904oag.5 for <ietf@ietf.org>; Tue, 01 Jan 2013 16:29:12 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=0adNW6N3wl0dhFgMjCOVXnoMq31ZZG4/T7XwkuCykWI=; b=hBfOKQzI1ooEoL5Oby6TGmeLA6RudVD5amTm/FDHapoLshIe2ZK96v5kJdZv5cWZ7B gjZtHUZzhOokuQ8YRIMwSGoo/nugGf+4pKqZ+0cFBqSzGfYCvBF3wI5btckXrFu5PCr+ xSRKYMzjJ2ahNBr5eWbY5IPOAlrP/oKGRHNG+QGS1fMAt4CRbPripJJWONVSTOBj5/4J /y0UVjYZclohTj+1omwv/BGBae5uoqLzbmTkvmmdeVjQDfj2OrnuBkZKFT2H6w12Amwx yCm0ej3V5NCWuRkCTNPBzYUqyyt3dzd/aXd5RUtJekFA4fdX8KtQ6vjz6heTS0J2e72x 8Dxw==
MIME-Version: 1.0
Received: by 10.182.95.205 with SMTP id dm13mr37323866obb.9.1357086551898; Tue, 01 Jan 2013 16:29:11 -0800 (PST)
Received: by 10.76.19.43 with HTTP; Tue, 1 Jan 2013 16:29:11 -0800 (PST)
In-Reply-To: <50E29EE0.1080107@gmail.com>
References: <CAMm+Lwh2cHRY+Dk2_SDtZZmUbPcgRpP89u3DHUcniJDrKrX_pw@mail.gmail.com> <CAMzo+1a0-90dnjnvs48a9DcNN9DY_edF5hH0__4XRuCaLHtL6Q@mail.gmail.com> <CAMm+LwjzjLc2-=4EdxwHOi21B3dOBUohYc5hhXZHL_Pk+iBBmQ@mail.gmail.com> <6.2.5.6.2.20121229192941.0aae33e8@resistor.net> <CAMm+LwiC0xtJU4vnGFPvAG4VKZdj7Tf3LfW0+pzwxKWTegRREw@mail.gmail.com> <a06240800cd074efd45b8@10.0.1.3> <CAMm+Lwiq+DCzXw572wKs78DG+XzYsJtwCVSPvNuVHSrT=Cr2nA@mail.gmail.com> <a06240809cd0799fee029@10.0.1.3> <50E29EE0.1080107@gmail.com>
Date: Tue, 1 Jan 2013 19:29:11 -0500
Message-ID: <CAMm+LwiqXY9bJV_9Cu54Wyt6rtBeJicubm0nUe1k+ftmGxnw6w@mail.gmail.com>
Subject: Re: WCIT outcome?
From: Phillip Hallam-Baker <hallam@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Content-Type: multipart/alternative; boundary=14dae93b6320dafa4304d2435575
Cc: IETF Discussion Mailing List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Jan 2013 00:29:15 -0000

--14dae93b6320dafa4304d2435575
Content-Type: text/plain; charset=ISO-8859-1

On Tue, Jan 1, 2013 at 3:31 AM, Brian E Carpenter <
brian.e.carpenter@gmail.com> wrote:

> I'v been hesitating to join in here because this seems distinctly OT
> to me, but there are some basics that need to be understood:
>
> On 31/12/2012 21:08, John Day wrote:
> > At 1:05 PM -0500 12/31/12, Phillip Hallam-Baker wrote:
> >> On Mon, Dec 31, 2012 at 9:51 AM, John Day
> >> <<mailto:jeanjour@comcast.net>jeanjour@comcast.net> wrote:
>
> ...
> >> MPs and Congressmen are elected decision makers. ITU participants can
> >> make decisions but they are not binding on anyone and only have effect
> >> if people like me choose to implement them.
> >
> > This was my point. The standards part of ITU is just like any other
> > standards organization. But there are other things it does which are not
> > like this, e.g. spectrum allocation.  There are other aspects with
> > respect to tariffs that are binding on signatories.
>
> Not only tariffs. Historically, it was national enforcement of
> international
> regulations set by CCITT (now known as ITU-T) that prevented
> interconnection
> of leased lines**. This is an arcane point today, but if CERN hadn't been
> able to use its status as an international organization to bypass that
> restriction in the 1980s, it's unlikely that TBL and Robert Cailliau would
> ever have been able to propagate the web. It's even unlikely that Phill
> would have been able to access Usenet newsgroups while on shift as a grad
> student on a CERN experiment.
>

I was never a grad student at CERN, I was a CERN Fellow. And I had access
to USENET from DESY but we were routing it through CERN at first.

Now it is an interesting question as to what might have happened if the Web
had not expanded as it did when it did. But one of the reasons that it
expanded was that there were a lot of parties involved who were actively
wanting to blow up the CITT tariffs and establish a free market. That was
HMG policy at any rate.



> Also, it is exactly because ITU was in charge of resource allocations
> such as radio spectrum and top-level POTS dialling codes that it was
> a very plausible potential home for IANA in 1997-8, before ICANN was
> created. Some of the ITU people who were active in that debate were just
> as active in the preparation for WCIT in 2012.
>

When the big question facing DNS admin was legal liability in the various
domain name disputes that were proliferating, having a treaty organization
with diplomatic immunity actually had some advantages.

But that was a very different time diplomatically. That was before Putin
was ordering assassinations on the streets of London with Polonium laced
teapots and before the colour revolutions rolled back the Russian sphere of
influence. And our side was hardly blameless, it was the US invasion of
Iraq that poisoned the well in the first place.



> ** CCITT document D.1. The 1988 version includes the restrictions on
> use of leased lines:
>
> http://www.itu.int/rec/dologin_pub.asp?lang=e&id=T-REC-D.1-198811-S!!PDF-E&type=items
>
> The 1991 version is much less restrictive, but it remains the case that
> interconnections are all "subject to national laws" and that is the basis
> for all national limitations on the Internet today. Nevertheless, the 1991
> revision of D.1 was absolutely essential for the Internet to grow
> internationally.
>

The idea of fixing the contract terms in an international treaty is utterly
bizarre.



> It would be foolish to imagine that the Internet is in some way immune
> to ITU-T regulations, which is why the effort to defeat the more radical
> WCIT proposals was so important.
>

While technically true, I think your wording is misleading.

ITU-T has absolutely no control over the Internet unless member governments
decide to give it that power. The importance of the protests was that they
prevented the US and EU governments from agreeing to cede that power.

Within the US government there are different factions. What was important
was to ensure that the pro-control faction did not get the chance to agree
to give the store away.


-- 
Website: http://hallambaker.com/

--14dae93b6320dafa4304d2435575
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<br><br><div class=3D"gmail_quote">On Tue, Jan 1, 2013 at 3:31 AM, Brian E =
Carpenter <span dir=3D"ltr">&lt;<a href=3D"mailto:brian.e.carpenter@gmail.c=
om" target=3D"_blank">brian.e.carpenter@gmail.com</a>&gt;</span> wrote:<br>=
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
I&#39;v been hesitating to join in here because this seems distinctly OT<br=
>
to me, but there are some basics that need to be understood:<br>
<div class=3D"im"><br>
On 31/12/2012 21:08, John Day wrote:<br>
&gt; At 1:05 PM -0500 12/31/12, Phillip Hallam-Baker wrote:<br>
&gt;&gt; On Mon, Dec 31, 2012 at 9:51 AM, John Day<br>
</div>&gt;&gt; &lt;&lt;mailto:<a href=3D"mailto:jeanjour@comcast.net">jeanj=
our@comcast.net</a>&gt;<a href=3D"mailto:jeanjour@comcast.net">jeanjour@com=
cast.net</a>&gt; wrote:<br>
<br>
...<br>
<div class=3D"im">&gt;&gt; MPs and Congressmen are elected decision makers.=
 ITU participants can<br>
&gt;&gt; make decisions but they are not binding on anyone and only have ef=
fect<br>
&gt;&gt; if people like me choose to implement them.<br>
&gt;<br>
&gt; This was my point. The standards part of ITU is just like any other<br=
>
&gt; standards organization. But there are other things it does which are n=
ot<br>
&gt; like this, e.g. spectrum allocation. =A0There are other aspects with<b=
r>
&gt; respect to tariffs that are binding on signatories.<br>
<br>
</div>Not only tariffs. Historically, it was national enforcement of intern=
ational<br>
regulations set by CCITT (now known as ITU-T) that prevented interconnectio=
n<br>
of leased lines**. This is an arcane point today, but if CERN hadn&#39;t be=
en<br>
able to use its status as an international organization to bypass that<br>
restriction in the 1980s, it&#39;s unlikely that TBL and Robert Cailliau wo=
uld<br>
ever have been able to propagate the web. It&#39;s even unlikely that Phill=
<br>
would have been able to access Usenet newsgroups while on shift as a grad<b=
r>
student on a CERN experiment.<br></blockquote><div><br></div><div>I was nev=
er a grad student at CERN, I was a CERN Fellow.=A0And I had access to USENE=
T from DESY but we were routing it through CERN at first.</div><div><br>
</div><div>Now it is an interesting question as to what might have happened=
 if the Web had not expanded as it did when it did. But one of the reasons =
that it expanded was that there were a lot of parties involved who were act=
ively wanting to blow up the CITT tariffs and establish a free market. That=
 was HMG policy at any rate.</div>
<div><br></div><div>=A0</div><blockquote class=3D"gmail_quote" style=3D"mar=
gin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Also, it is exactly because ITU was in charge of resource allocations<br>
such as radio spectrum and top-level POTS dialling codes that it was<br>
a very plausible potential home for IANA in 1997-8, before ICANN was<br>
created. Some of the ITU people who were active in that debate were just<br=
>
as active in the preparation for WCIT in 2012.<br></blockquote><div><br></d=
iv><div>When the big question facing DNS admin was legal liability in the v=
arious domain name disputes that were proliferating, having a treaty organi=
zation with diplomatic immunity actually had some advantages.</div>
<div><br></div><div>But that was a very different time diplomatically. That=
 was before Putin was ordering assassinations on the streets of London with=
 Polonium laced teapots and before the colour revolutions rolled back the R=
ussian sphere of influence. And our side was hardly blameless, it was the U=
S invasion of Iraq that poisoned the well in the first place.</div>
<div><br></div><div>=A0</div><blockquote class=3D"gmail_quote" style=3D"mar=
gin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
** CCITT document D.1. The 1988 version includes the restrictions on<br>
use of leased lines:<br>
<a href=3D"http://www.itu.int/rec/dologin_pub.asp?lang=3De&amp;id=3DT-REC-D=
.1-198811-S!!PDF-E&amp;type=3Ditems" target=3D"_blank">http://www.itu.int/r=
ec/dologin_pub.asp?lang=3De&amp;id=3DT-REC-D.1-198811-S!!PDF-E&amp;type=3Di=
tems</a><br>

<br>
The 1991 version is much less restrictive, but it remains the case that<br>
interconnections are all &quot;subject to national laws&quot; and that is t=
he basis<br>
for all national limitations on the Internet today. Nevertheless, the 1991<=
br>
revision of D.1 was absolutely essential for the Internet to grow<br>
internationally.<br></blockquote><div><br></div><div>The idea of fixing the=
 contract terms in an international treaty is utterly bizarre.=A0</div><div=
><br></div><div>=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:=
0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">

It would be foolish to imagine that the Internet is in some way immune<br>
to ITU-T regulations, which is why the effort to defeat the more radical<br=
>
WCIT proposals was so important.<br></blockquote><div><br></div><div>While =
technically true, I think your wording is misleading.</div><div><br></div><=
div>ITU-T has absolutely no control over the Internet unless member governm=
ents decide to give it that power. The importance of the protests was that =
they prevented the US and EU governments from agreeing to cede that power.<=
/div>
<div><br></div><div>Within the US government there are different factions. =
What was important was to ensure that the pro-control faction did not get t=
he chance to agree to give the store away.</div><div>=A0</div></div><div>
<br></div>-- <br>Website: <a href=3D"http://hallambaker.com/">http://hallam=
baker.com/</a><br>

--14dae93b6320dafa4304d2435575--

From jeanjour@comcast.net  Tue Jan  1 17:12:02 2013
Return-Path: <jeanjour@comcast.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4071721F8B19 for <ietf@ietfa.amsl.com>; Tue,  1 Jan 2013 17:12:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.42
X-Spam-Level: 
X-Spam-Status: No, score=-100.42 tagged_above=-999 required=5 tests=[AWL=0.016, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_NET=0.611, HTML_MESSAGE=0.001, RDNS_NONE=0.1, USER_IN_WHITELIST=-100]
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 cJE4oobETwee for <ietf@ietfa.amsl.com>; Tue,  1 Jan 2013 17:12:01 -0800 (PST)
Received: from qmta05.westchester.pa.mail.comcast.net (qmta05.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:43:76:96:62:48]) by ietfa.amsl.com (Postfix) with ESMTP id D0F2D21F8B0E for <ietf@ietf.org>; Tue,  1 Jan 2013 17:12:00 -0800 (PST)
Received: from omta24.westchester.pa.mail.comcast.net ([76.96.62.76]) by qmta05.westchester.pa.mail.comcast.net with comcast id idkz1k0011ei1Bg55pC0Ku; Wed, 02 Jan 2013 01:12:00 +0000
Received: from [10.0.1.3] ([98.229.211.49]) by omta24.westchester.pa.mail.comcast.net with comcast id ipBz1k00814WE023kpBzNC; Wed, 02 Jan 2013 01:12:00 +0000
Mime-Version: 1.0
Message-Id: <a06240829cd0934717452@[10.0.1.3]>
In-Reply-To: <CAMm+LwiqXY9bJV_9Cu54Wyt6rtBeJicubm0nUe1k+ftmGxnw6w@mail.gmail.com>
References: <CAMm+Lwh2cHRY+Dk2_SDtZZmUbPcgRpP89u3DHUcniJDrKrX_pw@mail.gmail.com> <CAMzo+1a0-90dnjnvs48a9DcNN9DY_edF5hH0__4XRuCaLHtL6Q@mail.gmail.com> <CAMm+LwjzjLc2-=4EdxwHOi21B3dOBUohYc5hhXZHL_Pk+iBBmQ@mail.gmail.com> <6.2.5.6.2.20121229192941.0aae33e8@resistor.net> <CAMm+LwiC0xtJU4vnGFPvAG4VKZdj7Tf3LfW0+pzwxKWTegRREw@mail.gmail.com> <a06240800cd074efd45b8@10.0.1.3> <CAMm+Lwiq+DCzXw572wKs78DG+XzYsJtwCVSPvNuVHSrT=Cr2nA@mail.gmail.com> <a06240809cd0799fee029@10.0.1.3>	<50E29EE0.1080107@gmail.com> <CAMm+LwiqXY9bJV_9Cu54Wyt6rtBeJicubm0nUe1k+ftmGxnw6w@mail.gmail.com>
Date: Tue, 1 Jan 2013 20:11:53 -0500
To: Phillip Hallam-Baker <hallam@gmail.com>, Brian E Carpenter <brian.e.carpenter@gmail.com>
From: John Day <jeanjour@comcast.net>
Subject: Re: WCIT outcome?
Content-Type: multipart/alternative; boundary="============_-855033377==_ma============"
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20121106; t=1357089120; bh=44GQFEM6IfnwefjwbJAEMu2Pg6TWhcgyH7fnstnG/54=; h=Received:Received:Mime-Version:Message-Id:Date:To:From:Subject: Content-Type; b=M2J2Jvbw/lmnaSiTT0ZLFlWwPXgy9zEdyFMAi7MvZnobVZvivmGWzPWczZdHlqE0S rruj7oVLaxblcGkDkssvMXUshGmfgshpmgL8n+5bUMQ+LH1Uc+i8fSYkBD5u1OAxSb dK/W/dEaeof8t6rggSMIlsQJXX0Z26J4VPj0l1PZjjBMFRdOEQVZ3i/Z0we/C7Sfpa 9ufc3NNlzUio3avwIGdm8jdcXhusaUeaoOAwJVjOcJwQkWTM1nxs+tTIaoykCo3pzl RS0xA7KW2m11BpZ3G//NMPzRhDz6pz+uhm5FV58dttRMlXt/aWaB7bhIKDFHHz8jK2 bNtJquspsQTrQ==
Cc: IETF Discussion Mailing List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Jan 2013 01:12:02 -0000

--============_-855033377==_ma============
Content-Type: text/plain; charset="us-ascii" ; format="flowed"

At 7:29 PM -0500 1/1/13, Phillip Hallam-Baker wrote:
>On Tue, Jan 1, 2013 at 3:31 AM, Brian E Carpenter 
><<mailto:brian.e.carpenter@gmail.com>brian.e.carpenter@gmail.com> 
>wrote:
>
>I'v been hesitating to join in here because this seems distinctly OT
>to me, but there are some basics that need to be understood:
>
>
>On 31/12/2012 21:08, John Day wrote:
>>  At 1:05 PM -0500 12/31/12, Phillip Hallam-Baker wrote:
>>>  On Mon, Dec 31, 2012 at 9:51 AM, John Day
>
>  >> 
><<mailto:<mailto:jeanjour@comcast.net>jeanjour@comcast.net><mailto:jeanjour@comcast.net>jeanjour@comcast.net> 
>wrote:
>
>...
>
>  >> MPs and Congressmen are elected decision makers. ITU participants can
>>>  make decisions but they are not binding on anyone and only have effect
>>>  if people like me choose to implement them.
>>
>>  This was my point. The standards part of ITU is just like any other
>>  standards organization. But there are other things it does which are not
>>  like this, e.g. spectrum allocation.  There are other aspects with
>>  respect to tariffs that are binding on signatories.
>
>Not only tariffs. Historically, it was national enforcement of international
>regulations set by CCITT (now known as ITU-T) that prevented interconnection
>of leased lines**. This is an arcane point today, but if CERN hadn't been
>able to use its status as an international organization to bypass that
>restriction in the 1980s, it's unlikely that TBL and Robert Cailliau would
>ever have been able to propagate the web. It's even unlikely that Phill
>would have been able to access Usenet newsgroups while on shift as a grad
>student on a CERN experiment.
>
>
>I was never a grad student at CERN, I was a CERN Fellow. And I had 
>access to USENET from DESY but we were routing it through CERN at 
>first.
>
>Now it is an interesting question as to what might have happened if 
>the Web had not expanded as it did when it did. But one of the 
>reasons that it expanded was that there were a lot of parties 
>involved who were actively wanting to blow up the CITT tariffs and 
>establish a free market. That was HMG policy at any rate.
>
>

I have heard tell (dropping into the vernacular) that to many, the 
web was just another application like Gopher until NCSA put a browser 
on it.  The question is what would have happened had they put the 
browser on top of something else?

>
>Also, it is exactly because ITU was in charge of resource allocations
>such as radio spectrum and top-level POTS dialling codes that it was
>a very plausible potential home for IANA in 1997-8, before ICANN was
>created. Some of the ITU people who were active in that debate were just
>as active in the preparation for WCIT in 2012.
>
>
>When the big question facing DNS admin was legal liability in the 
>various domain name disputes that were proliferating, having a 
>treaty organization with diplomatic immunity actually had some 
>advantages.

Agreed but the treaty organization was the WTO and another one I 
can't remember right now! ;-)  As long as the problem was punted to 
them one was okay.  I just don't see how ITU has purview over *uses* 
of the network. (Nor am I willing to easily cede that.)

This is why it is not a good idea to go along with the ITU 
beads-on-a-string model.  By doing so, it already clouds the picture 
and gives up ground.

>
>But that was a very different time diplomatically. That was before 
>Putin was ordering assassinations on the streets of London with 
>Polonium laced teapots and before the colour revolutions rolled back 
>the Russian sphere of influence. And our side was hardly blameless, 
>it was the US invasion of Iraq that poisoned the well in the first 
>place.
>
>

True, but what effect does this have?  The US did burn up a lot of 
good will for no good reason and then botched the job on top of it.

>
>** CCITT document D.1. The 1988 version includes the restrictions on
>use of leased lines:
><http://www.itu.int/rec/dologin_pub.asp?lang=e&id=T-REC-D.1-198811-S!!PDF-E&type=items>http://www.itu.int/rec/dologin_pub.asp?lang=e&id=T-REC-D.1-198811-S!!PDF-E&type=items
>
>The 1991 version is much less restrictive, but it remains the case that
>interconnections are all "subject to national laws" and that is the basis
>for all national limitations on the Internet today. Nevertheless, the 1991
>revision of D.1 was absolutely essential for the Internet to grow
>internationally.
>
>
>The idea of fixing the contract terms in an international treaty is 
>utterly bizarre.
>
>
>
>It would be foolish to imagine that the Internet is in some way immune
>to ITU-T regulations, which is why the effort to defeat the more radical
>WCIT proposals was so important.
>
>
>While technically true, I think your wording is misleading.

Why is this technically true?  Honest question.

>
>ITU-T has absolutely no control over the Internet unless member 
>governments decide to give it that power. The importance of the 
>protests was that they prevented the US and EU governments from 
>agreeing to cede that power.

Agreed.

>Within the US government there are different factions. What was 
>important was to ensure that the pro-control faction did not get the 
>chance to agree to give the store away.
>

My model here (for better or worse) is the origin of the US 
Constitution.  The Constitution does not create a hierarchical 
structure.  The States cede parts of their sovereignty to the Federal 
government. Those things better done across States, rather than 
individually:  Common currency, regulating interstate commerce, 
defense, etc.  The Federal government is alongside the State 
governments.  The EU is a confederation that is doing some of these 
as well.  The UN is a very weak confederation, so the question to 
consider is what aspects of *telecommunication*  (not defense or 
commerce or anything else) does it make sense that there should be 
international regulation (or binding agreements)?

So far, my list is pretty short.  In fact, there is wireless spectrum 
and that is it.  And even there, I would suggest only above certain 
transmitter power levels.

Actually, I would have to apply the same criteria to the FCC.  ;-)

--============_-855033377==_ma============
Content-Type: text/html; charset="us-ascii"

<!doctype html public "-//W3C//DTD W3 HTML//EN">
<html><head><style type="text/css"><!--
blockquote, dl, ul, ol, li { padding-top: 0 ; padding-bottom: 0 }
 --></style><title>Re: WCIT outcome?</title></head><body>
<div>At 7:29 PM -0500 1/1/13, Phillip Hallam-Baker wrote:</div>
<blockquote type="cite" cite>On Tue, Jan 1, 2013 at 3:31 AM, Brian E
Carpenter &lt;<a
href="mailto:brian.e.carpenter@gmail.com">brian.e.carpenter@gmail.com</a
>&gt; wrote:<br>
<blockquote>I'v been hesitating to join in here because this seems
distinctly OT<br>
to me, but there are some basics that need to be understood:<br>
</blockquote>
<blockquote><br>
On 31/12/2012 21:08, John Day wrote:<br>
&gt; At 1:05 PM -0500 12/31/12, Phillip Hallam-Baker wrote:<br>
&gt;&gt; On Mon, Dec 31, 2012 at 9:51 AM, John Day<br>
</blockquote>
<blockquote>&gt;&gt; &lt;&lt;mailto:<a
href="mailto:jeanjour@comcast.net">jeanjour@comcast.net</a>&gt;<a
href="mailto:jeanjour@comcast.net">jeanjour@comcast.net</a>&gt;
wrote:<br>
<br>
...<br>
</blockquote>
<blockquote>&gt;&gt; MPs and Congressmen are elected decision makers.
ITU participants can<br>
&gt;&gt; make decisions but they are not binding on anyone and only
have effect<br>
&gt;&gt; if people like me choose to implement them.<br>
&gt;<br>
&gt; This was my point. The standards part of ITU is just like any
other<br>
&gt; standards organization. But there are other things it does which
are not<br>
&gt; like this, e.g. spectrum allocation. &nbsp;There are other
aspects with<br>
&gt; respect to tariffs that are binding on signatories.<br>
</blockquote>
<blockquote>Not only tariffs. Historically, it was national
enforcement of international<br>
regulations set by CCITT (now known as ITU-T) that prevented
interconnection<br>
of leased lines**. This is an arcane point today, but if CERN hadn't
been<br>
able to use its status as an international organization to bypass
that<br>
restriction in the 1980s, it's unlikely that TBL and Robert Cailliau
would<br>
ever have been able to propagate the web. It's even unlikely that
Phill<br>
would have been able to access Usenet newsgroups while on shift as a
grad<br>
student on a CERN experiment.<br>
</blockquote>
</blockquote>
<blockquote type="cite" cite><br></blockquote>
<blockquote type="cite" cite>I was never a grad student at CERN, I was
a CERN Fellow.&nbsp;And I had access to USENET from DESY but we were
routing it through CERN at first.</blockquote>
<blockquote type="cite" cite><br></blockquote>
<blockquote type="cite" cite>Now it is an interesting question as to
what might have happened if the Web had not expanded as it did when it
did. But one of the reasons that it expanded was that there were a lot
of parties involved who were actively wanting to blow up the CITT
tariffs and establish a free market. That was HMG policy at any
rate.</blockquote>
<blockquote type="cite" cite><br></blockquote>
<blockquote type="cite" cite>&nbsp;</blockquote>
<div><br></div>
<div>I have heard tell (dropping into the vernacular) that to many,
the web was just another application like Gopher until NCSA put a
browser on it.&nbsp; The question is what would have happened had they
put the browser on top of something else?</div>
<div><br></div>
<blockquote type="cite" cite><br>
<blockquote>Also, it is exactly because ITU was in charge of resource
allocations<br>
such as radio spectrum and top-level POTS dialling codes that it
was<br>
a very plausible potential home for IANA in 1997-8, before ICANN
was<br>
created. Some of the ITU people who were active in that debate were
just<br>
as active in the preparation for WCIT in 2012.<br>
</blockquote>
</blockquote>
<blockquote type="cite" cite><br></blockquote>
<blockquote type="cite" cite>When the big question facing DNS admin
was legal liability in the various domain name disputes that were
proliferating, having a treaty organization with diplomatic immunity
actually had some advantages.</blockquote>
<div><br></div>
<div>Agreed but the treaty organization was the WTO and another one I
can't remember right now! ;-)&nbsp; As long as the problem was punted
to them one was okay.&nbsp; I just don't see how ITU has purview over
*uses* of the network. (Nor am I willing to easily cede that.)</div>
<div><br></div>
<div>This is why it is not a good idea to go along with the ITU
beads-on-a-string model.&nbsp; By doing so, it already clouds the
picture and gives up ground.</div>
<div><br></div>
<blockquote type="cite" cite><br></blockquote>
<blockquote type="cite" cite>But that was a very different time
diplomatically. That was before Putin was ordering assassinations on
the streets of London with Polonium laced teapots and before the
colour revolutions rolled back the Russian sphere of influence. And
our side was hardly blameless, it was the US invasion of Iraq that
poisoned the well in the first place.</blockquote>
<blockquote type="cite" cite><br></blockquote>
<blockquote type="cite" cite>&nbsp;</blockquote>
<div><br></div>
<div>True, but what effect does this have?&nbsp; The US did burn up a
lot of good will for no good reason and then botched the job on top of
it.</div>
<div><br></div>
<blockquote type="cite" cite><br>
<blockquote>** CCITT document D.1. The 1988 version includes the
restrictions on<br>
use of leased lines:</blockquote>
<blockquote><a
href=
"http://www.itu.int/rec/dologin_pub.asp?lang=e&amp;id=T-REC-D.1-198811-S!!PDF-E&amp;type=items"><span
></span
>http://www.itu.int/rec/dologin_pub.asp?lang=e&amp;id=T-REC-D.1-19881<span
></span>1-S!!PDF-E&amp;type=items</a></blockquote>
<blockquote><br>
The 1991 version is much less restrictive, but it remains the case
that<br>
interconnections are all &quot;subject to national laws&quot; and that
is the basis<br>
for all national limitations on the Internet today. Nevertheless, the
1991<br>
revision of D.1 was absolutely essential for the Internet to grow<br>
internationally.<br>
</blockquote>
</blockquote>
<blockquote type="cite" cite><br></blockquote>
<blockquote type="cite" cite>The idea of fixing the contract terms in
an international treaty is utterly bizarre.</blockquote>
<blockquote type="cite" cite><br></blockquote>
<blockquote type="cite" cite>&nbsp;<br>
<blockquote>It would be foolish to imagine that the Internet is in
some way immune<br>
to ITU-T regulations, which is why the effort to defeat the more
radical<br>
WCIT proposals was so important.<br>
</blockquote>
</blockquote>
<blockquote type="cite" cite><br></blockquote>
<blockquote type="cite" cite>While technically true, I think your
wording is misleading.</blockquote>
<div><br></div>
<div>Why is this technically true?&nbsp; Honest question.</div>
<div><br></div>
<blockquote type="cite" cite><br></blockquote>
<blockquote type="cite" cite>ITU-T has absolutely no control over the
Internet unless member governments decide to give it that power. The
importance of the protests was that they prevented the US and EU
governments from agreeing to cede that power.</blockquote>
<div><br></div>
<div>Agreed.<br>
</div>
<blockquote type="cite" cite>Within the US government there are
different factions. What was important was to ensure that the
pro-control faction did not get the chance to agree to give the store
away.</blockquote>
<blockquote type="cite" cite>&nbsp;</blockquote>
<div><br></div>
<div>My model here (for better or worse) is the origin of the US
Constitution.&nbsp; The Constitution does not create a hierarchical
structure.&nbsp; The States cede parts of their sovereignty to the
Federal government. Those things better done across States, rather
than individually:&nbsp; Common currency, regulating interstate
commerce, defense, etc.&nbsp; The Federal government is<i>
alongside</i> the State governments.&nbsp; The EU is a confederation
that is doing some of these as well.&nbsp; The UN is a very weak
confederation, so the question to consider is what aspects of
*telecommunication*&nbsp; (not defense or commerce or anything else)
does it make sense that there should be international regulation (or
binding agreements)?</div>
<div><br></div>
<div>So far, my list is pretty short.&nbsp; In fact, there is wireless
spectrum and that is it.&nbsp; And even there, I would suggest only
above certain transmitter power levels.</div>
<div><br></div>
<div>Actually, I would have to apply the same criteria to the FCC.&nbsp;
;-)</div>
<div><br></div>
</body>
</html>
--============_-855033377==_ma============--

From fred@cisco.com  Tue Jan  1 21:11:38 2013
Return-Path: <fred@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6CB4821E8049 for <ietf@ietfa.amsl.com>; Tue,  1 Jan 2013 21:11:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.49
X-Spam-Level: 
X-Spam-Status: No, score=-110.49 tagged_above=-999 required=5 tests=[AWL=0.109, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
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 9Fp60SZuOhyS for <ietf@ietfa.amsl.com>; Tue,  1 Jan 2013 21:11:31 -0800 (PST)
Received: from rcdn-iport-2.cisco.com (rcdn-iport-2.cisco.com [173.37.86.73]) by ietfa.amsl.com (Postfix) with ESMTP id CB0C721E8042 for <ietf@ietf.org>; Tue,  1 Jan 2013 21:11:31 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1623; q=dns/txt; s=iport; t=1357103491; x=1358313091; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=iB5NIiVOIkcGbViKa55tcakCWiR5f84Q4DOkklKlkLA=; b=khgiFSD/4wuaH7yfzuLaXouaeShQYrJV9kumx0pK2Uo10JuFSTIbFE7J TXnami8mUFc5yweTsx0+iegrYipCMD0LCD7St+LWN+TQ+lXXptU1aug4h NWE2S3/Jeu6fx9NjTd+qeghYAxAsUSDCBX9GNZhm0Rtg8UkKfS73dBzlV 0=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AmITAC7A41CtJXG9/2dsb2JhbABFgX+7XBZzghcHAQEBAwE6PwULAgEIIhQQMiUCBA4FCIVBB4I9Bqk8jkGMcoNHYQOmVIJ0gXE1
X-IronPort-AV: E=Sophos;i="4.84,394,1355097600"; d="scan'208";a="157938150"
Received: from rcdn-core2-2.cisco.com ([173.37.113.189]) by rcdn-iport-2.cisco.com with ESMTP; 02 Jan 2013 05:11:31 +0000
Received: from xhc-aln-x14.cisco.com (xhc-aln-x14.cisco.com [173.36.12.88]) by rcdn-core2-2.cisco.com (8.14.5/8.14.5) with ESMTP id r025BVrF024779 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 2 Jan 2013 05:11:31 GMT
Received: from xmb-rcd-x09.cisco.com ([169.254.9.13]) by xhc-aln-x14.cisco.com ([173.36.12.88]) with mapi id 14.02.0318.004; Tue, 1 Jan 2013 23:11:31 -0600
From: "Fred Baker (fred)" <fred@cisco.com>
To: Alessandro Vesely <vesely@tana.it>
Subject: Re: WCIT outcome?
Thread-Topic: WCIT outcome?
Thread-Index: AQHN54FlYJCzkCTdQ0uqQOTLW/C0V5gzy5gAgAC+wwCAAKkHAIAAsW0A
Date: Wed, 2 Jan 2013 05:11:30 +0000
Message-ID: <8C48B86A895913448548E6D15DA7553B72A8D6@xmb-rcd-x09.cisco.com>
References: <CAMm+Lwh2cHRY+Dk2_SDtZZmUbPcgRpP89u3DHUcniJDrKrX_pw@mail.gmail.com> <CAMzo+1a0-90dnjnvs48a9DcNN9DY_edF5hH0__4XRuCaLHtL6Q@mail.gmail.com> <CAMm+LwjzjLc2-=4EdxwHOi21B3dOBUohYc5hhXZHL_Pk+iBBmQ@mail.gmail.com> <6.2.5.6.2.20121229192941.0aae33e8@resistor.net> <CAMm+LwiC0xtJU4vnGFPvAG4VKZdj7Tf3LfW0+pzwxKWTegRREw@mail.gmail.com> <a06240800cd074efd45b8@10.0.1.3> <CAMm+Lwiq+DCzXw572wKs78DG+XzYsJtwCVSPvNuVHSrT=Cr2nA@mail.gmail.com> <a06240809cd0799fee029@[10.0.1.3]> <50E29EE0.1080107@gmail.com> <50E32CAA.4040507@tana.it>
In-Reply-To: <50E32CAA.4040507@tana.it>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.19.64.117]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <BBD396F7310BB044A4A2F13F3D2ED378@cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "<ietf@ietf.org>" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Jan 2013 05:11:38 -0000

On Jan 1, 2013, at 10:36 AM, Alessandro Vesely <vesely@tana.it> wrote:

> Was D.1 to ease wire tapping?  By example, I, as a mail server operator
> who is not a telecom, am not required by my country's laws to provide an
> instrumentation whereby authorized investigators can obtain a list of a
> user's correspondents on the fly.  Yet that kind of data is said to be
> essential for police operations.  OTOH, SMTP doesn't consider that kind
> of facilities, and fashionable implementations don't provide them.  What
> am I missing?

In most countries, wiretap laws apply to public facilities. An enterprise m=
ail server isn't a public facility.

> Perhaps, as the old telephone system is fading away, the institutions
> that founded it --local governments' branches-- should change their
> mindset or just fade away as well...  Should the IETF or other SDOs help
> such transition?

If you want something to fade away, making a fuss about it isn't a useful a=
pproach. The IETF's practice in the past has been to improve the Internet; =
I tend to think that's as it should be.

That said, I'm also of the opinion that preventing a police force from cond=
ucting a proper criminal investigation is not a path to success. We like to=
 say that the Internet routes around brokenness; so do police forces and le=
gislative bodies. They define "brokenness" as anything that prevents them f=
rom doing their job, the same way we do. What I would far rather see is a s=
et of technical mechanisms and supporting law that facilitate legitimate cr=
iminal investigations and expose the other kind.=

From randy@psg.com  Tue Jan  1 23:02:44 2013
Return-Path: <randy@psg.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 81C2A21F9110 for <ietf@ietfa.amsl.com>; Tue,  1 Jan 2013 23:02:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.544
X-Spam-Level: 
X-Spam-Status: No, score=-2.544 tagged_above=-999 required=5 tests=[AWL=0.055,  BAYES_00=-2.599]
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 4T4+HGPjwIrG for <ietf@ietfa.amsl.com>; Tue,  1 Jan 2013 23:02:44 -0800 (PST)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by ietfa.amsl.com (Postfix) with ESMTP id 23D5D21F910C for <ietf@ietf.org>; Tue,  1 Jan 2013 23:02:44 -0800 (PST)
Received: from localhost ([127.0.0.1] helo=ryuu.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.80.1 (FreeBSD)) (envelope-from <randy@psg.com>) id 1TqILZ-000O9B-Cq; Wed, 02 Jan 2013 07:02:41 +0000
Date: Wed, 02 Jan 2013 16:02:40 +0900
Message-ID: <m2mwwsawz3.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: "Fred Baker (fred)" <fred@cisco.com>
Subject: Re: WCIT outcome?
In-Reply-To: <8C48B86A895913448548E6D15DA7553B72A8D6@xmb-rcd-x09.cisco.com>
References: <CAMm+Lwh2cHRY+Dk2_SDtZZmUbPcgRpP89u3DHUcniJDrKrX_pw@mail.gmail.com> <CAMzo+1a0-90dnjnvs48a9DcNN9DY_edF5hH0__4XRuCaLHtL6Q@mail.gmail.com> <CAMm+LwjzjLc2-=4EdxwHOi21B3dOBUohYc5hhXZHL_Pk+iBBmQ@mail.gmail.com> <6.2.5.6.2.20121229192941.0aae33e8@resistor.net> <CAMm+LwiC0xtJU4vnGFPvAG4VKZdj7Tf3LfW0+pzwxKWTegRREw@mail.gmail.com> <a06240800cd074efd45b8@10.0.1.3> <CAMm+Lwiq+DCzXw572wKs78DG+XzYsJtwCVSPvNuVHSrT=Cr2nA@mail.gmail.com> <a06240809cd0799fee029@[10.0.1.3]> <50E29EE0.1080107@gmail.com> <50E32CAA.4040507@tana.it> <8C48B86A895913448548E6D15DA7553B72A8D6@xmb-rcd-x09.cisco.com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
Cc: "<ietf@ietf.org>" <ietf@ietf.org>, Alessandro Vesely <vesely@tana.it>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Jan 2013 07:02:44 -0000

> In most countries, wiretap laws apply to public facilities.

laws do not seem to have much relation to government spying.

randy

From ndonnang@isoc-cameroon.org  Wed Jan  2 00:23:58 2013
Return-Path: <ndonnang@isoc-cameroon.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AB52C21F9014 for <ietf@ietfa.amsl.com>; Wed,  2 Jan 2013 00:23:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.148
X-Spam-Level: *
X-Spam-Status: No, score=1.148 tagged_above=-999 required=5 tests=[AWL=-0.833,  BAYES_00=-2.599, HTML_MESSAGE=0.001, IP_NOT_FRIENDLY=0.334, RCVD_IN_BL_SPAMCOP_NET=1.96, RCVD_IN_SORBS_WEB=0.619, SARE_HTML_USL_OBFU=1.666]
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 JmR6I41bjHuP for <ietf@ietfa.amsl.com>; Wed,  2 Jan 2013 00:23:57 -0800 (PST)
Received: from gateway04.websitewelcome.com (gateway04.websitewelcome.com [67.18.144.11]) by ietfa.amsl.com (Postfix) with ESMTP id 515C621F9013 for <ietf@ietf.org>; Wed,  2 Jan 2013 00:23:57 -0800 (PST)
Received: by gateway04.websitewelcome.com (Postfix, from userid 5007) id 2D5B4FEB28C4D; Wed,  2 Jan 2013 02:23:53 -0600 (CST)
Received: from pathfinder.websitewelcome.com (pathfinder.websitewelcome.com [74.54.78.50]) by gateway04.websitewelcome.com (Postfix) with ESMTP id 22326FEB28C2D for <ietf@ietf.org>; Wed,  2 Jan 2013 02:23:53 -0600 (CST)
Received: from [195.24.199.34] (port=60860 helo=[127.0.0.1]) by pathfinder.websitewelcome.com with esmtpsa (TLSv1:DHE-RSA-CAMELLIA256-SHA:256) (Exim 4.80) (envelope-from <ndonnang@isoc-cameroon.org>) id 1TqJc8-0007cw-Mt; Wed, 02 Jan 2013 02:23:56 -0600
Message-ID: <50E3EE7D.9090304@isoc-cameroon.org>
Date: Wed, 02 Jan 2013 09:23:25 +0100
From: Victor Ndonnang <ndonnang@isoc-cameroon.org>
Organization: ISOC Cameroon Chapter
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: John Day <jeanjour@comcast.net>
Subject: Re: WCIT outcome?
References: <CAMm+Lwh2cHRY+Dk2_SDtZZmUbPcgRpP89u3DHUcniJDrKrX_pw@mail.gmail.com> <CAMzo+1a0-90dnjnvs48a9DcNN9DY_edF5hH0__4XRuCaLHtL6Q@mail.gmail.com> <CAMm+LwjzjLc2-=4EdxwHOi21B3dOBUohYc5hhXZHL_Pk+iBBmQ@mail.gmail.com> <6.2.5.6.2.20121229192941.0aae33e8@resistor.net> <CAMm+LwiC0xtJU4vnGFPvAG4VKZdj7Tf3LfW0+pzwxKWTegRREw@mail.gmail.com> <a06240800cd074efd45b8@10.0.1.3> <CAMm+Lwiq+DCzXw572wKs78DG+XzYsJtwCVSPvNuVHSrT=Cr2nA@mail.gmail.com> <a06240809cd0799fee029@10.0.1.3>	<50E29EE0.1080107@gmail.com> <CAMm+LwiqXY9bJV_9Cu54Wyt6rtBeJicubm0nUe1k+ftmGxnw6w@mail.gmail.com> <a06240829cd0934717452@[10.0.1.3]>
In-Reply-To: <a06240829cd0934717452@[10.0.1.3]>
Content-Type: multipart/mixed; boundary="------------040305080804040001060009"
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - pathfinder.websitewelcome.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - isoc-cameroon.org
X-BWhitelist: no
X-Source: 
X-Source-Args: 
X-Source-Dir: 
X-Source-Sender: ([127.0.0.1]) [195.24.199.34]:60860
X-Source-Auth: ndonnang@isoc-cameroon.org
X-Email-Count: 1
X-Source-Cap: aXNvY2NhbTtuZG9ubmFuZztwYXRoZmluZGVyLndlYnNpdGV3ZWxjb21lLmNvbQ==
Cc: Phillip Hallam-Baker <hallam@gmail.com>, IETF Discussion Mailing List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: ndonnang@isoc-cameroon.org
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Jan 2013 08:23:58 -0000

This is a multi-part message in MIME format.
--------------040305080804040001060009
Content-Type: multipart/alternative;
 boundary="------------000703070506040405030801"


--------------000703070506040405030801
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Dear all,

I have been following this discussing since and I'm learning a lot. Many 
thanks to all contributors and special Thanks to
Phillip Hallam-Baker who initiated it.
Happy and Prosperous New Year 2013 to the IETF Family!
Best Regards,
Victor Ndonnang.

On 02/01/2013 02:11, John Day wrote:
> Re: WCIT outcome?
> At 7:29 PM -0500 1/1/13, Phillip Hallam-Baker wrote:
>> On Tue, Jan 1, 2013 at 3:31 AM, Brian E Carpenter 
>> <brian.e.carpenter@gmail.com <mailto:brian.e.carpenter@gmail.com>> wrote:
>>
>>     I'v been hesitating to join in here because this seems distinctly OT
>>     to me, but there are some basics that need to be understood:
>>
>>
>>     On 31/12/2012 21:08, John Day wrote:
>>     > At 1:05 PM -0500 12/31/12, Phillip Hallam-Baker wrote:
>>     >> On Mon, Dec 31, 2012 at 9:51 AM, John Day
>>
>>     >> <<mailto:jeanjour@comcast.net
>>     <mailto:jeanjour@comcast.net>>jeanjour@comcast.net
>>     <mailto:jeanjour@comcast.net>> wrote:
>>
>>     ...
>>
>>     >> MPs and Congressmen are elected decision makers. ITU
>>     participants can
>>     >> make decisions but they are not binding on anyone and only
>>     have effect
>>     >> if people like me choose to implement them.
>>     >
>>     > This was my point. The standards part of ITU is just like any other
>>     > standards organization. But there are other things it does
>>     which are not
>>     > like this, e.g. spectrum allocation.  There are other aspects with
>>     > respect to tariffs that are binding on signatories.
>>
>>     Not only tariffs. Historically, it was national enforcement of
>>     international
>>     regulations set by CCITT (now known as ITU-T) that prevented
>>     interconnection
>>     of leased lines**. This is an arcane point today, but if CERN
>>     hadn't been
>>     able to use its status as an international organization to bypass
>>     that
>>     restriction in the 1980s, it's unlikely that TBL and Robert
>>     Cailliau would
>>     ever have been able to propagate the web. It's even unlikely that
>>     Phill
>>     would have been able to access Usenet newsgroups while on shift
>>     as a grad
>>     student on a CERN experiment.
>>
>>
>> I was never a grad student at CERN, I was a CERN Fellow. And I had 
>> access to USENET from DESY but we were routing it through CERN at first.
>>
>> Now it is an interesting question as to what might have happened if 
>> the Web had not expanded as it did when it did. But one of the 
>> reasons that it expanded was that there were a lot of parties 
>> involved who were actively wanting to blow up the CITT tariffs and 
>> establish a free market. That was HMG policy at any rate.
>>
>
> I have heard tell (dropping into the vernacular) that to many, the web 
> was just another application like Gopher until NCSA put a browser on 
> it.  The question is what would have happened had they put the browser 
> on top of something else?
>
>>
>>     Also, it is exactly because ITU was in charge of resource allocations
>>     such as radio spectrum and top-level POTS dialling codes that it was
>>     a very plausible potential home for IANA in 1997-8, before ICANN was
>>     created. Some of the ITU people who were active in that debate
>>     were just
>>     as active in the preparation for WCIT in 2012.
>>
>>
>> When the big question facing DNS admin was legal liability in the 
>> various domain name disputes that were proliferating, having a treaty 
>> organization with diplomatic immunity actually had some advantages.
>
> Agreed but the treaty organization was the WTO and another one I can't 
> remember right now! ;-)  As long as the problem was punted to them one 
> was okay.  I just don't see how ITU has purview over *uses* of the 
> network. (Nor am I willing to easily cede that.)
>
> This is why it is not a good idea to go along with the ITU 
> beads-on-a-string model.  By doing so, it already clouds the picture 
> and gives up ground.
>
>>
>> But that was a very different time diplomatically. That was before 
>> Putin was ordering assassinations on the streets of London with 
>> Polonium laced teapots and before the colour revolutions rolled back 
>> the Russian sphere of influence. And our side was hardly blameless, 
>> it was the US invasion of Iraq that poisoned the well in the first place.
>>
>
> True, but what effect does this have?  The US did burn up a lot of 
> good will for no good reason and then botched the job on top of it.
>
>>
>>     ** CCITT document D.1. The 1988 version includes the restrictions on
>>     use of leased lines:
>>
>>     http://www.itu.int/rec/dologin_pub.asp?lang=e&id=T-REC-D.1-198811-S!!PDF-E&type=items
>>     <http://www.itu.int/rec/dologin_pub.asp?lang=e&id=T-REC-D.1-198811-S%21%21PDF-E&type=items>
>>
>>
>>     The 1991 version is much less restrictive, but it remains the
>>     case that
>>     interconnections are all "subject to national laws" and that is
>>     the basis
>>     for all national limitations on the Internet today. Nevertheless,
>>     the 1991
>>     revision of D.1 was absolutely essential for the Internet to grow
>>     internationally.
>>
>>
>> The idea of fixing the contract terms in an international treaty is 
>> utterly bizarre.
>>
>>
>>     It would be foolish to imagine that the Internet is in some way
>>     immune
>>     to ITU-T regulations, which is why the effort to defeat the more
>>     radical
>>     WCIT proposals was so important.
>>
>>
>> While technically true, I think your wording is misleading.
>
> Why is this technically true?  Honest question.
>
>>
>> ITU-T has absolutely no control over the Internet unless member 
>> governments decide to give it that power. The importance of the 
>> protests was that they prevented the US and EU governments from 
>> agreeing to cede that power.
>
> Agreed.
>> Within the US government there are different factions. What was 
>> important was to ensure that the pro-control faction did not get the 
>> chance to agree to give the store away.
>
> My model here (for better or worse) is the origin of the US 
> Constitution.  The Constitution does not create a hierarchical 
> structure.  The States cede parts of their sovereignty to the Federal 
> government. Those things better done across States, rather than 
> individually:  Common currency, regulating interstate commerce, 
> defense, etc.  The Federal government is/alongside/ the State 
> governments.  The EU is a confederation that is doing some of these as 
> well.  The UN is a very weak confederation, so the question to 
> consider is what aspects of *telecommunication*  (not defense or 
> commerce or anything else) does it make sense that there should be 
> international regulation (or binding agreements)?
>
> So far, my list is pretty short.  In fact, there is wireless spectrum 
> and that is it.  And even there, I would suggest only above certain 
> transmitter power levels.
>
> Actually, I would have to apply the same criteria to the FCC. ;-)
>


--------------000703070506040405030801
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <font face="Helvetica, Arial, sans-serif">Dear all,<br>
      <br>
      I have been following this discussing since and I'm learning a
      lot. Many thanks to all contributors and special Thanks to </font><br>
    Phillip Hallam-Baker who initiated it.<br>
    Happy and Prosperous New Year 2013 to the IETF Family!<br>
    Best Regards,<br>
    Victor Ndonnang.<br>
    <br>
    <div class="moz-cite-prefix">On 02/01/2013 02:11, John Day wrote:<br>
    </div>
    <blockquote cite="mid:a06240829cd0934717452@%5B10.0.1.3%5D"
      type="cite">
      <style type="text/css"><!--
blockquote, dl, ul, ol, li { padding-top: 0 ; padding-bottom: 0 }
 --></style>
      <title>Re: WCIT outcome?</title>
      <div>At 7:29 PM -0500 1/1/13, Phillip Hallam-Baker wrote:</div>
      <blockquote type="cite" cite="">On Tue, Jan 1, 2013 at 3:31 AM,
        Brian E
        Carpenter &lt;<a moz-do-not-send="true"
          href="mailto:brian.e.carpenter@gmail.com">brian.e.carpenter@gmail.com</a>&gt;
        wrote:<br>
        <blockquote>I'v been hesitating to join in here because this
          seems
          distinctly OT<br>
          to me, but there are some basics that need to be understood:<br>
        </blockquote>
        <blockquote><br>
          On 31/12/2012 21:08, John Day wrote:<br>
          &gt; At 1:05 PM -0500 12/31/12, Phillip Hallam-Baker wrote:<br>
          &gt;&gt; On Mon, Dec 31, 2012 at 9:51 AM, John Day<br>
        </blockquote>
        <blockquote>&gt;&gt; &lt;&lt;mailto:<a moz-do-not-send="true"
            href="mailto:jeanjour@comcast.net">jeanjour@comcast.net</a>&gt;<a
            moz-do-not-send="true" href="mailto:jeanjour@comcast.net">jeanjour@comcast.net</a>&gt;
          wrote:<br>
          <br>
          ...<br>
        </blockquote>
        <blockquote>&gt;&gt; MPs and Congressmen are elected decision
          makers.
          ITU participants can<br>
          &gt;&gt; make decisions but they are not binding on anyone and
          only
          have effect<br>
          &gt;&gt; if people like me choose to implement them.<br>
          &gt;<br>
          &gt; This was my point. The standards part of ITU is just like
          any
          other<br>
          &gt; standards organization. But there are other things it
          does which
          are not<br>
          &gt; like this, e.g. spectrum allocation. &nbsp;There are other
          aspects with<br>
          &gt; respect to tariffs that are binding on signatories.<br>
        </blockquote>
        <blockquote>Not only tariffs. Historically, it was national
          enforcement of international<br>
          regulations set by CCITT (now known as ITU-T) that prevented
          interconnection<br>
          of leased lines**. This is an arcane point today, but if CERN
          hadn't
          been<br>
          able to use its status as an international organization to
          bypass
          that<br>
          restriction in the 1980s, it's unlikely that TBL and Robert
          Cailliau
          would<br>
          ever have been able to propagate the web. It's even unlikely
          that
          Phill<br>
          would have been able to access Usenet newsgroups while on
          shift as a
          grad<br>
          student on a CERN experiment.<br>
        </blockquote>
      </blockquote>
      <blockquote type="cite" cite=""><br>
      </blockquote>
      <blockquote type="cite" cite="">I was never a grad student at
        CERN, I was
        a CERN Fellow.&nbsp;And I had access to USENET from DESY but we were
        routing it through CERN at first.</blockquote>
      <blockquote type="cite" cite=""><br>
      </blockquote>
      <blockquote type="cite" cite="">Now it is an interesting question
        as to
        what might have happened if the Web had not expanded as it did
        when it
        did. But one of the reasons that it expanded was that there were
        a lot
        of parties involved who were actively wanting to blow up the
        CITT
        tariffs and establish a free market. That was HMG policy at any
        rate.</blockquote>
      <blockquote type="cite" cite=""><br>
      </blockquote>
      <blockquote type="cite" cite="">&nbsp;</blockquote>
      <div><br>
      </div>
      <div>I have heard tell (dropping into the vernacular) that to
        many,
        the web was just another application like Gopher until NCSA put
        a
        browser on it.&nbsp; The question is what would have happened had
        they
        put the browser on top of something else?</div>
      <div><br>
      </div>
      <blockquote type="cite" cite=""><br>
        <blockquote>Also, it is exactly because ITU was in charge of
          resource
          allocations<br>
          such as radio spectrum and top-level POTS dialling codes that
          it
          was<br>
          a very plausible potential home for IANA in 1997-8, before
          ICANN
          was<br>
          created. Some of the ITU people who were active in that debate
          were
          just<br>
          as active in the preparation for WCIT in 2012.<br>
        </blockquote>
      </blockquote>
      <blockquote type="cite" cite=""><br>
      </blockquote>
      <blockquote type="cite" cite="">When the big question facing DNS
        admin
        was legal liability in the various domain name disputes that
        were
        proliferating, having a treaty organization with diplomatic
        immunity
        actually had some advantages.</blockquote>
      <div><br>
      </div>
      <div>Agreed but the treaty organization was the WTO and another
        one I
        can't remember right now! ;-)&nbsp; As long as the problem was punted
        to them one was okay.&nbsp; I just don't see how ITU has purview over
        *uses* of the network. (Nor am I willing to easily cede that.)</div>
      <div><br>
      </div>
      <div>This is why it is not a good idea to go along with the ITU
        beads-on-a-string model.&nbsp; By doing so, it already clouds the
        picture and gives up ground.</div>
      <div><br>
      </div>
      <blockquote type="cite" cite=""><br>
      </blockquote>
      <blockquote type="cite" cite="">But that was a very different time
        diplomatically. That was before Putin was ordering
        assassinations on
        the streets of London with Polonium laced teapots and before the
        colour revolutions rolled back the Russian sphere of influence.
        And
        our side was hardly blameless, it was the US invasion of Iraq
        that
        poisoned the well in the first place.</blockquote>
      <blockquote type="cite" cite=""><br>
      </blockquote>
      <blockquote type="cite" cite="">&nbsp;</blockquote>
      <div><br>
      </div>
      <div>True, but what effect does this have?&nbsp; The US did burn up a
        lot of good will for no good reason and then botched the job on
        top of
        it.</div>
      <div><br>
      </div>
      <blockquote type="cite" cite=""><br>
        <blockquote>** CCITT document D.1. The 1988 version includes the
          restrictions on<br>
          use of leased lines:</blockquote>
        <blockquote><a moz-do-not-send="true"
href="http://www.itu.int/rec/dologin_pub.asp?lang=e&amp;id=T-REC-D.1-198811-S%21%21PDF-E&amp;type=items"><span></span>http://www.itu.int/rec/dologin_pub.asp?lang=e&amp;id=T-REC-D.1-19881<span></span>1-S!!PDF-E&amp;type=items</a></blockquote>
        <blockquote><br>
          The 1991 version is much less restrictive, but it remains the
          case
          that<br>
          interconnections are all "subject to national laws" and that
          is the basis<br>
          for all national limitations on the Internet today.
          Nevertheless, the
          1991<br>
          revision of D.1 was absolutely essential for the Internet to
          grow<br>
          internationally.<br>
        </blockquote>
      </blockquote>
      <blockquote type="cite" cite=""><br>
      </blockquote>
      <blockquote type="cite" cite="">The idea of fixing the contract
        terms in
        an international treaty is utterly bizarre.</blockquote>
      <blockquote type="cite" cite=""><br>
      </blockquote>
      <blockquote type="cite" cite="">&nbsp;<br>
        <blockquote>It would be foolish to imagine that the Internet is
          in
          some way immune<br>
          to ITU-T regulations, which is why the effort to defeat the
          more
          radical<br>
          WCIT proposals was so important.<br>
        </blockquote>
      </blockquote>
      <blockquote type="cite" cite=""><br>
      </blockquote>
      <blockquote type="cite" cite="">While technically true, I think
        your
        wording is misleading.</blockquote>
      <div><br>
      </div>
      <div>Why is this technically true?&nbsp; Honest question.</div>
      <div><br>
      </div>
      <blockquote type="cite" cite=""><br>
      </blockquote>
      <blockquote type="cite" cite="">ITU-T has absolutely no control
        over the
        Internet unless member governments decide to give it that power.
        The
        importance of the protests was that they prevented the US and EU
        governments from agreeing to cede that power.</blockquote>
      <div><br>
      </div>
      <div>Agreed.<br>
      </div>
      <blockquote type="cite" cite="">Within the US government there are
        different factions. What was important was to ensure that the
        pro-control faction did not get the chance to agree to give the
        store
        away.</blockquote>
      <blockquote type="cite" cite="">&nbsp;</blockquote>
      <div><br>
      </div>
      <div>My model here (for better or worse) is the origin of the US
        Constitution.&nbsp; The Constitution does not create a hierarchical
        structure.&nbsp; The States cede parts of their sovereignty to the
        Federal government. Those things better done across States,
        rather
        than individually:&nbsp; Common currency, regulating interstate
        commerce, defense, etc.&nbsp; The Federal government is<i>
          alongside</i> the State governments.&nbsp; The EU is a
        confederation
        that is doing some of these as well.&nbsp; The UN is a very weak
        confederation, so the question to consider is what aspects of
        *telecommunication*&nbsp; (not defense or commerce or anything else)
        does it make sense that there should be international regulation
        (or
        binding agreements)?</div>
      <div><br>
      </div>
      <div>So far, my list is pretty short.&nbsp; In fact, there is wireless
        spectrum and that is it.&nbsp; And even there, I would suggest only
        above certain transmitter power levels.</div>
      <div><br>
      </div>
      <div>Actually, I would have to apply the same criteria to the
        FCC.&nbsp;
        ;-)</div>
      <div><br>
      </div>
    </blockquote>
    <br>
  </body>
</html>

--------------000703070506040405030801--

--------------040305080804040001060009
Content-Type: text/x-vcard; charset=utf-8;
 name="ndonnang.vcf"
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
 filename="ndonnang.vcf"

begin:vcard
fn:Victor Ndonnang
n:Ndonnang;Victor
org:ISOC Cameroon Chapter
adr:;;;Yaounde;;B.P. 8149;Cameroon
email;internet:ndonnang@isoc-cameroon.org
title:Secretary General
tel;cell:+237 77750724
url:www.isoc.cm
version:2.1
end:vcard


--------------040305080804040001060009--

From brian.e.carpenter@gmail.com  Wed Jan  2 01:03:23 2013
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 074F521F9082 for <ietf@ietfa.amsl.com>; Wed,  2 Jan 2013 01:03:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.588
X-Spam-Level: 
X-Spam-Status: No, score=-101.588 tagged_above=-999 required=5 tests=[AWL=0.103, BAYES_00=-2.599, RCVD_ILLEGAL_IP=1.908, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
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 SnPZLL3ppYFW for <ietf@ietfa.amsl.com>; Wed,  2 Jan 2013 01:03:22 -0800 (PST)
Received: from mail-wg0-f52.google.com (mail-wg0-f52.google.com [74.125.82.52]) by ietfa.amsl.com (Postfix) with ESMTP id 3CA0121F907F for <ietf@ietf.org>; Wed,  2 Jan 2013 01:03:16 -0800 (PST)
Received: by mail-wg0-f52.google.com with SMTP id 12so6258173wgh.31 for <ietf@ietf.org>; Wed, 02 Jan 2013 01:03:15 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:organization:user-agent :mime-version:to:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=EeT7l21CGnjfQkhFDVwficqrGSunHcB9F52jBnfpvo8=; b=PyFDrxru0fAHfMn4GoBgAwoM3C/kIVZwyuYm5sqLbcldldJPo2YOSotRsjCkHqmBS+ nHRRV/wQ970DeGbHmEoxqz53MuON4wCGclmLeMKHhMBfmTALAPAhWdKVKjfmMQvK/gcl zS2veRr0NYaNQdlPxLEmmaS4Ql7dVM0oHQiyc+gj6uL7mzDy3LRtk9+mZKnVug0i2ZRw vn4n2TH58A+YE34q5IMhPoRBpJm2dDNMSE3JbpnWIm87A2rsbsS7h0ARI75PeGLgONZC 1TGfyKXDfWCtcoGpxasGrfhCP8fNz/27mJE/GxU1g3Kg5/Xs/w82GeQy5FU49H5R9m/B 0OpA==
X-Received: by 10.194.76.137 with SMTP id k9mr71938210wjw.29.1357117395118; Wed, 02 Jan 2013 01:03:15 -0800 (PST)
Received: from [192.168.1.65] (host-2-102-216-139.as13285.net. [2.102.216.139]) by mx.google.com with ESMTPS id eo10sm79331944wib.9.2013.01.02.01.03.13 (version=SSLv3 cipher=OTHER); Wed, 02 Jan 2013 01:03:14 -0800 (PST)
Message-ID: <50E3F7EE.6000402@gmail.com>
Date: Wed, 02 Jan 2013 09:03:42 +0000
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: IETF Discussion Mailing List <ietf@ietf.org>
Subject: Re: WCIT outcome?
References: <CAMm+Lwh2cHRY+Dk2_SDtZZmUbPcgRpP89u3DHUcniJDrKrX_pw@mail.gmail.com> <CAMzo+1a0-90dnjnvs48a9DcNN9DY_edF5hH0__4XRuCaLHtL6Q@mail.gmail.com> <CAMm+LwjzjLc2-=4EdxwHOi21B3dOBUohYc5hhXZHL_Pk+iBBmQ@mail.gmail.com> <6.2.5.6.2.20121229192941.0aae33e8@resistor.net> <CAMm+LwiC0xtJU4vnGFPvAG4VKZdj7Tf3LfW0+pzwxKWTegRREw@mail.gmail.com> <a06240800cd074efd45b8@10.0.1.3> <CAMm+Lwiq+DCzXw572wKs78DG+XzYsJtwCVSPvNuVHSrT=Cr2nA@mail.gmail.com> <a06240809cd0799fee029@[10.0.1.3]> <50E29EE0.1080107@gmail.com> <a06240815cd08da399dc6@[10.0.1.3]>
In-Reply-To: <a06240815cd08da399dc6@[10.0.1.3]>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Jan 2013 09:03:23 -0000

On 01/01/2013 18:32, John Day wrote:
...

>> Not only tariffs. Historically, it was national enforcement of
>> international
>> regulations set by CCITT (now known as ITU-T) that prevented
>> interconnection
>> of leased lines**.
> 
> But creating a VPN with in an international carrier that crossed
> national boundaries would not fall under that rule?  Actually neither
> would a VPN operating over a couple of carriers that crossed national
> boundaries, would it?

That depended on how the various national monopolists chose to
interpret the rules. In Switzerland we were particularly affected
by the fact that the PTT monopoly was a specific line item in the
federal Constitution. In the US, you had the benefit of Judge Greene.

>> This is an arcane point today, but if CERN hadn't been
>> able to use its status as an international organization to bypass that
>> restriction in the 1980s, it's unlikely that TBL and Robert Cailliau
>> would
>> ever have been able to propagate the web. It's even unlikely that Phill
>> would have been able to access Usenet newsgroups while on shift as a grad
>> student on a CERN experiment.
> 
> ;-) Actually what they don't know won't hurt them.  ;-) We were moving
> files from CERN to Argonne in the 70s through the 360/95 at Rutherford
> over the ARPANET.   Not exactly the way you want to do it but 15 years
> later I am sure it was upgraded a bit.

This would probably have counted as a store-and-forward network,
which was exempted in many countries.

>> Also, it is exactly because ITU was in charge of resource allocations
>> such as radio spectrum and top-level POTS dialling codes that it was
>> a very plausible potential home for IANA in 1997-8, before ICANN was
>> created. Some of the ITU people who were active in that debate were just
>> as active in the preparation for WCIT in 2012.
> 
> Yea, this one is more dicey.  Although I think there is an argument that
> says that you need ccoperation among providers about assignment, but I
> don't see why governments need to be involved.  When phone companies
> were owned by governments, then it made sense.  But phone companies are
> owned by governments any more.
> 
> That doesn't leave much does it?  (Not a facetious question, I am asking!)

Indeed. But I think you'll find that in general, the countries that signed
the WCIT treaty are those that still have some semblance of a government-
controlled PTT monopoly.

On 01/01/2013 18:36, Alessandro Vesely wrote:

> Was D.1 to ease wire tapping?

No. It was all about preserving the lucrative PTT monopolies.

On 01/01/2013 22:13, Jaap Akkerhuis wrote:

> In the early eigthies, after consulting with the telecom authorithy
> in the Netherlands we got the green light to move data for third
> parties, and thus the (then uucp based) EUnet was born.

Exactly, and EARN (European BITNET) was just the same.

> The green
> light was given in the anticipation of the libiralization of the
> EU telcom market. 

Exactly, and the 1988 revision of regulation D.1 was closely related
to the general move toward telecom liberalization.

As I said - this stuff *matters* for the Internet (both historically
and for the future).

    Brian

From sm@resistor.net  Wed Jan  2 04:34:18 2013
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CEE8021F90BF for <ietf@ietfa.amsl.com>; Wed,  2 Jan 2013 04:34:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.615
X-Spam-Level: 
X-Spam-Status: No, score=-102.615 tagged_above=-999 required=5 tests=[AWL=-0.016, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 AXL4G6-klzsx for <ietf@ietfa.amsl.com>; Wed,  2 Jan 2013 04:34:18 -0800 (PST)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 30ED321F903D for <ietf@ietf.org>; Wed,  2 Jan 2013 04:34:18 -0800 (PST)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r02CY62W018728; Wed, 2 Jan 2013 04:34:10 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1357130053; bh=0vZIGB/iPiZfMywdmXbuy85cc/NmqrWPVNHzNHrBDYA=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=kGwDlMuHIPbUrtxOvCwpK3p0F09ix+vUVdJUhedFaw2qv+KN9ttKu1OYgqp6CJ94h duvV9uOiLQ29xd9Q2EERzOBFIkfuQvUt1QOt4Lr1q7UQQseohqP9qin3DciaL2CxUz rkuxfGySxYmuRv2tbt2aJkUKcPxsFvwk7BYwS4FE=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1357130053; i=@resistor.net; bh=0vZIGB/iPiZfMywdmXbuy85cc/NmqrWPVNHzNHrBDYA=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=yLjCx7GVALFtm5h26+XkI0HMWTGlDrC4TeioflytPFdDUM7z9iU5ImJeXzJxnFQVQ JkeHbDb3MlaqJC0iutjLqyRmxRc5WA5G2g3JurKyzYLecX/2iA7EINsaY6DaG+gtCQ PCvxZrhEeBwDXi+zGy0FUJVizNwPFMAUUzfnHSxs=
Message-Id: <6.2.5.6.2.20130102023406.0b4b7d68@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Wed, 02 Jan 2013 04:33:26 -0800
To: John Day <jeanjour@comcast.net>, Phillip Hallam-Baker <hallam@gmail.com>
From: SM <sm@resistor.net>
Subject: Re: WCIT outcome?
In-Reply-To: <a06240809cd0799fee029@[10.0.1.3]>
References: <CAMm+Lwh2cHRY+Dk2_SDtZZmUbPcgRpP89u3DHUcniJDrKrX_pw@mail.gmail.com> <CAMzo+1a0-90dnjnvs48a9DcNN9DY_edF5hH0__4XRuCaLHtL6Q@mail.gmail.com> <CAMm+LwjzjLc2-=4EdxwHOi21B3dOBUohYc5hhXZHL_Pk+iBBmQ@mail.gmail.com> <6.2.5.6.2.20121229192941.0aae33e8@resistor.net> <CAMm+LwiC0xtJU4vnGFPvAG4VKZdj7Tf3LfW0+pzwxKWTegRREw@mail.gmail.com> <a06240800cd074efd45b8@10.0.1.3> <CAMm+Lwiq+DCzXw572wKs78DG+XzYsJtwCVSPvNuVHSrT=Cr2nA@mail.gmail.com> <a06240809cd0799fee029@[10.0.1.3]>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: IETF Discussion Mailing List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Jan 2013 12:34:18 -0000

At 13:08 31-12-2012, John Day wrote:
>jumped all over.  Generally, ITU meetings require unanimity to have 
>a consensus.  This

There seems to be different definitions of consensus; each body has 
its own meaning for that word.

>;-)  Why is that daunting?  ;-)  I hear that excuse often.  If we 
>had had that attitude when we started this effort 40 years ago.  We 
>would still be patching the PSTN.  There would be no Internet. Do 
>you think the Internet was a success because we convinced IBM and 
>AT&T it was a good idea?!!  I am sorry to see that the younger 
>generation is so faint of heart.  Can't take a little challenge!

Nowadays it is called being pragmatic.  The little challenge might be 
taking on the legacy.  I wonder how many fairy tales are part of the 
legacy. :-)

At 16:29 01-01-2013, Phillip Hallam-Baker wrote:
>ITU-T has absolutely no control over the Internet unless member 
>governments decide to give it that power. The importance of the 
>protests was that they prevented the US and EU governments from 
>agreeing to cede that power.

That might explain the the press releases about the WCIT discussions.

At 17:11 01-01-2013, John Day wrote:
>doing some of these as well.  The UN is a very weak confederation, 
>so the question to consider is what aspects of 
>*telecommunication*  (not defense or commerce or anything else) does 
>it make sense that there should be international regulation (or 
>binding agreements)?

Y.2001 covers topics which affect commerce (I am ignoring other 
angles).  There is leeway for expanding the scope beyond a narrow 
definition of telecommunication.  Everybody will lobby for their pet 
project as there is an opportunity to do so.

Regards,
-sm 


From jeanjour@comcast.net  Wed Jan  2 04:38:53 2013
Return-Path: <jeanjour@comcast.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 57E4C21F90C7 for <ietf@ietfa.amsl.com>; Wed,  2 Jan 2013 04:38:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.424
X-Spam-Level: 
X-Spam-Status: No, score=-100.424 tagged_above=-999 required=5 tests=[AWL=0.013, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_NET=0.611, RDNS_NONE=0.1, USER_IN_WHITELIST=-100]
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 juY4qKsQnjJW for <ietf@ietfa.amsl.com>; Wed,  2 Jan 2013 04:38:52 -0800 (PST)
Received: from qmta05.westchester.pa.mail.comcast.net (qmta05.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:43:76:96:62:48]) by ietfa.amsl.com (Postfix) with ESMTP id 99B9D21F90BF for <ietf@ietf.org>; Wed,  2 Jan 2013 04:38:52 -0800 (PST)
Received: from omta22.westchester.pa.mail.comcast.net ([76.96.62.73]) by qmta05.westchester.pa.mail.comcast.net with comcast id j0bW1k0071ap0As550esPc; Wed, 02 Jan 2013 12:38:52 +0000
Received: from [10.0.1.3] ([98.229.211.49]) by omta22.westchester.pa.mail.comcast.net with comcast id j0er1k00E14WE023i0er5S; Wed, 02 Jan 2013 12:38:52 +0000
Mime-Version: 1.0
Message-Id: <a0624082ecd09d7719b9e@[10.0.1.3]>
In-Reply-To: <50E3F7EE.6000402@gmail.com>
References: <CAMm+Lwh2cHRY+Dk2_SDtZZmUbPcgRpP89u3DHUcniJDrKrX_pw@mail.gmail.com> <CAMzo+1a0-90dnjnvs48a9DcNN9DY_edF5hH0__4XRuCaLHtL6Q@mail.gmail.com> <CAMm+LwjzjLc2-=4EdxwHOi21B3dOBUohYc5hhXZHL_Pk+iBBmQ@mail.gmail.com> <6.2.5.6.2.20121229192941.0aae33e8@resistor.net> <CAMm+LwiC0xtJU4vnGFPvAG4VKZdj7Tf3LfW0+pzwxKWTegRREw@mail.gmail.com> <a06240800cd074efd45b8@10.0.1.3> <CAMm+Lwiq+DCzXw572wKs78DG+XzYsJtwCVSPvNuVHSrT=Cr2nA@mail.gmail.com> <a06240809cd0799fee029@[10.0.1.3]> <50E29EE0.1080107@gmail.com> <a06240815cd08da399dc6@[10.0.1.3]> <50E3F7EE.6000402@gmail.com>
Date: Wed, 2 Jan 2013 07:36:18 -0500
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, IETF Discussion Mailing List <ietf@ietf.org>
From: John Day <jeanjour@comcast.net>
Subject: Re: WCIT outcome?
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20121106; t=1357130332; bh=QN+IMweSsu0fxG9U1/YncaJUDelLleBeBXpchIodVwQ=; h=Received:Received:Mime-Version:Message-Id:Date:To:From:Subject: Content-Type; b=TwwgmDExMC5W85NobMZSQ1MIQFspLtprrLLFOHpyCpsFGqVkQBRb+WKLmMlxovgWG Iu/VYUmvSnGMoSGq5xEUUbtmQZwU7BEf3ZOxOKQAUPvkDaups1N4eAgodBCBox6TWZ ORcJe3LNYoRCzwjMkdvoS+3g0pMYlTNudA3Qf0YIbKpMtDishAnHapMN9wDcS3PjH6 VUlNtlPUrIwixery7k9XVulp20faPWhU61glZkUG8y/fX9T6DWTZ3+yalGobDY9KWx xrP+D8fyLSHYb3ScSBMvB0qxhqxh1/Aie59ZFK6o0YLy3jPrTwF6jeTzwC+SU8RHwH FNVDdTLp4oytg==
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Jan 2013 12:38:53 -0000

At 9:03 AM +0000 1/2/13, Brian E Carpenter wrote:
>On 01/01/2013 18:32, John Day wrote:
>...
>
>>>  Not only tariffs. Historically, it was national enforcement of
>>>  international
>>>  regulations set by CCITT (now known as ITU-T) that prevented
>>>  interconnection
>>>  of leased lines**.
>>
>>  But creating a VPN with in an international carrier that crossed
>>  national boundaries would not fall under that rule?  Actually neither
>>  would a VPN operating over a couple of carriers that crossed national
>>  boundaries, would it?
>
>That depended on how the various national monopolists chose to
>interpret the rules. In Switzerland we were particularly affected
>by the fact that the PTT monopoly was a specific line item in the
>federal Constitution. In the US, you had the benefit of Judge Greene.

I could see it being viewed as commerce and subject to tariffs.  (Not 
that I think tariffs are a good idea.)

>
>>>  This is an arcane point today, but if CERN hadn't been
>>>  able to use its status as an international organization to bypass that
>>>  restriction in the 1980s, it's unlikely that TBL and Robert Cailliau
>>>  would
>>>  ever have been able to propagate the web. It's even unlikely that Phill
>>>  would have been able to access Usenet newsgroups while on shift as a grad
>>>  student on a CERN experiment.
>>
>>  ;-) Actually what they don't know won't hurt them.  ;-) We were moving
>>  files from CERN to Argonne in the 70s through the 360/95 at Rutherford
>>  over the ARPANET.   Not exactly the way you want to do it but 15 years
>>  later I am sure it was upgraded a bit.
>
>This would probably have counted as a store-and-forward network,
>which was exempted in many countries.

;-)  I of course was joking. But I remember being told that it was 
illegal, or maybe it was that no one was sure (we were all pretty new 
to this stuff back then) and figured asking was not a good idea!  ;-)

(In several reports at the time, our node was the highest user of the 
Rutherford, probably of nodes on the net at the time.)

>
>>>  Also, it is exactly because ITU was in charge of resource allocations
>>>  such as radio spectrum and top-level POTS dialling codes that it was
>>>  a very plausible potential home for IANA in 1997-8, before ICANN was
>>>  created. Some of the ITU people who were active in that debate were just
>>>  as active in the preparation for WCIT in 2012.
>>
>>  Yea, this one is more dicey.  Although I think there is an argument that
>>  says that you need ccoperation among providers about assignment, but I
>>  don't see why governments need to be involved.  When phone companies
>>  were owned by governments, then it made sense.  But phone companies are
>>  owned by governments any more.
>>
>>  That doesn't leave much does it?  (Not a facetious question, I am asking!)
>
>Indeed. But I think you'll find that in general, the countries that signed
>the WCIT treaty are those that still have some semblance of a government-
>controlled PTT monopoly.

I was wondering about that and guessing that it might be the case. 
Thanks for the data.

Also, I would agree with Fred's comment on helping the police. 
Although as we all know that can be hard call and one has to hope 
that the proper controls are on them as well.  The problem as I see 
it is that it is not a good idea to try to constrain a new technology 
to behave like the old technology.  It is the capability they want it 
shouldn't imply how.

Of course, the other problem which really wasn't present before (just 
because of cost and/or availability) is that if the user chooses to 
encrypt everything they send, the network provider can provide the 
data but that  is it.

From jeanjour@comcast.net  Wed Jan  2 05:18:53 2013
Return-Path: <jeanjour@comcast.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2A4CC21F8D44 for <ietf@ietfa.amsl.com>; Wed,  2 Jan 2013 05:18:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.426
X-Spam-Level: 
X-Spam-Status: No, score=-100.426 tagged_above=-999 required=5 tests=[AWL=0.011, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_NET=0.611, RDNS_NONE=0.1, USER_IN_WHITELIST=-100]
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 3j2HEFiTI7hE for <ietf@ietfa.amsl.com>; Wed,  2 Jan 2013 05:18:52 -0800 (PST)
Received: from qmta03.westchester.pa.mail.comcast.net (qmta03.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:43:76:96:62:32]) by ietfa.amsl.com (Postfix) with ESMTP id 3203621F9063 for <ietf@ietf.org>; Wed,  2 Jan 2013 05:18:52 -0800 (PST)
Received: from omta02.westchester.pa.mail.comcast.net ([76.96.62.19]) by qmta03.westchester.pa.mail.comcast.net with comcast id j05S1k0030QuhwU531JrBC; Wed, 02 Jan 2013 13:18:51 +0000
Received: from [10.0.1.3] ([98.229.211.49]) by omta02.westchester.pa.mail.comcast.net with comcast id j1Jq1k00l14WE023N1JrNx; Wed, 02 Jan 2013 13:18:51 +0000
Mime-Version: 1.0
Message-Id: <a0624082fcd09e07ab9c8@[10.0.1.3]>
In-Reply-To: <6.2.5.6.2.20130102023406.0b4b7d68@resistor.net>
References: <CAMm+Lwh2cHRY+Dk2_SDtZZmUbPcgRpP89u3DHUcniJDrKrX_pw@mail.gmail.com> <CAMzo+1a0-90dnjnvs48a9DcNN9DY_edF5hH0__4XRuCaLHtL6Q@mail.gmail.com> <CAMm+LwjzjLc2-=4EdxwHOi21B3dOBUohYc5hhXZHL_Pk+iBBmQ@mail.gmail.com> <6.2.5.6.2.20121229192941.0aae33e8@resistor.net> <CAMm+LwiC0xtJU4vnGFPvAG4VKZdj7Tf3LfW0+pzwxKWTegRREw@mail.gmail.com> <a06240800cd074efd45b8@10.0.1.3> <CAMm+Lwiq+DCzXw572wKs78DG+XzYsJtwCVSPvNuVHSrT=Cr2nA@mail.gmail.com> <a06240809cd0799fee029@[10.0.1.3]> <6.2.5.6.2.20130102023406.0b4b7d68@resistor.net>
Date: Wed, 2 Jan 2013 08:11:35 -0500
To: SM <sm@resistor.net>, John Day <jeanjour@comcast.net>, Phillip Hallam-Baker <hallam@gmail.com>
From: John Day <jeanjour@comcast.net>
Subject: Re: WCIT outcome?
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20121106; t=1357132731; bh=hN7FU1h0O0VtjzlSiyRKAYZM+BPWOA4iONPXDg/AK34=; h=Received:Received:Mime-Version:Message-Id:Date:To:From:Subject: Content-Type; b=It0TCRIakfj4yGOdpv76s3kRHj+6duj4glg16p7J8x/tPzKvaCIpscWarUp4ONsYs t/9o9KkNGfs2PU2i2X/wWtP6Iomtbeir4tPCaUH/u6pqpTd1rYgaTt7RiciFbdDUpM HonNDvs0mADv7rsan5gD3RQF41LVIFbPUvSmRUus91Svvuea1VohRS77lmRYUBIcun eR0z9g6jqbIPZ+UI/Oyaf9n+16Ex4zr+5xVL5oYcOPpZf9eHUeIgusnDBMbARqiBid u46ssUTMB6geU0W7cwO39yGnBoEXWJ/kZ/VsFp9MXCeHfb+f1D0yANGuZR8s7B0spt +LIOS9iaFaA2Q==
Cc: IETF Discussion Mailing List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Jan 2013 13:18:53 -0000

At 4:33 AM -0800 1/2/13, SM wrote:
>At 13:08 31-12-2012, John Day wrote:
>>jumped all over.  Generally, ITU meetings require unanimity to have 
>>a consensus.  This
>
>There seems to be different definitions of consensus; each body has 
>its own meaning for that word.

No, it isn't that.  I have been in too many meetings like this.  The 
reason it is done is because of what the chair wants.  I remember one 
standard where the stack of comments on the document was two feet 
high.  Normally a tenth that many comments would have had the 
document going for a second ballot rather than progressing.  Since 
most wanted it to progress even if it was probably severely flawed 
after all those changes, it was done.

No, this is not a case of different groups having different rules. 
It is a case of chair getting what he wanted.

>
>>;-)  Why is that daunting?  ;-)  I hear that excuse often.  If we 
>>had had that attitude when we started this effort 40 years ago.  We 
>>would still be patching the PSTN.  There would be no Internet. Do 
>>you think the Internet was a success because we convinced IBM and 
>>AT&T it was a good idea?!!  I am sorry to see that the younger 
>>generation is so faint of heart.  Can't take a little challenge!
>
>Nowadays it is called being pragmatic.  The little challenge might 
>be taking on the legacy.  I wonder how many fairy tales are part of 
>the legacy. :-)

Nice rationalization for your inaction.  It has been used a lot 
throughout history.  That doesn't change the facts. (BTW, a close 
inspection reveals that the legacy is all fairy tale.)

>At 16:29 01-01-2013, Phillip Hallam-Baker wrote:
>>ITU-T has absolutely no control over the Internet unless member 
>>governments decide to give it that power. The importance of the 
>>protests was that they prevented the US and EU governments from 
>>agreeing to cede that power.
>
>That might explain the the press releases about the WCIT discussions.
>
>At 17:11 01-01-2013, John Day wrote:
>>doing some of these as well.  The UN is a very weak confederation, 
>>so the question to consider is what aspects of *telecommunication* 
>>(not defense or commerce or anything else) does it make sense that 
>>there should be international regulation (or binding agreements)?
>
>Y.2001 covers topics which affect commerce (I am ignoring other 
>angles).  There is leeway for expanding the scope beyond a narrow 
>definition of telecommunication.  Everybody will lobby for their pet 
>project as there is an opportunity to do so.

Could you expand on this?

From carlosm3011@gmail.com  Wed Jan  2 05:44:44 2013
Return-Path: <carlosm3011@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EC13E21F8B4A for <ietf@ietfa.amsl.com>; Wed,  2 Jan 2013 05:44:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.289
X-Spam-Level: 
X-Spam-Status: No, score=-3.289 tagged_above=-999 required=5 tests=[AWL=0.310,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 OhhvuA8Wnb4l for <ietf@ietfa.amsl.com>; Wed,  2 Jan 2013 05:44:44 -0800 (PST)
Received: from mail-ye0-f182.google.com (mail-ye0-f182.google.com [209.85.213.182]) by ietfa.amsl.com (Postfix) with ESMTP id 485EA21F8B48 for <ietf@ietf.org>; Wed,  2 Jan 2013 05:44:44 -0800 (PST)
Received: by mail-ye0-f182.google.com with SMTP id q5so2188016yen.27 for <ietf@ietf.org>; Wed, 02 Jan 2013 05:44:43 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=2uPyYjXkGgrkZEf9uDM31HuJKaEigz3B6Kwh/G9KSKI=; b=M5h87KEB4c+oKS1qQQTCUqP5ViC/ZzVYumP9YXNmKE7paCksoL68ZiPYRbKkM2h1jE L+uxC7M6YCvq86F4eenASdfctIGJjnkaFmdzlWWozMnYn7Bw80sxOZgO3PRgXJ/GuJgN FNFOTnHbfQk7mpLIAqwOVK2x735JXE9hNRFW6OSHwuiovWYpnLW8miLeM1+sl+mb0mkS 2tYgHE3N8evOjZvFi0lJxR7AbaKJFMIpJmREcTTG5yLQZP0GgqsLUuCtdBy5qPnMglbh NYkaYcfJEetzSblQKbf4xLDH/3ScxvTQlOLWkg78EIwhQ6MHFdomnuYK+NEcosgtDWbj 9oXA==
X-Received: by 10.236.52.105 with SMTP id d69mr40565939yhc.129.1357134283821;  Wed, 02 Jan 2013 05:44:43 -0800 (PST)
Received: from europa.local ([200.7.85.148]) by mx.google.com with ESMTPS id l51sm45294450yhh.16.2013.01.02.05.44.40 (version=SSLv3 cipher=OTHER); Wed, 02 Jan 2013 05:44:42 -0800 (PST)
Message-ID: <50E439C5.2020808@gmail.com>
Date: Wed, 02 Jan 2013 11:44:37 -0200
From: "Carlos M. Martinez" <carlosm3011@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: Phillip Hallam-Baker <hallam@gmail.com>
Subject: Re: WCIT outcome?
References: <CAMm+Lwh2cHRY+Dk2_SDtZZmUbPcgRpP89u3DHUcniJDrKrX_pw@mail.gmail.com> <CAMzo+1a0-90dnjnvs48a9DcNN9DY_edF5hH0__4XRuCaLHtL6Q@mail.gmail.com> <CAMm+LwjzjLc2-=4EdxwHOi21B3dOBUohYc5hhXZHL_Pk+iBBmQ@mail.gmail.com>
In-Reply-To: <CAMm+LwjzjLc2-=4EdxwHOi21B3dOBUohYc5hhXZHL_Pk+iBBmQ@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: IETF Discussion Mailing List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Jan 2013 13:44:45 -0000

Hi!

On 12/29/12 4:19 PM, Phillip Hallam-Baker wrote:
> 
> 
> On Sat, Dec 29, 2012 at 5:43 AM, Jorge Amodio <jmamodio@gmail.com
> <mailto:jmamodio@gmail.com>> wrote:
> 
> 
>     ITU was founded previously as the International Telegraph Union
>     before AG Bell's phone was patented, no doubt the evolution of
>     telecommunications and the Internet puts ITU with its current
>     behavior in the path of becoming obsolete and extinct, but you can't
>     discount many positive contributions particularly from the standards
>     section.
> 
> 
> The original purpose was to stop consumers from reducing their telegraph
> bills by adopting codes. 

Radio spectrum allocation was a critical task at the time (it still is,
although the world doesn't depend that much on it anymore), and one of
the task the ITU actually has performed very well, being a positive and
constructive player.

I don't know if it's true, but I've read in the past that one of the
first events that brought up the need for spectrum regulation, and thus
ushered in the role of the ITU in it was the Titanic disaster.

> 
>  
> 
>     As the multistakeholder model and its associated processes, which is
>     far from perfect, continues to evolve, ITU must be part of the
>     evolution. The issue is that as an organization they must
>     accommodate and realize that now they are "part of it" and not "it"
>     anymore.
> 
> 
> ITU must change if it is to survive. But it was merely a means to an
> end. There is no reason that the ITU 'must' be kept in existence for its
> own sake. 
> 

+1. I do believe the ITU still has a lot of potential for good, but
sadly, the debate within the ITU has been hijacked by those who claim to
defend human rights and fairness while their actual actions say otherwise.

> 
> 
> Many parts of the world do not understand the difference between a
> standard and a regulation or law. Which is why they see control points
> that don't worry us. I do not see a problem with the US control of the
> IPv6 address supply because I know that it is very very easy to defeat
> that control. ICANN is a US corporation and the US government can
> obviously pass laws that prevent ICANN/IANA from releasing address
> blocks that would reach certain countries no matter what Crocker et. al.
> say to the contrary. But absent a deployed BGP security infrastructure,
> that has no effect since the rest of the planet is not going to observe
> a US embargo.

+1.

> 
> I can see that and most IETF-ers can see that. But the diplomats
> representing Russia and China cannot apparently. Which is probably not
> surprising given the type of education their upper classes (sorry
> children of party bosses) receive.

Here I don't agree. I believe they play dumb but actually according to
their interests.

> 
Warm regards,

~Carlos

From hallam@gmail.com  Wed Jan  2 06:14:41 2013
Return-Path: <hallam@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C1A0021F8455 for <ietf@ietfa.amsl.com>; Wed,  2 Jan 2013 06:14:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.563
X-Spam-Level: 
X-Spam-Status: No, score=-3.563 tagged_above=-999 required=5 tests=[AWL=0.035,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
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 wjSw+arz1CWO for <ietf@ietfa.amsl.com>; Wed,  2 Jan 2013 06:14:40 -0800 (PST)
Received: from mail-oa0-f50.google.com (mail-oa0-f50.google.com [209.85.219.50]) by ietfa.amsl.com (Postfix) with ESMTP id 4D16821F8450 for <ietf@ietf.org>; Wed,  2 Jan 2013 06:14:40 -0800 (PST)
Received: by mail-oa0-f50.google.com with SMTP id n16so12804129oag.23 for <ietf@ietf.org>; Wed, 02 Jan 2013 06:14:39 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=lrJZVlYmkZFcMB2cMr9vJPrfAcZsB3hCQ2275nM2eAg=; b=LcK9IPwcMAFcr6XSUGnh7jsYdMme4qYLYxoJ/Mi9pBDmDDFlIpHxLH74hE7pvGpC7I +SvgPujkv1afzhC9KNdp693PNlqX6tLVoqo/1iGkET4PAl0B9p23kiFgtxpJpVLnpol3 syKxgodKtQmi5GrNFFh8AyvNSPr4VLjIApZN/E+tOnFw73d6vF0G+7JaRaO+IJuRxX1H P06jqAjCnxYu+w3HdlI8rR0zbILcmX0gUZI7mc3rFdHxxUN4OL4lrWorqIYKyZJ1Tgfz RMyLKtp4Zq940T4RaJT/Dxced9vLkvyYZyTXMsjeYZCvHAG3OCQXmG+etOJTxenbaHnJ PZ2g==
MIME-Version: 1.0
Received: by 10.60.8.199 with SMTP id t7mr24912624oea.26.1357136079816; Wed, 02 Jan 2013 06:14:39 -0800 (PST)
Received: by 10.76.19.43 with HTTP; Wed, 2 Jan 2013 06:14:39 -0800 (PST)
In-Reply-To: <6.2.5.6.2.20130102023406.0b4b7d68@resistor.net>
References: <CAMm+Lwh2cHRY+Dk2_SDtZZmUbPcgRpP89u3DHUcniJDrKrX_pw@mail.gmail.com> <CAMzo+1a0-90dnjnvs48a9DcNN9DY_edF5hH0__4XRuCaLHtL6Q@mail.gmail.com> <CAMm+LwjzjLc2-=4EdxwHOi21B3dOBUohYc5hhXZHL_Pk+iBBmQ@mail.gmail.com> <6.2.5.6.2.20121229192941.0aae33e8@resistor.net> <CAMm+LwiC0xtJU4vnGFPvAG4VKZdj7Tf3LfW0+pzwxKWTegRREw@mail.gmail.com> <a06240800cd074efd45b8@10.0.1.3> <CAMm+Lwiq+DCzXw572wKs78DG+XzYsJtwCVSPvNuVHSrT=Cr2nA@mail.gmail.com> <a06240809cd0799fee029@10.0.1.3> <6.2.5.6.2.20130102023406.0b4b7d68@resistor.net>
Date: Wed, 2 Jan 2013 09:14:39 -0500
Message-ID: <CAMm+LwgsgaV7L-FY4MnM2Einaapo-BdiddBU+nYzTS6DMPXzQw@mail.gmail.com>
Subject: Re: WCIT outcome?
From: Phillip Hallam-Baker <hallam@gmail.com>
To: SM <sm@resistor.net>
Content-Type: multipart/alternative; boundary=e89a8ff1ce46f3062904d24edd42
Cc: IETF Discussion Mailing List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Jan 2013 14:14:41 -0000

--e89a8ff1ce46f3062904d24edd42
Content-Type: text/plain; charset=ISO-8859-1

On Wed, Jan 2, 2013 at 7:33 AM, SM <sm@resistor.net> wrote:

> At 13:08 31-12-2012, John Day wrote:
>
>> jumped all over.  Generally, ITU meetings require unanimity to have a
>> consensus.  This
>>
>
> There seems to be different definitions of consensus; each body has its
> own meaning for that word.
>
>
>  ;-)  Why is that daunting?  ;-)  I hear that excuse often.  If we had had
>> that attitude when we started this effort 40 years ago.  We would still be
>> patching the PSTN.  There would be no Internet. Do you think the Internet
>> was a success because we convinced IBM and AT&T it was a good idea?!!  I am
>> sorry to see that the younger generation is so faint of heart.  Can't take
>> a little challenge!
>>
>
> Nowadays it is called being pragmatic.  The little challenge might be
> taking on the legacy.  I wonder how many fairy tales are part of the
> legacy. :-)


I think the reason is rather different. Back in 1970 the only way to get
things done was to ignore the regulations that prohibited what you want to
do. I remember when a modem came with an 'acoustic coupler' because
connecting it directly to the phone line was illegal. Many of those
regulations came from the authorities attempting to maintain wiretap
capabilities and passive eavesdropping capabilities. Plessey System X used
in the UK was designed to allow any telephone handset to be used to bug the
room it was in which is why the UK authorities made it illegal to buy a
non-Plessey phone and plug it in.

Today the Internet has quite a few supporters that have a place at the top
table of government. Tim Berners-Lee can pick up the phone and talk right
to the top of the UK government, that is what being a Companion of Honor is
actually about.

That does not mean that regulations have to be considered binding. It does
however mean that ignoring them is not necessarily the only or the best
option.



> At 16:29 01-01-2013, Phillip Hallam-Baker wrote:
>
>> ITU-T has absolutely no control over the Internet unless member
>> governments decide to give it that power. The importance of the protests
>> was that they prevented the US and EU governments from agreeing to cede
>> that power.
>>
>
> That might explain the the press releases about the WCIT discussions.


That and Microsoft being on the warpath after the NSA hacked their internal
PKI with a cryptanalytic attack to deploy the Flame malware.



> At 17:11 01-01-2013, John Day wrote:
>
>> doing some of these as well.  The UN is a very weak confederation, so the
>> question to consider is what aspects of *telecommunication*  (not defense
>> or commerce or anything else) does it make sense that there should be
>> international regulation (or binding agreements)?
>>
>
> Y.2001 covers topics which affect commerce (I am ignoring other angles).
>  There is leeway for expanding the scope beyond a narrow definition of
> telecommunication.  Everybody will lobby for their pet project as there is
> an opportunity to do so.
>

There are government interests in telecommunications, not all of them are
illegitimate.

Maintaining the ability to crack other governments confidential
communications now seems to me to have far more downsides than up. Using
the technology developed to break the Enigma codes to compromise
communications of other governments might have been a good thing if it had
only been used against the Warsaw pact (East Germany used actual Enigma
machines right up to the point the story was made public). But they didn't
limit themselves to that and the main business of the NSA from 1952 through
1976 or so was breaching the communications systems of US allies so that
they could engineer a coup when it suited them. It is probably not an
accident that the coups stopped happening in the mid 70s right around the
time electronic cipher systems replaced the mechanical ones.

But beyond the illegitimate concerns, there are some important legitimate
ones. In particular a country like France has to be concerned that if it
gets into a trade dispute with the US that the US administration can't
force it into submission by threatening to cut off its connection to the
Internet or any other essential communication technology.

This is not a theoretical consideration. The reason that there is no
central repository for RFID product identifiers is that the French
government decided that the proposals on the table would give the US the
ability to control the sale of French products by ordering the maintainer
of the registry not to publish them. That would effectively make it
impossible to sell them through the electronic supply chain. So they made
sure that the registry did not happen.


Ensuring that no country establishes a technological control point like
that is a legitimate government interest and an essential one. That is the
real reason that there is so much politics surrounding ICANN.

So one option would be for ITU-T to refocus its energies on protecting the
legitimate government interest of preventing domination. But it is not
necessarily the best one. A better option would be to design the technology
to factor out the control points so that the technology is neutral on that
point.

-- 
Website: http://hallambaker.com/

--e89a8ff1ce46f3062904d24edd42
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<br><br><div class=3D"gmail_quote">On Wed, Jan 2, 2013 at 7:33 AM, SM <span=
 dir=3D"ltr">&lt;<a href=3D"mailto:sm@resistor.net" target=3D"_blank">sm@re=
sistor.net</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=
=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class=3D"im">At 13:08 31-12-2012, John Day wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
jumped all over. =A0Generally, ITU meetings require unanimity to have a con=
sensus. =A0This<br>
</blockquote>
<br></div>
There seems to be different definitions of consensus; each body has its own=
 meaning for that word.<div class=3D"im"><br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
;-) =A0Why is that daunting? =A0;-) =A0I hear that excuse often. =A0If we h=
ad had that attitude when we started this effort 40 years ago. =A0We would =
still be patching the PSTN. =A0There would be no Internet. Do you think the=
 Internet was a success because we convinced IBM and AT&amp;T it was a good=
 idea?!! =A0I am sorry to see that the younger generation is so faint of he=
art. =A0Can&#39;t take a little challenge!<br>

</blockquote>
<br></div>
Nowadays it is called being pragmatic. =A0The little challenge might be tak=
ing on the legacy. =A0I wonder how many fairy tales are part of the legacy.=
 :-)</blockquote><div><br></div><div>I think the reason is rather different=
. Back in 1970 the only way to get things done was to ignore the regulation=
s that prohibited what you want to do. I remember when a modem came with an=
 &#39;acoustic coupler&#39; because connecting it directly to the phone lin=
e was illegal. Many of those regulations came from the authorities attempti=
ng to maintain wiretap capabilities and passive eavesdropping capabilities.=
 Plessey System X used in the UK was designed to allow any telephone handse=
t to be used to bug the room it was in which is why the UK authorities made=
 it illegal to buy a non-Plessey phone and plug it in.=A0</div>
<div><br></div><div>Today the Internet has quite a few supporters that have=
 a place at the top table of government. Tim Berners-Lee can pick up the ph=
one and talk right to the top of the UK government, that is what being a Co=
mpanion of Honor is actually about.=A0</div>
<div><br></div><div>That does not mean that regulations have to be consider=
ed binding. It does however mean that ignoring them is not necessarily the =
only or the best option.=A0</div><div><br></div><div>=A0</div><blockquote c=
lass=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;=
padding-left:1ex">
<div class=3D"im">
At 16:29 01-01-2013, Phillip Hallam-Baker wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
ITU-T has absolutely no control over the Internet unless member governments=
 decide to give it that power. The importance of the protests was that they=
 prevented the US and EU governments from agreeing to cede that power.<br>

</blockquote>
<br></div>
That might explain the the press releases about the WCIT discussions.</bloc=
kquote><div><br></div><div>That and Microsoft being on the warpath after th=
e NSA hacked their internal PKI with a cryptanalytic attack to deploy the F=
lame malware.</div>
<div><br></div><div>=A0</div><blockquote class=3D"gmail_quote" style=3D"mar=
gin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class=3D"i=
m">
At 17:11 01-01-2013, John Day wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
doing some of these as well. =A0The UN is a very weak confederation, so the=
 question to consider is what aspects of *telecommunication* =A0(not defens=
e or commerce or anything else) does it make sense that there should be int=
ernational regulation (or binding agreements)?<br>

</blockquote>
<br></div>
Y.2001 covers topics which affect commerce (I am ignoring other angles). =
=A0There is leeway for expanding the scope beyond a narrow definition of te=
lecommunication. =A0Everybody will lobby for their pet project as there is =
an opportunity to do so.<br>
</blockquote><div><br></div><div>There are government interests in telecomm=
unications, not all of them are illegitimate.</div><div><br></div><div>Main=
taining the ability to crack other governments confidential communications =
now seems to me to have far more downsides than up. Using the technology de=
veloped to break the Enigma codes to compromise communications of other gov=
ernments might have been a good thing if it had only been used against the =
Warsaw pact (East Germany used actual Enigma machines right up to the point=
 the story was made public). But they didn&#39;t limit themselves to that a=
nd the main business of the NSA from 1952 through 1976 or so was breaching =
the communications systems of US allies so that they could engineer a coup =
when it suited them. It is probably not an accident that the coups stopped =
happening in the mid 70s right around the time electronic cipher systems re=
placed the mechanical ones.</div>
</div><div><br></div><div>But beyond the illegitimate concerns, there are s=
ome important legitimate ones. In particular a country like France has to b=
e concerned that if it gets into a trade dispute with the US that the US ad=
ministration can&#39;t force it into submission by threatening to cut off i=
ts connection to the Internet or any other essential communication technolo=
gy.</div>
<div><br></div><div>This is not a theoretical consideration. The reason tha=
t there is no central repository for RFID product identifiers is that the F=
rench government decided that the proposals on the table would give the US =
the ability to control the sale of French products by ordering the maintain=
er of the registry not to publish them. That would effectively make it impo=
ssible to sell them through the electronic supply chain. So they made sure =
that the registry did not happen.</div>
<div><br></div><div><br></div><div>Ensuring that no country establishes a t=
echnological control point like that is a legitimate government interest an=
d an essential one. That is the real reason that there is so much politics =
surrounding ICANN.</div>
<div><br></div><div>So one option would be for ITU-T to refocus its energie=
s on protecting the legitimate government interest of preventing domination=
. But it is not necessarily the best one. A better option would be to desig=
n the technology to factor out the control points so that the technology is=
 neutral on that point.</div>
<div><br></div>-- <br>Website: <a href=3D"http://hallambaker.com/">http://h=
allambaker.com/</a><br>

--e89a8ff1ce46f3062904d24edd42--

From stbryant@cisco.com  Wed Jan  2 06:28:58 2013
Return-Path: <stbryant@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 69E1F21F84E8 for <ietf@ietfa.amsl.com>; Wed,  2 Jan 2013 06:28:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.574
X-Spam-Level: 
X-Spam-Status: No, score=-110.574 tagged_above=-999 required=5 tests=[AWL=0.025, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
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 SvuWLbLAUqmY for <ietf@ietfa.amsl.com>; Wed,  2 Jan 2013 06:28:57 -0800 (PST)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140]) by ietfa.amsl.com (Postfix) with ESMTP id 8DB9C21F84E6 for <ietf@ietf.org>; Wed,  2 Jan 2013 06:28:57 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1211; q=dns/txt; s=iport; t=1357136937; x=1358346537; h=message-id:date:from:reply-to:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=Np0VF8sxXvkFgY9UsBog4xeTf6pabbat5mTATw7NWy0=; b=UFiqWSOO/+ZvlgRfNgbTxngvQalWVkoKmVo8w3kyyRSvyOA3MxI1Uhjc 1NCtkDCL81q084Yw+eREeWOhGOcbycF0X0rswv67bKTa2LpO/q+hevyLg py+hjnMXrZuGSrOdfIcgL018jXoF+FZoj8UteOYMuDKQtc4ybCnDVdM3v A=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhNUAGFD5FCQ/khN/2dsb2JhbABFgX+BSbY/g0UWc4IeAQEBBDhAARALGAkWDwkDAgECAUUGDQEHAQGID7hYkRoDlgyFa4pdgnQ
X-IronPort-AV: E=Sophos;i="4.84,396,1355097600"; d="scan'208";a="148938754"
Received: from ams-core-4.cisco.com ([144.254.72.77]) by ams-iport-1.cisco.com with ESMTP; 02 Jan 2013 14:28:56 +0000
Received: from cisco.com (mrwint.cisco.com [64.103.70.36]) by ams-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id r02ESupt008652 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 2 Jan 2013 14:28:56 GMT
Received: from [127.0.0.1] (localhost [127.0.0.1]) by cisco.com (8.14.4+Sun/8.8.8) with ESMTP id r02ESsJF008175; Wed, 2 Jan 2013 14:28:55 GMT
Message-ID: <50E44426.6080101@cisco.com>
Date: Wed, 02 Jan 2013 14:28:54 +0000
From: Stewart Bryant <stbryant@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: "Carlos M. Martinez" <carlosm3011@gmail.com>
Subject: Re: WCIT outcome?
References: <CAMm+Lwh2cHRY+Dk2_SDtZZmUbPcgRpP89u3DHUcniJDrKrX_pw@mail.gmail.com> <CAMzo+1a0-90dnjnvs48a9DcNN9DY_edF5hH0__4XRuCaLHtL6Q@mail.gmail.com> <CAMm+LwjzjLc2-=4EdxwHOi21B3dOBUohYc5hhXZHL_Pk+iBBmQ@mail.gmail.com> <50E439C5.2020808@gmail.com>
In-Reply-To: <50E439C5.2020808@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Phillip Hallam-Baker <hallam@gmail.com>, IETF Discussion Mailing List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: stbryant@cisco.com
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Jan 2013 14:28:58 -0000

On 02/01/2013 13:44, Carlos M. Martinez wrote:
>
> Radio spectrum allocation was a critical task at the time (it still is,
> although the world doesn't depend that much on it anymore), and one of
> the task the ITU actually has performed very well, being a positive and
> constructive player.
>
> I don't know if it's true, but I've read in the past that one of the
> first events that brought up the need for spectrum regulation, and thus
> ushered in the role of the ITU in it was the Titanic disaster.

Yes, there was chaos until the CCIR (ITU-R) process of international
radio regulation came into being.

However it remains to be seen what will happen as the various
computerized "dynamic" forms of frequency co-ordination
(in all their forms) replace the essentially static frequency co-
ordination method that has prevailed over the past 100 years,
and as SDR deployment allows radios to use more dynamic/
agile waveforms than were the possible up until quite recently.

Just as the Internet has challenged the ITU-T model of operation,
the computerization of radio (with the help of the Internet) will
to some degree or other challenge the ITU-R model of operation.

- Stewart


From jeanjour@comcast.net  Wed Jan  2 06:48:54 2013
Return-Path: <jeanjour@comcast.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 249CD21F856D for <ietf@ietfa.amsl.com>; Wed,  2 Jan 2013 06:48:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.427
X-Spam-Level: 
X-Spam-Status: No, score=-100.427 tagged_above=-999 required=5 tests=[AWL=0.009, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_NET=0.611, HTML_MESSAGE=0.001, RDNS_NONE=0.1, USER_IN_WHITELIST=-100]
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 bw0Nicau6Sbx for <ietf@ietfa.amsl.com>; Wed,  2 Jan 2013 06:48:52 -0800 (PST)
Received: from qmta03.westchester.pa.mail.comcast.net (qmta03.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:43:76:96:62:32]) by ietfa.amsl.com (Postfix) with ESMTP id 997A621F8525 for <ietf@ietf.org>; Wed,  2 Jan 2013 06:48:52 -0800 (PST)
Received: from omta06.westchester.pa.mail.comcast.net ([76.96.62.51]) by qmta03.westchester.pa.mail.comcast.net with comcast id izEa1k00916LCl0532orz8; Wed, 02 Jan 2013 14:48:51 +0000
Received: from [10.0.1.3] ([98.229.211.49]) by omta06.westchester.pa.mail.comcast.net with comcast id j2oq1k00r14WE023S2or80; Wed, 02 Jan 2013 14:48:51 +0000
Mime-Version: 1.0
Message-Id: <a06240834cd09f3ec48a7@[10.0.1.3]>
In-Reply-To: <CAMm+LwgsgaV7L-FY4MnM2Einaapo-BdiddBU+nYzTS6DMPXzQw@mail.gmail.com>
References: <CAMm+Lwh2cHRY+Dk2_SDtZZmUbPcgRpP89u3DHUcniJDrKrX_pw@mail.gmail.com> <CAMzo+1a0-90dnjnvs48a9DcNN9DY_edF5hH0__4XRuCaLHtL6Q@mail.gmail.com> <CAMm+LwjzjLc2-=4EdxwHOi21B3dOBUohYc5hhXZHL_Pk+iBBmQ@mail.gmail.com> <6.2.5.6.2.20121229192941.0aae33e8@resistor.net> <CAMm+LwiC0xtJU4vnGFPvAG4VKZdj7Tf3LfW0+pzwxKWTegRREw@mail.gmail.com> <a06240800cd074efd45b8@10.0.1.3> <CAMm+Lwiq+DCzXw572wKs78DG+XzYsJtwCVSPvNuVHSrT=Cr2nA@mail.gmail.com> <a06240809cd0799fee029@10.0.1.3> <6.2.5.6.2.20130102023406.0b4b7d68@resistor.net> <CAMm+LwgsgaV7L-FY4MnM2Einaapo-BdiddBU+nYzTS6DMPXzQw@mail.gmail.com>
Date: Wed, 2 Jan 2013 09:46:07 -0500
To: Phillip Hallam-Baker <hallam@gmail.com>, SM <sm@resistor.net>
From: John Day <jeanjour@comcast.net>
Subject: Re: WCIT outcome?
Content-Type: multipart/alternative; boundary="============_-854984365==_ma============"
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20121106; t=1357138131; bh=dx9WCwi3SJCZTHUx3jBaEYU9vAB05JSXYv7FxuF1MyM=; h=Received:Received:Mime-Version:Message-Id:Date:To:From:Subject: Content-Type; b=hUtj1iRNJhYK1+9UpAJ7ATJhI1TxyyEEgYo7fHgAKA3l2FLh3ZgqUQjtVd0Wr7/VK kW6qo0qOiczsZRAMhxkBd+GD7mUumBwzfFVGjXt+GZNYo6EcmN1tyCtItIE5wEpbSq 9HS5cWSj8z/+hRPfxyh7F8MGQMZz/yXIJt5xbsC7qRidnuI3l532FYn7QcJAC6n79E hlLHNDcZtuaawHRXy3U/Yto8xJmi2r2w5QCI+o8w4jOpFZeZVFYFHYsGtG0XUpgU6e b3Z308rm4INedl5q7gNY3hY4NXESt3xvIW3PHuEakdrsi6LGV+qeYQsVAGGheilIAO xLIZ/Gc43asSQ==
Cc: IETF Discussion Mailing List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Jan 2013 14:48:54 -0000

--============_-854984365==_ma============
Content-Type: text/plain; charset="us-ascii" ; format="flowed"

Interesting as always.

At 9:14 AM -0500 1/2/13, Phillip Hallam-Baker wrote:
>On Wed, Jan 2, 2013 at 7:33 AM, SM 
><<mailto:sm@resistor.net>sm@resistor.net> wrote:
>
>At 13:08 31-12-2012, John Day wrote:
>
>jumped all over.  Generally, ITU meetings require unanimity to have 
>a consensus.  This
>
>
>There seems to be different definitions of consensus; each body has 
>its own meaning for that word.
>
>
>;-)  Why is that daunting?  ;-)  I hear that excuse often.  If we 
>had had that attitude when we started this effort 40 years ago.  We 
>would still be patching the PSTN.  There would be no Internet. Do 
>you think the Internet was a success because we convinced IBM and 
>AT&T it was a good idea?!!  I am sorry to see that the younger 
>generation is so faint of heart.  Can't take a little challenge!
>
>
>Nowadays it is called being pragmatic.  The little challenge might 
>be taking on the legacy.  I wonder how many fairy tales are part of 
>the legacy. :-)
>
>
>I think the reason is rather different. Back in 1970 the only way to 
>get things done was to ignore the regulations that prohibited what 
>you want to do.

Huh?  The ARPANET was not ignoring any regulations.  Nor was the work 
at NPL or IRIA.

>I remember when a modem came with an 'acoustic coupler' because 
>connecting it directly to the phone line was illegal.

No, there was nothing illegal about it. The reason for acoustic 
couplers was that the RJ-11 had been invented yet and it was a pain 
to unscrew the box on the wall and re-wire every time you wanted to 
connect.

Ever see the French equivalent of RJ-11?  Good grief.  The French 
phone system must have carried a 100 amps!

It may have been illegal in some countries but certainly not in the US.

>Many of those regulations came from the authorities attempting to 
>maintain wiretap capabilities and passive eavesdropping 
>capabilities. Plessey System X used in the UK was designed to allow 
>any telephone handset to be used to bug the room it was in which is 
>why the UK authorities made it illegal to buy a non-Plessey phone 
>and plug it in.
>
>Today the Internet has quite a few supporters that have a place at 
>the top table of government. Tim Berners-Lee can pick up the phone 
>and talk right to the top of the UK government, that is what being a 
>Companion of Honor is actually about.
>
>That does not mean that regulations have to be considered binding. 
>It does however mean that ignoring them is not necessarily the only 
>or the best option.

While interesting, I am still not sure what this response has to do 
with the topic.

>
>
>
>At 16:29 01-01-2013, Phillip Hallam-Baker wrote:
>
>ITU-T has absolutely no control over the Internet unless member 
>governments decide to give it that power. The importance of the 
>protests was that they prevented the US and EU governments from 
>agreeing to cede that power.
>
>
>That might explain the the press releases about the WCIT discussions.
>
>
>That and Microsoft being on the warpath after the NSA hacked their 
>internal PKI with a cryptanalytic attack to deploy the Flame malware.
>
>
>
>At 17:11 01-01-2013, John Day wrote:
>
>doing some of these as well.  The UN is a very weak confederation, 
>so the question to consider is what aspects of *telecommunication* 
> (not defense or commerce or anything else) does it make sense that 
>there should be international regulation (or binding agreements)?
>
>
>Y.2001 covers topics which affect commerce (I am ignoring other 
>angles).  There is leeway for expanding the scope beyond a narrow 
>definition of telecommunication.  Everybody will lobby for their pet 
>project as there is an opportunity to do so.
>
>
>There are government interests in telecommunications, not all of 
>them are illegitimate.
>
>Maintaining the ability to crack other governments confidential 
>communications now seems to me to have far more downsides than up. 
>Using the technology developed to break the Enigma codes to 
>compromise communications of other governments might have been a 
>good thing if it had only been used against the Warsaw pact (East 
>Germany used actual Enigma machines right up to the point the story 
>was made public). But they didn't limit themselves to that and the 
>main business of the NSA from 1952 through 1976 or so was breaching 
>the communications systems of US allies so that they could engineer 
>a coup when it suited them. It is probably not an accident that the 
>coups stopped happening in the mid 70s right around the time 
>electronic cipher systems replaced the mechanical ones.

Errr, there were several coups last year.  Do you mean US initiated 
coups?  Are you sure there haven't been any? ;-)  I really doubt that 
that was the reason that they seem to fall off.  The success rate of 
the ones they did do was not exactly great and the fallout was often 
not worth the trouble.

Treaties on these sorts of things are pointless.  Agencies like NSA 
or NKVD aren't going to be bound by them anyway.

>
>But beyond the illegitimate concerns, there are some important 
>legitimate ones. In particular a country like France has to be 
>concerned that if it gets into a trade dispute with the US that the 
>US administration can't force it into submission by threatening to 
>cut off its connection to the Internet or any other essential 
>communication technology.
>
>This is not a theoretical consideration. The reason that there is no 
>central repository for RFID product identifiers is that the French 
>government decided that the proposals on the table would give the US 
>the ability to control the sale of French products by ordering the 
>maintainer of the registry not to publish them. That would 
>effectively make it impossible to sell them through the electronic 
>supply chain. So they made sure that the registry did not happen.
>

Then the RFID folks had written a lousy standard.  It is pretty easy 
to design a decentralized name space methodology, such that no one 
can control the whole thing.  Regulating to protect stupidity 
interferes with Darwin.  ;-)

>Ensuring that no country establishes a technological control point 
>like that is a legitimate government interest and an essential one. 
>That is the real reason that there is so much politics surrounding 
>ICANN.
>
>So one option would be for ITU-T to refocus its energies on 
>protecting the legitimate government interest of preventing 
>domination. But it is not necessarily the best one. A better option 
>would be to design the technology to factor out the control points 
>so that the technology is neutral on that point.

Very much agreed.  Which I believe we know how to do.  (But that too 
has its downside.)

>
>--
>Website: <http://hallambaker.com/>http://hallambaker.com/

--============_-854984365==_ma============
Content-Type: text/html; charset="us-ascii"

<!doctype html public "-//W3C//DTD W3 HTML//EN">
<html><head><style type="text/css"><!--
blockquote, dl, ul, ol, li { padding-top: 0 ; padding-bottom: 0 }
 --></style><title>Re: WCIT outcome?</title></head><body>
<div>Interesting as always.</div>
<div><br></div>
<div>At 9:14 AM -0500 1/2/13, Phillip Hallam-Baker wrote:</div>
<blockquote type="cite" cite>On Wed, Jan 2, 2013 at 7:33 AM, SM &lt;<a
href="mailto:sm@resistor.net">sm@resistor.net</a>&gt; wrote:<br>
<blockquote>At 13:08 31-12-2012, John Day wrote:<br>
<blockquote>jumped all over. &nbsp;Generally, ITU meetings require
unanimity to have a consensus. &nbsp;This<br>
</blockquote>
</blockquote>
<blockquote><br></blockquote>
<blockquote>There seems to be different definitions of consensus; each
body has its own meaning for that word.</blockquote>
<blockquote><br>
<br>
<blockquote>;-) &nbsp;Why is that daunting? &nbsp;;-) &nbsp;I hear
that excuse often. &nbsp;If we had had that attitude when we started
this effort 40 years ago. &nbsp;We would still be patching the PSTN.
&nbsp;There would be no Internet. Do you think the Internet was a
success because we convinced IBM and AT&amp;T it was a good idea?!!
&nbsp;I am sorry to see that the younger generation is so faint of
heart. &nbsp;Can't take a little challenge!<br>
</blockquote>
</blockquote>
<blockquote><br></blockquote>
<blockquote>Nowadays it is called being pragmatic. &nbsp;The little
challenge might be taking on the legacy. &nbsp;I wonder how many fairy
tales are part of the legacy. :-)<br>
</blockquote>
</blockquote>
<blockquote type="cite" cite><br></blockquote>
<blockquote type="cite" cite>I think the reason is rather different.
Back in 1970 the only way to get things done was to ignore the
regulations that prohibited what you want to do.</blockquote>
<div><br></div>
<div>Huh?&nbsp; The ARPANET was not ignoring any regulations.&nbsp;
Nor was the work at NPL or IRIA.</div>
<div><br></div>
<blockquote type="cite" cite>I remember when a modem came with an
'acoustic coupler' because connecting it directly to the phone line
was illegal.</blockquote>
<div><br></div>
<div>No, there was nothing illegal about it. The reason for acoustic
couplers was that the RJ-11 had been invented yet and it was a pain to
unscrew the box on the wall and re-wire every time you wanted to
connect.</div>
<div><br></div>
<div>Ever see the French equivalent of RJ-11?&nbsp; Good grief.&nbsp;
The French phone system must have carried a 100 amps!</div>
<div><br></div>
<div>It may have been illegal in some countries but certainly not in
the US.</div>
<div><br></div>
<blockquote type="cite" cite>Many of those regulations came from the
authorities attempting to maintain wiretap capabilities and passive
eavesdropping capabilities. Plessey System X used in the UK was
designed to allow any telephone handset to be used to bug the room it
was in which is why the UK authorities made it illegal to buy a
non-Plessey phone and plug it in.</blockquote>
<blockquote type="cite" cite><br></blockquote>
<blockquote type="cite" cite>Today the Internet has quite a few
supporters that have a place at the top table of government. Tim
Berners-Lee can pick up the phone and talk right to the top of the UK
government, that is what being a Companion of Honor is actually
about.</blockquote>
<blockquote type="cite" cite><br></blockquote>
<blockquote type="cite" cite>That does not mean that regulations have
to be considered binding. It does however mean that ignoring them is
not necessarily the only or the best option.</blockquote>
<div><br>
While interesting, I am still not sure what this response has to do
with the topic.<br>
</div>
<blockquote type="cite" cite><br></blockquote>
<blockquote type="cite" cite>&nbsp;<br>
<blockquote>At 16:29 01-01-2013, Phillip Hallam-Baker wrote:<br>
<blockquote>ITU-T has absolutely no control over the Internet unless
member governments decide to give it that power. The importance of the
protests was that they prevented the US and EU governments from
agreeing to cede that power.<br>
</blockquote>
</blockquote>
<blockquote><br></blockquote>
<blockquote>That might explain the the press releases about the WCIT
discussions.<br>
</blockquote>
</blockquote>
<blockquote type="cite" cite><br></blockquote>
<blockquote type="cite" cite>That and Microsoft being on the warpath
after the NSA hacked their internal PKI with a cryptanalytic attack to
deploy the Flame malware.</blockquote>
<blockquote type="cite" cite><br></blockquote>
<blockquote type="cite" cite>&nbsp;<br>
<blockquote>At 17:11 01-01-2013, John Day wrote:<br>
<blockquote>doing some of these as well. &nbsp;The UN is a very weak
confederation, so the question to consider is what aspects of
*telecommunication* &nbsp;(not defense or commerce or anything else)
does it make sense that there should be international regulation (or
binding agreements)?<br>
</blockquote>
</blockquote>
<blockquote><br></blockquote>
<blockquote>Y.2001 covers topics which affect commerce (I am ignoring
other angles). &nbsp;There is leeway for expanding the scope beyond a
narrow definition of telecommunication. &nbsp;Everybody will lobby for
their pet project as there is an opportunity to do so.<br>
</blockquote>
</blockquote>
<blockquote type="cite" cite><br></blockquote>
<blockquote type="cite" cite>There are government interests in
telecommunications, not all of them are illegitimate.</blockquote>
<blockquote type="cite" cite><br></blockquote>
<blockquote type="cite" cite>Maintaining the ability to crack other
governments confidential communications now seems to me to have far
more downsides than up. Using the technology developed to break the
Enigma codes to compromise communications of other governments might
have been a good thing if it had only been used against the Warsaw
pact (East Germany used actual Enigma machines right up to the point
the story was made public). But they didn't limit themselves to that
and the main business of the NSA from 1952 through 1976 or so was
breaching the communications systems of US allies so that they could
engineer a coup when it suited them. It is probably not an accident
that the coups stopped happening in the mid 70s right around the time
electronic cipher systems replaced the mechanical ones.</blockquote>
<div><br></div>
<div>Errr, there were several coups last year.&nbsp; Do you mean US
initiated coups?&nbsp; Are you sure there haven't been any? ;-)&nbsp;
I really doubt that that was the reason that they seem to fall off.&nbsp;
The success rate of the ones they did do was not exactly great and the
fallout was often not worth the trouble.</div>
<div><br></div>
<div>Treaties on these sorts of things are pointless.&nbsp; Agencies
like NSA or NKVD aren't going to be bound by them anyway.</div>
<div><br></div>
<blockquote type="cite" cite><br></blockquote>
<blockquote type="cite" cite>But beyond the illegitimate concerns,
there are some important legitimate ones. In particular a country like
France has to be concerned that if it gets into a trade dispute with
the US that the US administration can't force it into submission by
threatening to cut off its connection to the Internet or any other
essential communication technology.</blockquote>
<blockquote type="cite" cite><br></blockquote>
<blockquote type="cite" cite>This is not a theoretical consideration.
The reason that there is no central repository for RFID product
identifiers is that the French government decided that the proposals
on the table would give the US the ability to control the sale of
French products by ordering the maintainer of the registry not to
publish them. That would effectively make it impossible to sell them
through the electronic supply chain. So they made sure that the
registry did not happen.</blockquote>
<blockquote type="cite" cite><br></blockquote>
<div><br></div>
<div>Then the RFID folks had written a lousy standard.&nbsp; It is
pretty easy to design a decentralized name space methodology, such
that no one can control the whole thing.&nbsp; Regulating to protect
stupidity interferes with Darwin.&nbsp; ;-)</div>
<div><br></div>
<blockquote type="cite" cite>Ensuring that no country establishes a
technological control point like that is a legitimate government
interest and an essential one. That is the real reason that there is
so much politics surrounding ICANN.</blockquote>
<blockquote type="cite" cite><br></blockquote>
<blockquote type="cite" cite>So one option would be for ITU-T to
refocus its energies on protecting the legitimate government interest
of preventing domination. But it is not necessarily the best one. A
better option would be to design the technology to factor out the
control points so that the technology is neutral on that
point.</blockquote>
<div><br></div>
<div>Very much agreed.&nbsp; Which I believe we know how to do.&nbsp;
(But that too has its downside.)</div>
<div><br></div>
<blockquote type="cite" cite><br></blockquote>
<blockquote type="cite" cite>--</blockquote>
<blockquote type="cite" cite>Website: <a
href="http://hallambaker.com/">http://hallambaker.com/</a></blockquote
>
<div><br></div>
</body>
</html>
--============_-854984365==_ma============--

From hallam@gmail.com  Wed Jan  2 08:30:08 2013
Return-Path: <hallam@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7E2DA21F8438 for <ietf@ietfa.amsl.com>; Wed,  2 Jan 2013 08:30:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.565
X-Spam-Level: 
X-Spam-Status: No, score=-3.565 tagged_above=-999 required=5 tests=[AWL=0.033,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
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 osXgti7F6rMp for <ietf@ietfa.amsl.com>; Wed,  2 Jan 2013 08:30:07 -0800 (PST)
Received: from mail-ob0-f171.google.com (mail-ob0-f171.google.com [209.85.214.171]) by ietfa.amsl.com (Postfix) with ESMTP id 7D77221F8433 for <ietf@ietf.org>; Wed,  2 Jan 2013 08:30:07 -0800 (PST)
Received: by mail-ob0-f171.google.com with SMTP id dn14so12919032obc.16 for <ietf@ietf.org>; Wed, 02 Jan 2013 08:30:07 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=McdWUephajfZmU7PkGUJ5JTvypre4fSGohcI+dpj4AI=; b=xphqZRuPTd6leBXmUtRuf8tP0BwC/WHmL/An9TFlkV+QDvgMJk4TwIw2hKWuMvb1qQ G8o+3qyAPBKcxuNjZjDJ4+/Wx/eKVQfC6CQfHFsSVTI19dxSUCWHfdKs8chDMdJrbrZ2 19t+36Kf99hzuh5l4eXwcRISxi6uBCdmhmOmzcSZ2vt2F1hy8+Rfco4qDYC+aTsGo7CV 33RpKe37IpiZfSD8ZK/NUI22P7R3M2Qfo6TwFsD6fK548+9bYrrdUHtfEwOprizAu4yY N86Ihuo7uAPWjnN3KdawAPtTRP/dZCtem3eKz12ZL/s9jvzpJbbeBxZgCLBkERcH0p4F 14Og==
MIME-Version: 1.0
Received: by 10.60.29.193 with SMTP id m1mr25433944oeh.36.1357144207039; Wed, 02 Jan 2013 08:30:07 -0800 (PST)
Received: by 10.76.19.43 with HTTP; Wed, 2 Jan 2013 08:30:06 -0800 (PST)
In-Reply-To: <a06240834cd09f3ec48a7@10.0.1.3>
References: <CAMm+Lwh2cHRY+Dk2_SDtZZmUbPcgRpP89u3DHUcniJDrKrX_pw@mail.gmail.com> <CAMzo+1a0-90dnjnvs48a9DcNN9DY_edF5hH0__4XRuCaLHtL6Q@mail.gmail.com> <CAMm+LwjzjLc2-=4EdxwHOi21B3dOBUohYc5hhXZHL_Pk+iBBmQ@mail.gmail.com> <6.2.5.6.2.20121229192941.0aae33e8@resistor.net> <CAMm+LwiC0xtJU4vnGFPvAG4VKZdj7Tf3LfW0+pzwxKWTegRREw@mail.gmail.com> <a06240800cd074efd45b8@10.0.1.3> <CAMm+Lwiq+DCzXw572wKs78DG+XzYsJtwCVSPvNuVHSrT=Cr2nA@mail.gmail.com> <a06240809cd0799fee029@10.0.1.3> <6.2.5.6.2.20130102023406.0b4b7d68@resistor.net> <CAMm+LwgsgaV7L-FY4MnM2Einaapo-BdiddBU+nYzTS6DMPXzQw@mail.gmail.com> <a06240834cd09f3ec48a7@10.0.1.3>
Date: Wed, 2 Jan 2013 11:30:06 -0500
Message-ID: <CAMm+Lwhcv9wSpzixYp8QOx0fwTwcmOEcPaR2-gw6V+ObB2UFaA@mail.gmail.com>
Subject: Re: WCIT outcome?
From: Phillip Hallam-Baker <hallam@gmail.com>
To: John Day <jeanjour@comcast.net>
Content-Type: multipart/alternative; boundary=e89a8ff242a15e9c1f04d250c220
Cc: SM <sm@resistor.net>, IETF Discussion Mailing List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Jan 2013 16:30:08 -0000

--e89a8ff242a15e9c1f04d250c220
Content-Type: text/plain; charset=ISO-8859-1

On Wed, Jan 2, 2013 at 9:46 AM, John Day <jeanjour@comcast.net> wrote:

> **
> Interesting as always.
>
> But beyond the illegitimate concerns, there are some important legitimate
> ones. In particular a country like France has to be concerned that if it
> gets into a trade dispute with the US that the US administration can't
> force it into submission by threatening to cut off its connection to the
> Internet or any other essential communication technology.
>
> This is not a theoretical consideration. The reason that there is no
> central repository for RFID product identifiers is that the French
> government decided that the proposals on the table would give the US the
> ability to control the sale of French products by ordering the maintainer
> of the registry not to publish them. That would effectively make it
> impossible to sell them through the electronic supply chain. So they made
> sure that the registry did not happen.
>
>
>
> Then the RFID folks had written a lousy standard.  It is pretty easy to
> design a decentralized name space methodology, such that no one can control
> the whole thing.  Regulating to protect stupidity interferes with Darwin.
> ;-)
>

Which was my on-topic conclusion.

If IETF wants to avoid government level politics then we have to design the
technology in such a way that we eliminate or mitigate any control points.

The WebPKI has been successfully deployed precisely because it has
sufficient hierarchy to  be scalable without establishing a single control
point like the PEM proposal.

I don't think we will see DNSSEC or BGPSEC being allowed to propagate
unless attention is paid to the legitimate interest of states to avoid
technology capture.


DNSSEC does not replace the WebPKI, nor does BGPSEC. But we need all three
security layers if we are going to achieve a comprehensive security
solution for the Internet. Each technology has a very specific purpose:

BGPSEC: Prevent/mitigate Denial of Service attacks through bogus route
advertisement

DNSSEC: Distribute security policy information tied to the Internet naming
system

WebPKI: Establish accountability of the parties at the Internet end points.


At the moment we have a broken system because DNSSEC is being sold as a
'free' replacement for WebPKI which is a losing proposition as (1) the cost
of deploying DNSSEC is many times the cost of buying a domain validated SSL
certificate (2) the real purpose of the WebPKI is to establish
accountability which requires a stronger credential than merely having
bought a DNS name.

-- 
Website: http://hallambaker.com/

--e89a8ff242a15e9c1f04d250c220
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<br><br><div class=3D"gmail_quote">On Wed, Jan 2, 2013 at 9:46 AM, John Day=
 <span dir=3D"ltr">&lt;<a href=3D"mailto:jeanjour@comcast.net" target=3D"_b=
lank">jeanjour@comcast.net</a>&gt;</span> wrote:<br><blockquote class=3D"gm=
ail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-le=
ft:1ex">
<u></u>
<div>
<div>Interesting as always.</div><div class=3D"im"><blockquote type=3D"cite=
">But beyond the illegitimate concerns,
there are some important legitimate ones. In particular a country like
France has to be concerned that if it gets into a trade dispute with
the US that the US administration can&#39;t force it into submission by
threatening to cut off its connection to the Internet or any other
essential communication technology.</blockquote>
<blockquote type=3D"cite">This is not a theoretical consideration.
The reason that there is no central repository for RFID product
identifiers is that the French government decided that the proposals
on the table would give the US the ability to control the sale of
French products by ordering the maintainer of the registry not to
publish them. That would effectively make it impossible to sell them
through the electronic supply chain. So they made sure that the
registry did not happen.</blockquote>
<blockquote type=3D"cite"><br></blockquote>
<div><br></div>
</div><div>Then the RFID folks had written a lousy standard.=A0 It is
pretty easy to design a decentralized name space methodology, such
that no one can control the whole thing.=A0 Regulating to protect
stupidity interferes with Darwin.=A0 ;-)</div></div></blockquote><div><br><=
/div><div>Which was my on-topic conclusion.</div><div><br></div><div>If IET=
F wants to avoid government level politics then we have to design the techn=
ology in such a way that we eliminate or mitigate any control points.</div>
<div><br></div><div>The WebPKI has been successfully deployed precisely bec=
ause it has sufficient hierarchy to =A0be scalable without establishing a s=
ingle control point like the PEM proposal.</div><div><br></div><div>I don&#=
39;t think we will see DNSSEC or BGPSEC being allowed to propagate unless a=
ttention is paid to the legitimate interest of states to avoid technology c=
apture.</div>
<div><br></div><div><br></div><div>DNSSEC does not replace the WebPKI, nor =
does BGPSEC. But we need all three security layers if we are going to achie=
ve a comprehensive security solution for the Internet. Each technology has =
a very specific purpose:</div>
<div><br></div><div>BGPSEC: Prevent/mitigate Denial of Service attacks thro=
ugh bogus route advertisement</div><div><br></div><div>DNSSEC: Distribute s=
ecurity policy information tied to the Internet naming system</div><div>
<br></div><div>WebPKI: Establish accountability of the parties at the Inter=
net end points.</div><div><br></div><div><br></div><div>At the moment we ha=
ve a broken system because DNSSEC is being sold as a &#39;free&#39; replace=
ment for WebPKI which is a losing proposition as (1) the cost of deploying =
DNSSEC is many times the cost of buying a domain validated SSL certificate =
(2) the real purpose of the WebPKI is to establish accountability which req=
uires a stronger credential than merely having bought a DNS name.</div>
<div><br></div></div>-- <br>Website: <a href=3D"http://hallambaker.com/">ht=
tp://hallambaker.com/</a><br>

--e89a8ff242a15e9c1f04d250c220--

From dvburk@gmail.com  Sat Dec 29 10:51:27 2012
Return-Path: <dvburk@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A783221F84A1 for <ietf@ietfa.amsl.com>; Sat, 29 Dec 2012 10:51:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.598
X-Spam-Level: 
X-Spam-Status: No, score=-3.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
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 ZNIjCeYPB7MM for <ietf@ietfa.amsl.com>; Sat, 29 Dec 2012 10:51:26 -0800 (PST)
Received: from mail-la0-f54.google.com (mail-la0-f54.google.com [209.85.215.54]) by ietfa.amsl.com (Postfix) with ESMTP id 0F28421F8490 for <ietf@ietf.org>; Sat, 29 Dec 2012 10:51:25 -0800 (PST)
Received: by mail-la0-f54.google.com with SMTP id fp12so2330541lab.27 for <ietf@ietf.org>; Sat, 29 Dec 2012 10:51:25 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:subject:mime-version:content-type:from:in-reply-to:date :cc:message-id:references:to:x-mailer; bh=VM017LJ1MXtPDcNlTux5KJIdUTKZ8qDzzrkiwG1LJrM=; b=kVle0fH09Iw2gPeX0NBPYk6nWxGNIQawr1/Hlw58Ider6q5ZYE1P+0KhppiLJOnfY0 DmXqIhjZJSQ30WRtGCTglF38ojngGJQUhHiI1Sz1wzVhNYhoGQPUOS3ZyAwFhEsWeajr okKXc7SiEgGbvWTuKnygN1KhjN3rx3P1+wXMk3je12v1xjUK7VMS5eHg3ADS0+RtL/ce BqMURRHbtdusz5GFXj2Sm36ytWCxiQh8ob1+zz7ojpIhcTVMdUuC6DTzgl/7ErWyHDIs pWISg00QUs2VDP45CZLr5DRW7oYqCAi8D3DFvZSjUPHolt+R5bjBfEJWViikZAvGqLoM Yk0A==
X-Received: by 10.112.17.14 with SMTP id k14mr14726320lbd.61.1356807084893; Sat, 29 Dec 2012 10:51:24 -0800 (PST)
Received: from [192.168.200.100] (cdma-92-36-92-126.msk.skylink.ru. [92.36.92.126]) by mx.google.com with ESMTPS id hc20sm13722335lab.11.2012.12.29.10.51.22 (version=TLSv1/SSLv3 cipher=OTHER); Sat, 29 Dec 2012 10:51:23 -0800 (PST)
Subject: Re: WCIT outcome?
Mime-Version: 1.0 (Apple Message framework v1283)
Content-Type: multipart/alternative; boundary="Apple-Mail=_35E568E6-1C08-45ED-9F52-C3D91E788ED3"
From: Dmitry Burkov <dvburk@gmail.com>
In-Reply-To: <CAMm+LwjzjLc2-=4EdxwHOi21B3dOBUohYc5hhXZHL_Pk+iBBmQ@mail.gmail.com>
Date: Sat, 29 Dec 2012 22:51:20 +0400
Message-Id: <C3FF2B79-4215-4E22-86BC-D671BF040D00@burkov.aha.ru>
References: <CAMm+Lwh2cHRY+Dk2_SDtZZmUbPcgRpP89u3DHUcniJDrKrX_pw@mail.gmail.com> <CAMzo+1a0-90dnjnvs48a9DcNN9DY_edF5hH0__4XRuCaLHtL6Q@mail.gmail.com> <CAMm+LwjzjLc2-=4EdxwHOi21B3dOBUohYc5hhXZHL_Pk+iBBmQ@mail.gmail.com>
To: Phillip Hallam-Baker <hallam@gmail.com>
X-Mailer: Apple Mail (2.1283)
X-Mailman-Approved-At: Wed, 02 Jan 2013 08:53:00 -0800
Cc: IETF Discussion Mailing List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 29 Dec 2012 19:02:35 -0000

--Apple-Mail=_35E568E6-1C08-45ED-9F52-C3D91E788ED3
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=iso-8859-1


On Dec 29, 2012, at 10:19 PM, Phillip Hallam-Baker wrote:

to be honest I prefer don't comment your emails - but this time I =
changed mu rules...

>=20
>=20
> On Sat, Dec 29, 2012 at 5:43 AM, Jorge Amodio <jmamodio@gmail.com> =
wrote:
>=20
> =20
> As the multistakeholder model and its associated processes, which is =
far from perfect, continues to evolve, ITU must be part of the =
evolution. The issue is that as an organization they must accommodate =
and realize that now they are "part of it" and not "it" anymore.
>=20
> ITU must change if it is to survive. But it was merely a means to an =
end. There is no reason that the ITU 'must' be kept in existence for its =
own sake.=20
>=20
> Tim Berners-Lee has on numerous W3C AC meetings reminded people about =
the X-Windows consortium that did its job and then shut down.

X-Windows was dead from the beginning - we lost more regarding patents =
and html is still under- or overdeveloped:)
But the key point was not attack against ITU - but test the idea to =
replace Yalta agreements (it means - first test to replace UN)
>=20
>=20
> =20
> There is also a big confusion and still lack of a clear consensus on =
what "Internet governance" means or entitles, and many take it as =
"governing the Internet," hence governments want a piece of the action, =
and the constant and many times intended perception that the Internet is =
controlled by the USG and its development and evolution is US centric, =
which I believe at IETF we know since long time ago is not true. But =
many countries, and as you well say those where there was or still is a =
single telecom operator and controlled by government, see it that way.
>=20
> Many parts of the world do not understand the difference between a =
standard and a regulation or law. Which is why they see control points =
that don't worry us. I do not see a problem with the US control of the =
IPv6 address supply because I know that it is very very easy to defeat =
that control. ICANN is a US corporation and the US government can =
obviously pass laws that prevent ICANN/IANA from releasing address =
blocks that would reach certain countries no matter what Crocker et. al. =
say to the contrary. But absent a deployed BGP security infrastructure, =
that has no effect since the rest of the planet is not going to observe =
a US embargo.
>=20
> I can see that and most IETF-ers can see that. But the diplomats =
representing Russia and China cannot apparently. Which is probably not =
surprising given the type of education their upper classes (sorry =
children of party bosses) receive.

Don't think so - that these diplomats were so  stupid that they knew =
nothing about real situation :) Another issue - how clever they were in =
concrete event?

>=20
>=20
> =20
> The same forces that pushed at WCIT will keep doing the same thing on =
other international fora to insist with their Internet governance =
agenda, the ITRs will become effective in Jan 2015, two years, which on =
Internet time is an eternity, and it will be only valid if those =
countries that signed ratify the treaty. Meanwhile packets keep flowing, =
faster, bigger and with more destinations, not bad for a packet =
switching network that was not supposed to work. (During WCIT I was =
wondering, could you imagine doing the webcast via X.25? )
>=20
> Two years may be longer than some of the unstable regimes have left. I =
can't see Syria holding out that long and nor it appears can Russia. The =
next dominoes in line are the ex-Soviet republics round the Caspian sea =
where having the opposition boiled alive is still considered an =
acceptable means of control.

You are  absolutely wrong when put Syria in one line...  And I think =
that nobody can garantee absolute stability - be careful with such =
predictions. History showed us that the most stable leading countries =
can be easily dropped down...


>=20
> =20
> I agree that it is not clear what the outcome of WCIT12 was, but =
something that is clear is that ITU needs to evolve, or as Vint =
characterized them, the "dinosaurs" will become extinct.
>=20

I think that first of all - Vint also should estimate himself and  Tony =
( of course) - who are these dinosaurs? :)

> I think that what we should be doing is to help the ITU become extinct =
by eliminating the technical control points that would make ITU =
oversight of Internet governance necessary.
>=20
> This does not need to entail a great deal of technical changes but =
does require that we accept that they do have a valid interest.
> =20
>=20

dima

> --=20
> Website: http://hallambaker.com/


--Apple-Mail=_35E568E6-1C08-45ED-9F52-C3D91E788ED3
Content-Transfer-Encoding: 7bit
Content-Type: text/html;
	charset=iso-8859-1

<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On Dec 29, 2012, at 10:19 PM, Phillip Hallam-Baker wrote:</div><div><br></div><div>to be honest I prefer don't comment your emails - but this time I changed mu rules...</div><br class="Apple-interchange-newline"><blockquote type="cite"><br><br><div class="gmail_quote">On Sat, Dec 29, 2012 at 5:43 AM, Jorge Amodio <span dir="ltr">&lt;<a href="mailto:jmamodio@gmail.com" target="_blank">jmamodio@gmail.com</a>&gt;</span> wrote:<br><div><br></div><div>&nbsp;</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr"><div>As the multistakeholder model and its associated processes, which is far from perfect, continues to evolve, ITU must be part of the evolution. The issue is that as an organization they must accommodate and realize that now they are "part of it" and not "it" anymore.</div>
</div></blockquote><div><br></div><div>ITU must change if it is to survive. But it was merely a means to an end. There is no reason that the ITU 'must' be kept in existence for its own sake.&nbsp;</div><div><br></div><div>
Tim Berners-Lee has on numerous W3C AC meetings reminded people about the X-Windows consortium that did its job and then shut down.</div></div></blockquote><div><br></div>X-Windows was dead from the beginning - we lost more regarding patents and html is still under- or overdeveloped:)</div><div>But the key point was not attack against ITU - but test the idea to replace Yalta agreements (it means - first test to replace UN)<br><blockquote type="cite"><div class="gmail_quote"><div><br></div><div><br></div><div>&nbsp;</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr"><div>There is also a big confusion and still lack of a clear consensus on what "Internet governance" means or entitles, and many take it as "governing the Internet," hence governments want a piece of the action, and the constant and many times intended perception that the Internet is controlled by the USG and its development and evolution is US centric, which I believe at IETF we know since long time ago is not true. But many countries, and as you well say those where there was or still is a single telecom operator and controlled by government, see it that way.</div>
</div></blockquote><div><br></div><div>Many parts of the world do not understand the difference between a standard and a regulation or law. Which is why they see control points that don't worry us. I do not see a problem with the US control of the IPv6 address supply because I know that it is very very easy to defeat that control. ICANN is a US corporation and the US government can obviously pass laws that prevent ICANN/IANA from releasing address blocks that would reach certain countries no matter what Crocker et. al. say to the contrary. But absent a deployed BGP security infrastructure, that has no effect since the rest of the planet is not going to observe a US embargo.</div>
<div><br></div><div>I can see that and most IETF-ers can see that. But the diplomats representing Russia and China cannot apparently. Which is probably not surprising given the type of education their upper classes (sorry children of party bosses) receive.</div></div></blockquote><div><br></div>Don't think so - that these diplomats were so &nbsp;stupid that they knew nothing about real situation :) Another issue - how clever they were in concrete event?</div><div><br><blockquote type="cite"><div class="gmail_quote">
<div><br></div>
<div><br></div><div>&nbsp;</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div>The same forces that pushed at WCIT will keep doing the same thing on other international fora to insist with their Internet governance agenda, the ITRs will become effective in Jan 2015, two years, which on Internet time is an eternity, and it will be only valid if those countries that signed ratify the treaty. Meanwhile packets keep flowing, faster, bigger and with more destinations, not bad for a packet switching network that was not supposed to work. (During WCIT I was wondering, could you imagine doing the webcast via X.25? )</div>
</div></blockquote><div><br></div><div>Two years may be longer than some of the unstable regimes have left. I can't see Syria holding out that long and nor it appears can Russia. The next dominoes in line are the ex-Soviet republics round the Caspian sea where having the opposition boiled alive is still considered an acceptable means of control.</div></div></blockquote><div><br></div>You are &nbsp;absolutely wrong when put Syria in one line... &nbsp;And I think that nobody can garantee absolute stability - be careful with such predictions. History showed us that the most stable leading countries can be easily dropped down...</div><div><br></div><div><br><blockquote type="cite"><div class="gmail_quote">
<div><br></div><div>&nbsp;</div><blockquote class="gmail_quote" style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0.8ex; border-left-width: 1px; border-left-color: rgb(204, 204, 204); border-left-style: solid; padding-left: 1ex; position: static; z-index: auto; "><div dir="ltr"><div>I agree that it is not clear what the outcome of WCIT12 was, but something that is clear is that ITU needs to evolve, or as Vint&nbsp;characterized&nbsp;them, the "dinosaurs" will become extinct.</div>
</div></blockquote><div><br></div></div></blockquote><div><br></div>I think that first of all - Vint also should estimate himself and &nbsp;Tony ( of course) - who are these dinosaurs? :)</div><div><br><blockquote type="cite"><div class="gmail_quote"><div>I think that what we should be doing is to help the ITU become extinct by eliminating the technical control points that would make ITU oversight of Internet governance necessary.</div>
<div><br></div><div>This does not need to entail a great deal of technical changes but does require that we accept that they do have a valid interest.</div><div>&nbsp;</div></div><div><br></div></blockquote><div><br></div>dima</div><div><br><blockquote type="cite">-- <br>Website: <a href="http://hallambaker.com/">http://hallambaker.com/</a><br>

</blockquote></div><br></body></html>
--Apple-Mail=_35E568E6-1C08-45ED-9F52-C3D91E788ED3--

From paul@redbarn.org  Mon Dec 31 11:48:53 2012
Return-Path: <paul@redbarn.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4187421F87B3 for <ietf@ietfa.amsl.com>; Mon, 31 Dec 2012 11:48:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.051
X-Spam-Level: 
X-Spam-Status: No, score=-9.051 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_IMAGE_ONLY_20=1.546, HTML_IMAGE_RATIO_08=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8]
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 VlIU817eWU+I for <ietf@ietfa.amsl.com>; Mon, 31 Dec 2012 11:48:52 -0800 (PST)
Received: from ss.vix.com (ss.vix.com [24.104.150.2]) by ietfa.amsl.com (Postfix) with ESMTP id AAB5E21F8798 for <ietf@ietf.org>; Mon, 31 Dec 2012 11:48:52 -0800 (PST)
Received: from [IPv6:2001:559:8000:cb:31ad:76fa:fbb6:d551] (unknown [IPv6:2001:559:8000:cb:31ad:76fa:fbb6:d551]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by ss.vix.com (Postfix) with ESMTPSA id 7B596EBC96; Mon, 31 Dec 2012 19:48:51 +0000 (UTC) (envelope-from paul@redbarn.org)
Message-ID: <50E1EC65.8030205@redbarn.org>
Date: Mon, 31 Dec 2012 11:49:57 -0800
From: Paul Vixie <paul@redbarn.org>
User-Agent: Postbox 3.0.6 (Windows/20121031)
MIME-Version: 1.0
To: Noel Chiappa <jnc@mercury.lcs.mit.edu>
Subject: Re: [ih] 30th Anniversary of Transition to TCP/IP
References: <20121231192716.0AF8218C092@mercury.lcs.mit.edu>
In-Reply-To: <20121231192716.0AF8218C092@mercury.lcs.mit.edu>
Content-Type: multipart/alternative; boundary="------------070701070309030708000903"
X-Mailman-Approved-At: Wed, 02 Jan 2013 08:54:30 -0800
Cc: internet-history@postel.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 31 Dec 2012 19:48:53 -0000

This is a multi-part message in MIME format.
--------------070701070309030708000903
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit



> Noel Chiappa <mailto:jnc@mercury.lcs.mit.edu>
> Monday, December 31, 2012 11:27 AM
> ...
> It's been quite a ride.

born in 1963, i felt throughout the 70's and 80's that i had been born
too late, that all the fun stuff had been done already. now in the 10's
i feel like we're just getting going and that i was probably born too
soon, that all the fun stuff is coming 50 years from now.

yes, quite a ride.

paul

--------------070701070309030708000903
Content-Type: multipart/related;
 boundary="------------040501060602030005010608"


--------------040501060602030005010608
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<html><head>
<meta content="text/html; charset=ISO-8859-1" http-equiv="Content-Type">
</head><body bgcolor="#FFFFFF" text="#000000"><br>
<br>
<blockquote style="border: 0px none;" 
cite="mid:20121231192716.0AF8218C092@mercury.lcs.mit.edu" type="cite">
  <div style="margin:30px 25px 10px 25px;" class="__pbConvHr"><div 
style="display:table;width:100%;border-top:1px solid 
#EDEEF0;padding-top:5px"> 	<div 
style="display:table-cell;vertical-align:middle;padding-right:6px;"><img
 photoaddress="jnc@mercury.lcs.mit.edu" photoname="Noel Chiappa" 
src="cid:part1.08040201.04010206@redbarn.org" 
name="compose-unknown-contact.jpg" height="25px" width="25px"></div>   <div
 
style="display:table-cell;white-space:nowrap;vertical-align:middle;width:100%">
   	<a moz-do-not-send="true" href="mailto:jnc@mercury.lcs.mit.edu" 
style="color:#737F92 
!important;padding-right:6px;font-weight:bold;text-decoration:none 
!important;">Noel Chiappa</a></div>   <div 
style="display:table-cell;white-space:nowrap;vertical-align:middle;">   
  <font color="#9FA2A5"><span style="padding-left:6px">Monday, December 
31, 2012 11:27 AM</span></font></div></div></div>
  <div style="color:#888888;margin-left:24px;margin-right:24px;" 
__pbrmquotes="true" class="__pbConvBody"><div>...<br>It's been quite a 
ride.<br></div></div>
</blockquote>
<br>
born in 1963, i felt throughout the 70's and 80's that i had been born 
too late, that all the fun stuff had been done already. now in the 10's i
 feel like we're just getting going and that i was probably born too 
soon, that all the fun stuff is coming 50 years from now.<br>
<br>
yes, quite a ride.<br>
<br>
paul<br>
</body></html>

--------------040501060602030005010608
Content-Type: image/jpeg; x-apple-mail-type=stationery;
 name="compose-unknown-contact.jpg"
Content-Transfer-Encoding: base64
Content-ID: <part1.08040201.04010206@redbarn.org>
Content-Disposition: inline;
 filename="compose-unknown-contact.jpg"

/9j/4AAQSkZJRgABAQEARwBHAAD/2wBDAAEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEC
AQEBAQEBAgICAgICAgICAgICAgICAgICAgICAgICAgICAgL/2wBDAQEBAQEBAQICAgICAgIC
AgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgL/wAAR
CAAZABkDAREAAhEBAxEB/8QAGAAAAwEBAAAAAAAAAAAAAAAABgcICQr/xAA0EAABAwMCAgUK
BwAAAAAAAAACAQMEBQYRABITIQcUMUF2CBUXIjI2N0JRtVRWkZOV0dL/xAAYAQEAAwEAAAAA
AAAAAAAAAAADAAEEAv/EACQRAAICAAQGAwAAAAAAAAAAAAABAhEDMrHREyExM0FxgfDx/9oA
DAMBAAIRAxEAPwDuEt+gW/ULet6oVC3rfqNQqFv0OfPn1GhUqfOmzZtKZlS5UqZMaNwzNwiJ
VIl7eXLCaZIGwBl3TY8epPx2+jy2ZNPjvkwc9uhW8j7nCPhvOsQliYIeS7cvCpp8o50qwrC4
v3lsNSDbdmTEhvs2tahxpfV3WnmbbozJEw/gwdadbYExVRXKEKoSdvJcaOSqxE7/AAiX0gXx
+a69/JSf9alIlste0VzaNpeFrcT9KKymotyiaZ0KRCnzacoE7Kjzn4gi2KqUh3jqDHDHv4mR
UfruTWlMzlVUKIVNp9GguEJnAh0+IZjyAiisgyRDnu5azS8miKqjOTVkKqS/psG37fo1Fbab
eg25b8eZPeFJBBJSjMG5HjMeyihnaauZwe4OGiju13GAcpOwBeN+U8/IkGbsiS8b7ryogmbz
hbyc9REROfZhERO5ETShjPtvpGqTUyLErytS4siSwx5x2tRH4hPOI0DkjZtaJtFxuVEbIUUi
yeNujlBUJGbJN6nM/Cyf2Hf60YgjvKA+NPSP4gT7axpcPtr51YWJnYn9dnAQWl722p4ot37y
zqnlfp6FrqbwawG8/9k=
--------------040501060602030005010608--

--------------070701070309030708000903--

From mcr@sandelman.ca  Mon Dec 31 12:23:42 2012
Return-Path: <mcr@sandelman.ca>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7CEB021F8692 for <ietf@ietfa.amsl.com>; Mon, 31 Dec 2012 12:23:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.49
X-Spam-Level: 
X-Spam-Status: No, score=-1.49 tagged_above=-999 required=5 tests=[AWL=1.110,  BAYES_00=-2.599]
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 67sn8B-awAE5 for <ietf@ietfa.amsl.com>; Mon, 31 Dec 2012 12:23:42 -0800 (PST)
Received: from tuna.sandelman.ca (unknown [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) by ietfa.amsl.com (Postfix) with ESMTP id ED5C221F8470 for <ietf@ietf.org>; Mon, 31 Dec 2012 12:23:41 -0800 (PST)
Received: from sandelman.ca (unknown [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id DEF412016D for <ietf@ietf.org>; Mon, 31 Dec 2012 15:27:28 -0500 (EST)
Received: by sandelman.ca (Postfix, from userid 179) id D7C3C636C7; Mon, 31 Dec 2012 15:22:57 -0500 (EST)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id C89B9636C4 for <ietf@ietf.org>; Mon, 31 Dec 2012 15:22:57 -0500 (EST)
From: Michael Richardson <mcr@sandelman.ca>
To: IETF Discussion <ietf@ietf.org>
Subject: Re: travel guide for the next IETF...
In-Reply-To: <50DF09C7.1060009@dcrocker.net>
References: <50DF09C7.1060009@dcrocker.net>
X-Mailer: MH-E 8.3; nmh 1.3-dev; XEmacs 21.4 (patch 22)
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
Date: Mon, 31 Dec 2012 15:22:57 -0500
Message-ID: <20200.1356985377@sandelman.ca>
Sender: mcr@sandelman.ca
X-Mailman-Approved-At: Wed, 02 Jan 2013 08:54:30 -0800
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 31 Dec 2012 20:23:42 -0000

>>>>> "Dave" == Dave Crocker <dhc@dcrocker.net> writes:
    Dave> "Quick, name five reasons to go to Orlando. Here are mine:
    Dave> Puerto Rican 
    Dave> delicacies, alternative cinema, craft beer, African-American
    Dave> history and 
    Dave> psychic readings..."

Good... but how to get there?

We appear to be stuck in the middle of a monster hotel with a single
boulevard and nothing at all nearby (except that there is a shuttle
to Disney)

Shoping around for places to stay, there are some 3-star places for
<$50/night.   



From kwiereng@cisco.com  Mon Dec 31 13:46:17 2012
Return-Path: <kwiereng@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A2DCD21F8698; Mon, 31 Dec 2012 13:46:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.598
X-Spam-Level: 
X-Spam-Status: No, score=-10.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8]
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 ga7hxF6kvS9f; Mon, 31 Dec 2012 13:46:17 -0800 (PST)
Received: from rcdn-iport-9.cisco.com (rcdn-iport-9.cisco.com [173.37.86.80]) by ietfa.amsl.com (Postfix) with ESMTP id C2F1D21F867D; Mon, 31 Dec 2012 13:46:16 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2374; q=dns/txt; s=iport; t=1356990377; x=1358199977; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=ps+tNCDK7SX+7TxLnqpdoPvIfsPaOkKCj23fALzeVqI=; b=kfF6p0j0fB+k03bh7lNKuvoDNUAXmsyxhFXLfBWPxpg+f/yy0o8FvEF9 Z8+yXULOW+uo53Gm5ML4CyEDhNV0FmuwZ4wKS6Qmn2J7UJhr/z+6hYS+d YsK8oQFF25y/vJkQkFaIegwzviZF55vRmLicFxlGQXg+pw0PHt+jbdMQi U=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ArQHADsH4lCtJV2Y/2dsb2JhbABFgkl/uhkWc4IfAQEEeRACAQgEAToHMhQRAgQOBYgTDLdnjFeDYmEDlgyQSIJ0
X-IronPort-AV: E=Sophos;i="4.84,387,1355097600";  d="scan'208,217";a="154743057"
Received: from rcdn-core-1.cisco.com ([173.37.93.152]) by rcdn-iport-9.cisco.com with ESMTP; 31 Dec 2012 21:46:16 +0000
Received: from xhc-aln-x14.cisco.com (xhc-aln-x14.cisco.com [173.36.12.88]) by rcdn-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id qBVLkGoO011041 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 31 Dec 2012 21:46:16 GMT
Received: from xmb-aln-x12.cisco.com ([169.254.7.128]) by xhc-aln-x14.cisco.com ([173.36.12.88]) with mapi id 14.02.0318.004; Mon, 31 Dec 2012 15:46:15 -0600
From: "Klaas Wierenga (kwiereng)" <kwiereng@cisco.com>
To: IETF Chair <chair@ietf.org>
Subject: Re: 30th Anniversary of Transition to TCP/IP
Thread-Topic: 30th Anniversary of Transition to TCP/IP
Thread-Index: AQHN53tSblTZhFI4OEiE6CBj1XFyz5gzcY1e
Date: Mon, 31 Dec 2012 21:46:15 +0000
Message-ID: <EAD7068F-AF9D-4417-A068-61DD75A28FB9@cisco.com>
References: <9DA543CE-5AE0-41B9-B0B9-49C6B208CCEE@vigilsec.com>, <B2E21F96-6487-437C-826E-00F610729D22@ietf.org>
In-Reply-To: <B2E21F96-6487-437C-826E-00F610729D22@ietf.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: multipart/alternative; boundary="_000_EAD7068FAF9D4417A06861DD75A28FB9ciscocom_"
MIME-Version: 1.0
X-Mailman-Approved-At: Wed, 02 Jan 2013 08:54:30 -0800
Cc: IETF <ietf@ietf.org>, IETF Announce <ietf-announce@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 31 Dec 2012 21:46:17 -0000

--_000_EAD7068FAF9D4417A06861DD75A28FB9ciscocom_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Happy slow start of 2013!

Sent from my iPad

On 31 dec. 2012, at 18:21, "IETF Chair" <chair@ietf.org<mailto:chair@ietf.o=
rg>> wrote:

Happy New Year.  It is already 2013 in some part of the world.

The ARPANET transitioned to TCP/IP on 1 January 1983.  That was 30 years ag=
o, and it was a huge milestone in the journey toward the Internet as we kno=
w it.

You can see the transition plan.  Like so many other historic networking do=
cuments, it is an RFC.  See http://www.rfc-editor.org/rfc/rfc801.txt

Happy New Year,
  Russ


--_000_EAD7068FAF9D4417A06861DD75A28FB9ciscocom_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
</head>
<body dir=3D"auto">
<div>Happy slow start of 2013!<br>
<br>
Sent from my iPad</div>
<div><br>
On 31 dec. 2012, at 18:21, &quot;IETF Chair&quot; &lt;<a href=3D"mailto:cha=
ir@ietf.org">chair@ietf.org</a>&gt; wrote:<br>
<br>
</div>
<blockquote type=3D"cite">
<div>
<div style=3D"font-family: arial, helvetica, sans-serif; font-size: 10pt">
<div dir=3D"ltr">
<div class=3D"gmail_default" style=3D"">Happy New Year. &nbsp;It is already=
 2013 in some part of the world.</div>
<div class=3D"gmail_default" style=3D""><br>
</div>
<div class=3D"gmail_default" style=3D"">The ARPANET transitioned to TCP/IP =
on 1 January 1983. &nbsp;That was 30 years ago, and it was a huge milestone=
 in the journey toward the Internet as we know it.</div>
<div class=3D"gmail_default" style=3D""><br>
</div>
<div class=3D"gmail_default" style=3D"">You can see the transition plan. &n=
bsp;Like so many other historic networking documents, it is an RFC. &nbsp;S=
ee
<a href=3D"http://www.rfc-editor.org/rfc/rfc801.txt">http://www.rfc-editor.=
org/rfc/rfc801.txt</a>&nbsp;</div>
<div class=3D"gmail_default" style=3D""><br>
</div>
<div class=3D"gmail_default" style=3D"">Happy New Year,&nbsp;</div>
<div class=3D"gmail_default" style=3D"">&nbsp; Russ</div>
<div class=3D"gmail_default" style=3D""><br>
</div>
</div>
</div>
</div>
</blockquote>
</body>
</html>

--_000_EAD7068FAF9D4417A06861DD75A28FB9ciscocom_--

From nabil.n.bitar@verizon.com  Wed Jan  2 08:30:27 2013
Return-Path: <nabil.n.bitar@verizon.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6B0EA21F8652; Wed,  2 Jan 2013 08:30:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.598
X-Spam-Level: 
X-Spam-Status: No, score=-3.598 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
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 n7uEb1RXd2An; Wed,  2 Jan 2013 08:30:26 -0800 (PST)
Received: from fldsmtpe03.verizon.com (fldsmtpe03.verizon.com [140.108.26.142]) by ietfa.amsl.com (Postfix) with ESMTP id 8E49D21F8650; Wed,  2 Jan 2013 08:30:25 -0800 (PST)
X-IronPort-Anti-Spam-Filtered: false
Received: from unknown (HELO fldsmtpi03.verizon.com) ([166.68.71.145]) by fldsmtpe03.verizon.com with ESMTP; 02 Jan 2013 16:30:24 +0000
From: "Bitar, Nabil N" <nabil.n.bitar@verizon.com>
To: "Black, David" <david.black@emc.com>, "dinmohan@hotmail.com" <dinmohan@hotmail.com>, "Bitar, Nabil N" <nabil.n.bitar@verizon.com>, "sajassi@cisco.com" <sajassi@cisco.com>, "gen-art@ietf.org" <gen-art@ietf.org>
X-IronPort-AV: E=Sophos;i="4.84,396,1355097600";  d="scan'208,217";a="389401940"
Received: from fldp1lumxc7hb05.verizon.com (HELO FLDP1LUMXC7HB05.us.one.verizon.com) ([166.68.75.87]) by fldsmtpi03.verizon.com with ESMTP; 02 Jan 2013 16:30:24 +0000
Received: from fldp1lumxc7v63.us.one.verizon.com ([166.68.45.45]) by FLDP1LUMXC7HB05.us.one.verizon.com ([166.68.75.87]) with mapi; Wed, 2 Jan 2013 11:30:23 -0500
Date: Wed, 2 Jan 2013 11:28:41 -0500
Subject: Re: Gen-ART review of draft-ietf-pwe3-mpls-eth-oam-iwk-06
Thread-Topic: Gen-ART review of draft-ietf-pwe3-mpls-eth-oam-iwk-06
Thread-Index: Ac3pBnav5FvEKm/XSt61rsAl/DM1Ng==
Message-ID: <CD08F2D5.6DC40%nabil.n.bitar@verizon.com>
In-Reply-To: <7EB1738E-2545-4A33-B5C0-548630347568@mimectl>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.2.3.120616
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_CD08F2D56DC40nabilnbitarverizoncom_"
MIME-Version: 1.0
X-Mailman-Approved-At: Wed, 02 Jan 2013 08:54:30 -0800
Cc: "pwe3@ietf.org" <pwe3@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Jan 2013 16:30:27 -0000

--_000_CD08F2D56DC40nabilnbitarverizoncom_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi Dave,
Sorry for a late reply addressing your comments. Please, see inline.

Thanks,
Nabil

From: "Black, David" <david.black@emc.com<mailto:david.black@emc.com>>
Date: Monday, August 20, 2012 8:57 PM
To: "dinmohan@hotmail.com<mailto:dinmohan@hotmail.com>" <dinmohan@hotmail.c=
om<mailto:dinmohan@hotmail.com>>, "Bitar, Nabil N" <nabil.n.bitar@one.veriz=
on.com<mailto:nabil.n.bitar@one.verizon.com>>, Sagessi <sajassi@cisco.com<m=
ailto:sajassi@cisco.com>>, "gen-art@ietf.org<mailto:gen-art@ietf.org>" <gen=
-art@ietf.org<mailto:gen-art@ietf.org>>
Cc: "Black, David" <david.black@emc.com<mailto:david.black@emc.com>>, "pwe3=
@ietf.org<mailto:pwe3@ietf.org>" <pwe3@ietf.org<mailto:pwe3@ietf.org>>, "ie=
tf@ietf.org<mailto:ietf@ietf.org>" <ietf@ietf.org<mailto:ietf@ietf.org>>
Subject: Gen-ART review of draft-ietf-pwe3-mpls-eth-oam-iwk-06

I am the assigned Gen-ART reviewer for this draft. For background on Gen-AR=
T, please
see the FAQ at <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

Please resolve these comments along with any other Last Call comments you m=
ay receive.

Document: draft-ietf-pwe3-mpls-eth-oam-iwk-06
Reviewer: David L. Black
Review Date: August 20, 2012
IETF LC End Date: August 20, 2012

Summary:
This draft is basically ready for publication, but has nits that
should be fixed before publication.

<NB> Thanks.



This draft covers defect behavior for Ethernet pseudowires,

including defect state mapping and PE defect reporting behavior.

The draft is generally in good shape.  I found a few minor nits.



1) The draft uses a lot of acronyms - while each acronym appears to

be expanded on first use, an additional section near the start of the

draft listing all of them would be helpful.

<NB> Done.



2) There's a typo in the first paragraph of section 2:



     covers the following Ethernet OAM (Opertaions, Administration and



Opertaions -> Operations.

<NB> Thanks. Done.



3) The following normative reference is incomplete - please add additional

information that will enable a reader to locate the referenced document:



     [MEF16] "Ethernet Local Management Interface", MEF16, January 2006.

[MEF16] "Ethernet Local Management Interface", Metro Ethernet Forum Technic=
al Specification MEF16, January 2006.

<NB> changed it to :



4) idnits 2.12.13 did not like the pagination:



  =3D=3D The page length should not exceed 58 lines per page, but there was=
 22
     longer pages, the longest (page 1) being 61 lines

<NB> That will be fixed.

Thanks,
--David
----------------------------------------------------
David L. Black, Distinguished Engineer
EMC Corporation, 176 South St., Hopkinton, MA  01748
+1 (508) 293-7953             FAX: +1 (508) 293-7786
david.black@emc.com<mailto:david.black@emc.com>        Mobile: +1 (978) 394=
-7754
----------------------------------------------------

--_000_CD08F2D56DC40nabilnbitarverizoncom_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html><head><meta name=3D"Title" content=3D""><meta name=3D"Keywords" conte=
nt=3D""><meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Du=
tf-8"><meta name=3D"ProgId" content=3D"Word.Document"><meta name=3D"Generat=
or" content=3D"Microsoft Word 14"><meta name=3D"Originator" content=3D"Micr=
osoft Word 14"><link rel=3D"File-List" href=3D"file://localhost/Users/admin=
/Library/Caches/TemporaryItems/msoclip/0/clip_filelist.xml"><!--[if gte mso=
 9]><xml>
 <o:DocumentProperties>
  <o:Revision>0</o:Revision>
  <o:TotalTime>0</o:TotalTime>
  <o:Pages>1</o:Pages>
  <o:Words>17</o:Words>
  <o:Characters>97</o:Characters>
  <o:Company>Verizon</o:Company>
  <o:Lines>1</o:Lines>
  <o:Paragraphs>1</o:Paragraphs>
  <o:CharactersWithSpaces>113</o:CharactersWithSpaces>
  <o:Version>14.0</o:Version>
 </o:DocumentProperties>
 <o:OfficeDocumentSettings>
  <o:RelyOnVML/>
  <o:AllowPNG/>
 </o:OfficeDocumentSettings>
</xml><![endif]--><link rel=3D"themeData" href=3D"file://localhost/Users/ad=
min/Library/Caches/TemporaryItems/msoclip/0/clip_themedata.xml"><!--[if gte=
 mso 9]><xml>
 <w:WordDocument>
  <w:View>Normal</w:View>
  <w:Zoom>0</w:Zoom>
  <w:TrackMoves/>
  <w:TrackFormatting/>
  <w:PunctuationKerning/>
  <w:ValidateAgainstSchemas/>
  <w:SaveIfXMLInvalid>false</w:SaveIfXMLInvalid>
  <w:IgnoreMixedContent>false</w:IgnoreMixedContent>
  <w:AlwaysShowPlaceholderText>false</w:AlwaysShowPlaceholderText>
  <w:DoNotPromoteQF/>
  <w:LidThemeOther>EN-US</w:LidThemeOther>
  <w:LidThemeAsian>JA</w:LidThemeAsian>
  <w:LidThemeComplexScript>X-NONE</w:LidThemeComplexScript>
  <w:Compatibility>
   <w:BreakWrappedTables/>
   <w:SnapToGridInCell/>
   <w:WrapTextWithPunct/>
   <w:UseAsianBreakRules/>
   <w:DontGrowAutofit/>
   <w:SplitPgBreakAndParaMark/>
   <w:EnableOpenTypeKerning/>
   <w:DontFlipMirrorIndents/>
   <w:OverrideTableStyleHps/>
  </w:Compatibility>
  <m:mathPr>
   <m:mathFont m:val=3D"Cambria Math"/>
   <m:brkBin m:val=3D"before"/>
   <m:brkBinSub m:val=3D"&#45;-"/>
   <m:smallFrac m:val=3D"off"/>
   <m:dispDef/>
   <m:lMargin m:val=3D"0"/>
   <m:rMargin m:val=3D"0"/>
   <m:defJc m:val=3D"centerGroup"/>
   <m:wrapIndent m:val=3D"1440"/>
   <m:intLim m:val=3D"subSup"/>
   <m:naryLim m:val=3D"undOvr"/>
  </m:mathPr></w:WordDocument>
</xml><![endif]--><!--[if gte mso 9]><xml>
 <w:LatentStyles DefLockedState=3D"false" DefUnhideWhenUsed=3D"true"
  DefSemiHidden=3D"true" DefQFormat=3D"false" DefPriority=3D"99"
  LatentStyleCount=3D"276">
  <w:LsdException Locked=3D"false" Priority=3D"0" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Normal"/>
  <w:LsdException Locked=3D"false" Priority=3D"9" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"heading 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" Name=3D"=
heading 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" Name=3D"=
heading 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" Name=3D"=
heading 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" Name=3D"=
heading 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" Name=3D"=
heading 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" Name=3D"=
heading 7"/>
  <w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" Name=3D"=
heading 8"/>
  <w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" Name=3D"=
heading 9"/>
  <w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 7"/>
  <w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 8"/>
  <w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 9"/>
  <w:LsdException Locked=3D"false" Priority=3D"35" QFormat=3D"true" Name=3D=
"caption"/>
  <w:LsdException Locked=3D"false" Priority=3D"10" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Title"/>
  <w:LsdException Locked=3D"false" Priority=3D"1" Name=3D"Default Paragraph=
 Font"/>
  <w:LsdException Locked=3D"false" Priority=3D"11" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Subtitle"/>
  <w:LsdException Locked=3D"false" Priority=3D"22" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Strong"/>
  <w:LsdException Locked=3D"false" Priority=3D"20" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Emphasis"/>
  <w:LsdException Locked=3D"false" Priority=3D"59" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Table Grid"/>
  <w:LsdException Locked=3D"false" UnhideWhenUsed=3D"false" Name=3D"Placeho=
lder Text"/>
  <w:LsdException Locked=3D"false" Priority=3D"1" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"No Spacing"/>
  <w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light Shading"/>
  <w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light List"/>
  <w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light Grid"/>
  <w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium List 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium List 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Dark List"/>
  <w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful Shading"/>
  <w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful List"/>
  <w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful Grid"/>
  <w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light List Accent 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 1"/>
  <w:LsdException Locked=3D"false" UnhideWhenUsed=3D"false" Name=3D"Revisio=
n"/>
  <w:LsdException Locked=3D"false" Priority=3D"34" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"List Paragraph"/>
  <w:LsdException Locked=3D"false" Priority=3D"29" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Quote"/>
  <w:LsdException Locked=3D"false" Priority=3D"30" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Intense Quote"/>
  <w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light List Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light List Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light List Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light List Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light List Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"19" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Subtle Emphasis"/>
  <w:LsdException Locked=3D"false" Priority=3D"21" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Intense Emphasis"/>
  <w:LsdException Locked=3D"false" Priority=3D"31" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Subtle Reference"/>
  <w:LsdException Locked=3D"false" Priority=3D"32" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Intense Reference"/>
  <w:LsdException Locked=3D"false" Priority=3D"33" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Book Title"/>
  <w:LsdException Locked=3D"false" Priority=3D"37" Name=3D"Bibliography"/>
  <w:LsdException Locked=3D"false" Priority=3D"39" QFormat=3D"true" Name=3D=
"TOC Heading"/>
 </w:LatentStyles>
</xml><![endif]--><style>
<!--
 /* Font Definitions */
@font-face
	{font-family:"Courier New";
	panose-1:2 7 3 9 2 2 5 2 4 4;
	mso-font-charset:0;
	mso-generic-font-family:auto;
	mso-font-pitch:variable;
	mso-font-signature:-536859905 -1073711037 9 0 511 0;}
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;
	mso-font-charset:0;
	mso-generic-font-family:auto;
	mso-font-pitch:variable;
	mso-font-signature:-536870145 1107305727 0 0 415 0;}
@font-face
	{font-family:Batang;
	mso-font-alt:??;
	mso-font-charset:129;
	mso-generic-font-family:roman;
	mso-font-pitch:variable;
	mso-font-signature:-1342176593 1775729915 48 0 524447 0;}
 /* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{mso-style-unhide:no;
	mso-style-qformat:yes;
	mso-style-parent:"";
	margin-top:0in;
	margin-right:0in;
	margin-bottom:12.0pt;
	margin-left:.3in;
	line-height:12.0pt;
	mso-line-height-rule:exactly;
	mso-pagination:widow-orphan;
	tab-stops:.3in .6in .9in 1.2in 1.5in 1.8in 2.1in 2.4in 2.7in 3.0in 3.3in 3=
.6in 3.9in 4.2in 4.5in 4.8in 5.1in 5.4in 5.7in 6.0in 6.3in 6.6in 6.9in;
	font-size:12.0pt;
	font-family:"Courier New";
	mso-fareast-font-family:Batang;}
.MsoChpDefault
	{mso-style-type:export-only;
	mso-default-props:yes;
	font-size:10.0pt;
	mso-ansi-font-size:10.0pt;
	mso-bidi-font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;
	mso-header-margin:.5in;
	mso-footer-margin:.5in;
	mso-paper-source:0;}
div.WordSection1
	{page:WordSection1;}
-->
</style><!--[if gte mso 10]>
<style>
 /* Style Definitions */
table.MsoNormalTable
	{mso-style-name:"Table Normal";
	mso-tstyle-rowband-size:0;
	mso-tstyle-colband-size:0;
	mso-style-noshow:yes;
	mso-style-priority:99;
	mso-style-parent:"";
	mso-padding-alt:0in 5.4pt 0in 5.4pt;
	mso-para-margin:0in;
	mso-para-margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:10.0pt;
	font-family:"Times New Roman";}
</style>
<![endif]--></head><body style=3D"word-wrap: break-word; -webkit-nbsp-mode:=
 space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-si=
ze: 14px; font-family: Calibri, sans-serif; "><div><font class=3D"Apple-sty=
le-span" face=3D"Calibri,sans-serif">Hi Dave,</font></div><div><font class=
=3D"Apple-style-span" face=3D"Calibri,sans-serif">Sorry for a late reply ad=
dressing your comments. Please, see inline.</font></div><div><font class=3D=
"Apple-style-span" face=3D"Calibri,sans-serif"><br></font></div><div><font =
class=3D"Apple-style-span" face=3D"Calibri,sans-serif">Thanks,</font></div>=
<div><font class=3D"Apple-style-span" face=3D"Calibri,sans-serif">Nabil</fo=
nt></div><div style=3D"color: rgb(0, 0, 0); font-family: Calibri, sans-seri=
f; font-size: 14px; "><br></div><span id=3D"OLK_SRC_BODY_SECTION" style=3D"=
color: rgb(0, 0, 0); font-size: 14px; font-family: Calibri, sans-serif; "><=
div style=3D"font-family:Calibri; font-size:11pt; text-align:left; color:bl=
ack; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: =
0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; =
BORDER-RIGHT: medium none; PADDING-TOP: 3pt"><span style=3D"font-weight:bol=
d">From: </span> "Black, David" &lt;<a href=3D"mailto:david.black@emc.com">=
david.black@emc.com</a>&gt;<br><span style=3D"font-weight:bold">Date: </spa=
n> Monday, August 20, 2012 8:57 PM<br><span style=3D"font-weight:bold">To: =
</span> "<a href=3D"mailto:dinmohan@hotmail.com">dinmohan@hotmail.com</a>" =
&lt;<a href=3D"mailto:dinmohan@hotmail.com">dinmohan@hotmail.com</a>&gt;, "=
Bitar, Nabil N" &lt;<a href=3D"mailto:nabil.n.bitar@one.verizon.com">nabil.=
n.bitar@one.verizon.com</a>&gt;, Sagessi &lt;<a href=3D"mailto:sajassi@cisc=
o.com">sajassi@cisco.com</a>&gt;, "<a href=3D"mailto:gen-art@ietf.org">gen-=
art@ietf.org</a>" &lt;<a href=3D"mailto:gen-art@ietf.org">gen-art@ietf.org<=
/a>&gt;<br><span style=3D"font-weight:bold">Cc: </span> "Black, David" &lt;=
<a href=3D"mailto:david.black@emc.com">david.black@emc.com</a>&gt;, "<a hre=
f=3D"mailto:pwe3@ietf.org">pwe3@ietf.org</a>" &lt;<a href=3D"mailto:pwe3@ie=
tf.org">pwe3@ietf.org</a>&gt;, "<a href=3D"mailto:ietf@ietf.org">ietf@ietf.=
org</a>" &lt;<a href=3D"mailto:ietf@ietf.org">ietf@ietf.org</a>&gt;<br><spa=
n style=3D"font-weight:bold">Subject: </span> Gen-ART review of draft-ietf-=
pwe3-mpls-eth-oam-iwk-06<br></div><div><br></div><div dir=3D"ltr"><style ti=
tle=3D"owaParaStyle"><!--P {
	MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px
}
--></style><div ocsi=3D"x"><div dir=3D"ltr"><font color=3D"#000000" size=3D=
"2" face=3D"Courier New">I am the assigned Gen-ART reviewer for this draft.=
 For background on Gen-ART, please<br>see the FAQ at &lt;<a href=3D"http://=
wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq" target=3D"_blank">http://=
wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq</a>&gt;.<br><br>Please res=
olve these comments along with any other Last Call comments you may receive=
.<br><br>Document: <span lang=3D"EN">draft-ietf-pwe3-mpls-eth-oam-iwk-06</s=
pan></font></div><div dir=3D"ltr"><font color=3D"#000000" size=3D"2" face=
=3D"Courier New"><span lang=3D"EN"></span>Reviewer: David L. Black<br>Revie=
w Date: August 20, 2012<br>IETF LC End Date: August 20, 2012<br><br>Summary=
:<br>This draft is basically ready for publication, but has nits that<br>sh=
ould be fixed before publication.</font></div></div></div></span><div><br><=
/div><div>&lt;NB&gt; Thanks.</div><span id=3D"OLK_SRC_BODY_SECTION" style=
=3D"color: rgb(0, 0, 0); font-size: 14px; font-family: Calibri, sans-serif;=
 "><div dir=3D"ltr"><div ocsi=3D"x"><p><font color=3D"#000000" size=3D"2" f=
ace=3D"Courier New"><font face=3D"courier new"></font></font>&nbsp;</p><p><=
font color=3D"#000000" size=3D"2" face=3D"Courier New"><font face=3D"courie=
r new">This draft covers defect behavior for Ethernet pseudowires<a target=
=3D"_blank"></a>,</font></font></p><p><font color=3D"#000000" size=3D"2" fa=
ce=3D"Courier New"><font face=3D"courier new">including defect state mappin=
g and PE defect reporting behavior.</font></font></p><p><font color=3D"#000=
000" size=3D"2" face=3D"Courier New"><font face=3D"courier new">The draft i=
s generally in good shape.&nbsp; I found a few minor nits.</font></font></p=
><p><font size=3D"2" face=3D"courier new"></font>&nbsp;</p><p><font size=3D=
"2" face=3D"courier new">1) The draft uses a lot of acronyms - while each a=
cronym appears to</font></p><p><font size=3D"2" face=3D"Courier New">b<font=
 face=3D"courier new">e expanded on first use, an additional section near t=
he start of the</font></font></p><p><font face=3D"Courier New"><font face=
=3D"courier new"><font size=3D"2"><font face=3D"courier new">draft listing<=
/font> all of them </font></font></font><font size=3D"2" face=3D"courier ne=
w">would be helpful.</font></p></div></div></span><div><br></div><div>&lt;N=
B&gt; Done.</div><span id=3D"OLK_SRC_BODY_SECTION" style=3D"color: rgb(0, 0=
, 0); font-size: 14px; font-family: Calibri, sans-serif; "><div dir=3D"ltr"=
><div ocsi=3D"x"><p><font size=3D"2" face=3D"courier new"></font>&nbsp;</p>=
<p><font size=3D"2" face=3D"courier new">2) There's&nbsp;a typo in the firs=
t paragraph of section 2:</font></p><p><font size=3D"2" face=3D"courier new=
"></font>&nbsp;</p><font color=3D"#000000"><div dir=3D"ltr"><font size=3D"2=
"><span lang=3D"EN"><p><font face=3D"Courier New">&nbsp;&nbsp;&nbsp; &nbsp;=
covers the following Ethernet OAM (Opertaions<a target=3D"_blank"></a>, Adm=
inistration and </font></p><p><font face=3D"courier new"></font>&nbsp;</p><=
p><font face=3D"courier new"><a target=3D"_blank"></a><font face=3D"courier=
 new">Opertaions</font>&nbsp;-&gt; Operations.</font></p></span></font></di=
v></font></div></div></span><div><br></div><div>&lt;NB&gt; Thanks. Done.</d=
iv><span id=3D"OLK_SRC_BODY_SECTION" style=3D"color: rgb(0, 0, 0); font-siz=
e: 14px; font-family: Calibri, sans-serif; "><div dir=3D"ltr"><div ocsi=3D"=
x"><font color=3D"#000000"><div dir=3D"ltr"><font size=3D"2"><span lang=3D"=
EN"><p><font face=3D"courier new"></font>&nbsp;</p><p><font face=3D"courier=
 new">3) The following normative reference is incomplete - please add addit=
ional</font></p><p><font face=3D"courier new">information that will enable =
a reader to locate the referenced document:</font></p><p><font face=3D"cour=
ier new"></font>&nbsp;</p><font face=3D"courier new"><span lang=3D"EN"><p>&=
nbsp;&nbsp;&nbsp; &nbsp;[MEF16] "Ethernet Local Management Interface", MEF1=
6, January 2006.</p></span></font></span></font></div></font></div></div></=
span><div><br></div><span id=3D"OLK_SRC_BODY_SECTION" style=3D"color: rgb(0=
, 0, 0); font-family: Calibri, sans-serif; "><div dir=3D"ltr"><div ocsi=3D"=
x"><font color=3D"#000000"><div dir=3D"ltr"><span class=3D"Apple-style-span=
" style=3D"font-size: 14px; line-height: 16px; font-family: 'Courier New'; =
">[MEF16]
"Ethernet Local Management Interface", Metro Ethernet Forum Technical
Specification MEF16, January 2006.</span><font><span lang=3D"EN"><font face=
=3D"courier new"><span lang=3D"EN"><p style=3D"font-size: 14px; "><font fac=
e=3D"courier new"></font>&lt;NB&gt; changed it to :&nbsp;</p><p><!--[if gte=
 mso 9]><xml>
 <o:DocumentProperties>
  <o:Revision>0</o:Revision>
  <o:TotalTime>0</o:TotalTime>
  <o:Pages>1</o:Pages>
  <o:Words>17</o:Words>
  <o:Characters>97</o:Characters>
  <o:Company>Verizon</o:Company>
  <o:Lines>1</o:Lines>
  <o:Paragraphs>1</o:Paragraphs>
  <o:CharactersWithSpaces>113</o:CharactersWithSpaces>
  <o:Version>14.0</o:Version>
 </o:DocumentProperties>
 <o:OfficeDocumentSettings>
  <o:RelyOnVML/>
  <o:AllowPNG/>
 </o:OfficeDocumentSettings>
</xml><![endif]--><!--[if gte mso 9]><xml>
 <w:WordDocument>
  <w:View>Normal</w:View>
  <w:Zoom>0</w:Zoom>
  <w:TrackMoves/>
  <w:TrackFormatting/>
  <w:PunctuationKerning/>
  <w:ValidateAgainstSchemas/>
  <w:SaveIfXMLInvalid>false</w:SaveIfXMLInvalid>
  <w:IgnoreMixedContent>false</w:IgnoreMixedContent>
  <w:AlwaysShowPlaceholderText>false</w:AlwaysShowPlaceholderText>
  <w:DoNotPromoteQF/>
  <w:LidThemeOther>EN-US</w:LidThemeOther>
  <w:LidThemeAsian>JA</w:LidThemeAsian>
  <w:LidThemeComplexScript>X-NONE</w:LidThemeComplexScript>
  <w:Compatibility>
   <w:BreakWrappedTables/>
   <w:SnapToGridInCell/>
   <w:WrapTextWithPunct/>
   <w:UseAsianBreakRules/>
   <w:DontGrowAutofit/>
   <w:SplitPgBreakAndParaMark/>
   <w:EnableOpenTypeKerning/>
   <w:DontFlipMirrorIndents/>
   <w:OverrideTableStyleHps/>
  </w:Compatibility>
  <m:mathPr>
   <m:mathFont m:val=3D"Cambria Math"/>
   <m:brkBin m:val=3D"before"/>
   <m:brkBinSub m:val=3D"&#45;-"/>
   <m:smallFrac m:val=3D"off"/>
   <m:dispDef/>
   <m:lMargin m:val=3D"0"/>
   <m:rMargin m:val=3D"0"/>
   <m:defJc m:val=3D"centerGroup"/>
   <m:wrapIndent m:val=3D"1440"/>
   <m:intLim m:val=3D"subSup"/>
   <m:naryLim m:val=3D"undOvr"/>
  </m:mathPr></w:WordDocument>
</xml><![endif]--><!--[if gte mso 9]><xml>
 <w:LatentStyles DefLockedState=3D"false" DefUnhideWhenUsed=3D"true"
  DefSemiHidden=3D"true" DefQFormat=3D"false" DefPriority=3D"99"
  LatentStyleCount=3D"276">
  <w:LsdException Locked=3D"false" Priority=3D"0" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Normal"/>
  <w:LsdException Locked=3D"false" Priority=3D"9" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"heading 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" Name=3D"=
heading 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" Name=3D"=
heading 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" Name=3D"=
heading 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" Name=3D"=
heading 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" Name=3D"=
heading 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" Name=3D"=
heading 7"/>
  <w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" Name=3D"=
heading 8"/>
  <w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" Name=3D"=
heading 9"/>
  <w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 7"/>
  <w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 8"/>
  <w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 9"/>
  <w:LsdException Locked=3D"false" Priority=3D"35" QFormat=3D"true" Name=3D=
"caption"/>
  <w:LsdException Locked=3D"false" Priority=3D"10" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Title"/>
  <w:LsdException Locked=3D"false" Priority=3D"1" Name=3D"Default Paragraph=
 Font"/>
  <w:LsdException Locked=3D"false" Priority=3D"11" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Subtitle"/>
  <w:LsdException Locked=3D"false" Priority=3D"22" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Strong"/>
  <w:LsdException Locked=3D"false" Priority=3D"20" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Emphasis"/>
  <w:LsdException Locked=3D"false" Priority=3D"59" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Table Grid"/>
  <w:LsdException Locked=3D"false" UnhideWhenUsed=3D"false" Name=3D"Placeho=
lder Text"/>
  <w:LsdException Locked=3D"false" Priority=3D"1" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"No Spacing"/>
  <w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light Shading"/>
  <w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light List"/>
  <w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light Grid"/>
  <w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium List 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium List 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Dark List"/>
  <w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful Shading"/>
  <w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful List"/>
  <w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful Grid"/>
  <w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light List Accent 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 1"/>
  <w:LsdException Locked=3D"false" UnhideWhenUsed=3D"false" Name=3D"Revisio=
n"/>
  <w:LsdException Locked=3D"false" Priority=3D"34" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"List Paragraph"/>
  <w:LsdException Locked=3D"false" Priority=3D"29" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Quote"/>
  <w:LsdException Locked=3D"false" Priority=3D"30" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Intense Quote"/>
  <w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light List Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light List Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light List Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light List Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light List Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"19" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Subtle Emphasis"/>
  <w:LsdException Locked=3D"false" Priority=3D"21" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Intense Emphasis"/>
  <w:LsdException Locked=3D"false" Priority=3D"31" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Subtle Reference"/>
  <w:LsdException Locked=3D"false" Priority=3D"32" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Intense Reference"/>
  <w:LsdException Locked=3D"false" Priority=3D"33" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Book Title"/>
  <w:LsdException Locked=3D"false" Priority=3D"37" Name=3D"Bibliography"/>
  <w:LsdException Locked=3D"false" Priority=3D"39" QFormat=3D"true" Name=3D=
"TOC Heading"/>
 </w:LatentStyles>
</xml><![endif]--><!--[if gte mso 10]>
<style>
 /* Style Definitions */
table.MsoNormalTable
	{mso-style-name:"Table Normal";
	mso-tstyle-rowband-size:0;
	mso-tstyle-colband-size:0;
	mso-style-noshow:yes;
	mso-style-priority:99;
	mso-style-parent:"";
	mso-padding-alt:0in 5.4pt 0in 5.4pt;
	mso-para-margin:0in;
	mso-para-margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:10.0pt;
	font-family:"Times New Roman";}
</style>
<![endif]--><!--StartFragment--><!--EndFragment-->&nbsp;</p><p style=3D"fon=
t-size: 14px; "><font face=3D"courier new"><font face=3D"courier new">4)&nb=
sp;idnits<a target=3D"_blank"></a> 2.12.13 did not like the pagination:</fo=
nt></font></p><p style=3D"font-size: 14px; ">&nbsp;</p></span></font></span=
></font><p style=3D"font-size: 14px; "><font size=3D"2"><font face=3D"couri=
er new"><font face=3D"courier new">&nbsp; =3D=3D The page length should not=
 exceed 58 lines per page, but there was 22<br>&nbsp;&nbsp;&nbsp;&nbsp; lon=
ger pages, the longest (page 1) being 61 lines</font></font></font></p></di=
v></font></div></div></span><div>&lt;NB&gt; That will be fixed.</div><span =
id=3D"OLK_SRC_BODY_SECTION" style=3D"color: rgb(0, 0, 0); font-family: Cali=
bri, sans-serif; "><div dir=3D"ltr"><div ocsi=3D"x"><div dir=3D"ltr" style=
=3D"font-size: 14px; "><font face=3D"Courier New"><font color=3D"#000000" s=
ize=3D"2">&nbsp;</font></font></div><div style=3D"font-size: 14px; "><font =
size=3D"2" face=3D"Courier New">Thanks,</font></div><div style=3D"font-size=
: 14px; "><font size=3D"2" face=3D"courier new">--David</font></div><div st=
yle=3D"font-size: 14px; "><font face=3D"Courier New"><font size=3D"2">-----=
-----------------------------------------------<br>David L. Black, Distingu=
ished Engineer<br>EMC Corporation, 176 South St., Hopkinton, MA&nbsp; 01748=
<br>+1 (508) 293-7953&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp; FAX: +1 (508) 293-7786<br></font><font size=3D"2"><a hre=
f=3D"mailto:david.black@emc.com" target=3D"_blank"><font size=3D"2">david.b=
lack@emc.com</font></a><a target=3D"_blank"></a></font><font size=3D"2">&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Mobile: +1 (978) 394-7754<br>------=
----------------------------------------------<br></font></font></div></div=
></div></span></body></html>

--_000_CD08F2D56DC40nabilnbitarverizoncom_--

From Chris.Dearlove@baesystems.com  Wed Jan  2 09:34:16 2013
Return-Path: <Chris.Dearlove@baesystems.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 19BD721F86A8 for <ietf@ietfa.amsl.com>; Wed,  2 Jan 2013 09:34:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 PoCVEM8Fc25W for <ietf@ietfa.amsl.com>; Wed,  2 Jan 2013 09:34:15 -0800 (PST)
Received: from ukmta3.baesystems.com (ukmta3.baesystems.com [20.133.40.55]) by ietfa.amsl.com (Postfix) with ESMTP id 05C1C21F86A2 for <ietf@ietf.org>; Wed,  2 Jan 2013 09:34:14 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.84,397,1355097600"; d="scan'208";a="252597345"
Received: from unknown (HELO baemasodc004.greenlnk.net) ([10.108.36.11]) by Baemasodc001ir.sharelnk.net with ESMTP; 02 Jan 2013 17:34:13 +0000
Received: from baemasodc005.greenlnk.net ([10.108.52.29]) by baemasodc004.greenlnk.net (Switch-3.4.4/Switch-3.4.4) with ESMTP id r02HYDhu016709 for <ietf@ietf.org>; Wed, 2 Jan 2013 17:34:13 GMT
X-IronPort-AV: E=McAfee;i="5400,1158,6942"; a="2280082"
Received: from glkxh0005v.greenlnk.net ([10.109.2.36]) by baemasodc005.greenlnk.net with ESMTP; 02 Jan 2013 17:34:13 +0000
Received: from GLKXM0002V.GREENLNK.net ([169.254.2.7]) by GLKXH0005V.GREENLNK.net ([10.109.2.36]) with mapi id 14.02.0309.002; Wed, 2 Jan 2013 17:34:13 +0000
From: "Dearlove, Christopher (UK)" <Chris.Dearlove@baesystems.com>
To: "Carlos M. Martinez" <carlosm3011@gmail.com>, Phillip Hallam-Baker <hallam@gmail.com>
Subject: RE: WCIT outcome?
Thread-Topic: WCIT outcome?
Thread-Index: AQHN5Y2JvnLRPwHtzka5eKT9kbUSBJgvl3qAgAB/ZYCABfyigIAAPvnQ
Date: Wed, 2 Jan 2013 17:34:13 +0000
Message-ID: <B31EEDDDB8ED7E4A93FDF12A4EECD30D24FE4DAF@GLKXM0002V.GREENLNK.net>
References: <CAMm+Lwh2cHRY+Dk2_SDtZZmUbPcgRpP89u3DHUcniJDrKrX_pw@mail.gmail.com> <CAMzo+1a0-90dnjnvs48a9DcNN9DY_edF5hH0__4XRuCaLHtL6Q@mail.gmail.com> <CAMm+LwjzjLc2-=4EdxwHOi21B3dOBUohYc5hhXZHL_Pk+iBBmQ@mail.gmail.com> <50E439C5.2020808@gmail.com>
In-Reply-To: <50E439C5.2020808@gmail.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.109.62.6]
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: IETF Discussion Mailing List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Jan 2013 17:34:16 -0000

Carlos M. Martinez=20
> Radio spectrum allocation was a critical task at the time (it still is,
> although the world doesn't depend that much on it anymore),

Given the ever increasing number of mobile devices, one could argue that th=
e world
has never been more dependent on radio spectrum allocation. It's still not =
that long since
the UK Chancellor of the Exchequer made over =A320 billion from selling spe=
ctrum, something
possible since international treaties had agreed on its purpose for 3G comm=
unications.

--=20
Christopher Dearlove
Senior Principal Engineer, Communications Group
Communications, Networks and Image Analysis Capability
BAE Systems Advanced Technology Centre
West Hanningfield Road, Great Baddow, Chelmsford, CM2 8HN, UK
Tel: +44 1245 242194=A0|  Fax: +44 1245 242124
chris.dearlove@baesystems.com | http://www.baesystems.com

BAE Systems (Operations) Limited
Registered Office: Warwick House, PO Box 87, Farnborough Aerospace Centre, =
Farnborough, Hants, GU14 6YU, UK
Registered in England & Wales No: 1996687


********************************************************************
This email and any attachments are confidential to the intended
recipient and may also be privileged. If you are not the intended
recipient please delete it from your system and notify the sender.
You should not copy it or use it for any purpose nor disclose or
distribute its contents to any other person.
********************************************************************


From jnc@mercury.lcs.mit.edu  Wed Jan  2 09:58:40 2013
Return-Path: <jnc@mercury.lcs.mit.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7074A21F874B for <ietf@ietfa.amsl.com>; Wed,  2 Jan 2013 09:58:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.28
X-Spam-Level: 
X-Spam-Status: No, score=-6.28 tagged_above=-999 required=5 tests=[AWL=0.318,  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 R6vBVwXgd47A for <ietf@ietfa.amsl.com>; Wed,  2 Jan 2013 09:58:40 -0800 (PST)
Received: from mercury.lcs.mit.edu (mercury.lcs.mit.edu [18.26.0.122]) by ietfa.amsl.com (Postfix) with ESMTP id EEB9921F8745 for <ietf@ietf.org>; Wed,  2 Jan 2013 09:58:39 -0800 (PST)
Received: by mercury.lcs.mit.edu (Postfix, from userid 11178) id 2DDAE18C0BB; Wed,  2 Jan 2013 12:58:39 -0500 (EST)
To: ietf@ietf.org
Subject: Re: WCIT outcome?
Message-Id: <20130102175839.2DDAE18C0BB@mercury.lcs.mit.edu>
Date: Wed,  2 Jan 2013 12:58:39 -0500 (EST)
From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
Cc: jnc@mercury.lcs.mit.edu
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Jan 2013 17:58:40 -0000

    > From: John Day <jeanjour@comcast.net>

    > I remember when a modem came with an 'acoustic coupler' because
    > connecting it directly to the phone line was illegal.
    > No, there was nothing illegal about it. The reason for acoustic
    > couplers was that the RJ-11 had been invented yet and it was a pain to
    > unscrew the box on the wall and re-wire every time you wanted to
    > connect.
    > ...
    > It may have been illegal in some countries but certainly not in the US.

Huh? Remember the Carterphone decision?

The one that overturned FCC Tariff Number 132: "No equipment, apparatus,
circuit or device not furnished by the telephone company shall be attached to
or connected with the facilities furnished by the telephone company, whether
physically, by induction or otherwise." 

Now, your point about rewiring the jack may in fact be the reason for
_post-Carterphone_ acoustic couplers, but it was indeed at one time illegal
to connect directly (other than AT+T/WE supplied equipment).

	Noel

From d3e3e3@gmail.com  Wed Jan  2 10:44:27 2013
Return-Path: <d3e3e3@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7777621F883B for <ietf@ietfa.amsl.com>; Wed,  2 Jan 2013 10:44:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.387
X-Spam-Level: 
X-Spam-Status: No, score=-103.387 tagged_above=-999 required=5 tests=[AWL=0.212, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
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 QIWInC1RfDF6 for <ietf@ietfa.amsl.com>; Wed,  2 Jan 2013 10:44:26 -0800 (PST)
Received: from mail-ob0-f176.google.com (mail-ob0-f176.google.com [209.85.214.176]) by ietfa.amsl.com (Postfix) with ESMTP id AFEE621F883A for <ietf@ietf.org>; Wed,  2 Jan 2013 10:44:26 -0800 (PST)
Received: by mail-ob0-f176.google.com with SMTP id un3so12803280obb.7 for <ietf@ietf.org>; Wed, 02 Jan 2013 10:44:26 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=Lm159E9tOfSRJ5oFX2LVzpqJM45P1N3Rc3GxOQLQ2Lc=; b=ahtQBc6u1uIYr3N+47kk8SlmIHt+hvxCU0/18OTJTGK18r57tK4DiKkdtIXlse1f3y Qe+6i8sRMcYZd3H5oEcMtNDrZIzxpsFOFedLw+OhhoRx6xGVNsY16OEtayvbMqq70hiP NY+xPD9eAngfUc6gk6iSntFHpxynOyQTBGMoLYtQyLKDgUTJ60mtEy99U0QH3olQfBHu Wel7X8n6EhvMYabMlgG2CR5lheNNfBkz1YFXlx3BvcheSohDuadc7FZlwvhXjEPFg+z+ Zsdm63HwjUdIU5OQ0slTYFe1OPoI/jvKk/CDqvfyBa1BXyI6xD6s59C5kdMqkjuQwk8X mbug==
Received: by 10.60.13.73 with SMTP id f9mr25534036oec.131.1357152266232; Wed, 02 Jan 2013 10:44:26 -0800 (PST)
MIME-Version: 1.0
Received: by 10.76.144.105 with HTTP; Wed, 2 Jan 2013 10:44:06 -0800 (PST)
In-Reply-To: <20200.1356985377@sandelman.ca>
References: <50DF09C7.1060009@dcrocker.net> <20200.1356985377@sandelman.ca>
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Wed, 2 Jan 2013 13:44:06 -0500
Message-ID: <CAF4+nEFg9OYjjWU67vCB_KERoj-u+p5M8HJsZ7Fj4Z1fbyzxFQ@mail.gmail.com>
Subject: Re: travel guide for the next IETF...
To: Michael Richardson <mcr@sandelman.ca>
Content-Type: text/plain; charset=ISO-8859-1
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Jan 2013 18:44:27 -0000

Hi,

On Mon, Dec 31, 2012 at 3:22 PM, Michael Richardson <mcr@sandelman.ca> wrote:
>
>>>>>> "Dave" == Dave Crocker <dhc@dcrocker.net> writes:
>     Dave> "Quick, name five reasons to go to Orlando. Here are mine:
>     Dave> Puerto Rican
>     Dave> delicacies, alternative cinema, craft beer, African-American
>     Dave> history and
>     Dave> psychic readings..."
>
> Good... but how to get there?
>
> We appear to be stuck in the middle of a monster hotel with a single
> boulevard and nothing at all nearby (except that there is a shuttle
> to Disney)

There are some things on the other side of World Drive.

Thanks,
Donald
=============================
 Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
 155 Beaver Street, Milford, MA 01757 USA
 d3e3e3@gmail.com

> Shoping around for places to stay, there are some 3-star places for
> <$50/night.
>
>

From worley@shell01.TheWorld.com  Wed Jan  2 11:51:05 2013
Return-Path: <worley@shell01.TheWorld.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 95F2D21F8798 for <ietf@ietfa.amsl.com>; Wed,  2 Jan 2013 11:51:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.437
X-Spam-Level: 
X-Spam-Status: No, score=-100.437 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_NET=0.611,  RDNS_NONE=0.1, USER_IN_WHITELIST=-100]
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 s5y7BUtOP-98 for <ietf@ietfa.amsl.com>; Wed,  2 Jan 2013 11:51:05 -0800 (PST)
Received: from TheWorld.com (pcls4.std.com [192.74.137.144]) by ietfa.amsl.com (Postfix) with ESMTP id 4B26C21F8797 for <ietf@ietf.org>; Wed,  2 Jan 2013 11:51:05 -0800 (PST)
Received: from shell.TheWorld.com (svani@shell01.theworld.com [192.74.137.71]) by TheWorld.com (8.14.5/8.14.5) with ESMTP id r02Job7u019808 for <ietf@ietf.org>; Wed, 2 Jan 2013 14:50:39 -0500
Received: from shell01.TheWorld.com (localhost.theworld.com [127.0.0.1]) by shell.TheWorld.com (8.13.6/8.12.8) with ESMTP id r02JoZJ74367589 for <ietf@ietf.org>; Wed, 2 Jan 2013 14:50:35 -0500 (EST)
Received: (from worley@localhost) by shell01.TheWorld.com (8.13.6/8.13.6/Submit) id r02JoZXn4359632; Wed, 2 Jan 2013 14:50:35 -0500 (EST)
Date: Wed, 2 Jan 2013 14:50:35 -0500 (EST)
Message-Id: <201301021950.r02JoZXn4359632@shell01.TheWorld.com>
From: worley@ariadne.com (Dale R. Worley)
Sender: worley@ariadne.com (Dale R. Worley)
To: ietf@ietf.org
In-reply-to: <a06240834cd09f3ec48a7@[10.0.1.3]> (jeanjour@comcast.net)
Subject: Re: WCIT outcome?
References: <CAMm+Lwh2cHRY+Dk2_SDtZZmUbPcgRpP89u3DHUcniJDrKrX_pw@mail.gmail.com> <CAMzo+1a0-90dnjnvs48a9DcNN9DY_edF5hH0__4XRuCaLHtL6Q@mail.gmail.com> <CAMm+LwjzjLc2-=4EdxwHOi21B3dOBUohYc5hhXZHL_Pk+iBBmQ@mail.gmail.com> <6.2.5.6.2.20121229192941.0aae33e8@resistor.net> <CAMm+LwiC0xtJU4vnGFPvAG4VKZdj7Tf3LfW0+pzwxKWTegRREw@mail.gmail.com> <a06240800cd074efd45b8@10.0.1.3> <CAMm+Lwiq+DCzXw572wKs78DG+XzYsJtwCVSPvNuVHSrT=Cr2nA@mail.gmail.com> <a06240809cd0799fee029@10.0.1.3> <6.2.5.6.2.20130102023406.0b4b7d68@resistor.net> <CAMm+LwgsgaV7L-FY4MnM2Einaapo-BdiddBU+nYzTS6DMPXzQw@mail.gmail.com> <a06240834cd09f3ec48a7@[10.0.1.3]>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Jan 2013 19:51:05 -0000

> From: John Day <jeanjour@comcast.net>
> 
> No, there was nothing illegal about it. The reason for acoustic 
> couplers was that the RJ-11 had been invented yet and it was a pain 
> to unscrew the box on the wall and re-wire every time you wanted to 
> connect.

In the 1970s, in the US, and for inter-state use, you either had to
rent the modem from the phone company, or rent a "data-access
arrangement" device to connect your modem to the network.  The DAA
cost about as much as the modem, so there was little in the way of
independent modems.  Acoustic couplers got around that rule.

Also, in those days, there was a large four-pronged plug that could be
used for phones.  It was sometimes used when people wanted to move
phones around.  http://en.wikipedia.org/wiki/File:4prongplug.JPG

Dale

From jason_livingood@cable.comcast.com  Wed Jan  2 13:20:09 2013
Return-Path: <jason_livingood@cable.comcast.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B4FA921F8461 for <ietf@ietfa.amsl.com>; Wed,  2 Jan 2013 13:20:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.231
X-Spam-Level: 
X-Spam-Status: No, score=-105.231 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HOST_EQ_MODEMCABLE=1.368, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 3zrru1BkDKxl for <ietf@ietfa.amsl.com>; Wed,  2 Jan 2013 13:20:09 -0800 (PST)
Received: from cable.comcast.com (copdcavout01.cable.comcast.com [76.96.32.253]) by ietfa.amsl.com (Postfix) with ESMTP id D82E221F844F for <ietf@ietf.org>; Wed,  2 Jan 2013 13:20:08 -0800 (PST)
Received: from ([24.40.56.114]) by copdcavout01.cable.comcast.com with ESMTP  id C7WM3M1.48916699; Wed, 02 Jan 2013 13:52:30 -0700
Received: from PACDCEXMB06.cable.comcast.com ([169.254.8.8]) by PACDCEXHUB01.cable.comcast.com ([fe80::84e8:95f3:f13b:169e%12]) with mapi id 14.02.0318.001; Wed, 2 Jan 2013 16:20:04 -0500
From: "Livingood, Jason" <Jason_Livingood@cable.comcast.com>
To: Donald Eastlake <d3e3e3@gmail.com>, IETF Discussion <ietf@ietf.org>
Subject: Re: travel guide for the next IETF...
Thread-Topic: travel guide for the next IETF...
Thread-Index: AQHN6QnvV5YMASCeWE6oLAYVL/Dc1Zg2tAYA///X0QA=
Date: Wed, 2 Jan 2013 21:19:56 +0000
Message-ID: <10229F86C86EB444898E629583FD417149E19ADB@PACDCEXMB06.cable.comcast.com>
In-Reply-To: <CAF4+nEFg9OYjjWU67vCB_KERoj-u+p5M8HJsZ7Fj4Z1fbyzxFQ@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.2.4.120824
x-originating-ip: [24.40.55.72]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <ABFB1C83EEE46A4A976E96E3DA3021F3@cable.comcast.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Jan 2013 21:20:09 -0000

On 1/2/13 1:44 PM, "Donald Eastlake" <d3e3e3@gmail.com> wrote:


>>Good... but how to get there?
>>
>> We appear to be stuck in the middle of a monster hotel with a single
>> boulevard and nothing at all nearby (except that there is a shuttle
>> to Disney)
>
>There are some things on the other side of World Drive.

Things like this?=20
http://upload.wikimedia.org/wikipedia/commons/1/1c/Florida_Alligator.jpg

;-)

If anyone is into cars, the weekend the meeting starts is the Amelia
Island Concours D'Elegance from 8 March - 10 March. That is ~3 hours drive
north of Orlando. The show will be celebrating the 50th anniversary of the
Porsche 911 and Ford GT40. See http://www.ameliaconcours.org/

Jason



From john-ietf@jck.com  Wed Jan  2 13:36:44 2013
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B6F8621F862E for <ietf@ietfa.amsl.com>; Wed,  2 Jan 2013 13:36:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 Sxjwc6XKnx9d for <ietf@ietfa.amsl.com>; Wed,  2 Jan 2013 13:36:44 -0800 (PST)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 2B69621F8550 for <ietf@ietf.org>; Wed,  2 Jan 2013 13:36:44 -0800 (PST)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1TqVzN-000Gwd-Ki; Wed, 02 Jan 2013 16:36:41 -0500
Date: Wed, 02 Jan 2013 16:36:36 -0500
From: John C Klensin <john-ietf@jck.com>
To: "Livingood, Jason" <Jason_Livingood@cable.comcast.com>, Donald Eastlake <d3e3e3@gmail.com>, IETF Discussion <ietf@ietf.org>
Subject: Re: travel guide for the next IETF...
Message-ID: <C4F9345E5D25E140ADBB55AF@JcK-HP8200.jck.com>
In-Reply-To: <10229F86C86EB444898E629583FD417149E19ADB@PACDCEXMB06.cable.comcast.com>
References: <10229F86C86EB444898E629583FD417149E19ADB@PACDCEXMB06.cable.comcast.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Jan 2013 21:36:44 -0000

--On Wednesday, January 02, 2013 21:19 +0000 "Livingood, Jason"
<Jason_Livingood@cable.comcast.com> wrote:

> Things like this? 
> http://upload.wikimedia.org/wikipedia/commons/1/1c/Florida_All
> igator.jpg
> 
> ;-)

No, we expect those at the plenary as a special prize for boring
presentations :-)

   john





From ned+ietf@mauve.mrochek.com  Wed Jan  2 13:56:37 2013
Return-Path: <ned+ietf@mauve.mrochek.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C6EC521F8461 for <ietf@ietfa.amsl.com>; Wed,  2 Jan 2013 13:56:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 jDOgkWdTlIqh for <ietf@ietfa.amsl.com>; Wed,  2 Jan 2013 13:56:37 -0800 (PST)
Received: from mauve.mrochek.com (mauve.mrochek.com [66.59.230.40]) by ietfa.amsl.com (Postfix) with ESMTP id 0C88421F8460 for <ietf@ietf.org>; Wed,  2 Jan 2013 13:56:32 -0800 (PST)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01OOIM6G2QHC004M37@mauve.mrochek.com> for ietf@ietf.org; Wed, 2 Jan 2013 13:51:29 -0800 (PST)
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01OOHIFJWMKW00008S@mauve.mrochek.com> (original mail from NED@mauve.mrochek.com) for ietf@ietf.org; Wed, 2 Jan 2013 13:51:25 -0800 (PST)
From: ned+ietf@mauve.mrochek.com
Message-id: <01OOIM6DH1HW00008S@mauve.mrochek.com>
Date: Wed, 02 Jan 2013 13:34:21 -0800 (PST)
Subject: Re: WCIT outcome?
In-reply-to: "Your message dated Wed, 02 Jan 2013 12:58:39 -0500 (EST)" <20130102175839.2DDAE18C0BB@mercury.lcs.mit.edu>
MIME-version: 1.0
References: <20130102175839.2DDAE18C0BB@mercury.lcs.mit.edu>
To: jnc@mercury.lcs.mit.edu
Cc: ietf@ietf.org, jnc@mercury.lcs.mit.edu
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Jan 2013 21:56:37 -0000

>     > From: John Day <jeanjour@comcast.net>

>     > I remember when a modem came with an 'acoustic coupler' because
>     > connecting it directly to the phone line was illegal.
>     > No, there was nothing illegal about it. The reason for acoustic
>     > couplers was that the RJ-11 had been invented yet and it was a pain to
>     > unscrew the box on the wall and re-wire every time you wanted to
>     > connect.
>     > ...
>     > It may have been illegal in some countries but certainly not in the US.

> Huh? Remember the Carterphone decision?

Absolutely. Too bad the FCC didn't see fit to extend it to wireless.

> The one that overturned FCC Tariff Number 132: "No equipment, apparatus,
> circuit or device not furnished by the telephone company shall be attached to
> or connected with the facilities furnished by the telephone company, whether
> physically, by induction or otherwise."

> Now, your point about rewiring the jack may in fact be the reason for
> _post-Carterphone_ acoustic couplers, but it was indeed at one time illegal
> to connect directly (other than AT+T/WE supplied equipment).

I'm skeptical about this last part. Prior to the advent of RJ-11 Bell System
line cords used a large polarized four pin jack. After Carterphone all sorts of
stuff started to appear to accomodate these, including extension cords,
plug-jack passthroughs, and even "cube taps".

At one point there was something that said one phone in each home had to be
directly wired without a plug. I don't know if this was a regulation, a phone
company rule, or just a suggestion, but it also fell by the wayside after
Carterphone.

I certainly saw acoustic coupled equipment in use long after Carterphone, but
in my experience it was because of general intertia/unwillingness to do the
necessary engineering, not because of the lack of connectors.

				Ned

From dhc@dcrocker.net  Wed Jan  2 14:07:48 2013
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6B67A21F8617 for <ietf@ietfa.amsl.com>; Wed,  2 Jan 2013 14:07:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.297
X-Spam-Level: 
X-Spam-Status: No, score=-6.297 tagged_above=-999 required=5 tests=[AWL=0.302,  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 2KeuNmUJQiNl for <ietf@ietfa.amsl.com>; Wed,  2 Jan 2013 14:07:47 -0800 (PST)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id D7BEA21F8792 for <ietf@ietf.org>; Wed,  2 Jan 2013 14:07:47 -0800 (PST)
Received: from [192.168.1.66] (76-218-9-215.lightspeed.sntcca.sbcglobal.net [76.218.9.215]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id r02M7l9T024252 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 2 Jan 2013 14:07:47 -0800
Message-ID: <50E4AFAF.4000506@dcrocker.net>
Date: Wed, 02 Jan 2013 14:07:43 -0800
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: ned+ietf@mauve.mrochek.com
Subject: Re: WCIT outcome?
References: <20130102175839.2DDAE18C0BB@mercury.lcs.mit.edu> <01OOIM6DH1HW00008S@mauve.mrochek.com>
In-Reply-To: <01OOIM6DH1HW00008S@mauve.mrochek.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Wed, 02 Jan 2013 14:07:47 -0800 (PST)
Cc: jnc@mercury.lcs.mit.edu, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Jan 2013 22:07:48 -0000

On 1/2/2013 1:34 PM, ned+ietf@mauve.mrochek.com wrote:
>> Now, your point about rewiring the jack may in fact be the reason for
>> _post-Carterphone_ acoustic couplers, but it was indeed at one time illegal
>> to connect directly (other than AT+T/WE supplied equipment).
>
> I'm skeptical about this last part. Prior to the advent of RJ-11 Bell System
> line cords used a large polarized four pin jack. After Carterphone all sorts of
> stuff started to appear to accomodate these, including extension cords,
> plug-jack passthroughs, and even "cube taps".

Acoustic couplers date back farther than the 4-pin plugs.

As I understood the AT&T claim, they asserted a need to protect their 
network from misbehaving electronics and so required all interfacing to 
be through the handset that they provided.

Hence the overlay hack of an acoustic coupler.  Not unlike MIME...


> At one point there was something that said one phone in each home had to be
> directly wired without a plug. I don't know if this was a regulation, a phone
> company rule, or just a suggestion, but it also fell by the wayside after
> Carterphone.

It was usually enforced rigorously.  A given field tech might choose to 
overlook a local mod, but they were authorized to remove such things.

So in my apartment, I installed a shutoff switch to the line, to be able 
to sleep through attempts by my boss to call me in to work an additional 
shift as a computer operator, at UCLA, around 1970 -- if I answered, I 
was required to come in.  Remember there was no caller ID in those days.

The tech who needed to work on my phone service was very clear that he 
was supposed to remove it.  After checking that I had handled the wiring 
acceptably, he looked at me and said "so if I remove this, you'll 
probably just reinstall it, right?"  He then left it in place.

d/

-- 
  Dave Crocker
  Brandenburg InternetWorking
  bbiw.net

From dwm@xpasc.com  Wed Jan  2 14:16:33 2013
Return-Path: <dwm@xpasc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 962CB21F86A9 for <ietf@ietfa.amsl.com>; Wed,  2 Jan 2013 14:16:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.071
X-Spam-Level: 
X-Spam-Status: No, score=-3.071 tagged_above=-999 required=5 tests=[AWL=-1.764, BAYES_00=-2.599, MISSING_HEADERS=1.292]
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 P+aLOxRzJVEX for <ietf@ietfa.amsl.com>; Wed,  2 Jan 2013 14:16:33 -0800 (PST)
Received: from c2w3p-2.abacamail.com (c2w3p-2.abacamail.com [209.133.53.32]) by ietfa.amsl.com (Postfix) with ESMTP id 3786D21F8481 for <ietf@ietf.org>; Wed,  2 Jan 2013 14:16:33 -0800 (PST)
Received: from xpasc.com (unknown [68.164.244.188]) by c2w3p-2.abacamail.com (Postfix) with ESMTP id ACC643FCFD for <ietf@ietf.org>; Wed,  2 Jan 2013 22:16:32 +0000 (UTC)
Received: from egate.xpasc.com (egate.xpasc.com [10.1.2.49]) by xpasc.com (8.13.8/8.13.8) with ESMTP id r02MGWwm026982 for <ietf@ietf.org>; Wed, 2 Jan 2013 14:16:32 -0800
Date: Wed, 2 Jan 2013 14:16:32 -0800 (PST)
From: David Morris <dwm@xpasc.com>
cc: ietf@ietf.org
Subject: Re: WCIT outcome?
In-Reply-To: <01OOIM6DH1HW00008S@mauve.mrochek.com>
Message-ID: <alpine.LRH.2.01.1301021406190.26011@egate.xpasc.com>
References: <20130102175839.2DDAE18C0BB@mercury.lcs.mit.edu> <01OOIM6DH1HW00008S@mauve.mrochek.com>
User-Agent: Alpine 2.01 (LRH 1266 2009-07-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Milter-Version: master.1+13-gbab1945
X-AV-Type: clean
X-AV-Accuracy: exact
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: ietf@ietf.org
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Jan 2013 22:16:33 -0000

On Wed, 2 Jan 2013, ned+ietf@mauve.mrochek.com wrote:

> At one point there was something that said one phone in each home had to be
> directly wired without a plug. I don't know if this was a regulation, a phone
> company rule, or just a suggestion, but it also fell by the wayside after
> Carterphone.

May have varied by baby bell, but in Michigan, you could have as many 
jacks as you wished, but you had to lease them all from the telco. There
may have been a rule about having at least one hard wired phone, I don't
recall. In those days, the telco owned and was responsible for all inside
wiring.

> I certainly saw acoustic coupled equipment in use long after Carterphone, but
> in my experience it was because of general intertia/unwillingness to do the
> necessary engineering, not because of the lack of connectors.

Probably more to do with portability of accoustic couplers and the lack of
provisioning in motels, etc. for jacks.

From warren@kumari.net  Wed Jan  2 14:21:54 2013
Return-Path: <warren@kumari.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9A6BB21F86EA for <ietf@ietfa.amsl.com>; Wed,  2 Jan 2013 14:21:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 iDb+DjutRvpE for <ietf@ietfa.amsl.com>; Wed,  2 Jan 2013 14:21:53 -0800 (PST)
Received: from vimes.kumari.net (smtp1.kumari.net [204.194.22.1]) by ietfa.amsl.com (Postfix) with ESMTP id 54C0321F86E6 for <ietf@ietf.org>; Wed,  2 Jan 2013 14:21:53 -0800 (PST)
Received: from [192.168.1.136] (unknown [66.84.81.126]) by vimes.kumari.net (Postfix) with ESMTPSA id 17A7E1B402D4; Wed,  2 Jan 2013 17:21:50 -0500 (EST)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Subject: Re: [IETF] WCIT outcome?
From: Warren Kumari <warren@kumari.net>
In-Reply-To: <50E4AFAF.4000506@dcrocker.net>
Date: Wed, 2 Jan 2013 17:21:48 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <CA66AF11-0E18-490E-ADEC-FA3DF0BE39C2@kumari.net>
References: <20130102175839.2DDAE18C0BB@mercury.lcs.mit.edu> <01OOIM6DH1HW00008S@mauve.mrochek.com> <50E4AFAF.4000506@dcrocker.net>
To: dcrocker@bbiw.net
X-Mailer: Apple Mail (2.1499)
Cc: ned+ietf@mauve.mrochek.com, jnc@mercury.lcs.mit.edu, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Jan 2013 22:21:54 -0000

On Jan 2, 2013, at 5:07 PM, Dave Crocker <dhc@dcrocker.net> wrote:

>=20
> On 1/2/2013 1:34 PM, ned+ietf@mauve.mrochek.com wrote:
>>> Now, your point about rewiring the jack may in fact be the reason =
for
>>> _post-Carterphone_ acoustic couplers, but it was indeed at one time =
illegal
>>> to connect directly (other than AT+T/WE supplied equipment).
>>=20
>> I'm skeptical about this last part. Prior to the advent of RJ-11 Bell =
System
>> line cords used a large polarized four pin jack. After Carterphone =
all sorts of
>> stuff started to appear to accomodate these, including extension =
cords,
>> plug-jack passthroughs, and even "cube taps".
>=20
> Acoustic couplers date back farther than the 4-pin plugs.
>=20
> As I understood the AT&T claim, they asserted a need to protect their =
network from misbehaving electronics and so required all interfacing to =
be through the handset that they provided.
>=20
> Hence the overlay hack of an acoustic coupler.  Not unlike MIME...
>=20
>=20
>> At one point there was something that said one phone in each home had =
to be
>> directly wired without a plug. I don't know if this was a regulation, =
a phone
>> company rule, or just a suggestion, but it also fell by the wayside =
after
>> Carterphone.
>=20
> It was usually enforced rigorously.  A given field tech might choose =
to overlook a local mod, but they were authorized to remove such things.
>=20
> So in my apartment, I installed a shutoff switch to the line, to be =
able to sleep through attempts by my boss to call me in to work an =
additional shift as a computer operator, at UCLA, around 1970 -- if I =
answered, I was required to come in.  Remember there was no caller ID in =
those days.
>=20
> The tech who needed to work on my phone service was very clear that he =
was supposed to remove it.  After checking that I had handled the wiring =
acceptably, he looked at me and said "so if I remove this, you'll =
probably just reinstall it, right?"  He then left it in place.

I grew up in South Africa, with Telkom, the state run monopoly. =
Connecting anything other than a telephone was illegal, with (IIRC) the =
possibility of jail time. You would have to rent the phone unit itself =
from Telkom by going to the post-office and filling in a form, then =
waiting few a few weeks to months. If yo unmoved you had to return the =
unit and rent a new one=85

South Africa used weird jacks, shared with Benin, Burundi, Cameroon, =
Central African Republic, Cook Islands, Liberia, Namibia and Serbia.
(some pictures here: =
http://www.networkmuseum.net/2011/06/phone-plugs.html). The pins were =
made of some very soft metal (possibly high in lead, based upon the =
speed at with they would tarnish and appearance of the oxidation) and =
the wipers in the socket from a dissimilar metal. This would result in =
very poor / flaky connections, and kicking the jack to wiggle / reseat =
it was a common practice.

Fun times...

W

>=20
> d/
>=20
> --=20
> Dave Crocker
> Brandenburg InternetWorking
> bbiw.net
>=20

--=20
Eagles soar but a weasel will never get sucked into a jet engine=20



From sm@resistor.net  Wed Jan  2 15:08:01 2013
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 40AA721F8831 for <ietf@ietfa.amsl.com>; Wed,  2 Jan 2013 15:08:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.615
X-Spam-Level: 
X-Spam-Status: No, score=-102.615 tagged_above=-999 required=5 tests=[AWL=-0.016, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 DCD0V6ssMNsj for <ietf@ietfa.amsl.com>; Wed,  2 Jan 2013 15:07:59 -0800 (PST)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id D7D0D21F8830 for <ietf@ietf.org>; Wed,  2 Jan 2013 15:07:59 -0800 (PST)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r02N7q7r015414; Wed, 2 Jan 2013 15:07:55 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1357168077; bh=DxhEAjObcLW4Yuy1WXQ5I2GI55+yKRTXl9o+PzROI98=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=djAqHuUVDWbym1rtKKBC7kyuAN5pJxE+rWIWHBpOhPW1ypm2kN+vLkk4xHXoimBqy RaC5hl/LWVImfNzXRPM34PkR8hKzjW906mmIkAnlDl5eN2ujg4dUGUaJVJWmz+8rjI pkY/d1OlJ2/D1y+FaEliae/+BFOwLwLSxs1Esh/Q=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1357168077; i=@resistor.net; bh=DxhEAjObcLW4Yuy1WXQ5I2GI55+yKRTXl9o+PzROI98=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=2U3TDJLztJjsW+HvkmJ6Lq+pC9iqL5JS2by4QSEFrbsvmjhYR5zoTXG3Yyf3BWjY+ 4QBahpYinmDjE8q/R/R9NA/jKjVvcCCczQ10NTYuEW0TdLu0KDQVrBvvMxGwT55/Rz BCULhMW5hpsVzYwN9O9xcSSPJ/mldSeDCli9sHRE=
Message-Id: <6.2.5.6.2.20130102102429.0a460600@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Wed, 02 Jan 2013 15:06:02 -0800
To: John Day <jeanjour@comcast.net>
From: SM <sm@resistor.net>
Subject: Re: WCIT outcome?
In-Reply-To: <a0624082fcd09e07ab9c8@[10.0.1.3]>
References: <CAMm+Lwh2cHRY+Dk2_SDtZZmUbPcgRpP89u3DHUcniJDrKrX_pw@mail.gmail.com> <CAMzo+1a0-90dnjnvs48a9DcNN9DY_edF5hH0__4XRuCaLHtL6Q@mail.gmail.com> <CAMm+LwjzjLc2-=4EdxwHOi21B3dOBUohYc5hhXZHL_Pk+iBBmQ@mail.gmail.com> <6.2.5.6.2.20121229192941.0aae33e8@resistor.net> <CAMm+LwiC0xtJU4vnGFPvAG4VKZdj7Tf3LfW0+pzwxKWTegRREw@mail.gmail.com> <a06240800cd074efd45b8@10.0.1.3> <CAMm+Lwiq+DCzXw572wKs78DG+XzYsJtwCVSPvNuVHSrT=Cr2nA@mail.gmail.com> <a06240809cd0799fee029@[10.0.1.3]> <6.2.5.6.2.20130102023406.0b4b7d68@resistor.net> <a0624082fcd09e07ab9c8@[10.0.1.3]>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: IETF Discussion Mailing List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Jan 2013 23:08:01 -0000

Hi John,
At 05:11 02-01-2013, John Day wrote:
>Could you expand on this?

The question (asked in a previous message) used the word 
"telecommunication".  If one goes by the definition in Y.2001 it may 
not fit everybody's view of what "telecommunication" should 
mean.  The objectives in Y.2001 are broad.  They can be interpreted 
in various ways.  People will argue about what are important 
considerations and which of them should be subject to international 
regulations.  Does security, for example, affect commerce?  Should 
security include lawful interception?  Each question can raise other 
questions.  It's a slippery slope.

Regards,
-sm 


From johnl@iecc.com  Wed Jan  2 15:15:21 2013
Return-Path: <johnl@iecc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EC8F321F843F for <ietf@ietfa.amsl.com>; Wed,  2 Jan 2013 15:15:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -107.778
X-Spam-Level: 
X-Spam-Status: No, score=-107.778 tagged_above=-999 required=5 tests=[AWL=0.821, BAYES_50=0.001, HABEAS_ACCREDITED_SOI=-4.3, RCVD_IN_BSP_TRUSTED=-4.3, USER_IN_WHITELIST=-100]
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 EJf0XJZaM8sq for <ietf@ietfa.amsl.com>; Wed,  2 Jan 2013 15:15:21 -0800 (PST)
Received: from leila.iecc.com (leila6.iecc.com [IPv6:2001:470:1f07:1126:0:4c:6569:6c61]) by ietfa.amsl.com (Postfix) with ESMTP id 2624F21F843E for <ietf@ietf.org>; Wed,  2 Jan 2013 15:15:20 -0800 (PST)
Received: (qmail 95512 invoked from network); 2 Jan 2013 23:15:14 -0000
Received: from leila.iecc.com (64.57.183.34) by mail1.iecc.com with QMQP; 2 Jan 2013 23:15:14 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:vbr-info; s=50e4bf82.xn--hew.k1301; i=johnl@user.iecc.com; bh=jAMd68iF2/011JFRhrZBd+GVPwiTk/EFBVslDLyZf+o=; b=LfsBtHEPdkVldZERSB0hCI2FM39JgE3+6NWq+wrEZTovd3gUVfSh0StRgMU6Q2xOAJrLK92RYWOli49BASfXzrpTe3y05aaTMBMiJnnf+qJ/h6KhAE+5Z/zfXYar+bQHqgYI/WqunxUfYCWUbSj7j9pXKipgcqO4/SBuAiYkOrk=
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:vbr-info; s=50e4bf82.xn--hew.k1301; olt=johnl@user.iecc.com; bh=jAMd68iF2/011JFRhrZBd+GVPwiTk/EFBVslDLyZf+o=; b=oYsfJmr/2LC/O6yKOnhyo3xRLhbQwTc/w+4BuHNWGSHXSoEGg5anie8AjJHpt7Yqsg4BKizFpOb90qyxqvo5MEkone6gf0JcGDn7gcQXbPjy2f4UWvfnI42utV11q3R/lCW15pkZSIS2qPmfJoXiVEE+vSqjeExxWYqVImKrLAY=
VBR-Info: md=iecc.com; mc=all; mv=dwl.spamhaus.org
Date: 2 Jan 2013 23:14:51 -0000
Message-ID: <20130102231451.24327.qmail@joyce.lan>
From: "John Levine" <johnl@taugh.com>
To: ietf@ietf.org
Subject: Re: travel guide for the next IETF...
In-Reply-To: <CAF4+nEFg9OYjjWU67vCB_KERoj-u+p5M8HJsZ7Fj4Z1fbyzxFQ@mail.gmail.com>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Jan 2013 23:15:22 -0000

>> Good... but how to get there?

If you plan to do anything more than spend the whole trip at the
meeting hotel, you need a car.  Orlando is a cheap rental town, it's
not hard to rent something for $100 total for five days.

Cape Canaveral and Cocoa Beach are only an hour away for people who
think the list of attractions in Orlando itself is a bit thin.

R's,
John

PS: Is Xanadu The House Of The Future still in Kissimmee?  How about
the Tupperware Museum of Food Storage?

From ned+ietf@mauve.mrochek.com  Wed Jan  2 19:34:51 2013
Return-Path: <ned+ietf@mauve.mrochek.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7E2D721F8881 for <ietf@ietfa.amsl.com>; Wed,  2 Jan 2013 19:34:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 wNpqiC9x+-4g for <ietf@ietfa.amsl.com>; Wed,  2 Jan 2013 19:34:51 -0800 (PST)
Received: from mauve.mrochek.com (mauve.mrochek.com [66.59.230.40]) by ietfa.amsl.com (Postfix) with ESMTP id EEDB321F86BE for <ietf@ietf.org>; Wed,  2 Jan 2013 19:34:50 -0800 (PST)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01OOIXYVLORK003QL0@mauve.mrochek.com> for ietf@ietf.org; Wed, 2 Jan 2013 19:29:46 -0800 (PST)
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01OOHIFJWMKW00008S@mauve.mrochek.com> (original mail from NED@mauve.mrochek.com) for ietf@ietf.org; Wed, 2 Jan 2013 19:29:40 -0800 (PST)
From: ned+ietf@mauve.mrochek.com
Message-id: <01OOIXYRHRN000008S@mauve.mrochek.com>
Date: Wed, 02 Jan 2013 19:08:17 -0800 (PST)
Subject: Acoustic couplers (was: Re: WCIT outcome?)
In-reply-to: "Your message dated Wed, 02 Jan 2013 14:07:43 -0800" <50E4AFAF.4000506@dcrocker.net>
MIME-version: 1.0
Content-type: TEXT/PLAIN; format=flowed
References: <20130102175839.2DDAE18C0BB@mercury.lcs.mit.edu> <01OOIM6DH1HW00008S@mauve.mrochek.com> <50E4AFAF.4000506@dcrocker.net>
To: Dave Crocker <dhc@dcrocker.net>
Cc: ned+ietf@mauve.mrochek.com, jnc@mercury.lcs.mit.edu, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Jan 2013 03:34:51 -0000

> On 1/2/2013 1:34 PM, ned+ietf@mauve.mrochek.com wrote:
> >> Now, your point about rewiring the jack may in fact be the reason for
> >> _post-Carterphone_ acoustic couplers, but it was indeed at one time illegal
> >> to connect directly (other than AT+T/WE supplied equipment).
> >
> > I'm skeptical about this last part. Prior to the advent of RJ-11 Bell System
> > line cords used a large polarized four pin jack. After Carterphone all sorts of
> > stuff started to appear to accomodate these, including extension cords,
> > plug-jack passthroughs, and even "cube taps".

> Acoustic couplers date back farther than the 4-pin plugs.

Of course. However, we're talking about post-Carterphone here. Carterphone was
1968, and I'm sure four pin plugs were in use by then.

Also keep in mind that AT&T fought the Carterphone decision for many years.
They got some state regulators to issue their own restrictions, but the FCC
nixed them all. Then they said a special protection device had to be used. The
FCC shot that down too. They also tried fees, but for that to work people had
to tell AT&T to charge them, which of course didn't happen.

> ...

> > At one point there was something that said one phone in each home had to be
> > directly wired without a plug. I don't know if this was a regulation, a phone
> > company rule, or just a suggestion, but it also fell by the wayside after
> > Carterphone.

> It was usually enforced rigorously.  A given field tech might choose to
> overlook a local mod, but they were authorized to remove such things.

> So in my apartment, I installed a shutoff switch to the line, to be able
> to sleep through attempts by my boss to call me in to work an additional
> shift as a computer operator, at UCLA, around 1970 -- if I answered, I
> was required to come in.  Remember there was no caller ID in those days.

> The tech who needed to work on my phone service was very clear that he
> was supposed to remove it.  After checking that I had handled the wiring
> acceptably, he looked at me and said "so if I remove this, you'll
> probably just reinstall it, right?"  He then left it in place.

A line mod was probably against the rules irrespective of Carterphone in those
days. But had you bought your own phone with a ringer switch and hooked that
up, that absolutely would have been covered by Carterphone. Of course you would
then have had to convince AT&T of that - see above.

				Ned

From paf@frobbit.se  Wed Jan  2 22:59:44 2013
Return-Path: <paf@frobbit.se>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8D62121F8919 for <ietf@ietfa.amsl.com>; Wed,  2 Jan 2013 22:59:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.3
X-Spam-Level: 
X-Spam-Status: No, score=-2.3 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, NO_RELAYS=-0.001]
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 UyPBLd+ms7II for <ietf@ietfa.amsl.com>; Wed,  2 Jan 2013 22:59:42 -0800 (PST)
Received: from mail.frobbit.se (mail.frobbit.se [IPv6:2a02:80:3ffe::176]) by ietfa.amsl.com (Postfix) with ESMTP id B094A21F8917 for <ietf@ietf.org>; Wed,  2 Jan 2013 22:59:42 -0800 (PST)
Received: from [IPv6:2a02:80:3ffc::811b:6d4d:a6be:316b] (unknown [IPv6:2a02:80:3ffc:0:811b:6d4d:a6be:316b]) by mail.frobbit.se (Postfix) with ESMTPSA id 029A0205BA; Thu,  3 Jan 2013 07:59:41 +0100 (CET)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Subject: Re: [IETF] WCIT outcome?
From: =?windows-1252?Q?Patrik_F=E4ltstr=F6m?= <paf@frobbit.se>
In-Reply-To: <CA66AF11-0E18-490E-ADEC-FA3DF0BE39C2@kumari.net>
Date: Thu, 3 Jan 2013 07:59:40 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <A949F6DD-76E7-4E11-9D39-4C14B37732B0@frobbit.se>
References: <20130102175839.2DDAE18C0BB@mercury.lcs.mit.edu> <01OOIM6DH1HW00008S@mauve.mrochek.com> <50E4AFAF.4000506@dcrocker.net> <CA66AF11-0E18-490E-ADEC-FA3DF0BE39C2@kumari.net>
To: Warren Kumari <warren@kumari.net>
X-Mailer: Apple Mail (2.1499)
Cc: ned+ietf@mauve.mrochek.com, ietf@ietf.org, dcrocker@bbiw.net, jnc@mercury.lcs.mit.edu
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Jan 2013 06:59:44 -0000

On 2 jan 2013, at 23:21, Warren Kumari <warren@kumari.net> wrote:

> South Africa used weird jacks, shared with Benin, Burundi, Cameroon, =
Central African Republic, Cook Islands, Liberia, Namibia and Serbia.
> (some pictures here: =
http://www.networkmuseum.net/2011/06/phone-plugs.html). The pins were =
made of some very soft metal (possibly high in lead, based upon the =
speed at with they would tarnish and appearance of the oxidation) and =
the wipers in the socket from a dissimilar metal. This would result in =
very poor / flaky connections, and kicking the jack to wiggle / reseat =
it was a common practice.
>=20
> Fun times...

Please note that many access providers for Internet access require the =
end user to use a CPE that they provide. Both for wireless (mobile data, =
like 3G, 4G etc) and wired access.

Like the old days.

What changed things, like many have explained in different words, where =
agreements/laws/regulation that increased the power the end user had to =
choose whatever device they wanted. That enabled innovation and =
competition. Decisions by governments that overrun the interest of =
whoever run the access. Those decisions by themselves I claim helped =
growth of the Internet more than many other things (one could for =
example buy a modem from any vendor).

   Patrik


From mohta@necom830.hpcl.titech.ac.jp  Thu Jan  3 00:41:14 2013
Return-Path: <mohta@necom830.hpcl.titech.ac.jp>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6251021F8971 for <ietf@ietfa.amsl.com>; Thu,  3 Jan 2013 00:41:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.282
X-Spam-Level: 
X-Spam-Status: No, score=0.282 tagged_above=-999 required=5 tests=[AWL=0.372,  BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265]
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 B4RGOCAv+aZh for <ietf@ietfa.amsl.com>; Thu,  3 Jan 2013 00:41:14 -0800 (PST)
Received: from necom830.hpcl.titech.ac.jp (necom830.hpcl.titech.ac.jp [131.112.32.132]) by ietfa.amsl.com (Postfix) with SMTP id 8F67F21F86F7 for <ietf@ietf.org>; Thu,  3 Jan 2013 00:41:11 -0800 (PST)
Received: (qmail 55511 invoked from network); 3 Jan 2013 08:41:41 -0000
Received: from necom830.hpcl.titech.ac.jp (HELO ?127.0.0.1?) (131.112.32.132) by necom830.hpcl.titech.ac.jp with SMTP; 3 Jan 2013 08:41:41 -0000
Message-ID: <50E543C7.6070809@necom830.hpcl.titech.ac.jp>
Date: Thu, 03 Jan 2013 17:39:35 +0900
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: WCIT outcome?
References: <CAMm+Lwh2cHRY+Dk2_SDtZZmUbPcgRpP89u3DHUcniJDrKrX_pw@mail.gmail.com> <CAMzo+1a0-90dnjnvs48a9DcNN9DY_edF5hH0__4XRuCaLHtL6Q@mail.gmail.com> <CAMm+LwjzjLc2-=4EdxwHOi21B3dOBUohYc5hhXZHL_Pk+iBBmQ@mail.gmail.com> <50E439C5.2020808@gmail.com> <B31EEDDDB8ED7E4A93FDF12A4EECD30D24FE4DAF@GLKXM0002V.GREENLNK.net>
In-Reply-To: <B31EEDDDB8ED7E4A93FDF12A4EECD30D24FE4DAF@GLKXM0002V.GREENLNK.net>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Jan 2013 08:41:14 -0000

Dearlove, Christopher (UK) wrote:

> Given the ever increasing number of mobile devices, one could argue that the world
> has never been more dependent on radio spectrum allocation.

If you don't insist on allocating fixed bandwidths, CSMA/CA takes care 
of most of issues.

						Masataka Ohta

From daedulus@btconnect.com  Thu Jan  3 01:48:15 2013
Return-Path: <daedulus@btconnect.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 31B2C21F8A40 for <ietf@ietfa.amsl.com>; Thu,  3 Jan 2013 01:48:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.35
X-Spam-Level: 
X-Spam-Status: No, score=-4.35 tagged_above=-999 required=5 tests=[AWL=-0.751,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 Trw9PSU4C3TI for <ietf@ietfa.amsl.com>; Thu,  3 Jan 2013 01:48:14 -0800 (PST)
Received: from db3outboundpool.messaging.microsoft.com (db3ehsobe002.messaging.microsoft.com [213.199.154.140]) by ietfa.amsl.com (Postfix) with ESMTP id 3957821F8A69 for <ietf@ietf.org>; Thu,  3 Jan 2013 01:48:13 -0800 (PST)
Received: from mail28-db3-R.bigfish.com (10.3.81.226) by DB3EHSOBE004.bigfish.com (10.3.84.24) with Microsoft SMTP Server id 14.1.225.23; Thu, 3 Jan 2013 09:48:12 +0000
Received: from mail28-db3 (localhost [127.0.0.1])	by mail28-db3-R.bigfish.com (Postfix) with ESMTP id C1CC64602DC	for <ietf@ietf.org>; Thu,  3 Jan 2013 09:48:12 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.253.197; KIP:(null); UIP:(null); IPV:NLI; H:DBXPRD0710HT002.eurprd07.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: -21
X-BigFish: PS-21(zz98dI9371I542I1432I1453Izz1de0h1202h1e76h1d1ah1d2ahzz8275bh8275dh1033ILz2dh2a8h5a9h668h839h947hd24hf0ah1177h1179h1288h12a5h12a9h12bdh137ah139eh13b6h1441h1504h1537h162dh1631h1758h17f1h304l1155h)
Received: from mail28-db3 (localhost.localdomain [127.0.0.1]) by mail28-db3 (MessageSwitch) id 1357206486982124_26669; Thu,  3 Jan 2013 09:48:06 +0000 (UTC)
Received: from DB3EHSMHS003.bigfish.com (unknown [10.3.81.239])	by mail28-db3.bigfish.com (Postfix) with ESMTP id E423F420065	for <ietf@ietf.org>; Thu,  3 Jan 2013 09:48:06 +0000 (UTC)
Received: from DBXPRD0710HT002.eurprd07.prod.outlook.com (157.56.253.197) by DB3EHSMHS003.bigfish.com (10.3.87.103) with Microsoft SMTP Server (TLS) id 14.1.225.23; Thu, 3 Jan 2013 09:48:07 +0000
Received: from AMXPRD0310HT003.eurprd03.prod.outlook.com (157.56.248.133) by pod51017.outlook.com (10.255.79.165) with Microsoft SMTP Server (TLS) id 14.16.245.2; Thu, 3 Jan 2013 09:48:05 +0000
Message-ID: <004d01cde997$20fe90a0$4001a8c0@gateway.2wire.net>
From: t.p. <daedulus@btconnect.com>
To: <ietf@ietf.org>
References: <20130102175839.2DDAE18C0BB@mercury.lcs.mit.edu><01OOIM6DH1HW00008S@mauve.mrochek.com> <alpine.LRH.2.01.1301021406190.26011@egate.xpasc.com>
Subject: Re: WCIT outcome?
Date: Thu, 3 Jan 2013 09:45:49 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Originating-IP: [157.56.248.133]
X-OriginatorOrg: btconnect.com
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Jan 2013 09:48:15 -0000

----- Original Message -----
From: "David Morris" <dwm@xpasc.com>
Cc: <ietf@ietf.org>
Sent: Wednesday, January 02, 2013 10:16 PM
>
> On Wed, 2 Jan 2013, ned+ietf@mauve.mrochek.com wrote:
>
> > At one point there was something that said one phone in each home
had to be
> > directly wired without a plug. I don't know if this was a
regulation, a phone
> > company rule, or just a suggestion, but it also fell by the wayside
after
> > Carterphone.
>
> May have varied by baby bell, but in Michigan, you could have as many
> jacks as you wished, but you had to lease them all from the telco.
There
> may have been a rule about having at least one hard wired phone, I
don't
> recall. In those days, the telco owned and was responsible for all
inside
> wiring.
>
> > I certainly saw acoustic coupled equipment in use long after
Carterphone, but
> > in my experience it was because of general intertia/unwillingness to
do the
> > necessary engineering, not because of the lack of connectors.
>
> Probably more to do with portability of accoustic couplers and the
lack of
> provisioning in motels, etc. for jacks.

What a parochial discussion this has become!

Going back to the ITU-T (remember them:-), they, or their predecessors,
defined the interfaces, such as R, S, T, U, and it was then up to
individual governments to proscribe how far the national monopoly
extended.  The USA has a reputation for being liberal whereas where I
was, the monopoly PTT owned the wiring in my house, in my office and
everywhere else which, de facto, gave them a monopoly over the CPE.

One of the achievements of the EU (or its predecessors), perhaps its
only noteworthy achievement, was to pressurise member states to limit
the national monopoly, which in turn made the kind of telecommunications
we have now possible (outside America).

I suspect that large parts of the world have yet to get there.

Tom Petch



From Chris.Dearlove@baesystems.com  Thu Jan  3 01:55:49 2013
Return-Path: <Chris.Dearlove@baesystems.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9B0D221F86AF for <ietf@ietfa.amsl.com>; Thu,  3 Jan 2013 01:55:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 em2C04sEuqTJ for <ietf@ietfa.amsl.com>; Thu,  3 Jan 2013 01:55:49 -0800 (PST)
Received: from ukmta3.baesystems.com (ukmta3.baesystems.com [20.133.40.55]) by ietfa.amsl.com (Postfix) with ESMTP id A8A8921F85F7 for <ietf@ietf.org>; Thu,  3 Jan 2013 01:55:48 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.84,402,1355097600"; d="scan'208";a="252698860"
Received: from unknown (HELO baemasodc004.greenlnk.net) ([10.108.36.11]) by Baemasodc001ir.sharelnk.net with ESMTP; 03 Jan 2013 09:55:47 +0000
Received: from baemasodc005.greenlnk.net ([10.108.52.29]) by baemasodc004.greenlnk.net (Switch-3.4.4/Switch-3.4.4) with ESMTP id r039tlIb032678 for <ietf@ietf.org>; Thu, 3 Jan 2013 09:55:47 GMT
X-IronPort-AV: E=McAfee;i="5400,1158,6943"; a="2319592"
Received: from glkxh0003v.greenlnk.net ([10.109.2.34]) by baemasodc005.greenlnk.net with ESMTP; 03 Jan 2013 09:55:46 +0000
Received: from GLKXM0002V.GREENLNK.net ([169.254.2.7]) by GLKXH0003V.GREENLNK.net ([10.109.2.34]) with mapi id 14.02.0309.002; Thu, 3 Jan 2013 09:55:47 +0000
From: "Dearlove, Christopher (UK)" <Chris.Dearlove@baesystems.com>
To: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>, "ietf@ietf.org" <ietf@ietf.org>
Subject: RE: WCIT outcome?
Thread-Topic: WCIT outcome?
Thread-Index: AQHN5Y2JvnLRPwHtzka5eKT9kbUSBJgvl3qAgAB/ZYCABfyigIAAPvnQgAD+IoCAABPp0A==
Date: Thu, 3 Jan 2013 09:55:46 +0000
Message-ID: <B31EEDDDB8ED7E4A93FDF12A4EECD30D24FE5CCE@GLKXM0002V.GREENLNK.net>
References: <CAMm+Lwh2cHRY+Dk2_SDtZZmUbPcgRpP89u3DHUcniJDrKrX_pw@mail.gmail.com> <CAMzo+1a0-90dnjnvs48a9DcNN9DY_edF5hH0__4XRuCaLHtL6Q@mail.gmail.com> <CAMm+LwjzjLc2-=4EdxwHOi21B3dOBUohYc5hhXZHL_Pk+iBBmQ@mail.gmail.com> <50E439C5.2020808@gmail.com> <B31EEDDDB8ED7E4A93FDF12A4EECD30D24FE4DAF@GLKXM0002V.GREENLNK.net> <50E543C7.6070809@necom830.hpcl.titech.ac.jp>
In-Reply-To: <50E543C7.6070809@necom830.hpcl.titech.ac.jp>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.109.62.6]
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Jan 2013 09:55:49 -0000

It's really not that simple. If it were all the world would be doing it for=
 everything.

--=20
Christopher Dearlove
Senior Principal Engineer, Communications Group
Communications, Networks and Image Analysis Capability
BAE Systems Advanced Technology Centre
West Hanningfield Road, Great Baddow, Chelmsford, CM2 8HN, UK
Tel: +44 1245 242194=C2=A0|  Fax: +44 1245 242124
chris.dearlove@baesystems.com | http://www.baesystems.com

BAE Systems (Operations) Limited
Registered Office: Warwick House, PO Box 87, Farnborough Aerospace Centre, =
Farnborough, Hants, GU14 6YU, UK
Registered in England & Wales No: 1996687

-----Original Message-----
From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of Mas=
ataka Ohta
Sent: 03 January 2013 08:40
To: ietf@ietf.org
Subject: Re: WCIT outcome?

----------------------! WARNING ! ----------------------
This message originates from outside our organisation,
either from an external partner or from the internet.
Keep this in mind if you answer this message.
Follow the 'Report Suspicious Emails' link on IT matters
for instructions on reporting suspicious email messages.
--------------------------------------------------------

Dearlove, Christopher (UK) wrote:

> Given the ever increasing number of mobile devices, one could argue that =
the world
> has never been more dependent on radio spectrum allocation.

If you don't insist on allocating fixed bandwidths, CSMA/CA takes care=20
of most of issues.

=09=09=09=09=09=09Masataka Ohta

********************************************************************
This email and any attachments are confidential to the intended
recipient and may also be privileged. If you are not the intended
recipient please delete it from your system and notify the sender.
You should not copy it or use it for any purpose nor disclose or
distribute its contents to any other person.
********************************************************************


From mohta@necom830.hpcl.titech.ac.jp  Thu Jan  3 04:13:04 2013
Return-Path: <mohta@necom830.hpcl.titech.ac.jp>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C1EAE21F8A7E for <ietf@ietfa.amsl.com>; Thu,  3 Jan 2013 04:13:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.158
X-Spam-Level: 
X-Spam-Status: No, score=0.158 tagged_above=-999 required=5 tests=[AWL=0.248,  BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265]
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 Ne3eXd2drSB1 for <ietf@ietfa.amsl.com>; Thu,  3 Jan 2013 04:13:04 -0800 (PST)
Received: from necom830.hpcl.titech.ac.jp (necom830.hpcl.titech.ac.jp [131.112.32.132]) by ietfa.amsl.com (Postfix) with SMTP id E416021F868B for <ietf@ietf.org>; Thu,  3 Jan 2013 04:13:03 -0800 (PST)
Received: (qmail 56968 invoked from network); 3 Jan 2013 12:13:39 -0000
Received: from necom830.hpcl.titech.ac.jp (HELO ?127.0.0.1?) (131.112.32.132) by necom830.hpcl.titech.ac.jp with SMTP; 3 Jan 2013 12:13:39 -0000
Message-ID: <50E5756A.2090506@necom830.hpcl.titech.ac.jp>
Date: Thu, 03 Jan 2013 21:11:22 +0900
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: "Dearlove, Christopher (UK)" <Chris.Dearlove@baesystems.com>
Subject: Re: WCIT outcome?
References: <CAMm+Lwh2cHRY+Dk2_SDtZZmUbPcgRpP89u3DHUcniJDrKrX_pw@mail.gmail.com> <CAMzo+1a0-90dnjnvs48a9DcNN9DY_edF5hH0__4XRuCaLHtL6Q@mail.gmail.com> <CAMm+LwjzjLc2-=4EdxwHOi21B3dOBUohYc5hhXZHL_Pk+iBBmQ@mail.gmail.com> <50E439C5.2020808@gmail.com> <B31EEDDDB8ED7E4A93FDF12A4EECD30D24FE4DAF@GLKXM0002V.GREENLNK.net> <50E543C7.6070809@necom830.hpcl.titech.ac.jp> <B31EEDDDB8ED7E4A93FDF12A4EECD30D24FE5CCE@GLKXM0002V.GREENLNK.net>
In-Reply-To: <B31EEDDDB8ED7E4A93FDF12A4EECD30D24FE5CCE@GLKXM0002V.GREENLNK.net>
Content-Type: text/plain; charset=ISO-2022-JP
Content-Transfer-Encoding: 7bit
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Jan 2013 12:13:05 -0000

Dearlove, Christopher (UK) wrote:

> It's really not that simple. If it were all the world would be doing it for everything.

You should recognize that all the smart phones are working fine
(or even better than LTE) with Wifi and that Wifi support
prioritized packets.

						Masataka Ohta


From carlosm3011@gmail.com  Thu Jan  3 04:51:53 2013
Return-Path: <carlosm3011@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3C31721F869C for <ietf@ietfa.amsl.com>; Thu,  3 Jan 2013 04:51:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 WNVvMWKtyNyG for <ietf@ietfa.amsl.com>; Thu,  3 Jan 2013 04:51:52 -0800 (PST)
Received: from mail-gh0-f170.google.com (mail-gh0-f170.google.com [209.85.160.170]) by ietfa.amsl.com (Postfix) with ESMTP id A93EE21F8696 for <ietf@ietf.org>; Thu,  3 Jan 2013 04:51:52 -0800 (PST)
Received: by mail-gh0-f170.google.com with SMTP id g14so1752893ghb.1 for <ietf@ietf.org>; Thu, 03 Jan 2013 04:51:52 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=Ye8qmRV8svVq/11c4Ghtx39dmUI5YfwT27hSHmBnPgY=; b=Mpg2GNEGYPl6n59wNGbyQmFSALwqcYtA9cyq7FbPml+q/3pUHLD0IimCgzeS+FTczu e36lNZk3X0prwSqYz7wpIo55fj0GKgS7lcsOBYYmn6Rnzeu/XELzsfG7MB0DXonhs18h Cv4EGOLeAsRUYhmNfdHAjauYhiyNvaOwaeBZ2b9mueES1/liMyDqWMgm+AWE5BNNmcKz K2TUKo8GAlGSkmx8q78Fb81UN2OwVJp5EsmqYW+/TzRRiIV70Z2zml4DLg36P+viqJDn BHXDL5GELJ5RrzqVY2rewXrRdjeshm9+HQuRrys7pOlydkgHtHvjgd2oU2FOcHhhOJy3 0qrg==
X-Received: by 10.101.11.38 with SMTP id o38mr14135442ani.8.1357217512235; Thu, 03 Jan 2013 04:51:52 -0800 (PST)
Received: from europa.local ([2001:13c7:7001:5128:3172:ddba:db70:743d]) by mx.google.com with ESMTPS id s21sm49427947yhb.5.2013.01.03.04.51.49 (version=SSLv3 cipher=OTHER); Thu, 03 Jan 2013 04:51:51 -0800 (PST)
Message-ID: <50E57EE6.9010503@gmail.com>
Date: Thu, 03 Jan 2013 10:51:50 -0200
From: "Carlos M. Martinez" <carlosm3011@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: "Dearlove, Christopher (UK)" <Chris.Dearlove@baesystems.com>
Subject: Re: WCIT outcome?
References: <CAMm+Lwh2cHRY+Dk2_SDtZZmUbPcgRpP89u3DHUcniJDrKrX_pw@mail.gmail.com> <CAMzo+1a0-90dnjnvs48a9DcNN9DY_edF5hH0__4XRuCaLHtL6Q@mail.gmail.com> <CAMm+LwjzjLc2-=4EdxwHOi21B3dOBUohYc5hhXZHL_Pk+iBBmQ@mail.gmail.com> <50E439C5.2020808@gmail.com> <B31EEDDDB8ED7E4A93FDF12A4EECD30D24FE4DAF@GLKXM0002V.GREENLNK.net>
In-Reply-To: <B31EEDDDB8ED7E4A93FDF12A4EECD30D24FE4DAF@GLKXM0002V.GREENLNK.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
Cc: Phillip Hallam-Baker <hallam@gmail.com>, IETF Discussion Mailing List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Jan 2013 12:51:53 -0000

My point was not about the need (or lack thereof) of spectrum
management, but rather the need (or lack thereof) of an international
office for handling spectrum slots.

The kind of allocation management you mention is an easier one to
tackle. Radio allocation for mobile networks is distance-restricted, it
only has to deal with local frequencies unless your are installing
mobile antennas in border towns.

If countries can be good neighbors you don't need an elephantine
international bureaucracy to manage these type of spectrum allocation.
Where I live this has been the case, all cross-border frequency issues
were fixed through peer to peer negotiation between operators.

As for spectrum sales, well, again it's not the ITU who's doing it, the
regulators are.

Large-scale, global, spectrum management remains an issue (i'm thinking
about talk radio, marine/aircraft/satellite communications, navigation
aids and similar applications), but, IMO, is a less demanding/critical
task than it used to be, and thus the workload for the ITU-R should be
less than it used to be.

cheers!

~Carlos

On 1/2/13 3:34 PM, Dearlove, Christopher (UK) wrote:
> Carlos M. Martinez 
>> Radio spectrum allocation was a critical task at the time (it still is,
>> although the world doesn't depend that much on it anymore),
> 
> Given the ever increasing number of mobile devices, one could argue that the world
> has never been more dependent on radio spectrum allocation. It's still not that long since
> the UK Chancellor of the Exchequer made over £20 billion from selling spectrum, something
> possible since international treaties had agreed on its purpose for 3G communications.
> 

From Chris.Dearlove@baesystems.com  Thu Jan  3 05:16:34 2013
Return-Path: <Chris.Dearlove@baesystems.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 14E0521F8BBB for <ietf@ietfa.amsl.com>; Thu,  3 Jan 2013 05:16:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 tqLc6nH7AfY0 for <ietf@ietfa.amsl.com>; Thu,  3 Jan 2013 05:16:33 -0800 (PST)
Received: from ukmta3.baesystems.com (ukmta3.baesystems.com [20.133.40.55]) by ietfa.amsl.com (Postfix) with ESMTP id 041C421F8B6D for <ietf@ietf.org>; Thu,  3 Jan 2013 05:16:32 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.84,403,1355097600"; d="scan'208";a="252770327"
Received: from unknown (HELO baemasodc004.greenlnk.net) ([10.108.36.11]) by Baemasodc001ir.sharelnk.net with ESMTP; 03 Jan 2013 13:16:32 +0000
Received: from baemasodc005.greenlnk.net ([10.108.52.29]) by baemasodc004.greenlnk.net (Switch-3.4.4/Switch-3.4.4) with ESMTP id r03DGVj1001436 for <ietf@ietf.org>; Thu, 3 Jan 2013 13:16:31 GMT
X-IronPort-AV: E=McAfee;i="5400,1158,6943"; a="2351335"
Received: from glkxh0004v.greenlnk.net ([10.109.2.35]) by baemasodc005.greenlnk.net with ESMTP; 03 Jan 2013 13:16:31 +0000
Received: from GLKXM0002V.GREENLNK.net ([169.254.2.7]) by GLKXH0004V.GREENLNK.net ([10.109.2.35]) with mapi id 14.02.0309.002; Thu, 3 Jan 2013 13:16:31 +0000
From: "Dearlove, Christopher (UK)" <Chris.Dearlove@baesystems.com>
To: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
Subject: RE: WCIT outcome?
Thread-Topic: WCIT outcome?
Thread-Index: AQHN5Y2JvnLRPwHtzka5eKT9kbUSBJgvl3qAgAB/ZYCABfyigIAAPvnQgAD+IoCAABPp0IAAJ0MAgAARU4A=
Date: Thu, 3 Jan 2013 13:16:31 +0000
Message-ID: <B31EEDDDB8ED7E4A93FDF12A4EECD30D24FE5D0C@GLKXM0002V.GREENLNK.net>
References: <CAMm+Lwh2cHRY+Dk2_SDtZZmUbPcgRpP89u3DHUcniJDrKrX_pw@mail.gmail.com> <CAMzo+1a0-90dnjnvs48a9DcNN9DY_edF5hH0__4XRuCaLHtL6Q@mail.gmail.com> <CAMm+LwjzjLc2-=4EdxwHOi21B3dOBUohYc5hhXZHL_Pk+iBBmQ@mail.gmail.com> <50E439C5.2020808@gmail.com> <B31EEDDDB8ED7E4A93FDF12A4EECD30D24FE4DAF@GLKXM0002V.GREENLNK.net> <50E543C7.6070809@necom830.hpcl.titech.ac.jp> <B31EEDDDB8ED7E4A93FDF12A4EECD30D24FE5CCE@GLKXM0002V.GREENLNK.net> <50E5756A.2090506@necom830.hpcl.titech.ac.jp>
In-Reply-To: <50E5756A.2090506@necom830.hpcl.titech.ac.jp>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.109.62.6]
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Jan 2013 13:16:34 -0000

Yes, all smart phones support Wi-Fi. In some "unregulated" (not actually en=
tirely so) frequency bands, and with regulated powers, over a short range. =
But the main long range 2G/3G signals are TDMA or CDMA in regulated bands.

--=20
Christopher Dearlove
Senior Principal Engineer, Communications Group
Communications, Networks and Image Analysis Capability
BAE Systems Advanced Technology Centre
West Hanningfield Road, Great Baddow, Chelmsford, CM2 8HN, UK
Tel: +44 1245 242194=A0|  Fax: +44 1245 242124
chris.dearlove@baesystems.com | http://www.baesystems.com

BAE Systems (Operations) Limited
Registered Office: Warwick House, PO Box 87, Farnborough Aerospace Centre, =
Farnborough, Hants, GU14 6YU, UK
Registered in England & Wales No: 1996687


-----Original Message-----
From: Masataka Ohta [mailto:mohta@necom830.hpcl.titech.ac.jp]=20
Sent: 03 January 2013 12:11
To: Dearlove, Christopher (UK)
Cc: ietf@ietf.org
Subject: Re: WCIT outcome?

----------------------! WARNING ! ----------------------
This message originates from outside our organisation,
either from an external partner or from the internet.
Keep this in mind if you answer this message.
Follow the 'Report Suspicious Emails' link on IT matters
for instructions on reporting suspicious email messages.
--------------------------------------------------------

Dearlove, Christopher (UK) wrote:

> It's really not that simple. If it were all the world would be doing it f=
or everything.

You should recognize that all the smart phones are working fine
(or even better than LTE) with Wifi and that Wifi support
prioritized packets.

=09=09=09=09=09=09Masataka Ohta



********************************************************************
This email and any attachments are confidential to the intended
recipient and may also be privileged. If you are not the intended
recipient please delete it from your system and notify the sender.
You should not copy it or use it for any purpose nor disclose or
distribute its contents to any other person.
********************************************************************


From Chris.Dearlove@baesystems.com  Thu Jan  3 05:21:29 2013
Return-Path: <Chris.Dearlove@baesystems.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0E04E21E803A for <ietf@ietfa.amsl.com>; Thu,  3 Jan 2013 05:21:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 nr8uXQMVxwbH for <ietf@ietfa.amsl.com>; Thu,  3 Jan 2013 05:21:28 -0800 (PST)
Received: from ukmta3.baesystems.com (ukmta3.baesystems.com [20.133.40.55]) by ietfa.amsl.com (Postfix) with ESMTP id 015BE21E8034 for <ietf@ietf.org>; Thu,  3 Jan 2013 05:21:27 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.84,403,1355097600"; d="scan'208";a="252771547"
Received: from unknown (HELO baemasodc004.greenlnk.net) ([10.108.36.11]) by Baemasodc001ir.sharelnk.net with ESMTP; 03 Jan 2013 13:21:27 +0000
Received: from baemasodc005.greenlnk.net ([10.108.52.29]) by baemasodc004.greenlnk.net (Switch-3.4.4/Switch-3.4.4) with ESMTP id r03DLQbe004718 for <ietf@ietf.org>; Thu, 3 Jan 2013 13:21:26 GMT
X-IronPort-AV: E=McAfee;i="5400,1158,6943"; a="2351971"
Received: from glkxh0005v.greenlnk.net ([10.109.2.36]) by baemasodc005.greenlnk.net with ESMTP; 03 Jan 2013 13:21:26 +0000
Received: from GLKXM0002V.GREENLNK.net ([169.254.2.7]) by GLKXH0005V.GREENLNK.net ([10.109.2.36]) with mapi id 14.02.0309.002; Thu, 3 Jan 2013 13:21:25 +0000
From: "Dearlove, Christopher (UK)" <Chris.Dearlove@baesystems.com>
To: "Carlos M. Martinez" <carlosm3011@gmail.com>
Subject: RE: WCIT outcome?
Thread-Topic: WCIT outcome?
Thread-Index: AQHN5Y2JvnLRPwHtzka5eKT9kbUSBJgvl3qAgAB/ZYCABfyigIAAPvnQgAFEnACAAAcX4A==
Date: Thu, 3 Jan 2013 13:21:25 +0000
Message-ID: <B31EEDDDB8ED7E4A93FDF12A4EECD30D24FE5D1D@GLKXM0002V.GREENLNK.net>
References: <CAMm+Lwh2cHRY+Dk2_SDtZZmUbPcgRpP89u3DHUcniJDrKrX_pw@mail.gmail.com> <CAMzo+1a0-90dnjnvs48a9DcNN9DY_edF5hH0__4XRuCaLHtL6Q@mail.gmail.com> <CAMm+LwjzjLc2-=4EdxwHOi21B3dOBUohYc5hhXZHL_Pk+iBBmQ@mail.gmail.com> <50E439C5.2020808@gmail.com> <B31EEDDDB8ED7E4A93FDF12A4EECD30D24FE4DAF@GLKXM0002V.GREENLNK.net> <50E57EE6.9010503@gmail.com>
In-Reply-To: <50E57EE6.9010503@gmail.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.109.62.6]
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: Phillip Hallam-Baker <hallam@gmail.com>, IETF Discussion Mailing List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Jan 2013 13:21:29 -0000

I'd like my mobile phone to work all round the world, as it does. It takes =
more than one band, but only a few. And that took international regulation,=
 not just cross-border issues. And I'd like no one to spill interference in=
to the GPS band. And ... It really isn't as simple as you suggest. Yes, of =
course it's national governments that sell off 3G spectrum, but only after =
international agreements established that they could do so.

--=20
Christopher Dearlove
Senior Principal Engineer, Communications Group
Communications, Networks and Image Analysis Capability
BAE Systems Advanced Technology Centre
West Hanningfield Road, Great Baddow, Chelmsford, CM2 8HN, UK
Tel: +44 1245 242194=A0|  Fax: +44 1245 242124
chris.dearlove@baesystems.com | http://www.baesystems.com

BAE Systems (Operations) Limited
Registered Office: Warwick House, PO Box 87, Farnborough Aerospace Centre, =
Farnborough, Hants, GU14 6YU, UK
Registered in England & Wales No: 1996687


-----Original Message-----
From: Carlos M. Martinez [mailto:carlosm3011@gmail.com]=20
Sent: 03 January 2013 12:52
To: Dearlove, Christopher (UK)
Cc: Phillip Hallam-Baker; IETF Discussion Mailing List
Subject: Re: WCIT outcome?

----------------------! WARNING ! ----------------------
This message originates from outside our organisation,
either from an external partner or from the internet.
Keep this in mind if you answer this message.
Follow the 'Report Suspicious Emails' link on IT matters
for instructions on reporting suspicious email messages.
--------------------------------------------------------

My point was not about the need (or lack thereof) of spectrum
management, but rather the need (or lack thereof) of an international
office for handling spectrum slots.

The kind of allocation management you mention is an easier one to
tackle. Radio allocation for mobile networks is distance-restricted, it
only has to deal with local frequencies unless your are installing
mobile antennas in border towns.

If countries can be good neighbors you don't need an elephantine
international bureaucracy to manage these type of spectrum allocation.
Where I live this has been the case, all cross-border frequency issues
were fixed through peer to peer negotiation between operators.

As for spectrum sales, well, again it's not the ITU who's doing it, the
regulators are.

Large-scale, global, spectrum management remains an issue (i'm thinking
about talk radio, marine/aircraft/satellite communications, navigation
aids and similar applications), but, IMO, is a less demanding/critical
task than it used to be, and thus the workload for the ITU-R should be
less than it used to be.

cheers!

~Carlos

On 1/2/13 3:34 PM, Dearlove, Christopher (UK) wrote:
> Carlos M. Martinez=20
>> Radio spectrum allocation was a critical task at the time (it still is,
>> although the world doesn't depend that much on it anymore),
>=20
> Given the ever increasing number of mobile devices, one could argue that =
the world
> has never been more dependent on radio spectrum allocation. It's still no=
t that long since
> the UK Chancellor of the Exchequer made over =A320 billion from selling s=
pectrum, something
> possible since international treaties had agreed on its purpose for 3G co=
mmunications.
>=20


********************************************************************
This email and any attachments are confidential to the intended
recipient and may also be privileged. If you are not the intended
recipient please delete it from your system and notify the sender.
You should not copy it or use it for any purpose nor disclose or
distribute its contents to any other person.
********************************************************************


From mohta@necom830.hpcl.titech.ac.jp  Thu Jan  3 05:40:51 2013
Return-Path: <mohta@necom830.hpcl.titech.ac.jp>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4B23821F8BE0 for <ietf@ietfa.amsl.com>; Thu,  3 Jan 2013 05:40:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.096
X-Spam-Level: 
X-Spam-Status: No, score=0.096 tagged_above=-999 required=5 tests=[AWL=0.186,  BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265]
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 YjwingRScuxE for <ietf@ietfa.amsl.com>; Thu,  3 Jan 2013 05:40:50 -0800 (PST)
Received: from necom830.hpcl.titech.ac.jp (necom830.hpcl.titech.ac.jp [131.112.32.132]) by ietfa.amsl.com (Postfix) with SMTP id 7432621F8BD7 for <ietf@ietf.org>; Thu,  3 Jan 2013 05:40:50 -0800 (PST)
Received: (qmail 57738 invoked from network); 3 Jan 2013 13:41:21 -0000
Received: from necom830.hpcl.titech.ac.jp (HELO ?127.0.0.1?) (131.112.32.132) by necom830.hpcl.titech.ac.jp with SMTP; 3 Jan 2013 13:41:21 -0000
Message-ID: <50E589F3.80302@necom830.hpcl.titech.ac.jp>
Date: Thu, 03 Jan 2013 22:38:59 +0900
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: "Dearlove, Christopher (UK)" <Chris.Dearlove@baesystems.com>
Subject: Re: WCIT outcome?
References: <CAMm+Lwh2cHRY+Dk2_SDtZZmUbPcgRpP89u3DHUcniJDrKrX_pw@mail.gmail.com> <CAMzo+1a0-90dnjnvs48a9DcNN9DY_edF5hH0__4XRuCaLHtL6Q@mail.gmail.com> <CAMm+LwjzjLc2-=4EdxwHOi21B3dOBUohYc5hhXZHL_Pk+iBBmQ@mail.gmail.com> <50E439C5.2020808@gmail.com> <B31EEDDDB8ED7E4A93FDF12A4EECD30D24FE4DAF@GLKXM0002V.GREENLNK.net> <50E543C7.6070809@necom830.hpcl.titech.ac.jp> <B31EEDDDB8ED7E4A93FDF12A4EECD30D24FE5CCE@GLKXM0002V.GREENLNK.net> <50E5756A.2090506@necom830.hpcl.titech.ac.jp> <B31EEDDDB8ED7E4A93FDF12A4EECD30D24FE5D0C@GLKXM0002V.GREENLNK.net>
In-Reply-To: <B31EEDDDB8ED7E4A93FDF12A4EECD30D24FE5D0C@GLKXM0002V.GREENLNK.net>
Content-Type: text/plain; charset=ISO-2022-JP
Content-Transfer-Encoding: 7bit
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Jan 2013 13:40:51 -0000

Dearlove, Christopher (UK) wrote:

> Yes, all smart phones support Wi-Fi. In some "unregulated" (not
> actually entirely so) frequency bands, and with regulated powers,
> over a short range.

CSMA/CA can also work over a long range too and can, in a sense,
fairly arbitrate packets from different countries at border towns.

> But the main long range 2G/3G signals are
> TDMA or CDMA in regulated bands.

Forget them.

						Masataka Ohta

From john-ietf@jck.com  Thu Jan  3 05:47:54 2013
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4BA0321E8054 for <ietf@ietfa.amsl.com>; Thu,  3 Jan 2013 05:47:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 tp6fFTCQIaze for <ietf@ietfa.amsl.com>; Thu,  3 Jan 2013 05:47:53 -0800 (PST)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 33BB621E8050 for <ietf@ietf.org>; Thu,  3 Jan 2013 05:47:52 -0800 (PST)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1Tql9B-000IFP-PE; Thu, 03 Jan 2013 08:47:49 -0500
Date: Thu, 03 Jan 2013 08:47:44 -0500
From: John C Klensin <john-ietf@jck.com>
To: ned+ietf@mauve.mrochek.com, jnc@mercury.lcs.mit.edu
Subject: Re: Acoustic couplers (was: WCIT outcome?)
Message-ID: <9FDEEFFEF5F2A03DF5798648@JcK-HP8200.jck.com>
In-Reply-To: <01OOIM6DH1HW00008S@mauve.mrochek.com>
References: <20130102175839.2DDAE18C0BB@mercury.lcs.mit.edu> <01OOIM6DH1HW00008S@mauve.mrochek.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Jan 2013 13:47:54 -0000

--On Wednesday, January 02, 2013 13:34 -0800
ned+ietf@mauve.mrochek.com wrote:

>>     > From: John Day <jeanjour@comcast.net>
> 
>>     > I remember when a modem came with an 'acoustic coupler'
>>     > because connecting it directly to the phone line was
>>     > illegal. No, there was nothing illegal about it. The
>>     > reason for acoustic couplers was that the RJ-11 had
>>     > been invented yet and it was a pain to unscrew the box
>>     > on the wall and re-wire every time you wanted to
>>     > connect.
>>     > ...
>>     > It may have been illegal in some countries but
>>     > certainly not in the US.
> 
>> Huh? Remember the Carterphone decision?
> 
> Absolutely. Too bad the FCC didn't see fit to extend it to
> wireless.
>...
> At one point there was something that said one phone in each
> home had to be directly wired without a plug. I don't know if
> this was a regulation, a phone company rule, or just a
> suggestion, but it also fell by the wayside after Carterphone.

IIR regulation, in many states even for a while
post-Carterphone, and justified, again IIR -- as many things
have been justified in more recent years-- on the grounds of
emergency services applications.  After all, if there were an
emergency, you wouldn't want to go hunting for an unplugged
phone or, especially, to get something working that required
external (to the phone system) power.

And, while my memory of the period is a little vague at this
point, I'm pretty sure that the four-pin jack (and a few other
proprietary terminal-device connectors) showed up
pre-Carterphone, when AT&T/WE was (i) trying to sell alternate
phones (notably the early "Princess") to prove that what became
Carterphone wasn't necessary because they could meet the
relevant market demands and (ii) arguing that, if one wanted to
connect third-party equipment, they could supply a network
protection device into which the third-party stuff could plug.

RJ11 and friends came along when the FCC finally got rid of the
protective device/coupler nonsense in the mid-70s, long after
Carterphone (1968) and, in a series of steps that weren't
complete until the last half of the 90s, regulated/required
first the jacks then the wiring pinouts.

> I certainly saw acoustic coupled equipment in use long after
> Carterphone, but in my experience it was because of general
> intertia/unwillingness to do the necessary engineering, not
> because of the lack of connectors.

My recollection is that acoustic couplers started out as an
attempt to get around the protective device rules, not the "no
interconnection" one.  It that is correct, it would provide an
additional explanation for their being around into at least the
mid-70s.  I think part of what killed them was the growth of
different handset shapes along with multiple manufacturers of
telephones.  Those different shapes meant that one could no
longer design a recessed-cup device with fixed spread between
the two cups that would form a tight seal with all relevant
handset shapes.   I do have an acoustic coupling device from the
mid-90s that had an adjustable distance between the receiving
and sending attachments and a strap to attach it to the phone --
worked pretty well when one wanted to attach a modem in, e.g., a
hotel with hardwired connections between phone and wall and
setups that made pulling off the terminal cover and attaching
alligator clips impractical but it is clearly an exception to
Ned's suggestion that failure to make the transition was at
least partially due to unwillingness to do new engineering/
design work.

The situation in other countries was, of course, different.
Especially in places where the telephone carrier was effectively
its own regulator or managed to convince the regulators that
content mattered as much or more than physical connections,
there was a requirement for different jacks (usually at a higher
monthly rate) for modems and fax machines than was used for
voice.  I believe that particular approach survived and may have
been reinforced by efforts to promote deregulation within ITU
because the relevant carriers argued that the early deregulation
efforts applied only to POTS service and not to "data" ones.
That approach and position was contemporaneous with national
regulations in many countries that one could run all of the
TCP/IP services one wanted as long as they were run over the
national X.25 profile and sometimes as long as one claimed they
were "transitional" until OSI Connection-mode stabilized.
There might be a useful lesson or two in that bit of history.

    john


From carlosm3011@gmail.com  Thu Jan  3 05:50:34 2013
Return-Path: <carlosm3011@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A3D6C21F8C18 for <ietf@ietfa.amsl.com>; Thu,  3 Jan 2013 05:50:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 tlWeDsrHgTpJ for <ietf@ietfa.amsl.com>; Thu,  3 Jan 2013 05:50:34 -0800 (PST)
Received: from mail-qa0-f52.google.com (mail-qa0-f52.google.com [209.85.216.52]) by ietfa.amsl.com (Postfix) with ESMTP id 137F221F8C17 for <ietf@ietf.org>; Thu,  3 Jan 2013 05:50:33 -0800 (PST)
Received: by mail-qa0-f52.google.com with SMTP id d13so9691921qak.18 for <ietf@ietf.org>; Thu, 03 Jan 2013 05:50:33 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:reply-to:user-agent:mime-version:to :cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=jvLhLxncvHLVESH+XQKkqwJC83Nf7aSU2CVMKPvlnkU=; b=TCOucpb6+vY8nXgF1Q3+HawzUN+LFv1BBf0hPN94i/nlKFy0GtZhyblJzMIvxzGsgt Vz7W6aiov1Iv+PYnVm4zCxxQTFPlaVEqPMgBkJ3jBpguAGnnGXN1KLxhG5iZhz6W/ERQ VhMCPKtWYxuuoGFVQ0MlomQ206e+lv4PrGT6JG1yvuGSn1Y8S+qOzIADVFKFCJrCTLlp YyMXqEOAP5Kx35gten9+8t4xp85n1xkn8YSxelx3x5Fu89LL8ezrnM8GvgYZ49ABN2NK p0kEW7Q8eInD9OaRaq0rBVETnNASb2JeTxCMrGmLDg9g5Z1AryBia8deboirci3V47HP vT/w==
X-Received: by 10.49.14.202 with SMTP id r10mr32769821qec.10.1357221032316; Thu, 03 Jan 2013 05:50:32 -0800 (PST)
Received: from europa.local ([2001:13c7:7001:5128:3172:ddba:db70:743d]) by mx.google.com with ESMTPS id gv5sm13614269qab.11.2013.01.03.05.50.29 (version=SSLv3 cipher=OTHER); Thu, 03 Jan 2013 05:50:31 -0800 (PST)
Message-ID: <50E58CA6.2000901@gmail.com>
Date: Thu, 03 Jan 2013 11:50:30 -0200
From: "Carlos M. Martinez" <carlosm3011@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: "Dearlove, Christopher (UK)" <Chris.Dearlove@baesystems.com>
Subject: Re: WCIT outcome?
References: <CAMm+Lwh2cHRY+Dk2_SDtZZmUbPcgRpP89u3DHUcniJDrKrX_pw@mail.gmail.com> <CAMzo+1a0-90dnjnvs48a9DcNN9DY_edF5hH0__4XRuCaLHtL6Q@mail.gmail.com> <CAMm+LwjzjLc2-=4EdxwHOi21B3dOBUohYc5hhXZHL_Pk+iBBmQ@mail.gmail.com> <50E439C5.2020808@gmail.com> <B31EEDDDB8ED7E4A93FDF12A4EECD30D24FE4DAF@GLKXM0002V.GREENLNK.net> <50E57EE6.9010503@gmail.com> <B31EEDDDB8ED7E4A93FDF12A4EECD30D24FE5D1D@GLKXM0002V.GREENLNK.net>
In-Reply-To: <B31EEDDDB8ED7E4A93FDF12A4EECD30D24FE5D1D@GLKXM0002V.GREENLNK.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: Phillip Hallam-Baker <hallam@gmail.com>, IETF Discussion Mailing List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: carlos@lacnic.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Jan 2013 13:50:34 -0000

My only point is that it is not what is used to be. But we can agree to
disagree.

Happy new year all by the way.

~C.

On 1/3/13 11:21 AM, Dearlove, Christopher (UK) wrote:
> I'd like my mobile phone to work all round the world, as it does. It takes more than one band, but only a few. And that took international regulation, not just cross-border issues. And I'd like no one to spill interference into the GPS band. And ... It really isn't as simple as you suggest. Yes, of course it's national governments that sell off 3G spectrum, but only after international agreements established that they could do so.
> 

From hallam@gmail.com  Thu Jan  3 06:28:53 2013
Return-Path: <hallam@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D2CBD21E8053 for <ietf@ietfa.amsl.com>; Thu,  3 Jan 2013 06:28:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.567
X-Spam-Level: 
X-Spam-Status: No, score=-3.567 tagged_above=-999 required=5 tests=[AWL=0.031,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
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 JSDUPpLBOLrO for <ietf@ietfa.amsl.com>; Thu,  3 Jan 2013 06:28:52 -0800 (PST)
Received: from mail-ob0-f181.google.com (mail-ob0-f181.google.com [209.85.214.181]) by ietfa.amsl.com (Postfix) with ESMTP id 6F2B921F8C09 for <ietf@ietf.org>; Thu,  3 Jan 2013 06:28:52 -0800 (PST)
Received: by mail-ob0-f181.google.com with SMTP id oi10so13861556obb.12 for <ietf@ietf.org>; Thu, 03 Jan 2013 06:28:52 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=fExED97zIKHlm2sz5QVqQY4/DZWZ8S3PHqX23B3yxw8=; b=tNkMTzTRMnCtl85kzqR+e8iwRJj6YPPFmRLOKm0u/HsmQuUPwZpQ+itKMZJleHN7ts O/3LLH/oqBAOebgCXMZduih08uCWxOljfY3N8tN1F4TdmNHX85wuFgDn6eeARe/UwlGp U5zc+PxA5AnoHiXhiZnfFlb1856QaqyC8GXZCtlI35X7xD1hSbCd4ATuIbBK07IfJQG3 1xy3NSU/MKm+5oy2u3L4RGNiNizFxPxrPvASzEvZyx8ZzGRFN/gccKDD4GEYDIJKyVa3 aVay5cpdD0+lukhv47d42/755CP2bQICMLll/wcT6iDBGSrVI9RDtaR8DjRHpRi1f6IY GbtA==
MIME-Version: 1.0
Received: by 10.60.27.199 with SMTP id v7mr27581176oeg.23.1357223332002; Thu, 03 Jan 2013 06:28:52 -0800 (PST)
Received: by 10.76.19.43 with HTTP; Thu, 3 Jan 2013 06:28:51 -0800 (PST)
In-Reply-To: <B31EEDDDB8ED7E4A93FDF12A4EECD30D24FE5D1D@GLKXM0002V.GREENLNK.net>
References: <CAMm+Lwh2cHRY+Dk2_SDtZZmUbPcgRpP89u3DHUcniJDrKrX_pw@mail.gmail.com> <CAMzo+1a0-90dnjnvs48a9DcNN9DY_edF5hH0__4XRuCaLHtL6Q@mail.gmail.com> <CAMm+LwjzjLc2-=4EdxwHOi21B3dOBUohYc5hhXZHL_Pk+iBBmQ@mail.gmail.com> <50E439C5.2020808@gmail.com> <B31EEDDDB8ED7E4A93FDF12A4EECD30D24FE4DAF@GLKXM0002V.GREENLNK.net> <50E57EE6.9010503@gmail.com> <B31EEDDDB8ED7E4A93FDF12A4EECD30D24FE5D1D@GLKXM0002V.GREENLNK.net>
Date: Thu, 3 Jan 2013 09:28:51 -0500
Message-ID: <CAMm+Lwj9TCL4ya99C6Y051c+Cf0aCb2m_Um8i01a2s6ymzOqag@mail.gmail.com>
Subject: Re: WCIT outcome?
From: Phillip Hallam-Baker <hallam@gmail.com>
To: "Dearlove, Christopher (UK)" <Chris.Dearlove@baesystems.com>
Content-Type: multipart/alternative; boundary=e89a8fb2007895b9a804d2632e09
Cc: IETF Discussion Mailing List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Jan 2013 14:28:54 -0000

--e89a8fb2007895b9a804d2632e09
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

$20 billion for the wireless spectrum in the UK was quite a chunk of
change. And the US government raised $19 billion in a later auction. So it
is hardly surprising that there is intense government interest in
communications technology.

But one of the reasons those auctions were originally proposed was to force
various military interests to stop hogging 95% of the available bandwidth
on the offchance they might have a use for it some day. Putting a price on
the resource forced the Pentagon and GCHQ etc. to explain why they really
needed the resource which in most cases they didn't.

There are certainly a lot of political issues surrounding communications.
It is not an accident that the West German TV system was compatible with
the East German system so that East German sets could receive West German
signals. That is how the cold war was won.

But that does not change the principle that a technology that depends on
government regulation to work properly has a design error and a technology
that depends on inter-government regulation is worse.

Wireless spectrum interference was a consequence of broadcast technology.
Telephone monopolies were the consequence of the limited capabilities of
electromagnetic relay switch gear. We do not need to resort to either

There is a government interest in preventing the accumulation of monopoly
power through technical lock in. Europe has done a much better job of that
than the US. But modern wireless devices are simply a DSP connected to a
bit of wire. Adapting to pretty much any band is merely a matter of
software.


Dean Acheson once said that Britain has lost an empire and is looking for a
role. The ITU has the same problem. The technical limitations that made it
necessary to regulate communications through inter-governmental agreements
have largely disappeared. So now the only constituency the chair can find
is the governments who want to regulate communications because they are
afraid that their political institutions are fundamentally unstable.



On Thu, Jan 3, 2013 at 8:21 AM, Dearlove, Christopher (UK) <
Chris.Dearlove@baesystems.com> wrote:

> I'd like my mobile phone to work all round the world, as it does. It take=
s
> more than one band, but only a few. And that took international regulatio=
n,
> not just cross-border issues. And I'd like no one to spill interference
> into the GPS band. And ... It really isn't as simple as you suggest. Yes,
> of course it's national governments that sell off 3G spectrum, but only
> after international agreements established that they could do so.
>
> --
> Christopher Dearlove
> Senior Principal Engineer, Communications Group
> Communications, Networks and Image Analysis Capability
> BAE Systems Advanced Technology Centre
> West Hanningfield Road, Great Baddow, Chelmsford, CM2 8HN, UK
> Tel: +44 1245 242194 |  Fax: +44 1245 242124
> chris.dearlove@baesystems.com | http://www.baesystems.com
>
> BAE Systems (Operations) Limited
> Registered Office: Warwick House, PO Box 87, Farnborough Aerospace Centre=
,
> Farnborough, Hants, GU14 6YU, UK
> Registered in England & Wales No: 1996687
>
>
> -----Original Message-----
> From: Carlos M. Martinez [mailto:carlosm3011@gmail.com]
> Sent: 03 January 2013 12:52
> To: Dearlove, Christopher (UK)
> Cc: Phillip Hallam-Baker; IETF Discussion Mailing List
> Subject: Re: WCIT outcome?
>
> ----------------------! WARNING ! ----------------------
> This message originates from outside our organisation,
> either from an external partner or from the internet.
> Keep this in mind if you answer this message.
> Follow the 'Report Suspicious Emails' link on IT matters
> for instructions on reporting suspicious email messages.
> --------------------------------------------------------
>
> My point was not about the need (or lack thereof) of spectrum
> management, but rather the need (or lack thereof) of an international
> office for handling spectrum slots.
>
> The kind of allocation management you mention is an easier one to
> tackle. Radio allocation for mobile networks is distance-restricted, it
> only has to deal with local frequencies unless your are installing
> mobile antennas in border towns.
>
> If countries can be good neighbors you don't need an elephantine
> international bureaucracy to manage these type of spectrum allocation.
> Where I live this has been the case, all cross-border frequency issues
> were fixed through peer to peer negotiation between operators.
>
> As for spectrum sales, well, again it's not the ITU who's doing it, the
> regulators are.
>
> Large-scale, global, spectrum management remains an issue (i'm thinking
> about talk radio, marine/aircraft/satellite communications, navigation
> aids and similar applications), but, IMO, is a less demanding/critical
> task than it used to be, and thus the workload for the ITU-R should be
> less than it used to be.
>
> cheers!
>
> ~Carlos
>
> On 1/2/13 3:34 PM, Dearlove, Christopher (UK) wrote:
> > Carlos M. Martinez
> >> Radio spectrum allocation was a critical task at the time (it still is=
,
> >> although the world doesn't depend that much on it anymore),
> >
> > Given the ever increasing number of mobile devices, one could argue tha=
t
> the world
> > has never been more dependent on radio spectrum allocation. It's still
> not that long since
> > the UK Chancellor of the Exchequer made over =A320 billion from selling
> spectrum, something
> > possible since international treaties had agreed on its purpose for 3G
> communications.
> >
>
>
> ********************************************************************
> This email and any attachments are confidential to the intended
> recipient and may also be privileged. If you are not the intended
> recipient please delete it from your system and notify the sender.
> You should not copy it or use it for any purpose nor disclose or
> distribute its contents to any other person.
> ********************************************************************
>
>


--=20
Website: http://hallambaker.com/

--e89a8fb2007895b9a804d2632e09
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

$20 billion for the wireless spectrum in the UK was quite a chunk of change=
. And the US government raised $19 billion in a later auction. So it is har=
dly surprising that there is intense government interest in communications =
technology.<div>
<br></div><div>But one of the reasons those auctions were originally propos=
ed was to force various military interests to stop hogging 95% of the avail=
able bandwidth on the offchance they might have a use for it some day. Putt=
ing a price on the resource forced the Pentagon and GCHQ etc. to explain wh=
y they really needed the resource which in most cases they didn&#39;t.</div=
>
<div><br></div><div>There are certainly a lot of political issues surroundi=
ng communications. It is not an accident that the West German TV system was=
 compatible with the East German system so that East German sets could rece=
ive West German signals. That is how the cold war was won.=A0</div>
<div><br></div><div>But that does not change the principle that a technolog=
y that depends on government regulation to work properly has a design error=
 and a technology that depends on inter-government regulation is worse.=A0<=
/div>
<div><br></div><div>Wireless spectrum interference was a consequence of bro=
adcast technology. Telephone monopolies were the consequence of the limited=
 capabilities of electromagnetic relay switch gear. We do not need to resor=
t to either=A0</div>
<div><br></div><div>There is a government interest in preventing the accumu=
lation of monopoly power through technical lock in. Europe has done a much =
better job of that than the US. But modern wireless devices are simply a DS=
P connected to a bit of wire. Adapting to pretty much any band is merely a =
matter of software.</div>
<div><br></div><div><br></div><div>Dean Acheson once said that Britain has =
lost an empire and is looking for a role. The ITU has the same problem. The=
 technical limitations that made it necessary to regulate communications th=
rough inter-governmental agreements have largely disappeared. So now the on=
ly constituency the chair can find is the governments who want to regulate =
communications because they are afraid that their political institutions ar=
e fundamentally unstable.</div>
<div><br></div><div><br></div><div><br><div class=3D"gmail_quote">On Thu, J=
an 3, 2013 at 8:21 AM, Dearlove, Christopher (UK) <span dir=3D"ltr">&lt;<a =
href=3D"mailto:Chris.Dearlove@baesystems.com" target=3D"_blank">Chris.Dearl=
ove@baesystems.com</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">I&#39;d like my mobile phone to work all rou=
nd the world, as it does. It takes more than one band, but only a few. And =
that took international regulation, not just cross-border issues. And I&#39=
;d like no one to spill interference into the GPS band. And ... It really i=
sn&#39;t as simple as you suggest. Yes, of course it&#39;s national governm=
ents that sell off 3G spectrum, but only after international agreements est=
ablished that they could do so.<br>

<div class=3D"im"><br>
--<br>
Christopher Dearlove<br>
Senior Principal Engineer, Communications Group<br>
Communications, Networks and Image Analysis Capability<br>
BAE Systems Advanced Technology Centre<br>
West Hanningfield Road, Great Baddow, Chelmsford, CM2 8HN, UK<br>
Tel: <a href=3D"tel:%2B44%201245%20242194" value=3D"+441245242194">+44 1245=
 242194</a>=A0| =A0Fax: <a href=3D"tel:%2B44%201245%20242124" value=3D"+441=
245242124">+44 1245 242124</a><br>
<a href=3D"mailto:chris.dearlove@baesystems.com">chris.dearlove@baesystems.=
com</a> | <a href=3D"http://www.baesystems.com" target=3D"_blank">http://ww=
w.baesystems.com</a><br>
<br>
BAE Systems (Operations) Limited<br>
Registered Office: Warwick House, PO Box 87, Farnborough Aerospace Centre, =
Farnborough, Hants, GU14 6YU, UK<br>
Registered in England &amp; Wales No: 1996687<br>
<br>
<br>
</div>-----Original Message-----<br>
From: Carlos M. Martinez [mailto:<a href=3D"mailto:carlosm3011@gmail.com">c=
arlosm3011@gmail.com</a>]<br>
Sent: 03 January 2013 12:52<br>
To: Dearlove, Christopher (UK)<br>
Cc: Phillip Hallam-Baker; IETF Discussion Mailing List<br>
Subject: Re: WCIT outcome?<br>
<br>
----------------------! WARNING ! ----------------------<br>
This message originates from outside our organisation,<br>
either from an external partner or from the internet.<br>
Keep this in mind if you answer this message.<br>
Follow the &#39;Report Suspicious Emails&#39; link on IT matters<br>
for instructions on reporting suspicious email messages.<br>
--------------------------------------------------------<br>
<div class=3D"HOEnZb"><div class=3D"h5"><br>
My point was not about the need (or lack thereof) of spectrum<br>
management, but rather the need (or lack thereof) of an international<br>
office for handling spectrum slots.<br>
<br>
The kind of allocation management you mention is an easier one to<br>
tackle. Radio allocation for mobile networks is distance-restricted, it<br>
only has to deal with local frequencies unless your are installing<br>
mobile antennas in border towns.<br>
<br>
If countries can be good neighbors you don&#39;t need an elephantine<br>
international bureaucracy to manage these type of spectrum allocation.<br>
Where I live this has been the case, all cross-border frequency issues<br>
were fixed through peer to peer negotiation between operators.<br>
<br>
As for spectrum sales, well, again it&#39;s not the ITU who&#39;s doing it,=
 the<br>
regulators are.<br>
<br>
Large-scale, global, spectrum management remains an issue (i&#39;m thinking=
<br>
about talk radio, marine/aircraft/satellite communications, navigation<br>
aids and similar applications), but, IMO, is a less demanding/critical<br>
task than it used to be, and thus the workload for the ITU-R should be<br>
less than it used to be.<br>
<br>
cheers!<br>
<br>
~Carlos<br>
<br>
On 1/2/13 3:34 PM, Dearlove, Christopher (UK) wrote:<br>
&gt; Carlos M. Martinez<br>
&gt;&gt; Radio spectrum allocation was a critical task at the time (it stil=
l is,<br>
&gt;&gt; although the world doesn&#39;t depend that much on it anymore),<br=
>
&gt;<br>
&gt; Given the ever increasing number of mobile devices, one could argue th=
at the world<br>
&gt; has never been more dependent on radio spectrum allocation. It&#39;s s=
till not that long since<br>
&gt; the UK Chancellor of the Exchequer made over =A320 billion from sellin=
g spectrum, something<br>
&gt; possible since international treaties had agreed on its purpose for 3G=
 communications.<br>
&gt;<br>
<br>
<br>
</div></div><div class=3D"HOEnZb"><div class=3D"h5">***********************=
*********************************************<br>
This email and any attachments are confidential to the intended<br>
recipient and may also be privileged. If you are not the intended<br>
recipient please delete it from your system and notify the sender.<br>
You should not copy it or use it for any purpose nor disclose or<br>
distribute its contents to any other person.<br>
********************************************************************<br>
<br>
</div></div></blockquote></div><br><br clear=3D"all"><div><br></div>-- <br>=
Website: <a href=3D"http://hallambaker.com/">http://hallambaker.com/</a><br=
>
</div>

--e89a8fb2007895b9a804d2632e09--

From dhc@dcrocker.net  Thu Jan  3 06:53:02 2013
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A6E7821E805F for <ietf@ietfa.amsl.com>; Thu,  3 Jan 2013 06:53:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.358
X-Spam-Level: 
X-Spam-Status: No, score=-6.358 tagged_above=-999 required=5 tests=[AWL=0.241,  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 aMENzOQzs+N1 for <ietf@ietfa.amsl.com>; Thu,  3 Jan 2013 06:53:01 -0800 (PST)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 78D1A21E805D for <ietf@ietf.org>; Thu,  3 Jan 2013 06:53:01 -0800 (PST)
Received: from [192.168.1.66] (76-218-9-215.lightspeed.sntcca.sbcglobal.net [76.218.9.215]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id r03Equxl007858 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 3 Jan 2013 06:52:58 -0800
Message-ID: <50E59B43.8000702@dcrocker.net>
Date: Thu, 03 Jan 2013 06:52:51 -0800
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: Ned Freed <ned.freed@mrochek.com>
Subject: Re: Acoustic couplers
References: <20130102175839.2DDAE18C0BB@mercury.lcs.mit.edu> <01OOIM6DH1HW00008S@mauve.mrochek.com> <50E4AFAF.4000506@dcrocker.net> <01OOIXYRHRN000008S@mauve.mrochek.com>
In-Reply-To: <01OOIXYRHRN000008S@mauve.mrochek.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Thu, 03 Jan 2013 06:53:01 -0800 (PST)
Cc: ned+ietf@mauve.mrochek.com, jnc@mercury.lcs.mit.edu, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Jan 2013 14:53:02 -0000

On 1/2/2013 7:08 PM, Ned Freed wrote:
> Of course. However, we're talking about post-Carterphone here.
> Carterphone was
> 1968, and I'm sure four pin plugs were in use by then.

Not in Los Angeles.  As I recall, all the phone around there were 
hardwired into the 70s.


> Also keep in mind that AT&T fought the Carterphone decision for many years.

So it would seem...

I went to work at MCI in 1983, building MCI Mail.  Our group was on M 
street, near corporate HQ.  One morning I got a call telling me to come 
into work wearing sloppy clothes. (This was normally a 3-piece suit 
place.)  There had been a fire on the floor above, where the MCI 
attorneys for the case against AT&T worked.  Lots of water and smoke 
damage.  The claim was that the fire had burned, ummmmm... especially hot...


> A line mod was probably against the rules irrespective of Carterphone in
> those
> days. But had you bought your own phone with a ringer switch and hooked
> that

Not allowed at that point.  All user equipment that was wired to the 
system had to come from the phone company in L.A.


d/
-- 
  Dave Crocker
  Brandenburg InternetWorking
  bbiw.net

From mohta@necom830.hpcl.titech.ac.jp  Thu Jan  3 06:53:32 2013
Return-Path: <mohta@necom830.hpcl.titech.ac.jp>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 27CC421E8083 for <ietf@ietfa.amsl.com>; Thu,  3 Jan 2013 06:53:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.059
X-Spam-Level: 
X-Spam-Status: No, score=0.059 tagged_above=-999 required=5 tests=[AWL=0.149,  BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265]
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 xrxR-ik93xV6 for <ietf@ietfa.amsl.com>; Thu,  3 Jan 2013 06:53:30 -0800 (PST)
Received: from necom830.hpcl.titech.ac.jp (necom830.hpcl.titech.ac.jp [131.112.32.132]) by ietfa.amsl.com (Postfix) with SMTP id D114B21E8086 for <ietf@ietf.org>; Thu,  3 Jan 2013 06:53:15 -0800 (PST)
Received: (qmail 58172 invoked from network); 3 Jan 2013 14:53:43 -0000
Received: from necom830.hpcl.titech.ac.jp (HELO ?127.0.0.1?) (131.112.32.132) by necom830.hpcl.titech.ac.jp with SMTP; 3 Jan 2013 14:53:43 -0000
Message-ID: <50E59AE4.9080504@necom830.hpcl.titech.ac.jp>
Date: Thu, 03 Jan 2013 23:51:16 +0900
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: WCIT outcome?
References: <CAMm+Lwh2cHRY+Dk2_SDtZZmUbPcgRpP89u3DHUcniJDrKrX_pw@mail.gmail.com> <CAMzo+1a0-90dnjnvs48a9DcNN9DY_edF5hH0__4XRuCaLHtL6Q@mail.gmail.com> <CAMm+LwjzjLc2-=4EdxwHOi21B3dOBUohYc5hhXZHL_Pk+iBBmQ@mail.gmail.com> <50E439C5.2020808@gmail.com> <B31EEDDDB8ED7E4A93FDF12A4EECD30D24FE4DAF@GLKXM0002V.GREENLNK.net> <50E57EE6.9010503@gmail.com> <B31EEDDDB8ED7E4A93FDF12A4EECD30D24FE5D1D@GLKXM0002V.GREENLNK.net> <CAMm+Lwj9TCL4ya99C6Y051c+Cf0aCb2m_Um8i01a2s6ymzOqag@mail.gmail.com>
In-Reply-To: <CAMm+Lwj9TCL4ya99C6Y051c+Cf0aCb2m_Um8i01a2s6ymzOqag@mail.gmail.com>
Content-Type: text/plain; charset=ISO-2022-JP
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Jan 2013 14:53:32 -0000

Phillip Hallam-Baker wrote:

> But one of the reasons those auctions were originally proposed was to force
> various military interests to stop hogging 95% of the available bandwidth
> on the offchance they might have a use for it some day. Putting a price on
> the resource forced the Pentagon and GCHQ etc. to explain why they really
> needed the resource which in most cases they didn't.

If they are winning, they need the resource not inside but outside,
of their border.

If they really need them inside their border, they are loosing a
war, which authorizes them to preempt all the already assigned
bandwidth within their border.

Anyway, there can be no inter-border coordination by ITU-T
between fighting countries.

						Masataka Ohta

From steve@shinkuro.com  Thu Jan  3 07:08:53 2013
Return-Path: <steve@shinkuro.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6147921F8C0F for <ietf@ietfa.amsl.com>; Thu,  3 Jan 2013 07:08:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.469
X-Spam-Level: 
X-Spam-Status: No, score=-1.469 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DSL=1.129, UNPARSEABLE_RELAY=0.001]
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 jjy-k1EquEId for <ietf@ietfa.amsl.com>; Thu,  3 Jan 2013 07:08:52 -0800 (PST)
Received: from execdsl.com (remote.shinkuro.com [50.56.68.178]) by ietfa.amsl.com (Postfix) with ESMTP id ACD9521F8C12 for <ietf@ietf.org>; Thu,  3 Jan 2013 07:08:52 -0800 (PST)
Received: from dummy.name; Thu, 03 Jan 2013 15:12:30 +0000
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Subject: Re: Acoustic couplers
From: Steve Crocker <steve@shinkuro.com>
In-Reply-To: <50E59B43.8000702@dcrocker.net>
Date: Thu, 3 Jan 2013 10:10:47 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <2877F05C-BF25-42DE-BF77-1854CC955A54@shinkuro.com>
References: <20130102175839.2DDAE18C0BB@mercury.lcs.mit.edu> <01OOIM6DH1HW00008S@mauve.mrochek.com> <50E4AFAF.4000506@dcrocker.net> <01OOIXYRHRN000008S@mauve.mrochek.com> <50E59B43.8000702@dcrocker.net>
To: dcrocker@bbiw.net
X-Mailer: Apple Mail (2.1499)
Cc: ned+ietf@mauve.mrochek.com, Ned Freed <ned.freed@mrochek.com>, jnc@mercury.lcs.mit.edu, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Jan 2013 15:08:53 -0000

In 1974 I moved into a condo complex in Marina del Rey near USC-ISI.  As =
has been my usual practice, I ordered two POTS lines and I went to the =
phone company to get the phones.  The condo was pre-wired with jacks in =
each of the major rooms.  The phones I got from the phone company came =
with plugs that were wired for either line 1 or line 2.  It took me a =
minute of incredulity to understand the system.  Each jack was wired for =
both lines, and each phone was wired to connect to one or the other of =
the two lines.  Clever but definitely different from anything I had seen =
before.  I could move the phones from room to room.  Each phone "knew" =
whether it was for line 1 or line 2.

Steve

On Jan 3, 2013, at 9:52 AM, Dave Crocker <dhc@dcrocker.net> wrote:

>=20
>=20
> On 1/2/2013 7:08 PM, Ned Freed wrote:
>> Of course. However, we're talking about post-Carterphone here.
>> Carterphone was
>> 1968, and I'm sure four pin plugs were in use by then.
>=20
> Not in Los Angeles.  As I recall, all the phone around there were =
hardwired into the 70s.
>=20
>=20
>> Also keep in mind that AT&T fought the Carterphone decision for many =
years.
>=20
> So it would seem...
>=20
> I went to work at MCI in 1983, building MCI Mail.  Our group was on M =
street, near corporate HQ.  One morning I got a call telling me to come =
into work wearing sloppy clothes. (This was normally a 3-piece suit =
place.)  There had been a fire on the floor above, where the MCI =
attorneys for the case against AT&T worked.  Lots of water and smoke =
damage.  The claim was that the fire had burned, ummmmm... especially =
hot...
>=20
>=20
>> A line mod was probably against the rules irrespective of Carterphone =
in
>> those
>> days. But had you bought your own phone with a ringer switch and =
hooked
>> that
>=20
> Not allowed at that point.  All user equipment that was wired to the =
system had to come from the phone company in L.A.
>=20
>=20
> d/
> --=20
> Dave Crocker
> Brandenburg InternetWorking
> bbiw.net


From jgunn6@csc.com  Thu Jan  3 07:18:29 2013
Return-Path: <jgunn6@csc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 80B8421E8088; Thu,  3 Jan 2013 07:18:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.352
X-Spam-Level: 
X-Spam-Status: No, score=-6.352 tagged_above=-999 required=5 tests=[AWL=0.246,  BAYES_00=-2.599, HTML_MESSAGE=0.001, 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 CtUGtyan--Ir; Thu,  3 Jan 2013 07:18:28 -0800 (PST)
Received: from mail87.messagelabs.com (mail87.messagelabs.com [216.82.250.19]) by ietfa.amsl.com (Postfix) with ESMTP id D53A321E8083; Thu,  3 Jan 2013 07:18:25 -0800 (PST)
X-Env-Sender: jgunn6@csc.com
X-Msg-Ref: server-15.tower-87.messagelabs.com!1357226291!9325607!1
X-Originating-IP: [20.137.2.87]
X-StarScan-Received: 
X-StarScan-Version: 6.6.1.8; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 10183 invoked from network); 3 Jan 2013 15:18:12 -0000
Received: from amer-mta101.csc.com (HELO amer-mta101.csc.com) (20.137.2.87) by server-15.tower-87.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 3 Jan 2013 15:18:12 -0000
Received: from amer-gw09.amer.csc.com (amer-gw09.amer.csc.com [20.6.39.245]) by amer-mta101.csc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id r03EiRFU006750; Thu, 3 Jan 2013 10:18:07 -0500
In-Reply-To: <9FDEEFFEF5F2A03DF5798648@JcK-HP8200.jck.com>
References: <20130102175839.2DDAE18C0BB@mercury.lcs.mit.edu>	<01OOIM6DH1HW00008S@mauve.mrochek.com> <9FDEEFFEF5F2A03DF5798648@JcK-HP8200.jck.com>
To: John C Klensin <john-ietf@jck.com>
MIME-Version: 1.0
Subject: Re: Acoustic couplers (was: WCIT outcome?)
X-KeepSent: 02A69DA8:A07ED6DB-85257AE8:005227B4; type=4; name=$KeepSent
X-Mailer: Lotus Notes Release 8.5.2FP4 SHF97 March 26, 2012
From: Janet P Gunn <jgunn6@csc.com>
Message-ID: <OF02A69DA8.A07ED6DB-ON85257AE8.005227B4-85257AE8.0053AD65@csc.com>
Date: Thu, 3 Jan 2013 10:13:58 -0500
X-MIMETrack: Serialize by Router on AMER-GW09/SRV/CSC(Release 8.5.2FP3 HF204|September 20, 2011) at 01/03/2013 10:13:15 AM, Serialize complete at 01/03/2013 10:13:15 AM
Content-Type: multipart/alternative; boundary="=_alternative 0053AD3085257AE8_="
Cc: ned+ietf@mauve.mrochek.com, ietf-bounces@ietf.org, ietf@ietf.org, jnc@mercury.lcs.mit.edu
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Jan 2013 15:18:29 -0000

This is a multipart message in MIME format.
--=_alternative 0053AD3085257AE8_=
Content-Type: text/plain; charset="US-ASCII"

We definitely had an acoustic coupler, with its own phone line, so my 
father could work from home, in the mid and  late 70s.

He worked for IBM Research. If there had been a more technically advanced 
way of doing it, I am sure they would have used that.
 
There was not much "general intertia/unwillingness to do the necessary 
engineering" at the lab.

Janet


This is a PRIVATE message. If you are not the intended recipient, please 
delete without copying and kindly advise us by e-mail of the mistake in 
delivery. NOTE: Regardless of content, this e-mail shall not operate to 
bind CSC to any order or other contract unless pursuant to explicit 
written agreement or government initiative expressly permitting the use of 
e-mail for such purpose.

ietf-bounces@ietf.org wrote on 01/03/2013 08:47:44 AM:

> From: John C Klensin <john-ietf@jck.com>
> To: ned+ietf@mauve.mrochek.com, jnc@mercury.lcs.mit.edu
> Cc: ietf@ietf.org
> Date: 01/03/2013 08:48 AM
> Subject: Re: Acoustic couplers (was: WCIT outcome?)
> Sent by: ietf-bounces@ietf.org
> 
> 
> 
> --On Wednesday, January 02, 2013 13:34 -0800
> ned+ietf@mauve.mrochek.com wrote:
> 
> >>     > From: John Day <jeanjour@comcast.net>
> > 
> >>     > I remember when a modem came with an 'acoustic coupler'
> >>     > because connecting it directly to the phone line was
> >>     > illegal. No, there was nothing illegal about it. The
> >>     > reason for acoustic couplers was that the RJ-11 had
> >>     > been invented yet and it was a pain to unscrew the box
> >>     > on the wall and re-wire every time you wanted to
> >>     > connect.
> >>     > ...
> >>     > It may have been illegal in some countries but
> >>     > certainly not in the US.
> > 
> >> Huh? Remember the Carterphone decision?
> > 
> > Absolutely. Too bad the FCC didn't see fit to extend it to
> > wireless.
> >...
> > At one point there was something that said one phone in each
> > home had to be directly wired without a plug. I don't know if
> > this was a regulation, a phone company rule, or just a
> > suggestion, but it also fell by the wayside after Carterphone.
> 
> IIR regulation, in many states even for a while
> post-Carterphone, and justified, again IIR -- as many things
> have been justified in more recent years-- on the grounds of
> emergency services applications.  After all, if there were an
> emergency, you wouldn't want to go hunting for an unplugged
> phone or, especially, to get something working that required
> external (to the phone system) power.
> 
> And, while my memory of the period is a little vague at this
> point, I'm pretty sure that the four-pin jack (and a few other
> proprietary terminal-device connectors) showed up
> pre-Carterphone, when AT&T/WE was (i) trying to sell alternate
> phones (notably the early "Princess") to prove that what became
> Carterphone wasn't necessary because they could meet the
> relevant market demands and (ii) arguing that, if one wanted to
> connect third-party equipment, they could supply a network
> protection device into which the third-party stuff could plug.
> 
> RJ11 and friends came along when the FCC finally got rid of the
> protective device/coupler nonsense in the mid-70s, long after
> Carterphone (1968) and, in a series of steps that weren't
> complete until the last half of the 90s, regulated/required
> first the jacks then the wiring pinouts.
> 
> > I certainly saw acoustic coupled equipment in use long after
> > Carterphone, but in my experience it was because of general
> > intertia/unwillingness to do the necessary engineering, not
> > because of the lack of connectors.
> 
> My recollection is that acoustic couplers started out as an
> attempt to get around the protective device rules, not the "no
> interconnection" one.  It that is correct, it would provide an
> additional explanation for their being around into at least the
> mid-70s.  I think part of what killed them was the growth of
> different handset shapes along with multiple manufacturers of
> telephones.  Those different shapes meant that one could no
> longer design a recessed-cup device with fixed spread between
> the two cups that would form a tight seal with all relevant
> handset shapes.   I do have an acoustic coupling device from the
> mid-90s that had an adjustable distance between the receiving
> and sending attachments and a strap to attach it to the phone --
> worked pretty well when one wanted to attach a modem in, e.g., a
> hotel with hardwired connections between phone and wall and
> setups that made pulling off the terminal cover and attaching
> alligator clips impractical but it is clearly an exception to
> Ned's suggestion that failure to make the transition was at
> least partially due to unwillingness to do new engineering/
> design work.
> 
> The situation in other countries was, of course, different.
> Especially in places where the telephone carrier was effectively
> its own regulator or managed to convince the regulators that
> content mattered as much or more than physical connections,
> there was a requirement for different jacks (usually at a higher
> monthly rate) for modems and fax machines than was used for
> voice.  I believe that particular approach survived and may have
> been reinforced by efforts to promote deregulation within ITU
> because the relevant carriers argued that the early deregulation
> efforts applied only to POTS service and not to "data" ones.
> That approach and position was contemporaneous with national
> regulations in many countries that one could run all of the
> TCP/IP services one wanted as long as they were run over the
> national X.25 profile and sometimes as long as one claimed they
> were "transitional" until OSI Connection-mode stabilized.
> There might be a useful lesson or two in that bit of history.
> 
>     john
> 

--=_alternative 0053AD3085257AE8_=
Content-Type: text/html; charset="US-ASCII"

<font size=2 face="sans-serif">We definitely had an acoustic coupler,
with its own phone line, so my father could work from home, in the mid
and &nbsp;late 70s.</font>
<br>
<br><font size=2 face="sans-serif">He worked for IBM Research. If there
had been a more technically advanced way of doing it, I am sure they would
have used that.<br>
 </font>
<br><font size=2 face="sans-serif">There was not much &quot;</font><tt><font size=2>general
intertia/unwillingness to do the necessary engineering</font></tt><font size=2 face="sans-serif">&quot;
at the lab.</font>
<br>
<br><font size=2 face="sans-serif">Janet</font>
<br>
<br><font size=2 face="sans-serif"><br>
This is a PRIVATE message. If you are not the intended recipient, please
delete without copying and kindly advise us by e-mail of the mistake in
delivery. NOTE: Regardless of content, this e-mail shall not operate to
bind CSC to any order or other contract unless pursuant to explicit written
agreement or government initiative expressly permitting the use of e-mail
for such purpose.</font>
<br>
<br><tt><font size=2>ietf-bounces@ietf.org wrote on 01/03/2013 08:47:44
AM:<br>
<br>
&gt; From: John C Klensin &lt;john-ietf@jck.com&gt;</font></tt>
<br><tt><font size=2>&gt; To: ned+ietf@mauve.mrochek.com, jnc@mercury.lcs.mit.edu</font></tt>
<br><tt><font size=2>&gt; Cc: ietf@ietf.org</font></tt>
<br><tt><font size=2>&gt; Date: 01/03/2013 08:48 AM</font></tt>
<br><tt><font size=2>&gt; Subject: Re: Acoustic couplers (was: WCIT outcome?)</font></tt>
<br><tt><font size=2>&gt; Sent by: ietf-bounces@ietf.org</font></tt>
<br><tt><font size=2>&gt; <br>
&gt; <br>
&gt; <br>
&gt; --On Wednesday, January 02, 2013 13:34 -0800<br>
&gt; ned+ietf@mauve.mrochek.com wrote:<br>
&gt; <br>
&gt; &gt;&gt; &nbsp; &nbsp; &gt; From: John Day &lt;jeanjour@comcast.net&gt;<br>
&gt; &gt; <br>
&gt; &gt;&gt; &nbsp; &nbsp; &gt; I remember when a modem came with an 'acoustic
coupler'<br>
&gt; &gt;&gt; &nbsp; &nbsp; &gt; because connecting it directly to the
phone line was<br>
&gt; &gt;&gt; &nbsp; &nbsp; &gt; illegal. No, there was nothing illegal
about it. The<br>
&gt; &gt;&gt; &nbsp; &nbsp; &gt; reason for acoustic couplers was that
the RJ-11 had<br>
&gt; &gt;&gt; &nbsp; &nbsp; &gt; been invented yet and it was a pain to
unscrew the box<br>
&gt; &gt;&gt; &nbsp; &nbsp; &gt; on the wall and re-wire every time you
wanted to<br>
&gt; &gt;&gt; &nbsp; &nbsp; &gt; connect.<br>
&gt; &gt;&gt; &nbsp; &nbsp; &gt; ...<br>
&gt; &gt;&gt; &nbsp; &nbsp; &gt; It may have been illegal in some countries
but<br>
&gt; &gt;&gt; &nbsp; &nbsp; &gt; certainly not in the US.<br>
&gt; &gt; <br>
&gt; &gt;&gt; Huh? Remember the Carterphone decision?<br>
&gt; &gt; <br>
&gt; &gt; Absolutely. Too bad the FCC didn't see fit to extend it to<br>
&gt; &gt; wireless.<br>
&gt; &gt;...<br>
&gt; &gt; At one point there was something that said one phone in each<br>
&gt; &gt; home had to be directly wired without a plug. I don't know if<br>
&gt; &gt; this was a regulation, a phone company rule, or just a<br>
&gt; &gt; suggestion, but it also fell by the wayside after Carterphone.<br>
&gt; <br>
&gt; IIR regulation, in many states even for a while<br>
&gt; post-Carterphone, and justified, again IIR -- as many things<br>
&gt; have been justified in more recent years-- on the grounds of<br>
&gt; emergency services applications. &nbsp;After all, if there were an<br>
&gt; emergency, you wouldn't want to go hunting for an unplugged<br>
&gt; phone or, especially, to get something working that required<br>
&gt; external (to the phone system) power.<br>
&gt; <br>
&gt; And, while my memory of the period is a little vague at this<br>
&gt; point, I'm pretty sure that the four-pin jack (and a few other<br>
&gt; proprietary terminal-device connectors) showed up<br>
&gt; pre-Carterphone, when AT&amp;T/WE was (i) trying to sell alternate<br>
&gt; phones (notably the early &quot;Princess&quot;) to prove that what
became<br>
&gt; Carterphone wasn't necessary because they could meet the<br>
&gt; relevant market demands and (ii) arguing that, if one wanted to<br>
&gt; connect third-party equipment, they could supply a network<br>
&gt; protection device into which the third-party stuff could plug.<br>
&gt; <br>
&gt; RJ11 and friends came along when the FCC finally got rid of the<br>
&gt; protective device/coupler nonsense in the mid-70s, long after<br>
&gt; Carterphone (1968) and, in a series of steps that weren't<br>
&gt; complete until the last half of the 90s, regulated/required<br>
&gt; first the jacks then the wiring pinouts.<br>
&gt; <br>
&gt; &gt; I certainly saw acoustic coupled equipment in use long after<br>
&gt; &gt; Carterphone, but in my experience it was because of general<br>
&gt; &gt; intertia/unwillingness to do the necessary engineering, not<br>
&gt; &gt; because of the lack of connectors.<br>
&gt; <br>
&gt; My recollection is that acoustic couplers started out as an<br>
&gt; attempt to get around the protective device rules, not the &quot;no<br>
&gt; interconnection&quot; one. &nbsp;It that is correct, it would provide
an<br>
&gt; additional explanation for their being around into at least the<br>
&gt; mid-70s. &nbsp;I think part of what killed them was the growth of<br>
&gt; different handset shapes along with multiple manufacturers of<br>
&gt; telephones. &nbsp;Those different shapes meant that one could no<br>
&gt; longer design a recessed-cup device with fixed spread between<br>
&gt; the two cups that would form a tight seal with all relevant<br>
&gt; handset shapes. &nbsp; I do have an acoustic coupling device from
the<br>
&gt; mid-90s that had an adjustable distance between the receiving<br>
&gt; and sending attachments and a strap to attach it to the phone --<br>
&gt; worked pretty well when one wanted to attach a modem in, e.g., a<br>
&gt; hotel with hardwired connections between phone and wall and<br>
&gt; setups that made pulling off the terminal cover and attaching<br>
&gt; alligator clips impractical but it is clearly an exception to<br>
&gt; Ned's suggestion that failure to make the transition was at<br>
&gt; least partially due to unwillingness to do new engineering/<br>
&gt; design work.<br>
&gt; <br>
&gt; The situation in other countries was, of course, different.<br>
&gt; Especially in places where the telephone carrier was effectively<br>
&gt; its own regulator or managed to convince the regulators that<br>
&gt; content mattered as much or more than physical connections,<br>
&gt; there was a requirement for different jacks (usually at a higher<br>
&gt; monthly rate) for modems and fax machines than was used for<br>
&gt; voice. &nbsp;I believe that particular approach survived and may have<br>
&gt; been reinforced by efforts to promote deregulation within ITU<br>
&gt; because the relevant carriers argued that the early deregulation<br>
&gt; efforts applied only to POTS service and not to &quot;data&quot; ones.<br>
&gt; That approach and position was contemporaneous with national<br>
&gt; regulations in many countries that one could run all of the<br>
&gt; TCP/IP services one wanted as long as they were run over the<br>
&gt; national X.25 profile and sometimes as long as one claimed they<br>
&gt; were &quot;transitional&quot; until OSI Connection-mode stabilized.<br>
&gt; There might be a useful lesson or two in that bit of history.<br>
&gt; <br>
&gt; &nbsp; &nbsp; john<br>
&gt; <br>
</font></tt>
--=_alternative 0053AD3085257AE8_=--

From john-ietf@jck.com  Thu Jan  3 07:23:11 2013
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3A0BA21F8CA0 for <ietf@ietfa.amsl.com>; Thu,  3 Jan 2013 07:23:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 Y7uPwrQs-JG2 for <ietf@ietfa.amsl.com>; Thu,  3 Jan 2013 07:23:10 -0800 (PST)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id A931721F8C9F for <ietf@ietf.org>; Thu,  3 Jan 2013 07:23:10 -0800 (PST)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1TqmdJ-000ILy-3r; Thu, 03 Jan 2013 10:23:01 -0500
Date: Thu, 03 Jan 2013 10:22:56 -0500
From: John C Klensin <john-ietf@jck.com>
To: dcrocker@bbiw.net, Ned Freed <ned.freed@mrochek.com>
Subject: Re: Acoustic couplers
Message-ID: <CA6F2CEC906A278460919846@JcK-HP8200.jck.com>
In-Reply-To: <50E59B43.8000702@dcrocker.net>
References: <20130102175839.2DDAE18C0BB@mercury.lcs.mit.edu> <01OOIM6DH1HW00008S@mauve.mrochek.com> <50E4AFAF.4000506@dcrocker.net> <01OOIXYRHRN000008S@mauve.mrochek.com> <50E59B43.8000702@dcrocker.net>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Cc: ned+ietf@mauve.mrochek.com, jnc@mercury.lcs.mit.edu, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Jan 2013 15:23:11 -0000

--On Thursday, January 03, 2013 06:52 -0800 Dave Crocker
<dhc@dcrocker.net> wrote:

>...
>> A line mod was probably against the rules irrespective of
>> Carterphone in those
>> days. But had you bought your own phone with a ringer switch
>> and hooked that
> 
> Not allowed at that point.  All user equipment that was wired
> to the system had to come from the phone company in L.A.

And, if you intended to get around "wired to" by using a
(proprietary) jack that jack had to be installed by the phone
company and they could charge just about anything they liked for
that.

More important, I think that had you checked carefully and
mentioned "Carterphone" a few times (the information was rarely
if ever volunteered), you would have been told that of course
you could connect a third-party phone.  In Pac Bell's area, you
either had to do it via a Pac Bell-supplied network protection
device or the phone had to be AT&T/WG tested and certified to
not cause damage to the network.  The monthly price for the
protection device and the cost of certification were high enough
to make using (or manufacturing and selling) third-party
equipment implausible for any conventional endpoint application,
but the option was there in principle.    I don't know what the
situation was in GTE's area, but assume it was similar.  

Carterphone was a huge step forward, but the device itself was
acoustically connected and the decision did not open up the
possibility of connecting uncertified third-party equipment to
the PSTN (jacks or otherwise).   Many of the effects we now
depend on were not really available until the FCC abolished the
right of the the carriers to require protective devices that
they controlled and the MFJ broke the close link between the
design and manufacturing organization and the standards-setting
("system practices") one (and started to really open up
inter-carrier interconnects).  Those events didn't occur until
the last half of the 70s and first half of the 80s.

best,
    john


From john-ietf@jck.com  Thu Jan  3 07:36:32 2013
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5B73221F8A69 for <ietf@ietfa.amsl.com>; Thu,  3 Jan 2013 07:36:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 gVa83WfIWCFV for <ietf@ietfa.amsl.com>; Thu,  3 Jan 2013 07:36:31 -0800 (PST)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id C215521F89C0 for <ietf@ietf.org>; Thu,  3 Jan 2013 07:36:31 -0800 (PST)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1TqmqB-000IMk-5R; Thu, 03 Jan 2013 10:36:19 -0500
Date: Thu, 03 Jan 2013 10:36:14 -0500
From: John C Klensin <john-ietf@jck.com>
To: Steve Crocker <steve@shinkuro.com>, dcrocker@bbiw.net
Subject: Re: Acoustic couplers
Message-ID: <600960B19F7C535FA242D982@JcK-HP8200.jck.com>
In-Reply-To: <2877F05C-BF25-42DE-BF77-1854CC955A54@shinkuro.com>
References: <20130102175839.2DDAE18C0BB@mercury.lcs.mit.edu> <01OOIM6DH1HW00008S@mauve.mrochek.com> <50E4AFAF.4000506@dcrocker.net> <01OOIXYRHRN000008S@mauve.mrochek.com> <50E59B43.8000702@dcrocker.net> <2877F05C-BF25-42DE-BF77-1854CC955A54@shinkuro.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Cc: ned+ietf@mauve.mrochek.com, Ned Freed <ned.freed@mrochek.com>, jnc@mercury.lcs.mit.edu, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Jan 2013 15:36:32 -0000

--On Thursday, January 03, 2013 10:10 -0500 Steve Crocker
<steve@shinkuro.com> wrote:

> In 1974 I moved into a condo complex in Marina del Rey near
> USC-ISI.  As has been my usual practice, I ordered two POTS
> lines and I went to the phone company to get the phones.  The
> condo was pre-wired with jacks in each of the major rooms.
> The phones I got from the phone company came with plugs that
> were wired for either line 1 or line 2.  It took me a minute
> of incredulity to understand the system.  Each jack was wired
> for both lines, and each phone was wired to connect to one or
> the other of the two lines.  Clever but definitely different
> from anything I had seen before.  I could move the phones from
> room to room.  Each phone "knew" whether it was for line 1 or
> line 2.

Steve,

Just out of curiosity and if you remember, were those pre-wired
jacks the round four-pin puppies, RJ series, or something else?
I saw those sorts of setups several times with the four-pin
jacks but never with RJ11/14 ones.  Of course the "knowledge" in
the phone was about which pair was connected to the screw
terminals on the inside so, if one ignored the threats and took
the cover off the phone...    

Equally out of curiosity, was MdR in Pac Bell or GTE territory
at the time?  I know that some of their policies were different,
but don't know which ones and what the actual consequences were.

    john


From steve@shinkuro.com  Thu Jan  3 08:39:42 2013
Return-Path: <steve@shinkuro.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 673C521F8CCE for <ietf@ietfa.amsl.com>; Thu,  3 Jan 2013 08:39:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.469
X-Spam-Level: 
X-Spam-Status: No, score=-1.469 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DSL=1.129, UNPARSEABLE_RELAY=0.001]
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 nJFrUPHPVUPw for <ietf@ietfa.amsl.com>; Thu,  3 Jan 2013 08:39:42 -0800 (PST)
Received: from execdsl.com (remote.shinkuro.com [50.56.68.178]) by ietfa.amsl.com (Postfix) with ESMTP id D45F921F8C1A for <ietf@ietf.org>; Thu,  3 Jan 2013 08:39:41 -0800 (PST)
Received: from dummy.name; Thu, 03 Jan 2013 16:43:19 +0000
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Subject: Re: Acoustic couplers
From: Steve Crocker <steve@shinkuro.com>
In-Reply-To: <600960B19F7C535FA242D982@JcK-HP8200.jck.com>
Date: Thu, 3 Jan 2013 11:41:37 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <A2EB5895-E8D7-4CD2-921A-22082631D0B5@shinkuro.com>
References: <20130102175839.2DDAE18C0BB@mercury.lcs.mit.edu> <01OOIM6DH1HW00008S@mauve.mrochek.com> <50E4AFAF.4000506@dcrocker.net> <01OOIXYRHRN000008S@mauve.mrochek.com> <50E59B43.8000702@dcrocker.net> <2877F05C-BF25-42DE-BF77-1854CC955A54@shinkuro.com> <600960B19F7C535FA242D982@JcK-HP8200.jck.com>
To: John C Klensin <john-ietf@jck.com>
X-Mailer: Apple Mail (2.1499)
Cc: Ned Freed <ned.freed@mrochek.com>, ietf@ietf.org, ned+ietf@mauve.mrochek.com, dcrocker@bbiw.net, jnc@mercury.lcs.mit.edu
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Jan 2013 16:39:42 -0000

I honestly don't remember whether the plugs were the clunky four pin or =
the then-modern RJ11.  I recall studying RJ11 and RJ45 plugs and sockets =
at some point and discovering that some plugs and sockets had six wires =
instead of only four or two.  I never did learn if they had a different =
number.  The form factor was the same.

This was GTE territory.

Steve

On Jan 3, 2013, at 10:36 AM, John C Klensin <john-ietf@jck.com> wrote:

>=20
>=20
> --On Thursday, January 03, 2013 10:10 -0500 Steve Crocker
> <steve@shinkuro.com> wrote:
>=20
>> In 1974 I moved into a condo complex in Marina del Rey near
>> USC-ISI.  As has been my usual practice, I ordered two POTS
>> lines and I went to the phone company to get the phones.  The
>> condo was pre-wired with jacks in each of the major rooms.
>> The phones I got from the phone company came with plugs that
>> were wired for either line 1 or line 2.  It took me a minute
>> of incredulity to understand the system.  Each jack was wired
>> for both lines, and each phone was wired to connect to one or
>> the other of the two lines.  Clever but definitely different
>> from anything I had seen before.  I could move the phones from
>> room to room.  Each phone "knew" whether it was for line 1 or
>> line 2.
>=20
> Steve,
>=20
> Just out of curiosity and if you remember, were those pre-wired
> jacks the round four-pin puppies, RJ series, or something else?
> I saw those sorts of setups several times with the four-pin
> jacks but never with RJ11/14 ones.  Of course the "knowledge" in
> the phone was about which pair was connected to the screw
> terminals on the inside so, if one ignored the threats and took
> the cover off the phone...   =20
>=20
> Equally out of curiosity, was MdR in Pac Bell or GTE territory
> at the time?  I know that some of their policies were different,
> but don't know which ones and what the actual consequences were.
>=20
>    john
>=20


From worley@shell01.TheWorld.com  Wed Jan  2 11:51:06 2013
Return-Path: <worley@shell01.TheWorld.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 926F121F8831 for <ietf@ietfa.amsl.com>; Wed,  2 Jan 2013 11:51:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.437
X-Spam-Level: 
X-Spam-Status: No, score=-100.437 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_NET=0.611,  RDNS_NONE=0.1, USER_IN_WHITELIST=-100]
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 j8RjJJ0VhAFX for <ietf@ietfa.amsl.com>; Wed,  2 Jan 2013 11:51:06 -0800 (PST)
Received: from TheWorld.com (pcls2.std.com [192.74.137.142]) by ietfa.amsl.com (Postfix) with ESMTP id 192E921F8797 for <ietf@ietf.org>; Wed,  2 Jan 2013 11:51:06 -0800 (PST)
Received: from shell.TheWorld.com (root@shell01.theworld.com [192.74.137.71]) by TheWorld.com (8.14.5/8.14.5) with ESMTP id r02JoJug014423 for <ietf@ietf.org>; Wed, 2 Jan 2013 14:50:21 -0500
Received: from shell01.TheWorld.com (localhost.theworld.com [127.0.0.1]) by shell.TheWorld.com (8.13.6/8.12.8) with ESMTP id r02JoITM4365470 for <ietf@ietf.org>; Wed, 2 Jan 2013 14:50:18 -0500 (EST)
Received: (from worley@localhost) by shell01.TheWorld.com (8.13.6/8.13.6/Submit) id r02JoIB64379575; Wed, 2 Jan 2013 14:50:18 -0500 (EST)
Date: Wed, 2 Jan 2013 14:50:18 -0500 (EST)
Message-Id: <201301021950.r02JoIB64379575@shell01.TheWorld.com>
From: worley@alum.mit.edu (Dale R. Worley)
Sender: worley@alum.mit.edu (Dale R. Worley)
To: ietf@ietf.org
In-reply-to: <a06240834cd09f3ec48a7@[10.0.1.3]> (jeanjour@comcast.net)
Subject: Re: WCIT outcome?
References: <CAMm+Lwh2cHRY+Dk2_SDtZZmUbPcgRpP89u3DHUcniJDrKrX_pw@mail.gmail.com> <CAMzo+1a0-90dnjnvs48a9DcNN9DY_edF5hH0__4XRuCaLHtL6Q@mail.gmail.com> <CAMm+LwjzjLc2-=4EdxwHOi21B3dOBUohYc5hhXZHL_Pk+iBBmQ@mail.gmail.com> <6.2.5.6.2.20121229192941.0aae33e8@resistor.net> <CAMm+LwiC0xtJU4vnGFPvAG4VKZdj7Tf3LfW0+pzwxKWTegRREw@mail.gmail.com> <a06240800cd074efd45b8@10.0.1.3> <CAMm+Lwiq+DCzXw572wKs78DG+XzYsJtwCVSPvNuVHSrT=Cr2nA@mail.gmail.com> <a06240809cd0799fee029@10.0.1.3> <6.2.5.6.2.20130102023406.0b4b7d68@resistor.net> <CAMm+LwgsgaV7L-FY4MnM2Einaapo-BdiddBU+nYzTS6DMPXzQw@mail.gmail.com> <a06240834cd09f3ec48a7@[10.0.1.3]>
X-Mailman-Approved-At: Thu, 03 Jan 2013 09:01:17 -0800
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Jan 2013 19:51:06 -0000

> From: John Day <jeanjour@comcast.net>
> 
> No, there was nothing illegal about it. The reason for acoustic 
> couplers was that the RJ-11 had been invented yet and it was a pain 
> to unscrew the box on the wall and re-wire every time you wanted to 
> connect.

In the 1970s, in the US, and for inter-state use, you either had to
rent the modem from the phone company, or rent a "data-access
arrangement" device to connect your modem to the network.  The DAA
cost about as much as the modem, so there was little in the way of
independent modems.  Acoustic couplers got around that rule.

Also, in those days, there was a large four-pronged plug that could be
used for phones.  It was sometimes used when people wanted to move
phones around.  http://en.wikipedia.org/wiki/File:4prongplug.JPG

Dale

From Chris.Dearlove@baesystems.com  Thu Jan  3 10:49:06 2013
Return-Path: <Chris.Dearlove@baesystems.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B08AD21F8696 for <ietf@ietfa.amsl.com>; Thu,  3 Jan 2013 10:49:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8
X-Spam-Level: 
X-Spam-Status: No, score=-8 tagged_above=-999 required=5 tests=[RCVD_IN_DNSWL_HI=-8]
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 1EQIXXPTv5SD for <ietf@ietfa.amsl.com>; Thu,  3 Jan 2013 10:49:06 -0800 (PST)
Received: from ukmta3.baesystems.com (ukmta3.baesystems.com [20.133.40.55]) by ietfa.amsl.com (Postfix) with ESMTP id CD78821F8692 for <ietf@ietf.org>; Thu,  3 Jan 2013 10:49:05 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.84,404,1355097600"; d="scan'208";a="252852884"
Received: from unknown (HELO baemasodc004.greenlnk.net) ([10.108.36.11]) by Baemasodc001ir.sharelnk.net with ESMTP; 03 Jan 2013 18:49:03 +0000
Received: from baemasodc005.greenlnk.net ([10.108.52.29]) by baemasodc004.greenlnk.net (Switch-3.4.4/Switch-3.4.4) with ESMTP id r03In208012958 for <ietf@ietf.org>; Thu, 3 Jan 2013 18:49:02 GMT
X-IronPort-AV: E=McAfee;i="5400,1158,6944"; a="2389800"
Received: from glkxh0001v.greenlnk.net ([10.109.2.32]) by baemasodc005.greenlnk.net with ESMTP; 03 Jan 2013 18:49:02 +0000
Received: from GLKXM0002V.GREENLNK.net ([169.254.2.7]) by GLKXH0001V.GREENLNK.net ([10.109.2.32]) with mapi id 14.02.0309.002; Thu, 3 Jan 2013 18:49:02 +0000
From: "Dearlove, Christopher (UK)" <Chris.Dearlove@baesystems.com>
To: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
Subject: RE: WCIT outcome?
Thread-Topic: WCIT outcome?
Thread-Index: AQHN5Y2JvnLRPwHtzka5eKT9kbUSBJgvl3qAgAB/ZYCABfyigIAAPvnQgAD+IoCAABPp0IAAJ0MAgAARU4CAAAcogIAAVmAw
Date: Thu, 3 Jan 2013 18:49:01 +0000
Message-ID: <B31EEDDDB8ED7E4A93FDF12A4EECD30D24FE5DC6@GLKXM0002V.GREENLNK.net>
References: <CAMm+Lwh2cHRY+Dk2_SDtZZmUbPcgRpP89u3DHUcniJDrKrX_pw@mail.gmail.com> <CAMzo+1a0-90dnjnvs48a9DcNN9DY_edF5hH0__4XRuCaLHtL6Q@mail.gmail.com> <CAMm+LwjzjLc2-=4EdxwHOi21B3dOBUohYc5hhXZHL_Pk+iBBmQ@mail.gmail.com> <50E439C5.2020808@gmail.com> <B31EEDDDB8ED7E4A93FDF12A4EECD30D24FE4DAF@GLKXM0002V.GREENLNK.net> <50E543C7.6070809@necom830.hpcl.titech.ac.jp> <B31EEDDDB8ED7E4A93FDF12A4EECD30D24FE5CCE@GLKXM0002V.GREENLNK.net> <50E5756A.2090506@necom830.hpcl.titech.ac.jp> <B31EEDDDB8ED7E4A93FDF12A4EECD30D24FE5D0C@GLKXM0002V.GREENLNK.net> <50E589F3.80302@necom830.hpcl.titech.ac.jp>
In-Reply-To: <50E589F3.80302@necom830.hpcl.titech.ac.jp>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.109.62.6]
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Jan 2013 18:49:06 -0000

I think at this point we have parted company with the real world, so I will=
 drop out of this discussion.

--=20
Christopher Dearlove
Senior Principal Engineer, Communications Group
Communications, Networks and Image Analysis Capability
BAE Systems Advanced Technology Centre
West Hanningfield Road, Great Baddow, Chelmsford, CM2 8HN, UK
Tel: +44 1245 242194=A0|  Fax: +44 1245 242124
chris.dearlove@baesystems.com | http://www.baesystems.com

BAE Systems (Operations) Limited
Registered Office: Warwick House, PO Box 87, Farnborough Aerospace Centre, =
Farnborough, Hants, GU14 6YU, UK
Registered in England & Wales No: 1996687


-----Original Message-----
From: Masataka Ohta [mailto:mohta@necom830.hpcl.titech.ac.jp]=20
Sent: 03 January 2013 13:39
To: Dearlove, Christopher (UK)
Cc: ietf@ietf.org
Subject: Re: WCIT outcome?

----------------------! WARNING ! ----------------------
This message originates from outside our organisation,
either from an external partner or from the internet.
Keep this in mind if you answer this message.
Follow the 'Report Suspicious Emails' link on IT matters
for instructions on reporting suspicious email messages.
--------------------------------------------------------

Dearlove, Christopher (UK) wrote:

> Yes, all smart phones support Wi-Fi. In some "unregulated" (not
> actually entirely so) frequency bands, and with regulated powers,
> over a short range.

CSMA/CA can also work over a long range too and can, in a sense,
fairly arbitrate packets from different countries at border towns.

> But the main long range 2G/3G signals are
> TDMA or CDMA in regulated bands.

Forget them.

=09=09=09=09=09=09Masataka Ohta


********************************************************************
This email and any attachments are confidential to the intended
recipient and may also be privileged. If you are not the intended
recipient please delete it from your system and notify the sender.
You should not copy it or use it for any purpose nor disclose or
distribute its contents to any other person.
********************************************************************


From ben@nostrum.com  Thu Jan  3 15:39:11 2013
Return-Path: <ben@nostrum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9196E21F8DEF; Thu,  3 Jan 2013 15:39:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.6
X-Spam-Level: 
X-Spam-Status: No, score=-102.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, SPF_PASS=-0.001, USER_IN_WHITELIST=-100]
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 y62C2KMnBgiA; Thu,  3 Jan 2013 15:39:11 -0800 (PST)
Received: from shaman.nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id DDBAC21F8DEC; Thu,  3 Jan 2013 15:39:10 -0800 (PST)
Received: from [10.0.1.14] (cpe-76-187-92-156.tx.res.rr.com [76.187.92.156]) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id r03Nd9PO051762 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 3 Jan 2013 17:39:10 -0600 (CST) (envelope-from ben@nostrum.com)
From: Ben Campbell <ben@nostrum.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Subject: Gen-ART Telechat review of draft-ietf-dhc-relay-id-suboption-11
Date: Thu, 3 Jan 2013 17:39:10 -0600
Message-Id: <C93E994C-C69D-49BA-A106-7C2878FA9B72@nostrum.com>
To: "draft-ietf-dhc-relay-id-suboption.all@tools.ietf.org" <draft-ietf-dhc-relay-id-suboption.all@tools.ietf.org>
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
X-Mailer: Apple Mail (2.1499)
Received-SPF: pass (nostrum.com: 76.187.92.156 is authenticated by a trusted mechanism)
Cc: "gen-art@ietf.org Review Team" <gen-art@ietf.org>, "ietf@ietf.org List" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Jan 2013 23:39:11 -0000

I am the assigned Gen-ART reviewer for this draft. For background on
Gen-ART, please see the FAQ at
< http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

Please wait for direction from your document shepherd
or AD before posting a new version of the draft.

Document: draft-ietf-dhc-relay-id-suboption-11
Reviewer: Ben Campbell
Review Date: 2013-01-03
IESG Telechat date: 2013-01-10

Summary:  Ready for publication as a proposed standard.

Note: This review is incremental to my previous Gen-ART review at IETF =
last call. The only substantive comment from that review has been =
addressed in discussion. There are two remaining trivial editorial =
comments that the authors have agreed to address. Since there has not =
been an update since that previous review, I am including them for the =
sake of documentation. ** Nothing there is important enough to delay =
publication. **

Major issues:

Minor issues:

Nits/editorial comments:

[section copied from previous review]

> -- section 5, last paragraph:
>=20
> I suggest removing the scare quotes around "stability". If there are =
concerns about whether such stability is real, it would be better to say =
that directly.
>=20
> -- informative references:
>=20
> draft-ietf-dhc-dhcpv4-bulk-leasequery-06 is now 07

From alh-ietf@tndh.net  Thu Jan  3 16:59:54 2013
Return-Path: <alh-ietf@tndh.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0236A21F8E10 for <ietf@ietfa.amsl.com>; Thu,  3 Jan 2013 16:59:54 -0800 (PST)
X-Quarantine-ID: <nV4BU-aI+1B2>
X-Virus-Scanned: amavisd-new at amsl.com
X-Amavis-Alert: BAD HEADER SECTION, Improper folded header field made up entirely of whitespace (char 20 hex): X-Spam-Report: ...that system for details.\n \n Content previ[...]
X-Spam-Flag: NO
X-Spam-Score: 0
X-Spam-Level: 
X-Spam-Status: No, score=0 tagged_above=-999 required=5 tests=[BAYES_50=0.001,  NO_RELAYS=-0.001]
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 nV4BU-aI+1B2 for <ietf@ietfa.amsl.com>; Thu,  3 Jan 2013 16:59:53 -0800 (PST)
Received: from express.tndh.net (express.tndh.net [IPv6:2001:470:e930:1240:20d:56ff:fe04:4c0a]) by ietfa.amsl.com (Postfix) with ESMTP id D545921F8877 for <ietf@ietf.org>; Thu,  3 Jan 2013 16:59:52 -0800 (PST)
Received: from express.tndh.local ([2001:470:e930:1240:20d:56ff:fe04:4c0a] helo=eaglet) by express.tndh.net with esmtp (Exim 4.72 (FreeBSD)) (envelope-from <alh-ietf@tndh.net>) id 1TqvdQ-000AJE-Vv; Thu, 03 Jan 2013 16:59:51 -0800
From: "Tony Hain" <alh-ietf@tndh.net>
To: <ietf@ietf.org>
References: <CAMm+Lwh2cHRY+Dk2_SDtZZmUbPcgRpP89u3DHUcniJDrKrX_pw@mail.gmail.com>	<CAMzo+1a0-90dnjnvs48a9DcNN9DY_edF5hH0__4XRuCaLHtL6Q@mail.gmail.com>	<CAMm+LwjzjLc2-=4EdxwHOi21B3dOBUohYc5hhXZHL_Pk+iBBmQ@mail.gmail.com>	<6.2.5.6.2.20121229192941.0aae33e8@resistor.net>	<CAMm+LwiC0xtJU4vnGFPvAG4VKZdj7Tf3LfW0+pzwxKWTegRREw@mail.gmail.com>	<a06240800cd074efd45b8@10.0.1.3>	<CAMm+Lwiq+DCzXw572wKs78DG+XzYsJtwCVSPvNuVHSrT=Cr2nA@mail.gmail.com>	<a06240809cd0799fee029@[10.0.1.3]> <50E29EE0.1080107@gmail.com>	<50E32CAA.4040507@tana.it> <8C48B86A895913448548E6D15DA7553B72A8D6@xmb-rcd-x09.cisco.com>
In-Reply-To: <8C48B86A895913448548E6D15DA7553B72A8D6@xmb-rcd-x09.cisco.com>
Subject: RE: WCIT outcome?
Date: Thu, 3 Jan 2013 16:59:45 -0800
Message-ID: <00fd01cdea16$c956c720$5c045560$@tndh.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQLSnCD45NDVIWoUK8uGaD7jPXnB3gEvc1PuAjrLSsgB5a8deAKWQNdKAN2rb9oCXP2dawIkCyL3AwUFfZ0BmckBbQJjEZ2ilYybLJA=
Content-Language: en-us
X-SA-Exim-Connect-IP: 2001:470:e930:1240:20d:56ff:fe04:4c0a
X-SA-Exim-Mail-From: alh-ietf@tndh.net
X-SA-Exim-Scanned: No (on express.tndh.net); SAEximRunCond expanded to false
Cc: lynn.st.amour@isoc.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 04 Jan 2013 00:59:54 -0000

> Phillip Hallam-Baker wrote:
>
> ...
> There are some control points in the Internet but they are rather less
critical 
> than many imagine. IPv6 address space allocations, DNS zone management 
> and AIS numbers are arguably control points.
>
> If we can eliminate the control point nature of those resources then the 
> essential government needs in Internet regulation will have been met and
the 
> need for the ITU to be involved will disappear entirely. There are still
concerns 
> that an ITU-like body could usefully address. A treaty baring
cyber-sabotage 
> would be an important and useful effort that demands a diplomatic
approach.


> Fred Baker wrote:
>
> ...
> If you want something to fade away, making a fuss about it isn't a useful
> approach. The IETF's practice in the past has been to improve the
Internet; I
> tend to think that's as it should be.
> 
> That said, I'm also of the opinion that preventing a police force from
> conducting a proper criminal investigation is not a path to success. We
like to
> say that the Internet routes around brokenness; so do police forces and
> legislative bodies. They define "brokenness" as anything that prevents
them
> from doing their job, the same way we do. What I would far rather see is a
> set of technical mechanisms and supporting law that facilitate legitimate
> criminal investigations and expose the other kind.


> Brian E Carpenter wrote:
>
> ...
> That depended on how the various national monopolists chose to interpret
> the rules. In Switzerland we were particularly affected by the fact that
the
> PTT monopoly was a specific line item in the federal Constitution. In the
US,
> you had the benefit of Judge Greene.


> John Day wrote:
>
> ...
> Also, I would agree with Fred's comment on helping the police.
> Although as we all know that can be hard call and one has to hope that the
> proper controls are on them as well.  The problem as I see it is that it
is not a
> good idea to try to constrain a new technology to behave like the old
> technology.  It is the capability they want it shouldn't imply how.


Subject thread RE: Acoustic couplers (was: WCIT outcome?)
> John C Klensin wrote:
>
> ...
> That approach and position was contemporaneous with national regulations
> in many countries that one could run all of the TCP/IP services one wanted
as
> long as they were run over the national X.25 profile and sometimes as long
as
> one claimed they were "transitional" until OSI Connection-mode stabilized.
> There might be a useful lesson or two in that bit of history.


This entire thread(s) missed the point that about why the governments
control / restrict telecom. The national PTT's didn't come into existence
because the governments were better at operating those facilities than
private enterprise. Even the acronym hints at the evolutionary consolidation
and control over the flow of information. The fact that we are not already
operating as a collection of PTT(I/W) has more to do with the pace and
direction of global government agreements than it does with any special
characteristics of the inter-web standards process. Paraphrasing Klensin's
point 'use any bit pattern you want as long as it transits the regulated
infrastructure', is a case in point about consolidating and controlling the
flow of content. 

The IETF can't get into the realm of defining "legitimate criminal
investigations", because defining "legitimate" is the role of governments.
The only thing the IETF can / should do is recognize that governments have a
role, so facilitating basic information like identity and connection-point
is required.  Content control is out of scope for any particular government
related discussions, but is required by private enterprise so the IETF does
get involved, and those results will get used in unintended ways by
governments. Attempts to thwart that unintended use will only instigate more
explicit attempts at oversight and control over the standards process. 

Like it or not, governments are fundamentally opposed to the open nature of
'the Internet', and they always will be (even the 'reasonable' ones).
Managing information flow is how they derive and exercise power (even the
'open' ones use managed leaks to the free press to influence opinion).
Assuming that the standards process can be used to mitigate their exercise
of power is naive at best. The ITU will continue to exist, if nothing more
than a unified voice for the governments to state requirements of each
other. How long the IETF gets to stay independent of that will depend on how
responsive it is to meeting the needs of governments. If short-sighted
attempts at political maneuvering are exposed in the IETF, it will lose its
independence and finally bring that process under 'proper control'. 

It would be wise for the IETF participants to look at the countries that did
sign, and why. What is it that they are not getting that they need, and how
can that be resolved? To echo Day's point, it is the capability they
want/need, not the historical implementation. Some things that are business
relationship based and completely incompatible with the evolution of
technology like 'calling party pays', are easily dismissed by the 'resource
rich', but are absolutely critical to those that have relied on that income
to fund the information control organization. Simply acknowledging that this
is an area for research and investigation is a first step, which would
likely have softened the support the resolution did get. The I* has never
been good at, and is not currently equipped to deal with, the business model
part of the problem space. At the end of the day, I see this as the root of
the unhappiness with the IETF as a standards body. I doubt any of the
signatories would argue that the pace of technology evolution under an
independent standards process is a problem, *IF* they were getting their
business needs met. The only reason to slow and control the pace is to make
sure they are able to maintain control over information flow, and evolve /
align financial relationships. The IETF needs to either meet those
requirements, or acquiesce to the inevitable take-over.


Tony


PS: if you want to remove IPv6 allocations as a control point, see:  
        tools.ietf.org/id/draft-hain-ipv6-geo-addr-02.txt
that approach does require a 'peering business model' to be more like X.75
gateways, but itself does not require shutting down the existing peerings,
as they can operate in parallel.


From rbonica@juniper.net  Thu Jan  3 19:41:49 2013
Return-Path: <rbonica@juniper.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ABAC321F8AF8 for <ietf@ietfa.amsl.com>; Thu,  3 Jan 2013 19:41:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.346
X-Spam-Level: 
X-Spam-Status: No, score=-101.346 tagged_above=-999 required=5 tests=[AWL=2.121, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, UNRESOLVED_TEMPLATE=3.132, USER_IN_WHITELIST=-100]
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 MvuGm9Twj+ae for <ietf@ietfa.amsl.com>; Thu,  3 Jan 2013 19:41:49 -0800 (PST)
Received: from exprod7og107.obsmtp.com (exprod7og107.obsmtp.com [64.18.2.167]) by ietfa.amsl.com (Postfix) with ESMTP id 01E9021F8A2F for <ietf@ietf.org>; Thu,  3 Jan 2013 19:41:48 -0800 (PST)
Received: from P-EMHUB02-HQ.jnpr.net ([66.129.224.36]) (using TLSv1) by exprod7ob107.postini.com ([64.18.6.12]) with SMTP ID DSNKUOZPfFIFfnyoL+HTsM56lP562e4ejDiW@postini.com; Thu, 03 Jan 2013 19:41:49 PST
Received: from P-CLDFE01-HQ.jnpr.net (172.24.192.59) by P-EMHUB02-HQ.jnpr.net (172.24.192.36) with Microsoft SMTP Server (TLS) id 8.3.213.0; Thu, 3 Jan 2013 19:37:52 -0800
Received: from o365mail.juniper.net (207.17.137.224) by o365mail.juniper.net (172.24.192.59) with Microsoft SMTP Server id 14.1.355.2; Thu, 3 Jan 2013 19:37:51 -0800
Received: from ch1outboundpool.messaging.microsoft.com (216.32.181.182) by o365mail.juniper.net (207.17.137.224) with Microsoft SMTP Server (TLS) id 14.1.355.2; Thu, 3 Jan 2013 19:46:07 -0800
Received: from mail264-ch1-R.bigfish.com (10.43.68.252) by CH1EHSOBE005.bigfish.com (10.43.70.55) with Microsoft SMTP Server id 14.1.225.23; Fri, 4 Jan 2013 03:37:50 +0000
Received: from mail264-ch1 (localhost [127.0.0.1])	by mail264-ch1-R.bigfish.com (Postfix) with ESMTP id C81E1200083	for <ietf@ietf.org.FOPE.CONNECTOR.OVERRIDE>; Fri,  4 Jan 2013 03:37:50 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.238.5; KIP:(null); UIP:(null); (null); H:BY2PRD0512HT001.namprd05.prod.outlook.com; R:internal; EFV:INT
X-SpamScore: -23
X-BigFish: PS-23(zz9371I542I1432Izz1de0h1202h1e76h1d1ah1d2ahzz8275dh1033ILz2dh2a8h668h839h944hd25hf0ah1220h1288h12a5h12a9h12bdh137ah13b6h1441h1504h1537h153bh15d0h162dh1631h1758h1155h)
Received: from mail264-ch1 (localhost.localdomain [127.0.0.1]) by mail264-ch1 (MessageSwitch) id 1357270668166879_14822; Fri,  4 Jan 2013 03:37:48 +0000 (UTC)
Received: from CH1EHSMHS023.bigfish.com (snatpool1.int.messaging.microsoft.com [10.43.68.240])	by mail264-ch1.bigfish.com (Postfix) with ESMTP id 1C136CC004B;	Fri,  4 Jan 2013 03:37:48 +0000 (UTC)
Received: from BY2PRD0512HT001.namprd05.prod.outlook.com (157.56.238.5) by CH1EHSMHS023.bigfish.com (10.43.70.23) with Microsoft SMTP Server (TLS) id 14.1.225.23; Fri, 4 Jan 2013 03:37:44 +0000
Received: from BY2PRD0512MB653.namprd05.prod.outlook.com ([169.254.5.92]) by BY2PRD0512HT001.namprd05.prod.outlook.com ([10.255.243.34]) with mapi id 14.16.0245.002; Fri, 4 Jan 2013 03:37:43 +0000
From: Ronald Bonica <rbonica@juniper.net>
To: Randy Bush <randy@psg.com>, IETF Disgust <ietf@ietf.org>
Subject: RE: draft-bonica-special-purpose-04.txt
Thread-Topic: draft-bonica-special-purpose-04.txt
Thread-Index: AQHN34nnK3aq1YMHUkaRiaBj3e6hRJgjZZ9wgBU0h7A=
Date: Fri, 4 Jan 2013 03:37:42 +0000
Message-ID: <2CF4CB03E2AA464BA0982EC92A02CE2501E042A8@BY2PRD0512MB653.namprd05.prod.outlook.com>
References: <20121129205534.8983.43593.idtracker@ietfa.amsl.com> <m2fw3s2ii7.wl%randy@psg.com> <m2pq23mpl5.wl%randy@psg.com> 
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [66.129.232.2]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-FOPE-CONNECTOR: Id%0$Dn%*$RO%0$TLS%0$FQDN%$TlsDn%
X-FOPE-CONNECTOR: Id%12219$Dn%PSG.COM$RO%2$TLS%5$FQDN%onpremiseedge-1018244.customer.frontbridge.com$TlsDn%o365mail.juniper.net
X-FOPE-CONNECTOR: Id%12219$Dn%IETF.ORG$RO%2$TLS%5$FQDN%onpremiseedge-1018244.customer.frontbridge.com$TlsDn%o365mail.juniper.net
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 04 Jan 2013 03:41:49 -0000

Hi Randy,

I have just posted draft-bonica-special-purpose-05. I hope that this versio=
n addressed the issues that we discussed, off-line.

                                             Ron


> -----Original Message-----
> From: Ronald Bonica
> Sent: Friday, December 21, 2012 10:49 AM
> To: 'Randy Bush'; IETF Disgust
> Subject: RE: draft-bonica-special-purpose-04.txt
>=20
> Hi Randy,
>=20
> It seems that we need one or both or the following:
>=20
> - a better title for the new column
> - a better definition to be associated with that column
>=20
> Any suggestions?
>=20
>               Ron
>=20
>=20
> > -----Original Message-----
> > From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf
> > Of Randy Bush
> > Sent: Friday, December 21, 2012 9:45 AM
> > To: IETF Disgust
> > Subject: draft-bonica-special-purpose-04.txt
> >
> > i remain confused.  i am not being pedantic just to be a pita.  i
> > really worry that this document will be used to justtify strange
> > brokenness.
> >
> > from my 2012.11.29 message:
> >
> > > are the following definitions
> > >
> > >    o  Routable - A boolean value indicating whether a IP datagram
> > whose
> > >       destination address is drawn from the allocated special-
> purpose
> > >       address block is routable (i.e., may traverse more than a
> > single
> > >       IP interface)
> > >
> > >    o  Global - A boolean value indicating whether a IP datagram
> whose
> > >       destination address is drawn from the allocated special-
> purpose
> > >       address block is routable beyond a specified administrative
> > >       domain.
> > >
> > > intended to be baked in hardware, or are they SHOULDs to operators?
> > i
> > > look at RFC 1918 space and 127.0.0.0/8 and am not so sure how hard
> > > these boundaries are meant to be.  i worry because i think we
> regret
> > > how we specified (threw away is more like it) E space.
> > >
> > > does the prefix describes a specific prefix length or a covering
> > range?
> > >
> > > e.g. 192.0.0.0/24 is neither routable nor global, while a subnet,
> > > 192.0.0.0/29, is routable.  i.e. might i route and forward
> > > 192.0.0.128/25?
> >
> > another annoying example.
> >
> > 0.0.0.0/8 is said to be not routable, yet we commonly announce it in
> > bgp (or igp) and propagate it.  a protocol implmentor reading this
> > document would be justified in preventing the injection of 0.0.0.0/8
> > into a routing protocol.  [ let's not get into that it is commonly in
> > the fib. ]
> >
> > randy



From dean.willis@softarmor.com  Thu Jan  3 21:15:23 2013
Return-Path: <dean.willis@softarmor.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B829721F8E5C for <ietf@ietfa.amsl.com>; Thu,  3 Jan 2013 21:15:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.599
X-Spam-Level: 
X-Spam-Status: No, score=-103.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
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 f09TuMnE+uxn for <ietf@ietfa.amsl.com>; Thu,  3 Jan 2013 21:15:23 -0800 (PST)
Received: from mail-ye0-f176.google.com (mail-ye0-f176.google.com [209.85.213.176]) by ietfa.amsl.com (Postfix) with ESMTP id C69A221F8E58 for <ietf@ietf.org>; Thu,  3 Jan 2013 21:15:22 -0800 (PST)
Received: by mail-ye0-f176.google.com with SMTP id m1so2540016yen.21 for <ietf@ietf.org>; Thu, 03 Jan 2013 21:15:22 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=softarmor.com; s=google; h=x-received:from:content-type:content-transfer-encoding:subject :message-id:date:to:mime-version:x-mailer; bh=Jmvdb+szXoQ/8XmrgBwXzVdPPzc9XeBkjZU2Hr/F688=; b=XrNOkE/GcEKunIJpZ2E6YPwD2iStrM/8lTbhV3ZJOTb0R/Atpq2wIJt6velBzScXIQ /wL7nnD/i1zKtrcoOr8oC8Z2GDFjhN7BSiWKHa2W9hbCTb4bAHu0B5Sc2p6/VfXTLUdB HuUbbzL5qn9jeouFkdwXb6+gWoHt8IPJuHwAw=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:from:content-type:content-transfer-encoding:subject :message-id:date:to:mime-version:x-mailer:x-gm-message-state; bh=Jmvdb+szXoQ/8XmrgBwXzVdPPzc9XeBkjZU2Hr/F688=; b=U7qMZKXccS9FNhCAooTSNIji8UYgUWgeRzXjsDic1JsrHqjn0hDCIjJe/685HG3q5i R+XZrDsPU0jeC4BL4ie+kc/xEPSLnZi8ivdrW7Qm/Fj/Y8lR3w/QnyOplaAUKXNeghak CRvK14TsfCDZJ2sn3vdGydeVWPjpHa8pnBTSV3lRJ728fHJ6FxzzdwYK2IQFkqHARTyz mVo/wvwe7Fw+6qFOOP2yqBOuD2m93yFjYiWea2yKYYF/Y8LYsXbV4RC68fbj+rd5yyPH gPZINOsufo7DF2MDP4SSa5CVOtL8/AOwJk8YuXss/jwTDVzcBvvdQbLg2K3IsMqmbabJ oPQw==
X-Received: by 10.236.114.11 with SMTP id b11mr53893547yhh.61.1357276522220; Thu, 03 Jan 2013 21:15:22 -0800 (PST)
Received: from [192.168.2.115] (cpe-72-181-157-19.tx.res.rr.com. [72.181.157.19]) by mx.google.com with ESMTPS id j25sm52558720yhm.13.2013.01.03.21.15.21 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 03 Jan 2013 21:15:21 -0800 (PST)
From: Dean Willis <dean.willis@softarmor.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Subject: I'm struggling with 2219 language again
Message-Id: <7ED55FF1-3E1A-4DF7-918E-07790517B848@softarmor.com>
Date: Thu, 3 Jan 2013 23:15:20 -0600
To: ietf@ietf.org
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
X-Mailer: Apple Mail (2.1499)
X-Gm-Message-State: ALoCoQmmA9N/aaGPu0CRXIqomMOYUGgbMhBIgnJutZi2ftZBMUp/XHY65Ja+Bw3HPNTp2wwaOzRw
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 04 Jan 2013 05:15:23 -0000

I've always held to the idea that RFC 2119 language is for defining =
levels of compliance to requirements, and is best used very sparingly =
(as recommended in RFC 2119 itself). To me, RFC 2119 language doesn't =
make behavior normative -- rather, it describes the implications of =
doing something different than the defined behavior, from "will break =
the protocol if you change it" to "we have reason to think that there =
might be a reason we don't want to describe here that might influence =
you not to do this" to "here are some reasons that would cause you to do =
something different" and on to "doing something different might offend =
the sensibilities of the protocol author, but probably won't hurt =
anything else."

But I'm ghost-editing a document right now whose gen-art review =
suggested replacing the vast majority of "is" "does" and "are" prose =
with MUST. The comments seem to indicate that protocol-defining text not =
using RFC 2119 language (specifically MUST) is "not normative".

This makes me cringe. But my co-editor likes it a lot. And I see smart =
people like Ole also echoing the though that RFC 2119 language is what =
makes text normative.

For example, the protocol under discussion uses TLS or DTLS for a =
plethora of security reasons. So, every time the draft discusses sending =
a response to a request, we would say "the node MUST send a response, =
and this response MUST be constructed by (insert some concatenation =
procedure here) and MUST be transmitted using TLS or DTLS.

Or, a more specific example:

For the text:

In order to originate a message to a given Node-ID or
Resource-ID, a node constructs an appropriate destination list.


The Gen-ART comment here is:
-First sentence: "a node constructs" -> "a node MUST construct"


We'll literally end up with hundreds of RFC 2119 invocations (mostly =
MUST) in a protocol specification.

Is this a good or bad thing? My co-editor and I disagree -- he likes =
formalization of the description language, and I like the English prose. =
But it raises process questions for the IETF as a whole:=20

Are we deliberately evolving our language to use RFC 2119 terms as the =
principle verbs  of a formal specification language?

Either way, I'd like to see some consensus. Because my head is throbbing =
and I want to know if it MUST hurt, SHOULD hurst, or just hurts. But I =
MUST proceed in accordance with consensus, because to do otherwise would =
undermine the clarity of our entire specification family.

--
Dean=

From narten@us.ibm.com  Thu Jan  3 21:53:15 2013
Return-Path: <narten@us.ibm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B9D4C21F8E30 for <ietf@ietfa.amsl.com>; Thu,  3 Jan 2013 21:53:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.599
X-Spam-Level: 
X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
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 bzhWra5h8RW1 for <ietf@ietfa.amsl.com>; Thu,  3 Jan 2013 21:53:14 -0800 (PST)
Received: from e8.ny.us.ibm.com (e8.ny.us.ibm.com [32.97.182.138]) by ietfa.amsl.com (Postfix) with ESMTP id A73AB21F8E19 for <ietf@ietf.org>; Thu,  3 Jan 2013 21:53:14 -0800 (PST)
Received: from /spool/local by e8.ny.us.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for <ietf@ietf.org> from <narten@us.ibm.com>; Fri, 4 Jan 2013 00:53:13 -0500
Received: from d01dlp01.pok.ibm.com (9.56.250.166) by e8.ny.us.ibm.com (192.168.1.108) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted;  Fri, 4 Jan 2013 00:53:10 -0500
Received: from d01relay04.pok.ibm.com (d01relay04.pok.ibm.com [9.56.227.236]) by d01dlp01.pok.ibm.com (Postfix) with ESMTP id 3056738C8026 for <ietf@ietf.org>; Fri,  4 Jan 2013 00:53:10 -0500 (EST)
Received: from d01av03.pok.ibm.com (d01av03.pok.ibm.com [9.56.224.217]) by d01relay04.pok.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id r045r9r8324198 for <ietf@ietf.org>; Fri, 4 Jan 2013 00:53:09 -0500
Received: from d01av03.pok.ibm.com (loopback [127.0.0.1]) by d01av03.pok.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP id r045r97P005284 for <ietf@ietf.org>; Fri, 4 Jan 2013 03:53:09 -0200
Received: from rotala.raleigh.ibm.com (rotala.raleigh.ibm.com [9.44.115.148]) by d01av03.pok.ibm.com (8.14.4/8.13.1/NCO v10.0 AVin) with ESMTP id r045r8U7005244 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Fri, 4 Jan 2013 03:53:08 -0200
Received: from rotala.raleigh.ibm.com (localhost.localdomain [127.0.0.1]) by rotala.raleigh.ibm.com (8.14.5/8.12.5) with ESMTP id r045r7F2007086 for <ietf@ietf.org>; Fri, 4 Jan 2013 00:53:08 -0500
Received: (from narten@localhost) by rotala.raleigh.ibm.com (8.14.5/8.14.5/Submit) id r045r7x7007021 for ietf@ietf.org; Fri, 4 Jan 2013 00:53:07 -0500
From: Thomas Narten <narten@us.ibm.com>
Message-Id: <201301040553.r045r7x7007021@rotala.raleigh.ibm.com>
Date: Fri, 04 Jan 2013 00:53:06 -0500
To: ietf@ietf.org
Subject: Weekly posting summary for ietf@ietf.org
User-Agent: Heirloom mailx 12.5 7/5/10
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Content-Scanned: Fidelis XPS MAILER
x-cbid: 13010405-9360-0000-0000-00000EBEA964
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 04 Jan 2013 05:53:15 -0000

Total of 92 messages in the last 7 days.
 
script run at: Fri Jan  4 00:53:06 EST 2013
 
    Messages   |      Bytes        | Who
--------+------+--------+----------+------------------------
  8.70% |    8 | 14.15% |   126350 | hallam@gmail.com
  8.70% |    8 | 13.78% |   123045 | jeanjour@comcast.net
  7.61% |    7 |  4.67% |    41668 | dhc@dcrocker.net
  7.61% |    7 |  4.20% |    37492 | mohta@necom830.hpcl.titech.ac.jp
  5.43% |    5 |  4.45% |    39710 | chris.dearlove@baesystems.com
  1.09% |    1 |  6.54% |    58445 | nabil.n.bitar@verizon.com
  4.35% |    4 |  2.99% |    26738 | john-ietf@jck.com
  2.17% |    2 |  3.84% |    34288 | ndonnang@isoc-cameroon.org
  3.26% |    3 |  2.52% |    22490 | daedulus@btconnect.com
  3.26% |    3 |  2.51% |    22394 | carlosm3011@gmail.com
  3.26% |    3 |  2.30% |    20536 | sm@resistor.net
  2.17% |    2 |  2.93% |    26167 | jgunn6@csc.com
  1.09% |    1 |  3.36% |    29966 | jeff.hodges@kingsmountain.com
  2.17% |    2 |  1.94% |    17347 | brian.e.carpenter@gmail.com
  2.17% |    2 |  1.84% |    16456 | paf@frobbit.se
  2.17% |    2 |  1.76% |    15760 | fred@cisco.com
  2.17% |    2 |  1.50% |    13398 | ned+ietf@mauve.mrochek.com
  2.17% |    2 |  1.48% |    13218 | steve@shinkuro.com
  2.17% |    2 |  1.13% |    10083 | randy@psg.com
  2.17% |    2 |  1.09% |     9759 | jnc@mercury.lcs.mit.edu
  1.09% |    1 |  2.15% |    19202 | jmamodio@gmail.com
  1.09% |    1 |  1.89% |    16888 | dvburk@gmail.com
  1.09% |    1 |  1.34% |    11969 | alh-ietf@tndh.net
  1.09% |    1 |  1.08% |     9668 | rbonica@juniper.net
  1.09% |    1 |  1.06% |     9454 | jaap@nlnetlabs.nl
  1.09% |    1 |  0.96% |     8605 | paul@redbarn.org
  1.09% |    1 |  0.90% |     8008 | kwiereng@cisco.com
  1.09% |    1 |  0.85% |     7587 | warren@kumari.net
  1.09% |    1 |  0.79% |     7029 | stbryant@cisco.com
  1.09% |    1 |  0.78% |     6983 | narten@us.ibm.com
  1.09% |    1 |  0.77% |     6839 | vesely@tana.it
  1.09% |    1 |  0.74% |     6601 | chair@ietf.org
  1.09% |    1 |  0.68% |     6031 | d3e3e3@gmail.com
  1.09% |    1 |  0.67% |     6019 | worley@alum.mit.edu
  1.09% |    1 |  0.67% |     6009 | ben@nostrum.com
  1.09% |    1 |  0.66% |     5916 | worley@ariadne.com
  1.09% |    1 |  0.65% |     5790 | abdussalambaryun@gmail.com
  1.09% |    1 |  0.65% |     5786 | johnl@taugh.com
  1.09% |    1 |  0.65% |     5772 | lixia@cs.ucla.edu
  1.09% |    1 |  0.64% |     5718 | jason_livingood@cable.comcast.com
  1.09% |    1 |  0.63% |     5652 | gjshep@gmail.com
  1.09% |    1 |  0.62% |     5565 | dwm@xpasc.com
  1.09% |    1 |  0.61% |     5469 | smb@cs.columbia.edu
  1.09% |    1 |  0.59% |     5240 | mcr@sandelman.ca
--------+------+--------+----------+------------------------
100.00% |   92 |100.00% |   893110 | Total


From eng.mahmoudemam@yahoo.com  Thu Jan  3 23:06:15 2013
Return-Path: <eng.mahmoudemam@yahoo.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0418521F8E07 for <ietf@ietfa.amsl.com>; Thu,  3 Jan 2013 23:06:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.76
X-Spam-Level: 
X-Spam-Status: No, score=0.76 tagged_above=-999 required=5 tests=[AWL=0.758, BAYES_50=0.001, HTML_MESSAGE=0.001]
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 AWDLn5HVzdOp for <ietf@ietfa.amsl.com>; Thu,  3 Jan 2013 23:06:14 -0800 (PST)
Received: from nm33-vm4.bullet.mail.ne1.yahoo.com (nm33-vm4.bullet.mail.ne1.yahoo.com [98.138.229.68]) by ietfa.amsl.com (Postfix) with ESMTP id 6E30321F8D71 for <ietf@ietf.org>; Thu,  3 Jan 2013 23:06:14 -0800 (PST)
Received: from [98.138.226.176] by nm33.bullet.mail.ne1.yahoo.com with NNFMP; 04 Jan 2013 07:06:10 -0000
Received: from [98.138.87.4] by tm11.bullet.mail.ne1.yahoo.com with NNFMP; 04 Jan 2013 07:06:10 -0000
Received: from [127.0.0.1] by omp1004.mail.ne1.yahoo.com with NNFMP; 04 Jan 2013 07:06:10 -0000
X-Yahoo-Newman-Property: ymail-3
X-Yahoo-Newman-Id: 649620.26328.bm@omp1004.mail.ne1.yahoo.com
Received: (qmail 2105 invoked by uid 60001); 4 Jan 2013 07:06:10 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1357283170; bh=K4D7P1kQ58HjA4N6F0fMWQNkmALyhI/L6QAjsLFCK/4=; h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:In-Reply-To:MIME-Version:Content-Type; b=YYhgLXyGKBeKLXFgms15v9kdSTbDNpUSQlSOKWBe0eEzIFs07Q70Xl7y1MuMY3N39omQFtuZYZcXzJHVIKqFMkp9Ck4L3crlHLBptTb9qwKAexT40zD2ZWwJuN0wHOf2cB6FKVb2IewvNzZDU7Ij6u5qYEz8t1cHQy3qIJWt2hE=
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:In-Reply-To:MIME-Version:Content-Type; b=PVRINPgaI711HoqDRGxS/ENZdIm3p6tK+4bmTRq8J9FykrUX5KVfSN4U27BwD1WR1e49duzyrD1Ra9KJEtymKZiD7En5axCWzKjLaeZsfqO1Jdc78Emuddgq6SHDPOBkYOySPI7IDjtY5mrFevszGZbkZE6xJEx/SVZKNq/NHxc=;
X-YMail-OSG: rIx2mGAVM1lLN1tttYZPjxGOr5mj8V4CZ2DnTXqKNVQlK2B _pkhp.73MG6JIWRdbs5rI7NfNO5C.2NO2bDShYG07Li9YSZAbEmvKhYm9QSj l93BjeIDRsS_LAj8kAxu.dzgZk.NupAigqG8UCukp.d.P2uJPYsXEUkP6MH4 i4bE0DhUm1iovhRXYPCNHEj.IWLz0l27zYc1SFZR1hYCsJ4iupaakPp7CF_V qLuRdXn1ddGFppe.1CdnD.10DyjkeYaZlTXqCntlynuZs1Weie.Tc9keTTSx QXnXzgjd1Ue1_N4Aekr9rJD6YqI3mcL9cq3cgYVsPSjs2qowdU4Baz7InRfD oWI44rindSkVgT49KjcOppKxokp1utvJ50QmT8xzO8ZSmlG6v7FpQkQ9Hp3k VB4LwScyuPlBS1bFJSqAzAuipPanwcyqAaaylFp4W_4gWMW6jir6auQWWLwk QruBA17HzO3rrdamgE8oe2Ckt7SMPCFUoI5rvYghUYRokRPW56O7oD4ORs6U GZaZy
Received: from [217.55.236.140] by web121706.mail.ne1.yahoo.com via HTTP; Thu, 03 Jan 2013 23:06:10 PST
X-Rocket-MIMEInfo: 001.001, CgpIZWxsbyBldmVyeWJvZHksCgoKSSBhbSBhIHJlc2VhcmNoZXIgb2YgTWFzdGVyJ3MgZGVncmVlICwgd29ya2luZyBvbiBMRUFDSCByb3V0aW5nIHByb3RvY29swqBmb3Igd2lyZWxlc3Mgc2Vuc29yIG5ldHdvcmtzIGFuZCBpIG5lZWQgdG8ga25vdyBmb3Igd2hpY2ggc3RhbmRhcmQgZG9lcyBMRUFDSCAsIGl0cyBmYW1pbHkgLG9yIGV2ZW4gTGF5ZXIgMyBiZWxvbmcgdG8uCsKgClRoYW5rIHlvdQEwAQEBAQ--
X-Mailer: YahooMailWebService/0.8.129.483
References: <1357236650.92594.YahooMailNeo@web121705.mail.ne1.yahoo.com> <1357242683.46577.YahooMailNeo@web121701.mail.ne1.yahoo.com>
Message-ID: <1357283170.91996.YahooMailNeo@web121706.mail.ne1.yahoo.com>
Date: Thu, 3 Jan 2013 23:06:10 -0800 (PST)
From: Mahmoud Emam <eng.mahmoudemam@yahoo.com>
Subject: Hello ::Please I need to know LEACH protocol standard???
To: "ietf@ietf.org" <ietf@ietf.org>
In-Reply-To: <1357242683.46577.YahooMailNeo@web121701.mail.ne1.yahoo.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="-730330825-903917708-1357283170=:91996"
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: Mahmoud Emam <eng.mahmoudemam@yahoo.com>
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 04 Jan 2013 07:06:15 -0000

---730330825-903917708-1357283170=:91996
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable

=0A=0AHello everybody,=0A=0A=0AI am a researcher of Master's degree , worki=
ng on LEACH routing protocol=A0for wireless sensor networks and i need to k=
now for which standard does LEACH , its family ,or even Layer 3 belong to.=
=0A=A0=0AThank you
---730330825-903917708-1357283170=:91996
Content-Type: text/html; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable

<html><body><div style=3D"color:#000; background-color:#fff; font-family:bo=
okman old style, new york, times, serif;font-size:18pt"><div><br></div><div=
 style=3D"font-family: 'bookman old style', 'new york', times, serif; font-=
size: 18pt;"><div style=3D"font-family: 'times new roman', 'new york', time=
s, serif; font-size: 12pt;"><div id=3D"yiv1901863708"><div><div style=3D"co=
lor: rgb(0, 0, 0); background-color: rgb(255, 255, 255); font-family: 'book=
man old style', 'new york', times, serif; font-size: 18pt;"><div style=3D"f=
ont-family: 'bookman old style', 'new york', times, serif; font-size: 18pt;=
"><div style=3D"font-family: 'times new roman', 'new york', times, serif; f=
ont-size: 12pt;">=0A<div id=3D"yiv1901863708"><div><div style=3D"color: rgb=
(0, 0, 0); background-color: rgb(255, 255, 255); font-family: 'bookman old =
style', 'new york', times, serif; font-size: 18pt;"><div>Hello everybody,</=
div><div><br></div><div style=3D"color: rgb(0, 0, 0); font-size: 24px; font=
-family: 'bookman old style', 'new york', times, serif; background-color: t=
ransparent; font-style: normal;"><br></div><div><span style=3D"font-size:18=
pt;">I am a researcher of Master's degree , working on LEACH routing protoc=
ol&nbsp;</span><span style=3D"font-size:18pt;">for wireless sensor networks=
 and i need to know for which standard does LEACH , its family ,or even Lay=
er 3 belong to.</span></div><div style=3D"color: rgb(0, 0, 0); font-size: 1=
8pt; font-family: 'bookman old style', 'new york', times, serif; background=
-color: transparent; font-style: normal;"><span style=3D"font-size:18pt;">&=
nbsp;</span></div><blockquote style=3D"border:none;padding:0px;"><div style=
=3D"text-align: right; color:
 rgb(0, 0, 0); font-size: 18pt; font-family: 'bookman old style', 'new york=
', times, serif; background-color: transparent; font-style: normal;"><span =
style=3D"font-size:18pt;">Thank you</span></div></blockquote></div></div></=
div><br><br> </div> </div>  </div></div></div><br><br> </div> </div>  </div=
></body></html>
---730330825-903917708-1357283170=:91996--

From eng.mahmoudemam@yahoo.com  Thu Jan  3 23:12:14 2013
Return-Path: <eng.mahmoudemam@yahoo.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1C5F521F85F3 for <ietf@ietfa.amsl.com>; Thu,  3 Jan 2013 23:12:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.358
X-Spam-Level: 
X-Spam-Status: No, score=0.358 tagged_above=-999 required=5 tests=[AWL=0.356,  BAYES_50=0.001, HTML_MESSAGE=0.001]
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 YEP64MC9gkSA for <ietf@ietfa.amsl.com>; Thu,  3 Jan 2013 23:12:13 -0800 (PST)
Received: from nm19-vm2.bullet.mail.ne1.yahoo.com (nm19-vm2.bullet.mail.ne1.yahoo.com [98.138.91.95]) by ietfa.amsl.com (Postfix) with ESMTP id 7238421F856D for <ietf@ietf.org>; Thu,  3 Jan 2013 23:12:13 -0800 (PST)
Received: from [98.138.90.52] by nm19.bullet.mail.ne1.yahoo.com with NNFMP; 04 Jan 2013 07:12:13 -0000
Received: from [98.138.87.10] by tm5.bullet.mail.ne1.yahoo.com with NNFMP; 04 Jan 2013 07:12:13 -0000
Received: from [127.0.0.1] by omp1010.mail.ne1.yahoo.com with NNFMP; 04 Jan 2013 07:12:13 -0000
X-Yahoo-Newman-Property: ymail-3
X-Yahoo-Newman-Id: 52473.50534.bm@omp1010.mail.ne1.yahoo.com
Received: (qmail 96608 invoked by uid 60001); 4 Jan 2013 07:05:33 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1357283133; bh=Hto6f/xbFTyA8KIkVI/7itOAIjWxVUt1w/yygE4wl+M=; h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:In-Reply-To:MIME-Version:Content-Type; b=hMGJO3wrUMAsEciGw6SLW9N6eB0zluTtNsxCLcz1fqCY/hTdHFQ98xF8D89PY94g/yjYVLTneR6xQXf6K4smo7AdBhEybEy88OlUzg0PgfiXh56O++quIS3MSRIiexM1b5xxvnKUowvqqIb1gHmeT8xK81F5GuLM7yX35SgzZhM=
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:In-Reply-To:MIME-Version:Content-Type; b=WijDFzLpoW2oT5JkwEYxUN6Liqb4m6ZDvUHOttBKhMsBi5nO8zIbNrdUGWeCW4cnF11+h9O/8M1a3aIBHVag2RkHby9oNEJ/gm+6+ZxHPSGj5NSmQmRyhNyENrWon6zKPIZSB2HAx0N2m6K4e23EjRaKVRTZYYWN4IyL/L/hZvA=;
X-YMail-OSG: 3QUFtgoVM1k7imWEuOfdoGl7.ruE8pQ7z2PXrvQKRRY3qXj dPgncVwEGzPa6QCmOneiRZC2nij3SqwIISAlud3wQGdqrG8ImEjVn9Saarm. uNHRjqaQOBN9pRTzjfPsWroRhuI6rqlffmeqrJxhfqxG4mJbEIM2.F_oWPDj xeWkx1WESSbb4VqhGHizLKbtHY6XuA9EX1J.pr7gBdjlRel.7RGkcfE4yXBz M.O298wqRrPFGD2BLXya0zU1uDEmInMtitXW1Tru5k_jNI524wadbvBsN1kI nlwH5A5mka_u2A6LE6YmgHh6XAoqeKbnswWECP0ao1Si5I277QlLdXpLW64v 7sHLjwJkwmynduCTGZcv1_mT6VTwhA3Xa66uK41pJ1lRDZyo5IovTEkYNe4s ue6F_UW3P5qGJ.G9wC94nkT70DZn4ksr.Il1X7M05Sda9wBzQa4PRXrUCta2 8JShFw8Qpw.mt0EHH9L3rJNMHWC2w_JEwfw0oaBZ3.UdtS.0QaYIua1LtBZ. RMufF
Received: from [217.55.236.140] by web121706.mail.ne1.yahoo.com via HTTP; Thu, 03 Jan 2013 23:05:33 PST
X-Rocket-MIMEInfo: 001.001, CgpIZWxsbyBldmVyeWJvZHksCgoKSSBhbSBhIHJlc2VhcmNoZXIgb2YgTWFzdGVyJ3MgZGVncmVlICwgd29ya2luZyBvbiBMRUFDSCByb3V0aW5nIHByb3RvY29swqBmb3Igd2lyZWxlc3Mgc2Vuc29yIG5ldHdvcmtzIGFuZCBpIG5lZWQgdG8ga25vdyBmb3Igd2hpY2ggc3RhbmRhcmQgZG9lcyBMRUFDSCAsIGl0cyBmYW1pbHkgLG9yIGV2ZW4gTGF5ZXIgMyBiZWxvbmcgdG8uCsKgClRoYW5rIHlvdQEwAQEBAQ--
X-Mailer: YahooMailWebService/0.8.129.483
References: <1357236650.92594.YahooMailNeo@web121705.mail.ne1.yahoo.com> <1357242683.46577.YahooMailNeo@web121701.mail.ne1.yahoo.com>
Message-ID: <1357283133.26707.YahooMailNeo@web121706.mail.ne1.yahoo.com>
Date: Thu, 3 Jan 2013 23:05:33 -0800 (PST)
From: Mahmoud Emam <eng.mahmoudemam@yahoo.com>
Subject: Hello ::Please I need to know LEACH protocol standard???
To: "ietf@ietf.org" <ietf@ietf.org>
In-Reply-To: <1357242683.46577.YahooMailNeo@web121701.mail.ne1.yahoo.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="-730330825-520880701-1357283133=:26707"
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: Mahmoud Emam <eng.mahmoudemam@yahoo.com>
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 04 Jan 2013 07:12:14 -0000

---730330825-520880701-1357283133=:26707
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable

=0A=0AHello everybody,=0A=0A=0AI am a researcher of Master's degree , worki=
ng on LEACH routing protocol=A0for wireless sensor networks and i need to k=
now for which standard does LEACH , its family ,or even Layer 3 belong to.=
=0A=A0=0AThank you
---730330825-520880701-1357283133=:26707
Content-Type: text/html; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable

<html><body><div style=3D"color:#000; background-color:#fff; font-family:bo=
okman old style, new york, times, serif;font-size:18pt"><div><br></div><div=
 style=3D"font-family: 'bookman old style', 'new york', times, serif; font-=
size: 18pt;"><div style=3D"font-family: 'times new roman', 'new york', time=
s, serif; font-size: 12pt;"><div id=3D"yiv1901863708"><div><div style=3D"co=
lor: rgb(0, 0, 0); background-color: rgb(255, 255, 255); font-family: 'book=
man old style', 'new york', times, serif; font-size: 18pt;"><div style=3D"f=
ont-family: 'bookman old style', 'new york', times, serif; font-size: 18pt;=
"><div style=3D"font-family: 'times new roman', 'new york', times, serif; f=
ont-size: 12pt;">=0A<div id=3D"yiv1901863708"><div><div style=3D"color: rgb=
(0, 0, 0); background-color: rgb(255, 255, 255); font-family: 'bookman old =
style', 'new york', times, serif; font-size: 18pt;"><div>Hello everybody,</=
div><div><br></div><div style=3D"color: rgb(0, 0, 0); font-size: 24px; font=
-family: 'bookman old style', 'new york', times, serif; background-color: t=
ransparent; font-style: normal;"><br></div><div><span style=3D"font-size:18=
pt;">I am a researcher of Master's degree , working on LEACH routing protoc=
ol&nbsp;</span><span style=3D"font-size:18pt;">for wireless sensor networks=
 and i need to know for which standard does LEACH , its family ,or even Lay=
er 3 belong to.</span></div><div style=3D"color: rgb(0, 0, 0); font-size: 1=
8pt; font-family: 'bookman old style', 'new york', times, serif; background=
-color: transparent; font-style: normal;"><span style=3D"font-size:18pt;">&=
nbsp;</span></div><blockquote style=3D"border:none;padding:0px;"><div style=
=3D"text-align: right; color:
 rgb(0, 0, 0); font-size: 18pt; font-family: 'bookman old style', 'new york=
', times, serif; background-color: transparent; font-style: normal;"><span =
style=3D"font-size:18pt;">Thank you</span></div></blockquote></div></div></=
div><br><br> </div> </div>  </div></div></div><br><br> </div> </div>  </div=
></body></html>
---730330825-520880701-1357283133=:26707--

From ole@cisco.com  Thu Jan  3 23:55:18 2013
Return-Path: <ole@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 64BD221F8E91 for <ietf@ietfa.amsl.com>; Thu,  3 Jan 2013 23:55:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.599
X-Spam-Level: 
X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
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 4MzgeN2JlsOI for <ietf@ietfa.amsl.com>; Thu,  3 Jan 2013 23:55:17 -0800 (PST)
Received: from mtv-iport-3.cisco.com (mtv-iport-3.cisco.com [173.36.130.14]) by ietfa.amsl.com (Postfix) with ESMTP id 2BCF921F8E7F for <ietf@ietf.org>; Thu,  3 Jan 2013 23:55:16 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=322; q=dns/txt; s=iport; t=1357286116; x=1358495716; h=date:from:reply-to:to:cc:subject:in-reply-to:message-id: references:mime-version; bh=qCe2L32rStzy7TsRLvTvvJH0h0Zu+Of2naBRczD+mwc=; b=BJSRus3TK7YJBu2N+15wQrADipaU7EZXOGWNbMSTRJ5UrUXOvDst9+0G TbgARKKEwGKa2fU2TWiTcidfdShRzWzWYYdqv/l9uh6jFNfPloUKc/FV9 lSk+fB0/tZedov7uzEnPr2AAfUAkyo/i9Vxa5sDPOaXu3K5r7eNX4278Z A=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AiYJACGK5lCrRDoH/2dsb2JhbABCA4VzpQuFH40wFnOCHwEBBDo/EAtGRRIGExqHZwMODa94A4ZtjHF6gy4DiGKORoRPhU+FDoMVgVA
X-IronPort-AV: E=Sophos;i="4.84,409,1355097600"; d="scan'208";a="65374962"
Received: from mtv-core-2.cisco.com ([171.68.58.7]) by mtv-iport-3.cisco.com with ESMTP; 04 Jan 2013 07:55:15 +0000
Received: from [10.27.1.132] (sjc-ole-8913.cisco.com [10.27.1.132]) by mtv-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id r047tF9E006964 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 4 Jan 2013 07:55:15 GMT
Date: Thu, 3 Jan 2013 23:55:07 -0800 (PST)
From: Ole Jacobsen <ole@cisco.com>
To: John Levine <johnl@taugh.com>
Subject: Re: travel guide for the next IETF...
In-Reply-To: <20130102231451.24327.qmail@joyce.lan>
Message-ID: <alpine.OSX.2.01.1301032354480.80268@173-11-110-132-sfba.hfc.comcastbusiness.net>
References: <20130102231451.24327.qmail@joyce.lan>
User-Agent: Alpine 2.01 (OSX 1266 2009-07-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: Ole Jacobsen <ole@cisco.com>
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 04 Jan 2013 07:55:18 -0000

You have been warned.

http://news.yahoo.com/video/request-ketchup-philly-cheesesteak-leads-001204299.html


Ole J. Jacobsen
Editor and Publisher,  The Internet Protocol Journal
Cisco Systems
Tel: +1 408-527-8972   Mobile: +1 415-370-4628
E-mail: ole@cisco.com  URL: http://www.cisco.com/ipj
Skype: organdemo



From brian.e.carpenter@gmail.com  Fri Jan  4 00:02:31 2013
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 386D321F8CE5 for <ietf@ietfa.amsl.com>; Fri,  4 Jan 2013 00:02:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.691
X-Spam-Level: 
X-Spam-Status: No, score=-101.691 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_ILLEGAL_IP=1.908, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
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 ov0PJpFlbqk9 for <ietf@ietfa.amsl.com>; Fri,  4 Jan 2013 00:02:29 -0800 (PST)
Received: from mail-wi0-f178.google.com (mail-wi0-f178.google.com [209.85.212.178]) by ietfa.amsl.com (Postfix) with ESMTP id 7B2C721F8CD6 for <ietf@ietf.org>; Fri,  4 Jan 2013 00:02:29 -0800 (PST)
Received: by mail-wi0-f178.google.com with SMTP id hn3so9060911wib.11 for <ietf@ietf.org>; Fri, 04 Jan 2013 00:02:28 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:organization:user-agent :mime-version:to:cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=RgACn09DSZkNh+KYaqK92yUryjt7LEF079fj+T9LEjE=; b=PVsSXVMn3YjeQqZn1gPM2ccmcjsFrXz+LQtugBGQrnc14PBtSf9rx6dmmuK+P8gZ23 nlT62NO5iWL1wdW/uXh7LOrZ+XhOCI+5aiq227RiYOFbSbvnFIGFlYDyUoESul76sAMP j1NHuIYQcR7IF2fUCuvFFDGE4HpJgr6+rH0aECrmgFhSR/R3cGPJARpqqJew07+jvdOl z3HDZILV1EkMI1+QHXavM7lWhNApvHmcV/zreTE2J5Wyf7SS6jF+hkNiwz126F2+yMFX 1ncv+WYLYdkfXnpWGA2HkPCjLjMm8JbFFLooLdMePaodBg5yHls+tF7aHjskAlVI9IJz wpGA==
X-Received: by 10.194.110.231 with SMTP id id7mr82361837wjb.6.1357286548522; Fri, 04 Jan 2013 00:02:28 -0800 (PST)
Received: from [192.168.1.65] (host-2-102-219-29.as13285.net. [2.102.219.29]) by mx.google.com with ESMTPS id bw9sm66221430wib.5.2013.01.04.00.02.27 (version=SSLv3 cipher=OTHER); Fri, 04 Jan 2013 00:02:27 -0800 (PST)
Message-ID: <50E68CB5.4010107@gmail.com>
Date: Fri, 04 Jan 2013 08:03:01 +0000
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Dean Willis <dean.willis@softarmor.com>
Subject: Re: I'm struggling with 2219 language again
References: <7ED55FF1-3E1A-4DF7-918E-07790517B848@softarmor.com>
In-Reply-To: <7ED55FF1-3E1A-4DF7-918E-07790517B848@softarmor.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 04 Jan 2013 08:02:31 -0000

On 04/01/2013 05:15, Dean Willis wrote:
...
> Either way, I'd like to see some consensus. Because my head is throbbing and I want to know if it MUST hurt, SHOULD hurst, or just hurts. But I MUST proceed in accordance with consensus, because to do otherwise would undermine the clarity of our entire specification family.

This Gen-ART reviewer believes that words like "must" have well defined meanings
in the English language, so shouting is not needed at every use. There are
standards track documents that don't use RFC 2119 at all, and I am not only
referring to RFC 791.

I think the upper case keywords should be used only when necessary to clarify
points of potential non-interoperability or insecurity. I'm quite sure that
I've broken that recommendation quite often, and it will always remain
a judgment call. However, inserting a MUST in every sentence that describes
behaviour is surely going too far. I guess the test is whether a reasonably
careful reader might interpret a sentence incorrectly while writing code;
and if so, would a normative keyword help?

     Brian

From randy@psg.com  Fri Jan  4 00:42:00 2013
Return-Path: <randy@psg.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C676021F861F for <ietf@ietfa.amsl.com>; Fri,  4 Jan 2013 00:42:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.486
X-Spam-Level: 
X-Spam-Status: No, score=-2.486 tagged_above=-999 required=5 tests=[AWL=0.114,  BAYES_00=-2.599]
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 bQyjGkp+dGJX for <ietf@ietfa.amsl.com>; Fri,  4 Jan 2013 00:42:00 -0800 (PST)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by ietfa.amsl.com (Postfix) with ESMTP id 6D71621F8554 for <ietf@ietf.org>; Fri,  4 Jan 2013 00:42:00 -0800 (PST)
Received: from localhost ([127.0.0.1] helo=ryuu.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.80.1 (FreeBSD)) (envelope-from <randy@psg.com>) id 1Tr2qk-0005y4-IA; Fri, 04 Jan 2013 08:41:59 +0000
Date: Fri, 04 Jan 2013 17:41:56 +0900
Message-ID: <m24nixibl7.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Ronald Bonica <rbonica@juniper.net>
Subject: Re: draft-bonica-special-purpose-04.txt
In-Reply-To: <2CF4CB03E2AA464BA0982EC92A02CE2501E042A8@BY2PRD0512MB653.namprd05.prod.outlook.com>
References: <20121129205534.8983.43593.idtracker@ietfa.amsl.com> <m2fw3s2ii7.wl%randy@psg.com> <m2pq23mpl5.wl%randy@psg.com> <2CF4CB03E2AA464BA0982EC92A02CE2501E042A8@BY2PRD0512MB653.namprd05.prod.outlook.com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
Cc: IETF Disgust <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 04 Jan 2013 08:42:00 -0000

ron,

> I have just posted draft-bonica-special-purpose-05. I hope that this
> version addressed the issues that we discussed, off-line.

indeed it does.  s/prefix/address block/  and  s/routable/forwardable/
hits my two issues on the head.  thank you.

it might be good if, now that these changes have been made, for someone
more knowledgeable than i to go through each entry.  i kinda did and
nothing set off large alarms.

randy

From dave@cridland.net  Fri Jan  4 01:57:56 2013
Return-Path: <dave@cridland.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B08BF21F8E50 for <ietf@ietfa.amsl.com>; Fri,  4 Jan 2013 01:57:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.977
X-Spam-Level: 
X-Spam-Status: No, score=-2.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1]
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 cmIzw+RoaZeY for <ietf@ietfa.amsl.com>; Fri,  4 Jan 2013 01:57:55 -0800 (PST)
Received: from mail-ob0-f171.google.com (mail-ob0-f171.google.com [209.85.214.171]) by ietfa.amsl.com (Postfix) with ESMTP id 763BB21F8DF1 for <ietf@ietf.org>; Fri,  4 Jan 2013 01:57:52 -0800 (PST)
Received: by mail-ob0-f171.google.com with SMTP id dn14so14550638obc.2 for <ietf@ietf.org>; Fri, 04 Jan 2013 01:57:50 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cridland.net; s=google; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=VvturzWFN/MT/gboTw3mtOwr47I6WBd8/aX5fy1oTq0=; b=ENNpnozPDwS9b5yBch7eTwHjk5ooOkDYcbOxqeyFe4HIq/AM9Io0mNNKJ7WMDhNaJ2 zejtfgzTf+Min5XH9rMd1QFAcoSDrd96QrCskwawrMdHSTOzXYw5KKsguQ8/knCV/vaW uPhkUeRZPKmJ+2ZaxVr9ILvQwlwGkrwblGWsg=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:x-gm-message-state; bh=VvturzWFN/MT/gboTw3mtOwr47I6WBd8/aX5fy1oTq0=; b=W5SHk3a+EH+hQVbInnbFzl9z03LvSDe/fYiswpv+tGl3Z89vI/k8ddTJIXYMKc+kdK p9UsBTaYLZ+ozxseGBTv7jRHml1nx/wEurknQ0+7zDyLwNrLHDlIgoMQx3f/NNwWsqHw h/JHhcLSWGBnkcEu4JT+UagpmF8+2gEc2LNDAgZJPWzUdZlD90sJmyuYJMOGGaBVX31D 112Rh1o3Q2nl2upMJZO1VxNae771s8seDyUjDHMTsAmLAbjuRmuqypqXmlj2RcAfwvQ/ 7llsA20P5PFGbdVfL5kWkfEtqHZswrX0LmSocvm0qHQtAFkpaWQSadLSQQB3H8S45DBJ yJqA==
MIME-Version: 1.0
Received: by 10.60.171.201 with SMTP id aw9mr29537354oec.126.1357293470540; Fri, 04 Jan 2013 01:57:50 -0800 (PST)
Received: by 10.60.116.129 with HTTP; Fri, 4 Jan 2013 01:57:50 -0800 (PST)
In-Reply-To: <50E68CB5.4010107@gmail.com>
References: <7ED55FF1-3E1A-4DF7-918E-07790517B848@softarmor.com> <50E68CB5.4010107@gmail.com>
Date: Fri, 4 Jan 2013 09:57:50 +0000
Message-ID: <CAKHUCzyxeCRmYMSeLXDy9WOxte3w-JzdiXc8q1M4x1dXDybPWw@mail.gmail.com>
Subject: Re: I'm struggling with 2219 language again
From: Dave Cridland <dave@cridland.net>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
X-Gm-Message-State: ALoCoQlZyzU47mQRumasZJLlVLb7Amt+wf2qMAkNqoA8u+acY7Ax+D0n9khUYCs5ddZJzc4iM4Kj
Cc: ietf@ietf.org, Dean Willis <dean.willis@softarmor.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 04 Jan 2013 09:57:56 -0000

On Fri, Jan 4, 2013 at 8:03 AM, Brian E Carpenter
<brian.e.carpenter@gmail.com> wrote:
>
> This Gen-ART reviewer believes that words like "must" have well defined meanings
> in the English language, so shouting is not needed at every use. There are
> standards track documents that don't use RFC 2119 at all, and I am not only
> referring to RFC 791.
>

IMAP's CONDSTORE is a relatively recent example (authored by Pete
Resnick). It got all the way to WGLC before anyone noticed, as I
recall. (Possibly even through, I can't recall).

>
> I think the upper case keywords should be used only when necessary to clarify
> points of potential non-interoperability or insecurity. I'm quite sure that
> I've broken that recommendation quite often, and it will always remain
> a judgment call. However, inserting a MUST in every sentence that describes
> behaviour is surely going too far. I guess the test is whether a reasonably
> careful reader might interpret a sentence incorrectly while writing code;
> and if so, would a normative keyword help?


RFC 2119 language is not a stick to beat an implementor with, but a
signpost to highlight or clarify important cases. If the signpost is
used too often, the temptation is to mentally downgrade the language
when reading. It's often not needed, and only serves to make the
language look "more RFC", or just saves an author from considering how
to best describe the protocol. Neither is good.

But in any case, a Gen Art reviewers comments hold no more weight than
any others, and if your personal style, like mine, leans toward
minimizing the use of RFC 2119 language and putting the effort into
general clarity and readability, then I think you should ignore the
proposed solution and treat the comments as a suggestion that the
areas might benefit from more clarity of intent.

Dave.

From lberger@labn.net  Fri Jan  4 05:23:40 2013
Return-Path: <lberger@labn.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 008D921F8906 for <ietf@ietfa.amsl.com>; Fri,  4 Jan 2013 05:23:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.038
X-Spam-Level: 
X-Spam-Status: No, score=-101.038 tagged_above=-999 required=5 tests=[AWL=1.562, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 uZ8o1nkJjJY0 for <ietf@ietfa.amsl.com>; Fri,  4 Jan 2013 05:23:39 -0800 (PST)
Received: from oproxy11-pub.bluehost.com (oproxy11-pub.bluehost.com [173.254.64.10]) by ietfa.amsl.com (Postfix) with SMTP id 4932C21F8903 for <ietf@ietf.org>; Fri,  4 Jan 2013 05:23:39 -0800 (PST)
Received: (qmail 2787 invoked by uid 0); 4 Jan 2013 13:23:15 -0000
Received: from unknown (HELO box313.bluehost.com) (69.89.31.113) by oproxy11.bluehost.com with SMTP; 4 Jan 2013 13:23:15 -0000
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=labn.net; s=default;  h=Content-Transfer-Encoding:Content-Type:In-Reply-To:References:Subject:CC:To:MIME-Version:From:Date:Message-ID; bh=3STEYuut4O/QhNSi2lj57N8nYRVqYoa6yOLzKDPh260=;  b=CL7tYXftd2Qo3upPgZ7dRwAZH1xIA1ghGNwef47/tvLUShvUBSJiiWJqHExoLx/nhOi9ogsbVlF4F+j2jk3GBIBWfkCqX5J1J869TU6Skkc4x/SRFd6kn7o74E/+PNSk;
Received: from box313.bluehost.com ([69.89.31.113]:45916 helo=[127.0.0.1]) by box313.bluehost.com with esmtpa (Exim 4.76) (envelope-from <lberger@labn.net>) id 1Tr7Ex-00055T-0I; Fri, 04 Jan 2013 06:23:15 -0700
Message-ID: <50E6D7CB.6050905@labn.net>
Date: Fri, 04 Jan 2013 08:23:23 -0500
From: Lou Berger <lberger@labn.net>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: Dean Willis <dean.willis@softarmor.com>
Subject: Re: I'm struggling with 2219 language again
References: <7ED55FF1-3E1A-4DF7-918E-07790517B848@softarmor.com>
In-Reply-To: <7ED55FF1-3E1A-4DF7-918E-07790517B848@softarmor.com>
X-Enigmail-Version: 1.4.6
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Identified-User: {1038:box313.bluehost.com:labnmobi:labn.net} {sentby:smtp auth 69.89.31.113 authed with lberger@labn.net}
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 04 Jan 2013 13:23:40 -0000

On 1/4/2013 12:15 AM, Dean Willis wrote:
...
> Are we deliberately evolving our language to use RFC 2119 terms as
> the principle verbs  of a formal specification language?
...

My view on this has evolved over time.  I used to follow the practice of
using 2219 language only for emphasis.  Over time, primarily motivated
by reviewers comments and reader questions, I've migrated to the
position that 2119 language should be used whenever and wherever a point
of conformance is being made.  While this may be a bit of an extreme
position, it ensures that authors, reviewers, readers, implementors,
etc. are in sync as to what is expected from an interoperable
implementation that conforms to a standard.  I think the importance of
such unambiguity has increased over time as the number of implementors
and non-native English speakers in our community have increased.

I also think it's important to follow section 6 of 2119, i.e., if it's
not a point of interoperability or harmful behavior, there's no need to
use 2119 conformance language.

So, my view is now:

a) lower case usage of 2119 key words *in RFCs* means the normal English
meaning of such words, but does not place any requirement on
implementations, i.e., is purely informative text.

b) upper case usage of 2119 key words *in RFCs*, as stated in [RFC2119],
places "requirements in the specification", i.e., is conformance
language with which an implementation must follow to ensure
interoperability (or harm).  (And does not = shouting as would be the
case in other contexts).

I take this view when writing and reviewing PS drafts...

Lou

From rbarnes@bbn.com  Fri Jan  4 06:47:33 2013
Return-Path: <rbarnes@bbn.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0613721F8871 for <ietf@ietfa.amsl.com>; Fri,  4 Jan 2013 06:47:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 eJddym7ze3Vz for <ietf@ietfa.amsl.com>; Fri,  4 Jan 2013 06:47:32 -0800 (PST)
Received: from smtp.bbn.com (smtp.bbn.com [128.33.1.81]) by ietfa.amsl.com (Postfix) with ESMTP id 64FB221F8689 for <ietf@ietf.org>; Fri,  4 Jan 2013 06:47:28 -0800 (PST)
Received: from ros-dhcp192-1-51-63.bbn.com ([192.1.51.63]:63472) by smtp.bbn.com with esmtps (TLSv1:AES128-SHA:128) (Exim 4.77 (FreeBSD)) (envelope-from <rbarnes@bbn.com>) id 1Tr8YP-0000vy-Jb; Fri, 04 Jan 2013 09:47:25 -0500
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Subject: Re: travel guide for the next IETF...
From: Richard Barnes <rbarnes@bbn.com>
In-Reply-To: <alpine.OSX.2.01.1301032354480.80268@173-11-110-132-sfba.hfc.comcastbusiness.net>
Date: Fri, 4 Jan 2013 09:47:24 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <21112D4A-CA16-4ACD-BD38-2194A992004B@bbn.com>
References: <20130102231451.24327.qmail@joyce.lan> <alpine.OSX.2.01.1301032354480.80268@173-11-110-132-sfba.hfc.comcastbusiness.net>
To: Ole Jacobsen <ole@cisco.com>
X-Mailer: Apple Mail (2.1499)
Cc: John Levine <johnl@taugh.com>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 04 Jan 2013 14:47:33 -0000

It gets worse if you head west to the Tampa bay...

=
<http://www.tampabay.com/news/publicsafety/crime/man-shot-at-st-pete-pizza=
-joint-had-been-complaining-about-slow-service/1266589>


On Jan 4, 2013, at 2:55 AM, Ole Jacobsen <ole@cisco.com> wrote:

>=20
> You have been warned.
>=20
> =
http://news.yahoo.com/video/request-ketchup-philly-cheesesteak-leads-00120=
4299.html
>=20
>=20
> Ole J. Jacobsen
> Editor and Publisher,  The Internet Protocol Journal
> Cisco Systems
> Tel: +1 408-527-8972   Mobile: +1 415-370-4628
> E-mail: ole@cisco.com  URL: http://www.cisco.com/ipj
> Skype: organdemo
>=20
>=20


From nabil.n.bitar@verizon.com  Fri Jan  4 08:17:47 2013
Return-Path: <nabil.n.bitar@verizon.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0509D21F874F; Fri,  4 Jan 2013 08:17:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.598
X-Spam-Level: 
X-Spam-Status: No, score=-3.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
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 SFsF4T+BnBzg; Fri,  4 Jan 2013 08:17:45 -0800 (PST)
Received: from fldsmtpe02.verizon.com (fldsmtpe02.verizon.com [140.108.26.141]) by ietfa.amsl.com (Postfix) with ESMTP id 86D4221F874B; Fri,  4 Jan 2013 08:17:44 -0800 (PST)
X-IronPort-Anti-Spam-Filtered: false
Received: from unknown (HELO fldsmtpi02.verizon.com) ([166.68.71.144]) by fldsmtpe02.verizon.com with ESMTP; 04 Jan 2013 16:17:43 +0000
From: "Bitar, Nabil N" <nabil.n.bitar@verizon.com>
To: "Black, David" <david.black@emc.com>, "dinmohan@hotmail.com" <dinmohan@hotmail.com>, "Bitar, Nabil N" <nabil.n.bitar@verizon.com>, "sajassi@cisco.com" <sajassi@cisco.com>, "gen-art@ietf.org" <gen-art@ietf.org>
X-IronPort-AV: E=Sophos;i="4.84,411,1355097600";  d="scan'208,217";a="390238357"
Received: from fldp1lumxc7hb02.verizon.com (HELO FLDP1LUMXC7HB02.us.one.verizon.com) ([166.68.75.85]) by fldsmtpi02.verizon.com with ESMTP; 04 Jan 2013 16:17:43 +0000
Received: from fldp1lumxc7v63.us.one.verizon.com ([166.68.45.45]) by FLDP1LUMXC7HB02.us.one.verizon.com ([166.68.75.85]) with mapi; Fri, 4 Jan 2013 11:17:42 -0500
Date: Fri, 4 Jan 2013 11:17:28 -0500
Subject: Re: Gen-ART review of draft-ietf-pwe3-mpls-eth-oam-iwk-06
Thread-Topic: Gen-ART review of draft-ietf-pwe3-mpls-eth-oam-iwk-06
Thread-Index: Ac3qlwXZXlAGSIXyRDGAHQx69rTk+A==
Message-ID: <CD0C3AE6.6E673%nabil.n.bitar@verizon.com>
In-Reply-To: <CD08F2D5.6DC40%nabil.n.bitar@verizon.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.2.3.120616
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_CD0C3AE66E673nabilnbitarverizoncom_"
MIME-Version: 1.0
Cc: "pwe3@ietf.org" <pwe3@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 04 Jan 2013 16:17:47 -0000

--_000_CD0C3AE66E673nabilnbitarverizoncom_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi Dave,
Related to abbreviations comment below and to be clearer, I renamed the ori=
ginal terminology section to "Abbreviations and Terminology". I also create=
d a subsection called "Abbreviations" ,and "Terminology" became the second =
subsection.  Here iis how the edits look

3. Abbreviations and Terminology
3.1. Abbreviations

        AIS   Alarm Indication Signal

   AC    Attachment Circuit

   BFD   Bidirectional Forwarding Detection

   CC    Continuity Check

   CCM   Continuity Check Message

   CE    Customer Equipment

   CV    Connectivity Verification

   E-LMI Ethernet Local Management Interface

   EVC   Ethernet Virtual Circuit

   LDP   Label Distribution Protocol

   LoS   Loss of Signal

   MA    Maintenance Association

   MD    Maintenance Domain

   ME    Maintenance Entity

   MEG   Maintenance Entity Group

   MEP   Maintenance End Point

   MIP   Maintenance End Point

   MPLS  Multiprotocol Label Switching

   MS-PW Multi-Segment Pseudowire

   NS    Native Service

   OAM   Operations, Administration, and Maintenance

   PE    Provider Edge

   PSN   Packet Switched Network

   PW    Pseudowire

   RDI   Remote Defect Indication for Continuity Check Message

   RDI   Reverse Defect Indication

   S-PE  Switching Provider Edge

   TLV   Type Length Value

   T-PE  Terminating Provider Edge

3.2. Terminology
This document uses the following terms with corresponding definitions:
- MD Level:  Maintenance Domain (MD) Level which identifies a value in the =
range of 0-7 associated with Ethernet OAM frame. MD Level identifies the sp=
an of the Ethernet OAM frame.
 - MEP:    Maintenance End Point is responsible for origination and termina=
tion of OAM frames for a given MEG.
 - MIP:      Maintenance Intermediate Point is located between peer MEPs an=
d can process OAM frames but does not initiate or terminate them.
Further, this document also uses the terminology and conventions used in [R=
FC6310].


Thanks,
Nabil

From: <Bitar>, Nabil N <nabil.n.bitar@one.verizon.com<mailto:nabil.n.bitar@=
one.verizon.com>>
Date: Wednesday, January 2, 2013 11:28 AM
To: "Black, David" <david.black@emc.com<mailto:david.black@emc.com>>, "dinm=
ohan@hotmail.com<mailto:dinmohan@hotmail.com>" <dinmohan@hotmail.com<mailto=
:dinmohan@hotmail.com>>, "Bitar, Nabil N" <nabil.n.bitar@one.verizon.com<ma=
ilto:nabil.n.bitar@one.verizon.com>>, Sagessi <sajassi@cisco.com<mailto:saj=
assi@cisco.com>>, "gen-art@ietf.org<mailto:gen-art@ietf.org>" <gen-art@ietf=
.org<mailto:gen-art@ietf.org>>
Cc: "pwe3@ietf.org<mailto:pwe3@ietf.org>" <pwe3@ietf.org<mailto:pwe3@ietf.o=
rg>>, "ietf@ietf.org<mailto:ietf@ietf.org>" <ietf@ietf.org<mailto:ietf@ietf=
.org>>
Subject: Re: Gen-ART review of draft-ietf-pwe3-mpls-eth-oam-iwk-06

Hi Dave,
Sorry for a late reply addressing your comments. Please, see inline.

Thanks,
Nabil

From: "Black, David" <david.black@emc.com<mailto:david.black@emc.com>>
Date: Monday, August 20, 2012 8:57 PM
To: "dinmohan@hotmail.com<mailto:dinmohan@hotmail.com>" <dinmohan@hotmail.c=
om<mailto:dinmohan@hotmail.com>>, "Bitar, Nabil N" <nabil.n.bitar@one.veriz=
on.com<mailto:nabil.n.bitar@one.verizon.com>>, Sagessi <sajassi@cisco.com<m=
ailto:sajassi@cisco.com>>, "gen-art@ietf.org<mailto:gen-art@ietf.org>" <gen=
-art@ietf.org<mailto:gen-art@ietf.org>>
Cc: "Black, David" <david.black@emc.com<mailto:david.black@emc.com>>, "pwe3=
@ietf.org<mailto:pwe3@ietf.org>" <pwe3@ietf.org<mailto:pwe3@ietf.org>>, "ie=
tf@ietf.org<mailto:ietf@ietf.org>" <ietf@ietf.org<mailto:ietf@ietf.org>>
Subject: Gen-ART review of draft-ietf-pwe3-mpls-eth-oam-iwk-06

I am the assigned Gen-ART reviewer for this draft. For background on Gen-AR=
T, please
see the FAQ at <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

Please resolve these comments along with any other Last Call comments you m=
ay receive.

Document: draft-ietf-pwe3-mpls-eth-oam-iwk-06
Reviewer: David L. Black
Review Date: August 20, 2012
IETF LC End Date: August 20, 2012

Summary:
This draft is basically ready for publication, but has nits that
should be fixed before publication.

<NB> Thanks.



This draft covers defect behavior for Ethernet pseudowires,

including defect state mapping and PE defect reporting behavior.

The draft is generally in good shape.  I found a few minor nits.



1) The draft uses a lot of acronyms - while each acronym appears to

be expanded on first use, an additional section near the start of the

draft listing all of them would be helpful.

<NB> Done.



2) There's a typo in the first paragraph of section 2:



     covers the following Ethernet OAM (Opertaions, Administration and



Opertaions -> Operations.

<NB> Thanks. Done.



3) The following normative reference is incomplete - please add additional

information that will enable a reader to locate the referenced document:



     [MEF16] "Ethernet Local Management Interface", MEF16, January 2006.

[MEF16] "Ethernet Local Management Interface", Metro Ethernet Forum Technic=
al Specification MEF16, January 2006.

<NB> changed it to :



4) idnits 2.12.13 did not like the pagination:



  =3D=3D The page length should not exceed 58 lines per page, but there was=
 22
     longer pages, the longest (page 1) being 61 lines

<NB> That will be fixed.

Thanks,
--David
----------------------------------------------------
David L. Black, Distinguished Engineer
EMC Corporation, 176 South St., Hopkinton, MA  01748
+1 (508) 293-7953             FAX: +1 (508) 293-7786
david.black@emc.com<mailto:david.black@emc.com>        Mobile: +1 (978) 394=
-7754
----------------------------------------------------

--_000_CD0C3AE66E673nabilnbitarverizoncom_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html><head><meta name=3D"Title" content=3D""><meta name=3D"Keywords" conte=
nt=3D""><meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Du=
tf-8"><meta name=3D"ProgId" content=3D"Word.Document"><meta name=3D"Generat=
or" content=3D"Microsoft Word 14"><meta name=3D"Originator" content=3D"Micr=
osoft Word 14"><link rel=3D"File-List" href=3D"file://localhost/Users/admin=
/Library/Caches/TemporaryItems/msoclip/0/clip_filelist.xml"><!--[if gte mso=
 9]><xml>
 <o:DocumentProperties>
  <o:Revision>0</o:Revision>
  <o:TotalTime>0</o:TotalTime>
  <o:Pages>1</o:Pages>
  <o:Words>231</o:Words>
  <o:Characters>1322</o:Characters>
  <o:Company>Verizon</o:Company>
  <o:Lines>11</o:Lines>
  <o:Paragraphs>3</o:Paragraphs>
  <o:CharactersWithSpaces>1550</o:CharactersWithSpaces>
  <o:Version>14.0</o:Version>
 </o:DocumentProperties>
 <o:OfficeDocumentSettings>
  <o:RelyOnVML/>
  <o:AllowPNG/>
 </o:OfficeDocumentSettings>
</xml><![endif]--><link rel=3D"themeData" href=3D"file://localhost/Users/ad=
min/Library/Caches/TemporaryItems/msoclip/0/clip_themedata.xml"><!--[if gte=
 mso 9]><xml>
 <w:WordDocument>
  <w:View>Normal</w:View>
  <w:Zoom>0</w:Zoom>
  <w:TrackMoves/>
  <w:TrackFormatting/>
  <w:PunctuationKerning/>
  <w:ValidateAgainstSchemas/>
  <w:SaveIfXMLInvalid>false</w:SaveIfXMLInvalid>
  <w:IgnoreMixedContent>false</w:IgnoreMixedContent>
  <w:AlwaysShowPlaceholderText>false</w:AlwaysShowPlaceholderText>
  <w:DoNotPromoteQF/>
  <w:LidThemeOther>EN-US</w:LidThemeOther>
  <w:LidThemeAsian>JA</w:LidThemeAsian>
  <w:LidThemeComplexScript>X-NONE</w:LidThemeComplexScript>
  <w:Compatibility>
   <w:BreakWrappedTables/>
   <w:SnapToGridInCell/>
   <w:WrapTextWithPunct/>
   <w:UseAsianBreakRules/>
   <w:DontGrowAutofit/>
   <w:SplitPgBreakAndParaMark/>
   <w:EnableOpenTypeKerning/>
   <w:DontFlipMirrorIndents/>
   <w:OverrideTableStyleHps/>
  </w:Compatibility>
  <m:mathPr>
   <m:mathFont m:val=3D"Cambria Math"/>
   <m:brkBin m:val=3D"before"/>
   <m:brkBinSub m:val=3D"&#45;-"/>
   <m:smallFrac m:val=3D"off"/>
   <m:dispDef/>
   <m:lMargin m:val=3D"0"/>
   <m:rMargin m:val=3D"0"/>
   <m:defJc m:val=3D"centerGroup"/>
   <m:wrapIndent m:val=3D"1440"/>
   <m:intLim m:val=3D"subSup"/>
   <m:naryLim m:val=3D"undOvr"/>
  </m:mathPr></w:WordDocument>
</xml><![endif]--><!--[if gte mso 9]><xml>
 <w:LatentStyles DefLockedState=3D"false" DefUnhideWhenUsed=3D"true"
  DefSemiHidden=3D"true" DefQFormat=3D"false" DefPriority=3D"99"
  LatentStyleCount=3D"276">
  <w:LsdException Locked=3D"false" Priority=3D"0" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Normal"/>
  <w:LsdException Locked=3D"false" Priority=3D"0" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"heading 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"0" QFormat=3D"true" Name=3D"=
heading 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"0" QFormat=3D"true" Name=3D"=
heading 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"0" QFormat=3D"true" Name=3D"=
heading 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"0" QFormat=3D"true" Name=3D"=
heading 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"0" QFormat=3D"true" Name=3D"=
heading 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"0" QFormat=3D"true" Name=3D"=
heading 7"/>
  <w:LsdException Locked=3D"false" Priority=3D"0" QFormat=3D"true" Name=3D"=
heading 8"/>
  <w:LsdException Locked=3D"false" Priority=3D"0" QFormat=3D"true" Name=3D"=
heading 9"/>
  <w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 7"/>
  <w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 8"/>
  <w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 9"/>
  <w:LsdException Locked=3D"false" Priority=3D"35" QFormat=3D"true" Name=3D=
"caption"/>
  <w:LsdException Locked=3D"false" Priority=3D"10" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Title"/>
  <w:LsdException Locked=3D"false" Priority=3D"1" Name=3D"Default Paragraph=
 Font"/>
  <w:LsdException Locked=3D"false" Priority=3D"11" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Subtitle"/>
  <w:LsdException Locked=3D"false" Priority=3D"22" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Strong"/>
  <w:LsdException Locked=3D"false" Priority=3D"20" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Emphasis"/>
  <w:LsdException Locked=3D"false" Priority=3D"59" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Table Grid"/>
  <w:LsdException Locked=3D"false" UnhideWhenUsed=3D"false" Name=3D"Placeho=
lder Text"/>
  <w:LsdException Locked=3D"false" Priority=3D"1" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"No Spacing"/>
  <w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light Shading"/>
  <w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light List"/>
  <w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light Grid"/>
  <w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium List 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium List 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Dark List"/>
  <w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful Shading"/>
  <w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful List"/>
  <w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful Grid"/>
  <w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light List Accent 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 1"/>
  <w:LsdException Locked=3D"false" UnhideWhenUsed=3D"false" Name=3D"Revisio=
n"/>
  <w:LsdException Locked=3D"false" Priority=3D"34" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"List Paragraph"/>
  <w:LsdException Locked=3D"false" Priority=3D"29" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Quote"/>
  <w:LsdException Locked=3D"false" Priority=3D"30" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Intense Quote"/>
  <w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light List Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light List Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light List Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light List Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light List Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"19" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Subtle Emphasis"/>
  <w:LsdException Locked=3D"false" Priority=3D"21" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Intense Emphasis"/>
  <w:LsdException Locked=3D"false" Priority=3D"31" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Subtle Reference"/>
  <w:LsdException Locked=3D"false" Priority=3D"32" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Intense Reference"/>
  <w:LsdException Locked=3D"false" Priority=3D"33" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Book Title"/>
  <w:LsdException Locked=3D"false" Priority=3D"37" Name=3D"Bibliography"/>
  <w:LsdException Locked=3D"false" Priority=3D"39" QFormat=3D"true" Name=3D=
"TOC Heading"/>
 </w:LatentStyles>
</xml><![endif]--><style>
<!--
 /* Font Definitions */
@font-face
	{font-family:Arial;
	panose-1:2 11 6 4 2 2 2 2 2 4;
	mso-font-charset:0;
	mso-generic-font-family:auto;
	mso-font-pitch:variable;
	mso-font-signature:-536859905 -1073711037 9 0 511 0;}
@font-face
	{font-family:"Courier New";
	panose-1:2 7 3 9 2 2 5 2 4 4;
	mso-font-charset:0;
	mso-generic-font-family:auto;
	mso-font-pitch:variable;
	mso-font-signature:-536859905 -1073711037 9 0 511 0;}
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;
	mso-font-charset:0;
	mso-generic-font-family:auto;
	mso-font-pitch:variable;
	mso-font-signature:-536870145 1107305727 0 0 415 0;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;
	mso-font-charset:0;
	mso-generic-font-family:auto;
	mso-font-pitch:variable;
	mso-font-signature:-520092929 1073786111 9 0 415 0;}
@font-face
	{font-family:Batang;
	mso-font-alt:??;
	mso-font-charset:129;
	mso-generic-font-family:roman;
	mso-font-pitch:variable;
	mso-font-signature:-1342176593 1775729915 48 0 524447 0;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;
	mso-font-charset:0;
	mso-generic-font-family:auto;
	mso-font-pitch:variable;
	mso-font-signature:-520092929 1073806591 9 0 415 0;}
 /* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{mso-style-unhide:no;
	mso-style-qformat:yes;
	mso-style-parent:"";
	margin-top:0in;
	margin-right:0in;
	margin-bottom:12.0pt;
	margin-left:.3in;
	line-height:12.0pt;
	mso-line-height-rule:exactly;
	mso-pagination:widow-orphan;
	tab-stops:.3in .6in .9in 1.2in 1.5in 1.8in 2.1in 2.4in 2.7in 3.0in 3.3in 3=
.6in 3.9in 4.2in 4.5in 4.8in 5.1in 5.4in 5.7in 6.0in 6.3in 6.6in 6.9in;
	font-size:12.0pt;
	font-family:"Courier New";
	mso-fareast-font-family:Batang;}
h1
	{mso-style-unhide:no;
	mso-style-qformat:yes;
	mso-style-link:"Heading 1 Char";
	mso-style-next:Normal;
	margin-top:0in;
	margin-right:0in;
	margin-bottom:12.0pt;
	margin-left:22.5pt;
	text-indent:-22.5pt;
	line-height:12.0pt;
	mso-line-height-rule:exactly;
	mso-pagination:widow-orphan;
	page-break-after:avoid;
	mso-outline-level:1;
	mso-list:l0 level1 lfo1;
	tab-stops:.3in .6in .9in 1.2in 1.5in 1.8in 2.1in 2.4in 2.7in 3.0in 3.3in 3=
.6in 3.9in 4.2in 4.5in 4.8in 5.1in 5.4in 5.7in 6.0in 6.3in 6.6in 6.9in;
	font-size:12.0pt;
	font-family:"Courier New";
	mso-fareast-font-family:Batang;
	mso-font-kerning:0pt;
	font-weight:normal;}
h2
	{mso-style-unhide:no;
	mso-style-qformat:yes;
	mso-style-link:"Heading 2 Char";
	mso-style-next:Normal;
	margin-top:0in;
	margin-right:0in;
	margin-bottom:12.0pt;
	margin-left:.3in;
	text-indent:-.3in;
	line-height:12.0pt;
	mso-line-height-rule:exactly;
	mso-pagination:widow-orphan;
	page-break-after:avoid;
	mso-outline-level:2;
	mso-list:l0 level2 lfo1;
	tab-stops:.3in .6in .9in 1.2in 1.5in 1.8in 2.1in 2.4in 2.7in 3.0in 3.3in 3=
.6in 3.9in 4.2in 4.5in 4.8in 5.1in 5.4in 5.7in 6.0in 6.3in 6.6in 6.9in;
	font-size:12.0pt;
	mso-bidi-font-size:14.0pt;
	font-family:"Courier New";
	mso-fareast-font-family:Batang;
	mso-bidi-font-family:Arial;
	font-weight:normal;
	mso-bidi-font-weight:bold;
	mso-bidi-font-style:italic;}
h3
	{mso-style-unhide:no;
	mso-style-qformat:yes;
	mso-style-link:"Heading 3 Char";
	mso-style-next:Normal;
	margin-top:0in;
	margin-right:0in;
	margin-bottom:12.0pt;
	margin-left:.3in;
	text-indent:-.3in;
	line-height:12.0pt;
	mso-line-height-rule:exactly;
	mso-pagination:widow-orphan;
	page-break-after:avoid;
	mso-outline-level:3;
	mso-list:l0 level3 lfo1;
	tab-stops:.3in .6in .9in 1.2in 1.5in 1.8in 2.1in 2.4in 2.7in 3.0in 3.3in 3=
.6in 3.9in 4.2in 4.5in 4.8in 5.1in 5.4in 5.7in 6.0in 6.3in 6.6in 6.9in;
	font-size:12.0pt;
	mso-bidi-font-size:13.0pt;
	font-family:"Courier New";
	mso-fareast-font-family:Batang;
	mso-bidi-font-family:Arial;
	font-weight:normal;
	mso-bidi-font-weight:bold;}
h4
	{mso-style-unhide:no;
	mso-style-qformat:yes;
	mso-style-link:"Heading 4 Char";
	mso-style-next:Normal;
	margin-top:0in;
	margin-right:0in;
	margin-bottom:12.0pt;
	margin-left:.3in;
	text-indent:-.3in;
	line-height:12.0pt;
	mso-line-height-rule:exactly;
	mso-pagination:widow-orphan;
	page-break-after:avoid;
	mso-outline-level:4;
	mso-list:l0 level4 lfo1;
	tab-stops:.3in .6in .9in 1.2in 1.5in 1.8in 2.1in 2.4in 2.7in 3.0in 3.3in 3=
.6in 3.9in 4.2in 4.5in 4.8in 5.1in 5.4in 5.7in 6.0in 6.3in 6.6in 6.9in;
	font-size:12.0pt;
	mso-bidi-font-size:14.0pt;
	font-family:"Courier New";
	mso-fareast-font-family:Batang;
	font-weight:normal;
	mso-bidi-font-weight:bold;}
h5
	{mso-style-unhide:no;
	mso-style-qformat:yes;
	mso-style-link:"Heading 5 Char";
	mso-style-next:Normal;
	margin-top:0in;
	margin-right:0in;
	margin-bottom:12.0pt;
	margin-left:.3in;
	text-indent:-.3in;
	line-height:12.0pt;
	mso-line-height-rule:exactly;
	mso-pagination:widow-orphan;
	page-break-after:avoid;
	mso-outline-level:5;
	mso-list:l0 level5 lfo1;
	tab-stops:.3in .6in .9in 1.2in 1.5in 1.8in 2.1in 2.4in 2.7in 3.0in 3.3in 3=
.6in 3.9in 4.2in 4.5in 4.8in 5.1in 5.4in 5.7in 6.0in 6.3in 6.6in 6.9in;
	font-size:12.0pt;
	mso-bidi-font-size:13.0pt;
	font-family:"Courier New";
	mso-fareast-font-family:Batang;
	font-weight:normal;
	mso-bidi-font-weight:bold;
	mso-bidi-font-style:italic;}
h6
	{mso-style-unhide:no;
	mso-style-qformat:yes;
	mso-style-link:"Heading 6 Char";
	mso-style-next:Normal;
	margin-top:0in;
	margin-right:0in;
	margin-bottom:12.0pt;
	margin-left:.3in;
	text-indent:-.3in;
	line-height:12.0pt;
	mso-line-height-rule:exactly;
	mso-pagination:widow-orphan;
	page-break-after:avoid;
	mso-outline-level:6;
	mso-list:l0 level6 lfo1;
	tab-stops:.3in .6in .9in 1.2in 1.5in 1.8in 2.1in 2.4in 2.7in 3.0in 3.3in 3=
.6in 3.9in 4.2in 4.5in 4.8in 5.1in 5.4in 5.7in 6.0in 6.3in 6.6in 6.9in;
	font-size:12.0pt;
	mso-bidi-font-size:11.0pt;
	font-family:"Courier New";
	mso-fareast-font-family:Batang;
	font-weight:normal;
	mso-bidi-font-weight:bold;}
p.MsoHeading7, li.MsoHeading7, div.MsoHeading7
	{mso-style-unhide:no;
	mso-style-qformat:yes;
	mso-style-link:"Heading 7 Char";
	mso-style-next:Normal;
	margin-top:0in;
	margin-right:0in;
	margin-bottom:12.0pt;
	margin-left:.3in;
	text-indent:-.3in;
	line-height:12.0pt;
	mso-line-height-rule:exactly;
	mso-pagination:widow-orphan;
	page-break-after:avoid;
	mso-outline-level:7;
	mso-list:l0 level7 lfo1;
	tab-stops:.3in .6in .9in 1.2in 1.5in 1.8in 2.1in 2.4in 2.7in 3.0in 3.3in 3=
.6in 3.9in 4.2in 4.5in 4.8in 5.1in 5.4in 5.7in 6.0in 6.3in 6.6in 6.9in;
	font-size:12.0pt;
	font-family:"Courier New";
	mso-fareast-font-family:Batang;}
p.MsoHeading8, li.MsoHeading8, div.MsoHeading8
	{mso-style-unhide:no;
	mso-style-qformat:yes;
	mso-style-link:"Heading 8 Char";
	mso-style-next:Normal;
	margin-top:0in;
	margin-right:0in;
	margin-bottom:12.0pt;
	margin-left:.3in;
	text-indent:-.3in;
	line-height:12.0pt;
	mso-line-height-rule:exactly;
	mso-pagination:widow-orphan;
	page-break-after:avoid;
	mso-outline-level:8;
	mso-list:l0 level8 lfo1;
	tab-stops:.3in .6in .9in 1.2in 1.5in 1.8in 2.1in 2.4in 2.7in 3.0in 3.3in 3=
.6in 3.9in 4.2in 4.5in 4.8in 5.1in 5.4in 5.7in 6.0in 6.3in 6.6in 6.9in;
	font-size:12.0pt;
	font-family:"Courier New";
	mso-fareast-font-family:Batang;
	mso-bidi-font-style:italic;}
p.MsoHeading9, li.MsoHeading9, div.MsoHeading9
	{mso-style-unhide:no;
	mso-style-qformat:yes;
	mso-style-link:"Heading 9 Char";
	mso-style-next:Normal;
	margin-top:0in;
	margin-right:0in;
	margin-bottom:12.0pt;
	margin-left:.3in;
	text-indent:-.3in;
	line-height:12.0pt;
	mso-line-height-rule:exactly;
	mso-pagination:widow-orphan;
	page-break-after:avoid;
	mso-outline-level:9;
	mso-list:l0 level9 lfo1;
	tab-stops:.3in .6in .9in 1.2in 1.5in 1.8in 2.1in 2.4in 2.7in 3.0in 3.3in 3=
.6in 3.9in 4.2in 4.5in 4.8in 5.1in 5.4in 5.7in 6.0in 6.3in 6.6in 6.9in;
	font-size:12.0pt;
	mso-bidi-font-size:11.0pt;
	font-family:"Courier New";
	mso-fareast-font-family:Batang;
	mso-bidi-font-family:Arial;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:10.5pt;
	font-family:Consolas;
	mso-fareast-font-family:Calibri;
	mso-fareast-theme-font:minor-latin;
	mso-bidi-font-family:"Times New Roman";
	mso-bidi-theme-font:minor-bidi;}
span.Heading1Char
	{mso-style-name:"Heading 1 Char";
	mso-style-unhide:no;
	mso-style-locked:yes;
	mso-style-link:"Heading 1";
	font-family:"Courier New";
	mso-ascii-font-family:"Courier New";
	mso-fareast-font-family:Batang;
	mso-hansi-font-family:"Courier New";
	mso-bidi-font-family:"Courier New";}
span.Heading2Char
	{mso-style-name:"Heading 2 Char";
	mso-style-unhide:no;
	mso-style-locked:yes;
	mso-style-link:"Heading 2";
	mso-bidi-font-size:14.0pt;
	font-family:"Courier New";
	mso-ascii-font-family:"Courier New";
	mso-fareast-font-family:Batang;
	mso-hansi-font-family:"Courier New";
	mso-bidi-font-family:Arial;
	mso-bidi-font-weight:bold;
	mso-bidi-font-style:italic;}
span.Heading3Char
	{mso-style-name:"Heading 3 Char";
	mso-style-unhide:no;
	mso-style-locked:yes;
	mso-style-link:"Heading 3";
	mso-bidi-font-size:13.0pt;
	font-family:"Courier New";
	mso-ascii-font-family:"Courier New";
	mso-fareast-font-family:Batang;
	mso-hansi-font-family:"Courier New";
	mso-bidi-font-family:Arial;
	mso-bidi-font-weight:bold;}
span.Heading4Char
	{mso-style-name:"Heading 4 Char";
	mso-style-unhide:no;
	mso-style-locked:yes;
	mso-style-link:"Heading 4";
	mso-bidi-font-size:14.0pt;
	font-family:"Courier New";
	mso-ascii-font-family:"Courier New";
	mso-fareast-font-family:Batang;
	mso-hansi-font-family:"Courier New";
	mso-bidi-font-family:"Courier New";
	mso-bidi-font-weight:bold;}
span.Heading5Char
	{mso-style-name:"Heading 5 Char";
	mso-style-unhide:no;
	mso-style-locked:yes;
	mso-style-link:"Heading 5";
	mso-bidi-font-size:13.0pt;
	font-family:"Courier New";
	mso-ascii-font-family:"Courier New";
	mso-fareast-font-family:Batang;
	mso-hansi-font-family:"Courier New";
	mso-bidi-font-family:"Courier New";
	mso-bidi-font-weight:bold;
	mso-bidi-font-style:italic;}
span.Heading6Char
	{mso-style-name:"Heading 6 Char";
	mso-style-unhide:no;
	mso-style-locked:yes;
	mso-style-link:"Heading 6";
	mso-bidi-font-size:11.0pt;
	font-family:"Courier New";
	mso-ascii-font-family:"Courier New";
	mso-fareast-font-family:Batang;
	mso-hansi-font-family:"Courier New";
	mso-bidi-font-family:"Courier New";
	mso-bidi-font-weight:bold;}
span.Heading7Char
	{mso-style-name:"Heading 7 Char";
	mso-style-unhide:no;
	mso-style-locked:yes;
	mso-style-link:"Heading 7";
	font-family:"Courier New";
	mso-ascii-font-family:"Courier New";
	mso-fareast-font-family:Batang;
	mso-hansi-font-family:"Courier New";
	mso-bidi-font-family:"Courier New";}
span.Heading8Char
	{mso-style-name:"Heading 8 Char";
	mso-style-unhide:no;
	mso-style-locked:yes;
	mso-style-link:"Heading 8";
	font-family:"Courier New";
	mso-ascii-font-family:"Courier New";
	mso-fareast-font-family:Batang;
	mso-hansi-font-family:"Courier New";
	mso-bidi-font-family:"Courier New";
	mso-bidi-font-style:italic;}
span.Heading9Char
	{mso-style-name:"Heading 9 Char";
	mso-style-unhide:no;
	mso-style-locked:yes;
	mso-style-link:"Heading 9";
	mso-bidi-font-size:11.0pt;
	font-family:"Courier New";
	mso-ascii-font-family:"Courier New";
	mso-fareast-font-family:Batang;
	mso-hansi-font-family:"Courier New";
	mso-bidi-font-family:Arial;}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-unhide:no;
	mso-style-locked:yes;
	mso-style-link:"Plain Text";
	mso-ansi-font-size:10.5pt;
	mso-bidi-font-size:10.5pt;
	font-family:Consolas;
	mso-ascii-font-family:Consolas;
	mso-fareast-font-family:Calibri;
	mso-fareast-theme-font:minor-latin;
	mso-hansi-font-family:Consolas;
	mso-bidi-font-family:"Times New Roman";
	mso-bidi-theme-font:minor-bidi;}
.MsoChpDefault
	{mso-style-type:export-only;
	mso-default-props:yes;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;
	mso-header-margin:.5in;
	mso-footer-margin:.5in;
	mso-paper-source:0;}
div.WordSection1
	{page:WordSection1;}
 /* List Definitions */
@list l0
	{mso-list-id:730737984;
	mso-list-template-ids:1011512210;}
@list l0:level1
	{mso-level-style-link:"Heading 1";
	mso-level-suffix:none;
	mso-level-text:"%1\. ";
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:120.6pt;
	text-indent:-.3in;
	mso-ansi-font-size:10.5pt;
	mso-bidi-font-size:10.5pt;}
@list l0:level2
	{mso-level-style-link:"Heading 2";
	mso-level-suffix:none;
	mso-level-text:"%1\.%2\. ";
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:.3in;
	text-indent:-.3in;
	mso-ansi-font-size:10.5pt;
	mso-bidi-font-size:10.5pt;}
@list l0:level3
	{mso-level-style-link:"Heading 3";
	mso-level-suffix:none;
	mso-level-text:"%1\.%2\.%3\. ";
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:.3in;
	text-indent:-.3in;}
@list l0:level4
	{mso-level-style-link:"Heading 4";
	mso-level-suffix:none;
	mso-level-text:"%1\.%2\.%3\.%4\. ";
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:.3in;
	text-indent:-.3in;}
@list l0:level5
	{mso-level-style-link:"Heading 5";
	mso-level-suffix:none;
	mso-level-text:"%1\.%2\.%3\.%4\.%5\. ";
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:.3in;
	text-indent:-.3in;}
@list l0:level6
	{mso-level-style-link:"Heading 6";
	mso-level-suffix:none;
	mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\. ";
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:.3in;
	text-indent:-.3in;}
@list l0:level7
	{mso-level-style-link:"Heading 7";
	mso-level-suffix:none;
	mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7\. ";
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:.3in;
	text-indent:-.3in;}
@list l0:level8
	{mso-level-style-link:"Heading 8";
	mso-level-suffix:none;
	mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7\.%8\. ";
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:.3in;
	text-indent:-.3in;}
@list l0:level9
	{mso-level-style-link:"Heading 9";
	mso-level-suffix:none;
	mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7\.%8\.%9\. ";
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:.3in;
	text-indent:-.3in;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
-->
</style><!--[if gte mso 10]>
<style>
 /* Style Definitions */
table.MsoNormalTable
	{mso-style-name:"Table Normal";
	mso-tstyle-rowband-size:0;
	mso-tstyle-colband-size:0;
	mso-style-noshow:yes;
	mso-style-priority:99;
	mso-style-parent:"";
	mso-padding-alt:0in 5.4pt 0in 5.4pt;
	mso-para-margin:0in;
	mso-para-margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Times New Roman";}
</style>
<![endif]--></head><body style=3D"color: rgb(0, 0, 0); font-size: 14px; fon=
t-family: Calibri, sans-serif; word-wrap: break-word; -webkit-nbsp-mode: sp=
ace; -webkit-line-break: after-white-space; "><div style=3D"font-family: Ca=
libri, sans-serif; ">Hi Dave,</div><div style=3D"font-family: Calibri, sans=
-serif; ">Related to abbreviations comment below and to be clearer, I renam=
ed the original terminology section to "Abbreviations and Terminology". I a=
lso created a subsection called "Abbreviations" ,and "Terminology" became t=
he second subsection. &nbsp;Here iis how the edits look</div><div style=3D"=
font-family: Calibri, sans-serif; "><br></div><div><!--[if gte mso 9]><xml>
 <o:DocumentProperties>
  <o:Revision>0</o:Revision>
  <o:TotalTime>0</o:TotalTime>
  <o:Pages>1</o:Pages>
  <o:Words>231</o:Words>
  <o:Characters>1322</o:Characters>
  <o:Company>Verizon</o:Company>
  <o:Lines>11</o:Lines>
  <o:Paragraphs>3</o:Paragraphs>
  <o:CharactersWithSpaces>1550</o:CharactersWithSpaces>
  <o:Version>14.0</o:Version>
 </o:DocumentProperties>
 <o:OfficeDocumentSettings>
  <o:RelyOnVML/>
  <o:AllowPNG/>
 </o:OfficeDocumentSettings>
</xml><![endif]--><!--[if gte mso 9]><xml>
 <w:WordDocument>
  <w:View>Normal</w:View>
  <w:Zoom>0</w:Zoom>
  <w:TrackMoves/>
  <w:TrackFormatting/>
  <w:PunctuationKerning/>
  <w:ValidateAgainstSchemas/>
  <w:SaveIfXMLInvalid>false</w:SaveIfXMLInvalid>
  <w:IgnoreMixedContent>false</w:IgnoreMixedContent>
  <w:AlwaysShowPlaceholderText>false</w:AlwaysShowPlaceholderText>
  <w:DoNotPromoteQF/>
  <w:LidThemeOther>EN-US</w:LidThemeOther>
  <w:LidThemeAsian>JA</w:LidThemeAsian>
  <w:LidThemeComplexScript>X-NONE</w:LidThemeComplexScript>
  <w:Compatibility>
   <w:BreakWrappedTables/>
   <w:SnapToGridInCell/>
   <w:WrapTextWithPunct/>
   <w:UseAsianBreakRules/>
   <w:DontGrowAutofit/>
   <w:SplitPgBreakAndParaMark/>
   <w:EnableOpenTypeKerning/>
   <w:DontFlipMirrorIndents/>
   <w:OverrideTableStyleHps/>
  </w:Compatibility>
  <m:mathPr>
   <m:mathFont m:val=3D"Cambria Math"/>
   <m:brkBin m:val=3D"before"/>
   <m:brkBinSub m:val=3D"&#45;-"/>
   <m:smallFrac m:val=3D"off"/>
   <m:dispDef/>
   <m:lMargin m:val=3D"0"/>
   <m:rMargin m:val=3D"0"/>
   <m:defJc m:val=3D"centerGroup"/>
   <m:wrapIndent m:val=3D"1440"/>
   <m:intLim m:val=3D"subSup"/>
   <m:naryLim m:val=3D"undOvr"/>
  </m:mathPr></w:WordDocument>
</xml><![endif]--><!--[if gte mso 9]><xml>
 <w:LatentStyles DefLockedState=3D"false" DefUnhideWhenUsed=3D"true"
  DefSemiHidden=3D"true" DefQFormat=3D"false" DefPriority=3D"99"
  LatentStyleCount=3D"276">
  <w:LsdException Locked=3D"false" Priority=3D"0" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Normal"/>
  <w:LsdException Locked=3D"false" Priority=3D"0" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"heading 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"0" QFormat=3D"true" Name=3D"=
heading 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"0" QFormat=3D"true" Name=3D"=
heading 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"0" QFormat=3D"true" Name=3D"=
heading 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"0" QFormat=3D"true" Name=3D"=
heading 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"0" QFormat=3D"true" Name=3D"=
heading 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"0" QFormat=3D"true" Name=3D"=
heading 7"/>
  <w:LsdException Locked=3D"false" Priority=3D"0" QFormat=3D"true" Name=3D"=
heading 8"/>
  <w:LsdException Locked=3D"false" Priority=3D"0" QFormat=3D"true" Name=3D"=
heading 9"/>
  <w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 7"/>
  <w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 8"/>
  <w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 9"/>
  <w:LsdException Locked=3D"false" Priority=3D"35" QFormat=3D"true" Name=3D=
"caption"/>
  <w:LsdException Locked=3D"false" Priority=3D"10" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Title"/>
  <w:LsdException Locked=3D"false" Priority=3D"1" Name=3D"Default Paragraph=
 Font"/>
  <w:LsdException Locked=3D"false" Priority=3D"11" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Subtitle"/>
  <w:LsdException Locked=3D"false" Priority=3D"22" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Strong"/>
  <w:LsdException Locked=3D"false" Priority=3D"20" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Emphasis"/>
  <w:LsdException Locked=3D"false" Priority=3D"59" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Table Grid"/>
  <w:LsdException Locked=3D"false" UnhideWhenUsed=3D"false" Name=3D"Placeho=
lder Text"/>
  <w:LsdException Locked=3D"false" Priority=3D"1" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"No Spacing"/>
  <w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light Shading"/>
  <w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light List"/>
  <w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light Grid"/>
  <w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium List 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium List 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Dark List"/>
  <w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful Shading"/>
  <w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful List"/>
  <w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful Grid"/>
  <w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light List Accent 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 1"/>
  <w:LsdException Locked=3D"false" UnhideWhenUsed=3D"false" Name=3D"Revisio=
n"/>
  <w:LsdException Locked=3D"false" Priority=3D"34" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"List Paragraph"/>
  <w:LsdException Locked=3D"false" Priority=3D"29" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Quote"/>
  <w:LsdException Locked=3D"false" Priority=3D"30" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Intense Quote"/>
  <w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light List Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light List Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light List Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light List Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light List Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"19" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Subtle Emphasis"/>
  <w:LsdException Locked=3D"false" Priority=3D"21" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Intense Emphasis"/>
  <w:LsdException Locked=3D"false" Priority=3D"31" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Subtle Reference"/>
  <w:LsdException Locked=3D"false" Priority=3D"32" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Intense Reference"/>
  <w:LsdException Locked=3D"false" Priority=3D"33" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Book Title"/>
  <w:LsdException Locked=3D"false" Priority=3D"37" Name=3D"Bibliography"/>
  <w:LsdException Locked=3D"false" Priority=3D"39" QFormat=3D"true" Name=3D=
"TOC Heading"/>
 </w:LatentStyles>
</xml><![endif]--><!--[if gte mso 10]>
<style>
 /* Style Definitions */
table.MsoNormalTable
	{mso-style-name:"Table Normal";
	mso-tstyle-rowband-size:0;
	mso-tstyle-colband-size:0;
	mso-style-noshow:yes;
	mso-style-priority:99;
	mso-style-parent:"";
	mso-padding-alt:0in 5.4pt 0in 5.4pt;
	mso-para-margin:0in;
	mso-para-margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Times New Roman";}
</style>
<![endif]--><!--StartFragment--><h1 style=3D"font-family: Calibri, sans-ser=
if; margin-right: 18.95pt; "><a name=3D"_Toc218760256"></a><a name=3D"_Toc2=
18759895"><span style=3D"mso-bookmark:
_Toc218760256"><span style=3D"font-size:10.5pt;mso-fareast-font-family:
&quot;Courier New&quot;"><span style=3D"mso-list:Ignore">3. </span></span><=
!--[endif]--><span style=3D"font-size:10.5pt">Abbreviations and Terminology=
</span></span></a><span style=3D"font-size:10.5pt"><o:p></o:p></span></h1><=
h2 style=3D"font-family: Calibri, sans-serif; "><a name=3D"_Toc218760257"><=
/a><a name=3D"_Toc218759896"><span style=3D"mso-bookmark:_Toc218760257"><sp=
an style=3D"font-size:10.5pt;mso-fareast-font-family:&quot;Courier New&quot=
;;mso-bidi-font-family:
&quot;Courier New&quot;"><span style=3D"mso-list:Ignore">3.1. </span></span=
><!--[endif]--><span style=3D"font-size:10.5pt">Abbreviations</span></span>=
</a><span style=3D"font-size:
10.5pt"><o:p></o:p></span></h2><p class=3D"MsoPlainText" style=3D"font-fami=
ly: Calibri, sans-serif; "><span style=3D"mso-spacerun:yes">&nbsp; &nbsp; &=
nbsp; &nbsp;&nbsp;</span><span style=3D"font-family: 'Courier New'; ">AIS<s=
pan style=3D"mso-spacerun:yes">&nbsp;&nbsp;
</span>Alarm Indication Signal<o:p></o:p></span></p><p class=3D"MsoPlainTex=
t" style=3D"font-family: Calibri, sans-serif; "><span style=3D"font-family:=
 'Courier New'; "><span style=3D"mso-spacerun:yes">&nbsp;&nbsp; </span>AC<s=
pan style=3D"mso-spacerun:yes">&nbsp;&nbsp;&nbsp;
</span>Attachment Circuit<o:p></o:p></span></p><p class=3D"MsoPlainText" st=
yle=3D"font-family: Calibri, sans-serif; "><span style=3D"font-family: 'Cou=
rier New'; "><span style=3D"mso-spacerun:yes">&nbsp;&nbsp; </span>BFD<span =
style=3D"mso-spacerun:yes">&nbsp;&nbsp;
</span>Bidirectional Forwarding Detection<o:p></o:p></span></p><p class=3D"=
MsoPlainText" style=3D"font-family: Calibri, sans-serif; "><span style=3D"f=
ont-family: 'Courier New'; "><span style=3D"mso-spacerun:yes">&nbsp;&nbsp; =
</span>CC<span style=3D"mso-spacerun:yes">&nbsp;&nbsp;&nbsp;
</span>Continuity Check<o:p></o:p></span></p><p class=3D"MsoPlainText" styl=
e=3D"font-family: Calibri, sans-serif; "><span style=3D"font-family: 'Couri=
er New'; "><span style=3D"mso-spacerun:yes">&nbsp;&nbsp; </span>CCM<span st=
yle=3D"mso-spacerun:yes">&nbsp;&nbsp;
</span>Continuity Check Message<o:p></o:p></span></p><p class=3D"MsoPlainTe=
xt" style=3D"font-family: Calibri, sans-serif; "><span style=3D"font-family=
: 'Courier New'; "><span style=3D"mso-spacerun:yes">&nbsp;&nbsp; </span>CE<=
span style=3D"mso-spacerun:yes">&nbsp;&nbsp;&nbsp;
</span>Customer Equipment<o:p></o:p></span></p><p class=3D"MsoPlainText" st=
yle=3D"font-family: Calibri, sans-serif; "><span style=3D"font-family: 'Cou=
rier New'; "><span style=3D"mso-spacerun:yes">&nbsp;&nbsp; </span>CV<span s=
tyle=3D"mso-spacerun:yes">&nbsp;&nbsp;&nbsp;
</span>Connectivity Verification<o:p></o:p></span></p><p class=3D"MsoPlainT=
ext" style=3D"font-family: Calibri, sans-serif; "><span style=3D"font-famil=
y: 'Courier New'; "><span style=3D"mso-spacerun:yes">&nbsp;&nbsp; </span>E-=
LMI Ethernet Local Management Interface<o:p></o:p></span></p><p class=3D"Ms=
oPlainText" style=3D"font-family: Calibri, sans-serif; "><span style=3D"fon=
t-family: 'Courier New'; "><span style=3D"mso-spacerun:yes">&nbsp;&nbsp; </=
span>EVC<span style=3D"mso-spacerun:yes">&nbsp;&nbsp;
</span>Ethernet Virtual Circuit<o:p></o:p></span></p><p class=3D"MsoPlainTe=
xt" style=3D"font-family: Calibri, sans-serif; "><span style=3D"font-family=
: 'Courier New'; "><span style=3D"mso-spacerun:yes">&nbsp;&nbsp; </span>LDP=
<span style=3D"mso-spacerun:yes">&nbsp;&nbsp;
</span>Label Distribution Protocol<o:p></o:p></span></p><p class=3D"MsoPlai=
nText" style=3D"font-family: Calibri, sans-serif; "><span style=3D"font-fam=
ily: 'Courier New'; "><span style=3D"mso-spacerun:yes">&nbsp;&nbsp; </span>=
LoS<span style=3D"mso-spacerun:yes">&nbsp;&nbsp;
</span>Loss of Signal<o:p></o:p></span></p><p class=3D"MsoPlainText" style=
=3D"font-family: Calibri, sans-serif; "><span style=3D"font-family: 'Courie=
r New'; "><span style=3D"mso-spacerun:yes">&nbsp;&nbsp; </span>MA<span styl=
e=3D"mso-tab-count:1"> </span><span style=3D"mso-spacerun:yes">&nbsp;&nbsp;=
 </span>Maintenance Association<o:p></o:p></span></p><p class=3D"MsoPlainTe=
xt" style=3D"font-family: Calibri, sans-serif; "><span style=3D"font-family=
: 'Courier New'; "><span style=3D"mso-spacerun:yes">&nbsp;&nbsp; </span>MD<=
span style=3D"mso-spacerun:yes">&nbsp;&nbsp;&nbsp;
</span>Maintenance Domain<o:p></o:p></span></p><p class=3D"MsoPlainText" st=
yle=3D"font-family: Calibri, sans-serif; "><span style=3D"font-family: 'Cou=
rier New'; "><span style=3D"mso-spacerun:yes">&nbsp;&nbsp; </span>ME<span s=
tyle=3D"mso-spacerun:yes">&nbsp;&nbsp;&nbsp;
</span>Maintenance Entity<o:p></o:p></span></p><p class=3D"MsoPlainText" st=
yle=3D"font-family: Calibri, sans-serif; "><span style=3D"font-family: 'Cou=
rier New'; "><span style=3D"mso-spacerun:yes">&nbsp;&nbsp; </span>MEG<span =
style=3D"mso-spacerun:yes">&nbsp;&nbsp;
</span>Maintenance Entity Group<o:p></o:p></span></p><p class=3D"MsoPlainTe=
xt" style=3D"font-family: Calibri, sans-serif; "><span style=3D"font-family=
: 'Courier New'; "><span style=3D"mso-spacerun:yes">&nbsp;&nbsp; </span>MEP=
<span style=3D"mso-spacerun:yes">&nbsp;&nbsp;
</span>Maintenance End Point<o:p></o:p></span></p><p class=3D"MsoPlainText"=
 style=3D"font-family: Calibri, sans-serif; "><span style=3D"font-family: '=
Courier New'; "><span style=3D"mso-spacerun:yes">&nbsp;&nbsp; </span>MIP<sp=
an style=3D"mso-spacerun:yes">&nbsp;&nbsp;
</span>Maintenance End Point<o:p></o:p></span></p><p class=3D"MsoPlainText"=
 style=3D"font-family: Calibri, sans-serif; "><span style=3D"font-family: '=
Courier New'; "><span style=3D"mso-spacerun:yes">&nbsp;&nbsp; </span>MPLS<s=
pan style=3D"mso-spacerun:yes">&nbsp;
</span>Multiprotocol Label Switching<o:p></o:p></span></p><p class=3D"MsoPl=
ainText" style=3D"font-family: Calibri, sans-serif; "><span style=3D"font-f=
amily: 'Courier New'; "><span style=3D"mso-spacerun:yes">&nbsp;&nbsp; </spa=
n>MS-PW Multi-Segment Pseudowire<o:p></o:p></span></p><p class=3D"MsoPlainT=
ext" style=3D"font-family: Calibri, sans-serif; "><span style=3D"font-famil=
y: 'Courier New'; "><span style=3D"mso-spacerun:yes">&nbsp;&nbsp; </span>NS=
<span style=3D"mso-spacerun:yes">&nbsp;&nbsp;&nbsp;
</span>Native Service<o:p></o:p></span></p><p class=3D"MsoPlainText" style=
=3D"font-family: Calibri, sans-serif; "><span style=3D"font-family: 'Courie=
r New'; "><span style=3D"mso-spacerun:yes">&nbsp;&nbsp; </span>OAM<span sty=
le=3D"mso-spacerun:yes">&nbsp;&nbsp;
</span>Operations, Administration, and Maintenance<o:p></o:p></span></p><p =
class=3D"MsoPlainText" style=3D"font-family: Calibri, sans-serif; "><span s=
tyle=3D"font-family: 'Courier New'; "><span style=3D"mso-spacerun:yes">&nbs=
p;&nbsp; </span>PE<span style=3D"mso-spacerun:yes">&nbsp;&nbsp;&nbsp;
</span>Provider Edge<o:p></o:p></span></p><p class=3D"MsoPlainText" style=
=3D"font-family: Calibri, sans-serif; "><span style=3D"font-family: 'Courie=
r New'; "><span style=3D"mso-spacerun:yes">&nbsp;&nbsp; </span>PSN<span sty=
le=3D"mso-spacerun:yes">&nbsp;&nbsp;
</span>Packet Switched Network<o:p></o:p></span></p><p class=3D"MsoPlainTex=
t" style=3D"font-family: Calibri, sans-serif; "><span style=3D"font-family:=
 'Courier New'; "><span style=3D"mso-spacerun:yes">&nbsp;&nbsp; </span>PW<s=
pan style=3D"mso-spacerun:yes">&nbsp;&nbsp;&nbsp;
</span>Pseudowire<o:p></o:p></span></p><p class=3D"MsoPlainText" style=3D"f=
ont-family: Calibri, sans-serif; "><span style=3D"font-family: 'Courier New=
'; "><span style=3D"mso-spacerun:yes">&nbsp;&nbsp; </span>RDI<span style=3D=
"mso-spacerun:yes">&nbsp;&nbsp;
</span>Remote Defect Indication for Continuity Check Message<o:p></o:p></sp=
an></p><p class=3D"MsoPlainText"><font class=3D"Apple-style-span" face=3D"C=
ourier New">&nbsp; &nbsp;RDI &nbsp; Reverse Defect Indication&nbsp;</font><=
/p><p class=3D"MsoPlainText" style=3D"font-family: Calibri, sans-serif; "><=
span style=3D"font-family: 'Courier New'; "><span style=3D"mso-spacerun:yes=
">&nbsp;&nbsp; </span>S-PE<span style=3D"mso-spacerun:yes">&nbsp;
</span>Switching Provider Edge<o:p></o:p></span></p><p class=3D"MsoPlainTex=
t" style=3D"font-family: Calibri, sans-serif; "><span style=3D"font-family:=
 'Courier New'; "><span style=3D"mso-spacerun:yes">&nbsp;&nbsp; </span>TLV<=
span style=3D"mso-spacerun:yes">&nbsp;&nbsp;
</span>Type Length Value<o:p></o:p></span></p><p class=3D"MsoPlainText" sty=
le=3D"font-family: Calibri, sans-serif; "><span style=3D"font-family: 'Cour=
ier New'; "><span style=3D"mso-spacerun:yes">&nbsp;&nbsp; </span>T-PE<span =
style=3D"mso-spacerun:yes">&nbsp;
</span>Terminating Provider Edge<o:p></o:p></span></p><p class=3D"MsoNormal=
" style=3D"font-family: Calibri, sans-serif; "><span style=3D"font-size:10.=
5pt"><o:p>&nbsp;</o:p></span></p><h2 style=3D"font-family: Calibri, sans-se=
rif; "><a name=3D"_Toc218760258"></a><a name=3D"_Toc218759897"><span style=
=3D"mso-bookmark:_Toc218760258"><span style=3D"font-size:10.5pt;mso-fareast=
-font-family:&quot;Courier New&quot;;mso-bidi-font-family:
&quot;Courier New&quot;"><span style=3D"mso-list:Ignore">3.2. </span></span=
><!--[endif]--><span style=3D"font-size:10.5pt">Terminology</span></span></=
a><span style=3D"font-size:
10.5pt"><o:p></o:p></span></h2><p class=3D"MsoNormal" style=3D"font-family:=
 Calibri, sans-serif; margin-left: 0in; "><span style=3D"font-size:10.5pt">=
This
document uses the following terms with corresponding definitions: <o:p></o:=
p></span></p><p class=3D"MsoNormal" style=3D"font-family: Calibri, sans-ser=
if; "><span style=3D"font-size:10.5pt">- MD Level:<span style=3D"mso-spacer=
un:yes">&nbsp; </span>Maintenance Domain (MD) Level which
identifies a value in the range of 0-7 associated with Ethernet OAM frame. =
MD
Level identifies the span of the Ethernet OAM frame.<o:p></o:p></span></p><=
p class=3D"MsoNormal" style=3D"font-family: Calibri, sans-serif; text-align=
: justify; "><span style=3D"font-size:10.5pt"><span style=3D"mso-spacerun:y=
es">&nbsp;</span>- MEP:<span style=3D"mso-spacerun:yes">&nbsp; </span><span=
 style=3D"mso-spacerun:yes">&nbsp;&nbsp;</span>Maintenance End Point is res=
ponsible for
origination and termination of OAM frames for a given MEG.<o:p></o:p></span=
></p><p class=3D"MsoNormal" style=3D"font-family: Calibri, sans-serif; "><s=
pan style=3D"font-size:10.5pt"><span style=3D"mso-spacerun:yes">&nbsp;</spa=
n>- MIP: <span style=3D"mso-spacerun:yes">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</s=
pan>Maintenance Intermediate Point is located
between peer MEPs and can process OAM frames but does not initiate or termi=
nate
them.<o:p></o:p></span></p><p class=3D"MsoNormal" style=3D"font-family: Cal=
ibri, sans-serif; margin-left: 0in; "><span style=3D"font-size:10.5pt">Furt=
her,
this document also uses the terminology and conventions used in [RFC6310].<=
/span><o:p></o:p></p><p class=3D"MsoNormal" style=3D"font-family: Calibri, =
sans-serif; margin-left: 0in; "><span style=3D"font-size:10.5pt"><br></span=
></p><p class=3D"MsoNormal" style=3D"font-family: Calibri, sans-serif; marg=
in-left: 0in; "><span style=3D"font-size:10.5pt"><br></span></p><p class=3D=
"MsoNormal" style=3D"font-family: Calibri, sans-serif; margin-left: 0in; ">=
<span style=3D"font-size:10.5pt">Thanks,</span></p><p class=3D"MsoNormal" s=
tyle=3D"font-family: Calibri, sans-serif; margin-left: 0in; "><span style=
=3D"font-size:10.5pt">Nabil</span></p><!--EndFragment--></div><div style=3D=
"font-family: Calibri, sans-serif; "><br></div><span id=3D"OLK_SRC_BODY_SEC=
TION" style=3D"font-family: Calibri, sans-serif; "><div style=3D"font-famil=
y:Calibri; font-size:11pt; text-align:left; color:black; BORDER-BOTTOM: med=
ium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in;=
 PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium no=
ne; PADDING-TOP: 3pt"><span style=3D"font-weight:bold">From: </span> &lt;Bi=
tar&gt;, Nabil N &lt;<a href=3D"mailto:nabil.n.bitar@one.verizon.com">nabil=
.n.bitar@one.verizon.com</a>&gt;<br><span style=3D"font-weight:bold">Date: =
</span> Wednesday, January 2, 2013 11:28 AM<br><span style=3D"font-weight:b=
old">To: </span> "Black, David" &lt;<a href=3D"mailto:david.black@emc.com">=
david.black@emc.com</a>&gt;, "<a href=3D"mailto:dinmohan@hotmail.com">dinmo=
han@hotmail.com</a>" &lt;<a href=3D"mailto:dinmohan@hotmail.com">dinmohan@h=
otmail.com</a>&gt;, "Bitar, Nabil N" &lt;<a href=3D"mailto:nabil.n.bitar@on=
e.verizon.com">nabil.n.bitar@one.verizon.com</a>&gt;, Sagessi &lt;<a href=
=3D"mailto:sajassi@cisco.com">sajassi@cisco.com</a>&gt;, "<a href=3D"mailto=
:gen-art@ietf.org">gen-art@ietf.org</a>" &lt;<a href=3D"mailto:gen-art@ietf=
.org">gen-art@ietf.org</a>&gt;<br><span style=3D"font-weight:bold">Cc: </sp=
an> "<a href=3D"mailto:pwe3@ietf.org">pwe3@ietf.org</a>" &lt;<a href=3D"mai=
lto:pwe3@ietf.org">pwe3@ietf.org</a>&gt;, "<a href=3D"mailto:ietf@ietf.org"=
>ietf@ietf.org</a>" &lt;<a href=3D"mailto:ietf@ietf.org">ietf@ietf.org</a>&=
gt;<br><span style=3D"font-weight:bold">Subject: </span> Re: Gen-ART review=
 of draft-ietf-pwe3-mpls-eth-oam-iwk-06<br></div><div><br></div><div><meta =
http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dutf-8"><meta na=
me=3D"Title" content=3D""><meta name=3D"Keywords" content=3D""><meta name=
=3D"ProgId" content=3D"Word.Document"><meta name=3D"Generator" content=3D"M=
icrosoft Word 14"><meta name=3D"Originator" content=3D"Microsoft Word 14"><=
link rel=3D"File-List" href=3D"file://localhost/Users/admin/Library/Caches/=
TemporaryItems/msoclip/0/clip_filelist.xml"><!--[if gte mso 9]><xml>
 <o:DocumentProperties>
  <o:Revision>0</o:Revision>
  <o:TotalTime>0</o:TotalTime>
  <o:Pages>1</o:Pages>
  <o:Words>17</o:Words>
  <o:Characters>97</o:Characters>
  <o:Company>Verizon</o:Company>
  <o:Lines>1</o:Lines>
  <o:Paragraphs>1</o:Paragraphs>
  <o:CharactersWithSpaces>113</o:CharactersWithSpaces>
  <o:Version>14.0</o:Version>
 </o:DocumentProperties>
 <o:OfficeDocumentSettings>
  <o:RelyOnVML/>
  <o:AllowPNG/>
 </o:OfficeDocumentSettings>
</xml><![endif]--><link rel=3D"themeData" href=3D"file://localhost/Users/ad=
min/Library/Caches/TemporaryItems/msoclip/0/clip_themedata.xml"><!--[if gte=
 mso 9]><xml>
 <w:WordDocument>
  <w:View>Normal</w:View>
  <w:Zoom>0</w:Zoom>
  <w:TrackMoves/>
  <w:TrackFormatting/>
  <w:PunctuationKerning/>
  <w:ValidateAgainstSchemas/>
  <w:SaveIfXMLInvalid>false</w:SaveIfXMLInvalid>
  <w:IgnoreMixedContent>false</w:IgnoreMixedContent>
  <w:AlwaysShowPlaceholderText>false</w:AlwaysShowPlaceholderText>
  <w:DoNotPromoteQF/>
  <w:LidThemeOther>EN-US</w:LidThemeOther>
  <w:LidThemeAsian>JA</w:LidThemeAsian>
  <w:LidThemeComplexScript>X-NONE</w:LidThemeComplexScript>
  <w:Compatibility>
   <w:BreakWrappedTables/>
   <w:SnapToGridInCell/>
   <w:WrapTextWithPunct/>
   <w:UseAsianBreakRules/>
   <w:DontGrowAutofit/>
   <w:SplitPgBreakAndParaMark/>
   <w:EnableOpenTypeKerning/>
   <w:DontFlipMirrorIndents/>
   <w:OverrideTableStyleHps/>
  </w:Compatibility>
  <m:mathPr>
   <m:mathFont m:val=3D"Cambria Math"/>
   <m:brkBin m:val=3D"before"/>
   <m:brkBinSub m:val=3D"&#45;-"/>
   <m:smallFrac m:val=3D"off"/>
   <m:dispDef/>
   <m:lMargin m:val=3D"0"/>
   <m:rMargin m:val=3D"0"/>
   <m:defJc m:val=3D"centerGroup"/>
   <m:wrapIndent m:val=3D"1440"/>
   <m:intLim m:val=3D"subSup"/>
   <m:naryLim m:val=3D"undOvr"/>
  </m:mathPr></w:WordDocument>
</xml><![endif]--><!--[if gte mso 9]><xml>
 <w:LatentStyles DefLockedState=3D"false" DefUnhideWhenUsed=3D"true"
  DefSemiHidden=3D"true" DefQFormat=3D"false" DefPriority=3D"99"
  LatentStyleCount=3D"276">
  <w:LsdException Locked=3D"false" Priority=3D"0" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Normal"/>
  <w:LsdException Locked=3D"false" Priority=3D"9" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"heading 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" Name=3D"=
heading 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" Name=3D"=
heading 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" Name=3D"=
heading 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" Name=3D"=
heading 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" Name=3D"=
heading 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" Name=3D"=
heading 7"/>
  <w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" Name=3D"=
heading 8"/>
  <w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" Name=3D"=
heading 9"/>
  <w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 7"/>
  <w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 8"/>
  <w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 9"/>
  <w:LsdException Locked=3D"false" Priority=3D"35" QFormat=3D"true" Name=3D=
"caption"/>
  <w:LsdException Locked=3D"false" Priority=3D"10" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Title"/>
  <w:LsdException Locked=3D"false" Priority=3D"1" Name=3D"Default Paragraph=
 Font"/>
  <w:LsdException Locked=3D"false" Priority=3D"11" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Subtitle"/>
  <w:LsdException Locked=3D"false" Priority=3D"22" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Strong"/>
  <w:LsdException Locked=3D"false" Priority=3D"20" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Emphasis"/>
  <w:LsdException Locked=3D"false" Priority=3D"59" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Table Grid"/>
  <w:LsdException Locked=3D"false" UnhideWhenUsed=3D"false" Name=3D"Placeho=
lder Text"/>
  <w:LsdException Locked=3D"false" Priority=3D"1" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"No Spacing"/>
  <w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light Shading"/>
  <w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light List"/>
  <w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light Grid"/>
  <w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium List 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium List 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Dark List"/>
  <w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful Shading"/>
  <w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful List"/>
  <w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful Grid"/>
  <w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light List Accent 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 1"/>
  <w:LsdException Locked=3D"false" UnhideWhenUsed=3D"false" Name=3D"Revisio=
n"/>
  <w:LsdException Locked=3D"false" Priority=3D"34" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"List Paragraph"/>
  <w:LsdException Locked=3D"false" Priority=3D"29" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Quote"/>
  <w:LsdException Locked=3D"false" Priority=3D"30" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Intense Quote"/>
  <w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light List Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light List Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light List Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light List Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light List Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"19" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Subtle Emphasis"/>
  <w:LsdException Locked=3D"false" Priority=3D"21" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Intense Emphasis"/>
  <w:LsdException Locked=3D"false" Priority=3D"31" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Subtle Reference"/>
  <w:LsdException Locked=3D"false" Priority=3D"32" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Intense Reference"/>
  <w:LsdException Locked=3D"false" Priority=3D"33" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Book Title"/>
  <w:LsdException Locked=3D"false" Priority=3D"37" Name=3D"Bibliography"/>
  <w:LsdException Locked=3D"false" Priority=3D"39" QFormat=3D"true" Name=3D=
"TOC Heading"/>
 </w:LatentStyles>
</xml><![endif]--><style>
<!--
 /* Font Definitions */
@font-face
	{font-family:"Courier New";
	panose-1:2 7 3 9 2 2 5 2 4 4;
	mso-font-charset:0;
	mso-generic-font-family:auto;
	mso-font-pitch:variable;
	mso-font-signature:-536859905 -1073711037 9 0 511 0;}
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;
	mso-font-charset:0;
	mso-generic-font-family:auto;
	mso-font-pitch:variable;
	mso-font-signature:-536870145 1107305727 0 0 415 0;}
@font-face
	{font-family:Batang;
	mso-font-alt:??;
	mso-font-charset:129;
	mso-generic-font-family:roman;
	mso-font-pitch:variable;
	mso-font-signature:-1342176593 1775729915 48 0 524447 0;}
 /* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{mso-style-unhide:no;
	mso-style-qformat:yes;
	mso-style-parent:"";
	margin-top:0in;
	margin-right:0in;
	margin-bottom:12.0pt;
	margin-left:.3in;
	line-height:12.0pt;
	mso-line-height-rule:exactly;
	mso-pagination:widow-orphan;
	tab-stops:.3in .6in .9in 1.2in 1.5in 1.8in 2.1in 2.4in 2.7in 3.0in 3.3in 3=
.6in 3.9in 4.2in 4.5in 4.8in 5.1in 5.4in 5.7in 6.0in 6.3in 6.6in 6.9in;
	font-size:12.0pt;
	font-family:"Courier New";
	mso-fareast-font-family:Batang;}
.MsoChpDefault
	{mso-style-type:export-only;
	mso-default-props:yes;
	font-size:10.0pt;
	mso-ansi-font-size:10.0pt;
	mso-bidi-font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;
	mso-header-margin:.5in;
	mso-footer-margin:.5in;
	mso-paper-source:0;}
div.WordSection1
	{page:WordSection1;}
-->
</style><!--[if gte mso 10]>
<style>
 /* Style Definitions */
table.MsoNormalTable
	{mso-style-name:"Table Normal";
	mso-tstyle-rowband-size:0;
	mso-tstyle-colband-size:0;
	mso-style-noshow:yes;
	mso-style-priority:99;
	mso-style-parent:"";
	mso-padding-alt:0in 5.4pt 0in 5.4pt;
	mso-para-margin:0in;
	mso-para-margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:10.0pt;
	font-family:"Times New Roman";}
</style>
<![endif]--><div style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px=
; font-family: Calibri, sans-serif; "><div><font class=3D"Apple-style-span"=
 face=3D"Calibri,sans-serif">Hi Dave,</font></div><div><font class=3D"Apple=
-style-span" face=3D"Calibri,sans-serif">Sorry for a late reply addressing =
your comments. Please, see inline.</font></div><div><font class=3D"Apple-st=
yle-span" face=3D"Calibri,sans-serif"><br></font></div><div><font class=3D"=
Apple-style-span" face=3D"Calibri,sans-serif">Thanks,</font></div><div><fon=
t class=3D"Apple-style-span" face=3D"Calibri,sans-serif">Nabil</font></div>=
<div style=3D"color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-s=
ize: 14px; "><br></div><span id=3D"OLK_SRC_BODY_SECTION" style=3D"color: rg=
b(0, 0, 0); font-size: 14px; font-family: Calibri, sans-serif; "><div style=
=3D"font-family:Calibri; font-size:11pt; text-align:left; color:black; BORD=
ER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; PADD=
ING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; BORDER-RI=
GHT: medium none; PADDING-TOP: 3pt"><span style=3D"font-weight:bold">From: =
</span>"Black, David" &lt;<a href=3D"mailto:david.black@emc.com">david.blac=
k@emc.com</a>&gt;<br><span style=3D"font-weight:bold">Date: </span>Monday, =
August 20, 2012 8:57 PM<br><span style=3D"font-weight:bold">To: </span>"<a =
href=3D"mailto:dinmohan@hotmail.com">dinmohan@hotmail.com</a>" &lt;<a href=
=3D"mailto:dinmohan@hotmail.com">dinmohan@hotmail.com</a>&gt;, "Bitar, Nabi=
l N" &lt;<a href=3D"mailto:nabil.n.bitar@one.verizon.com">nabil.n.bitar@one=
.verizon.com</a>&gt;,
 Sagessi &lt;<a href=3D"mailto:sajassi@cisco.com">sajassi@cisco.com</a>&gt;=
, "<a href=3D"mailto:gen-art@ietf.org">gen-art@ietf.org</a>" &lt;<a href=3D=
"mailto:gen-art@ietf.org">gen-art@ietf.org</a>&gt;<br><span style=3D"font-w=
eight:bold">Cc: </span>"Black, David" &lt;<a href=3D"mailto:david.black@emc=
.com">david.black@emc.com</a>&gt;, "<a href=3D"mailto:pwe3@ietf.org">pwe3@i=
etf.org</a>" &lt;<a href=3D"mailto:pwe3@ietf.org">pwe3@ietf.org</a>&gt;, "<=
a href=3D"mailto:ietf@ietf.org">ietf@ietf.org</a>"
 &lt;<a href=3D"mailto:ietf@ietf.org">ietf@ietf.org</a>&gt;<br><span style=
=3D"font-weight:bold">Subject: </span>Gen-ART review of draft-ietf-pwe3-mpl=
s-eth-oam-iwk-06<br></div><div><br></div><div dir=3D"ltr"><style title=3D"o=
waParaStyle"><!--P {
	MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px
}
--></style><div ocsi=3D"x"><div dir=3D"ltr"><font color=3D"#000000" size=3D=
"2" face=3D"Courier New">I am the assigned Gen-ART reviewer for this draft.=
 For background on Gen-ART, please<br>
see the FAQ at &lt;<a href=3D"http://wiki.tools.ietf.org/area/gen/trac/wiki=
/GenArtfaq" target=3D"_blank">http://wiki.tools.ietf.org/area/gen/trac/wiki=
/GenArtfaq</a>&gt;.<br><br>
Please resolve these comments along with any other Last Call comments you m=
ay receive.<br><br>
Document: <span lang=3D"EN">draft-ietf-pwe3-mpls-eth-oam-iwk-06</span></fon=
t></div><div dir=3D"ltr"><font color=3D"#000000" size=3D"2" face=3D"Courier=
 New"><span lang=3D"EN"></span>Reviewer: David L. Black<br>
Review Date: August 20, 2012<br>
IETF LC End Date: August 20, 2012<br><br>
Summary:<br>
This draft is basically ready for publication, but has nits that<br>
should be fixed before publication.</font></div></div></div></span><div><br=
></div><div>&lt;NB&gt; Thanks.</div><span id=3D"OLK_SRC_BODY_SECTION" style=
=3D"color: rgb(0, 0, 0); font-size: 14px; font-family: Calibri, sans-serif;=
 "><div dir=3D"ltr"><div ocsi=3D"x"><p><font color=3D"#000000" size=3D"2" f=
ace=3D"Courier New"><font face=3D"courier new"></font></font>&nbsp;</p><p><=
font color=3D"#000000" size=3D"2" face=3D"Courier New"><font face=3D"courie=
r new">This draft covers defect behavior for Ethernet pseudowires<a target=
=3D"_blank"></a>,</font></font></p><p><font color=3D"#000000" size=3D"2" fa=
ce=3D"Courier New"><font face=3D"courier new">including defect state mappin=
g and PE defect reporting behavior.</font></font></p><p><font color=3D"#000=
000" size=3D"2" face=3D"Courier New"><font face=3D"courier new">The draft i=
s generally in good shape.&nbsp; I found a few minor nits.</font></font></p=
><p><font size=3D"2" face=3D"courier new"></font>&nbsp;</p><p><font size=3D=
"2" face=3D"courier new">1) The draft uses a lot of acronyms - while each a=
cronym appears to</font></p><p><font size=3D"2" face=3D"Courier New">b<font=
 face=3D"courier new">e expanded on first use, an additional section near t=
he start of the</font></font></p><p><font face=3D"Courier New"><font face=
=3D"courier new"><font size=3D"2"><font face=3D"courier new">draft listing<=
/font> all of them
</font></font></font><font size=3D"2" face=3D"courier new">would be helpful=
.</font></p></div></div></span><div><br></div><div>&lt;NB&gt; Done.</div><s=
pan id=3D"OLK_SRC_BODY_SECTION" style=3D"color: rgb(0, 0, 0); font-size: 14=
px; font-family: Calibri, sans-serif; "><div dir=3D"ltr"><div ocsi=3D"x"><p=
><font size=3D"2" face=3D"courier new"></font>&nbsp;</p><p><font size=3D"2"=
 face=3D"courier new">2) There's&nbsp;a typo in the first paragraph of sect=
ion 2:</font></p><p><font size=3D"2" face=3D"courier new"></font>&nbsp;</p>=
<font color=3D"#000000"><div dir=3D"ltr"><font size=3D"2"><span lang=3D"EN"=
><p><font face=3D"Courier New">&nbsp;&nbsp;&nbsp; &nbsp;covers the followin=
g Ethernet OAM (Opertaions<a target=3D"_blank"></a>, Administration and
</font></p><p><font face=3D"courier new"></font>&nbsp;</p><p><font face=3D"=
courier new"><a target=3D"_blank"></a><font face=3D"courier new">Opertaions=
</font>&nbsp;-&gt; Operations.</font></p></span></font></div></font></div><=
/div></span><div><br></div><div>&lt;NB&gt; Thanks. Done.</div><span id=3D"O=
LK_SRC_BODY_SECTION" style=3D"color: rgb(0, 0, 0); font-size: 14px; font-fa=
mily: Calibri, sans-serif; "><div dir=3D"ltr"><div ocsi=3D"x"><font color=
=3D"#000000"><div dir=3D"ltr"><font size=3D"2"><span lang=3D"EN"><p><font f=
ace=3D"courier new"></font>&nbsp;</p><p><font face=3D"courier new">3) The f=
ollowing normative reference is incomplete - please add additional</font></=
p><p><font face=3D"courier new">information that will enable a reader to lo=
cate the referenced document:</font></p><p><font face=3D"courier new"></fon=
t>&nbsp;</p><font face=3D"courier new"><span lang=3D"EN"><p>&nbsp;&nbsp;&nb=
sp; &nbsp;[MEF16] "Ethernet Local Management Interface", MEF16, January 200=
6.</p></span></font></span></font></div></font></div></div></span><div><br>=
</div><span id=3D"OLK_SRC_BODY_SECTION" style=3D"color: rgb(0, 0, 0); font-=
family: Calibri, sans-serif; "><div dir=3D"ltr"><div ocsi=3D"x"><font color=
=3D"#000000"><div dir=3D"ltr"><span class=3D"Apple-style-span" style=3D"lin=
e-height: 16px; font-family: 'Courier New'; ">[MEF16] "Ethernet Local Manag=
ement Interface", Metro Ethernet Forum Technical Specification MEF16, Janua=
ry 2006.</span><font><span lang=3D"EN"><font face=3D"courier new"><span lan=
g=3D"EN"><p style=3D"font-size: 14px; "><font face=3D"courier new"></font>&=
lt;NB&gt; changed it to :&nbsp;</p><p><!--[if gte mso 9]><xml>
 <o:DocumentProperties>
  <o:Revision>0</o:Revision>
  <o:TotalTime>0</o:TotalTime>
  <o:Pages>1</o:Pages>
  <o:Words>17</o:Words>
  <o:Characters>97</o:Characters>
  <o:Company>Verizon</o:Company>
  <o:Lines>1</o:Lines>
  <o:Paragraphs>1</o:Paragraphs>
  <o:CharactersWithSpaces>113</o:CharactersWithSpaces>
  <o:Version>14.0</o:Version>
 </o:DocumentProperties>
 <o:OfficeDocumentSettings>
  <o:RelyOnVML/>
  <o:AllowPNG/>
 </o:OfficeDocumentSettings>
</xml><![endif]--><!--[if gte mso 9]><xml>
 <w:WordDocument>
  <w:View>Normal</w:View>
  <w:Zoom>0</w:Zoom>
  <w:TrackMoves/>
  <w:TrackFormatting/>
  <w:PunctuationKerning/>
  <w:ValidateAgainstSchemas/>
  <w:SaveIfXMLInvalid>false</w:SaveIfXMLInvalid>
  <w:IgnoreMixedContent>false</w:IgnoreMixedContent>
  <w:AlwaysShowPlaceholderText>false</w:AlwaysShowPlaceholderText>
  <w:DoNotPromoteQF/>
  <w:LidThemeOther>EN-US</w:LidThemeOther>
  <w:LidThemeAsian>JA</w:LidThemeAsian>
  <w:LidThemeComplexScript>X-NONE</w:LidThemeComplexScript>
  <w:Compatibility>
   <w:BreakWrappedTables/>
   <w:SnapToGridInCell/>
   <w:WrapTextWithPunct/>
   <w:UseAsianBreakRules/>
   <w:DontGrowAutofit/>
   <w:SplitPgBreakAndParaMark/>
   <w:EnableOpenTypeKerning/>
   <w:DontFlipMirrorIndents/>
   <w:OverrideTableStyleHps/>
  </w:Compatibility>
  <m:mathPr>
   <m:mathFont m:val=3D"Cambria Math"/>
   <m:brkBin m:val=3D"before"/>
   <m:brkBinSub m:val=3D"&#45;-"/>
   <m:smallFrac m:val=3D"off"/>
   <m:dispDef/>
   <m:lMargin m:val=3D"0"/>
   <m:rMargin m:val=3D"0"/>
   <m:defJc m:val=3D"centerGroup"/>
   <m:wrapIndent m:val=3D"1440"/>
   <m:intLim m:val=3D"subSup"/>
   <m:naryLim m:val=3D"undOvr"/>
  </m:mathPr></w:WordDocument>
</xml><![endif]--><!--[if gte mso 9]><xml>
 <w:LatentStyles DefLockedState=3D"false" DefUnhideWhenUsed=3D"true"
  DefSemiHidden=3D"true" DefQFormat=3D"false" DefPriority=3D"99"
  LatentStyleCount=3D"276">
  <w:LsdException Locked=3D"false" Priority=3D"0" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Normal"/>
  <w:LsdException Locked=3D"false" Priority=3D"9" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"heading 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" Name=3D"=
heading 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" Name=3D"=
heading 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" Name=3D"=
heading 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" Name=3D"=
heading 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" Name=3D"=
heading 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" Name=3D"=
heading 7"/>
  <w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" Name=3D"=
heading 8"/>
  <w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" Name=3D"=
heading 9"/>
  <w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 7"/>
  <w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 8"/>
  <w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 9"/>
  <w:LsdException Locked=3D"false" Priority=3D"35" QFormat=3D"true" Name=3D=
"caption"/>
  <w:LsdException Locked=3D"false" Priority=3D"10" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Title"/>
  <w:LsdException Locked=3D"false" Priority=3D"1" Name=3D"Default Paragraph=
 Font"/>
  <w:LsdException Locked=3D"false" Priority=3D"11" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Subtitle"/>
  <w:LsdException Locked=3D"false" Priority=3D"22" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Strong"/>
  <w:LsdException Locked=3D"false" Priority=3D"20" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Emphasis"/>
  <w:LsdException Locked=3D"false" Priority=3D"59" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Table Grid"/>
  <w:LsdException Locked=3D"false" UnhideWhenUsed=3D"false" Name=3D"Placeho=
lder Text"/>
  <w:LsdException Locked=3D"false" Priority=3D"1" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"No Spacing"/>
  <w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light Shading"/>
  <w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light List"/>
  <w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light Grid"/>
  <w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium List 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium List 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Dark List"/>
  <w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful Shading"/>
  <w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful List"/>
  <w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful Grid"/>
  <w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light List Accent 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 1"/>
  <w:LsdException Locked=3D"false" UnhideWhenUsed=3D"false" Name=3D"Revisio=
n"/>
  <w:LsdException Locked=3D"false" Priority=3D"34" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"List Paragraph"/>
  <w:LsdException Locked=3D"false" Priority=3D"29" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Quote"/>
  <w:LsdException Locked=3D"false" Priority=3D"30" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Intense Quote"/>
  <w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 1"/>
  <w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light List Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 2"/>
  <w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light List Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 3"/>
  <w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light List Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 4"/>
  <w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light List Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 5"/>
  <w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light List Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 6"/>
  <w:LsdException Locked=3D"false" Priority=3D"19" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Subtle Emphasis"/>
  <w:LsdException Locked=3D"false" Priority=3D"21" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Intense Emphasis"/>
  <w:LsdException Locked=3D"false" Priority=3D"31" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Subtle Reference"/>
  <w:LsdException Locked=3D"false" Priority=3D"32" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Intense Reference"/>
  <w:LsdException Locked=3D"false" Priority=3D"33" SemiHidden=3D"false"
   UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Book Title"/>
  <w:LsdException Locked=3D"false" Priority=3D"37" Name=3D"Bibliography"/>
  <w:LsdException Locked=3D"false" Priority=3D"39" QFormat=3D"true" Name=3D=
"TOC Heading"/>
 </w:LatentStyles>
</xml><![endif]--><!--[if gte mso 10]>
<style>
 /* Style Definitions */
table.MsoNormalTable
	{mso-style-name:"Table Normal";
	mso-tstyle-rowband-size:0;
	mso-tstyle-colband-size:0;
	mso-style-noshow:yes;
	mso-style-priority:99;
	mso-style-parent:"";
	mso-padding-alt:0in 5.4pt 0in 5.4pt;
	mso-para-margin:0in;
	mso-para-margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:10.0pt;
	font-family:"Times New Roman";}
</style>
<![endif]--><!--StartFragment--><!--EndFragment-->&nbsp;</p><p style=3D"fon=
t-size: 14px; "><font face=3D"courier new"><font face=3D"courier new">4)&nb=
sp;idnits<a target=3D"_blank"></a> 2.12.13 did not like the pagination:</fo=
nt></font></p><p style=3D"font-size: 14px; ">&nbsp;</p></span></font></span=
></font><p style=3D"font-size: 14px; "><font size=3D"2"><font face=3D"couri=
er new"><font face=3D"courier new">&nbsp; =3D=3D The page length should not=
 exceed 58 lines per page, but there was 22<br>
&nbsp;&nbsp;&nbsp;&nbsp; longer pages, the longest (page 1) being 61 lines<=
/font></font></font></p></div></font></div></div></span><div>&lt;NB&gt; Tha=
t will be fixed.</div><span id=3D"OLK_SRC_BODY_SECTION" style=3D"color: rgb=
(0, 0, 0); font-family: Calibri, sans-serif; "><div dir=3D"ltr"><div ocsi=
=3D"x"><div dir=3D"ltr" style=3D"font-size: 14px; "><font face=3D"Courier N=
ew"><font color=3D"#000000" size=3D"2">&nbsp;</font></font></div><div style=
=3D"font-size: 14px; "><font size=3D"2" face=3D"Courier New">Thanks,</font>=
</div><div style=3D"font-size: 14px; "><font size=3D"2" face=3D"courier new=
">--David</font></div><div style=3D"font-size: 14px; "><font face=3D"Courie=
r New"><font size=3D"2">---------------------------------------------------=
-<br>
David L. Black, Distinguished Engineer<br>
EMC Corporation, 176 South St., Hopkinton, MA&nbsp; 01748<br>
+1 (508) 293-7953&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp; FAX: +1 (508) 293-7786<br></font><font size=3D"2"><a href=3D=
"mailto:david.black@emc.com" target=3D"_blank"><font size=3D"2">david.black=
@emc.com</font></a><a target=3D"_blank"></a></font><font size=3D"2">&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Mobile: +1 (978) 394-7754<br>
----------------------------------------------------<br></font></font></div=
></div></div></span></div></div></span></body></html>

--_000_CD0C3AE66E673nabilnbitarverizoncom_--

From huubatwork@gmail.com  Fri Jan  4 08:30:23 2013
Return-Path: <huubatwork@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AA96A21F88C8; Fri,  4 Jan 2013 08:30:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 u8Vr-cCLtpzR; Fri,  4 Jan 2013 08:30:23 -0800 (PST)
Received: from mail-wg0-f48.google.com (mail-wg0-f48.google.com [74.125.82.48]) by ietfa.amsl.com (Postfix) with ESMTP id CDCEE21F87E1; Fri,  4 Jan 2013 08:30:15 -0800 (PST)
Received: by mail-wg0-f48.google.com with SMTP id dt10so7725976wgb.27 for <multiple recipients>; Fri, 04 Jan 2013 08:30:14 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:disposition-notification-to:date:from :reply-to:user-agent:mime-version:to:cc:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=nGKxL2jbXFCo5h4DRSgym7nmnDh+H03fs2cf8o1ozAY=; b=boTD+4bfSCELbrQx9kiHFcy3tw2ecLXoJiyXDbq0+Ros5YA4Sj4tGhuw7DSfnzrAnb SGiYOBhdm4RFD42do7V4VMQ+GWYTW6kj4lAYUOXO7Om0Q7ptkPE1R52pFsEg9vQlZlsV Foyx/8tmLzwwNg4yTpIYUMGFY4uQMNSR2AyCVykTEc6hhVb7kzy+LtasyY3Y2wtovQqt /Tpc6Dmg6uhEaAZiZ3/xIZOxxxK9KESvBzlFL3LgokYLX5HEnPBvREs7Bhd5R7/krfjm q5PBzih3VV6ERkl0L0TkBSKakgMoP+dhSenb1cuGfuLAPk9BdUAhQ0/hFsSjRawxba2t mRSQ==
X-Received: by 10.180.77.35 with SMTP id p3mr68788242wiw.18.1357317014844; Fri, 04 Jan 2013 08:30:14 -0800 (PST)
Received: from McAsterix.local (dhcp-077-250-051-060.chello.nl. [77.250.51.60]) by mx.google.com with ESMTPS id fv2sm94493841wib.4.2013.01.04.08.30.13 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 04 Jan 2013 08:30:14 -0800 (PST)
Message-ID: <50E70396.6040806@gmail.com>
Date: Fri, 04 Jan 2013 17:30:14 +0100
From: Huub van Helvoort <huubatwork@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: "Bitar, Nabil N" <nabil.n.bitar@verizon.com>
Subject: Re: Gen-ART review of draft-ietf-pwe3-mpls-eth-oam-iwk-06
References: <CD0C3AE6.6E673%nabil.n.bitar@verizon.com>
In-Reply-To: <CD0C3AE6.6E673%nabil.n.bitar@verizon.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "sajassi@cisco.com" <sajassi@cisco.com>, "ietf@ietf.org" <ietf@ietf.org>, "Black, David" <david.black@emc.com>, "dinmohan@hotmail.com" <dinmohan@hotmail.com>, "pwe3@ietf.org" <pwe3@ietf.org>, "gen-art@ietf.org" <gen-art@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: huubatwork@gmail.com
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 04 Jan 2013 16:30:23 -0000

All,

Some nits that need to be fixed:


> ME  Maintenance Entity
>
> MEG  Maintenance Entity Group
>
> MEP Maintenance End Point

MEP  "ME End Point" or "Maintenance Entity End Point"
>
> MIP  Maintenance End Point

MIP  "ME Intermediate Point" or "Maintenance Entity Intermediate Point"



>     3.2. Terminology

> - MEP:  Maintenance End Point is responsible for origination and
> termination of OAM frames for a given MEG.

- MEP:  Maintenance Entity End Point is responsible for origination

> - MIP: Maintenance Intermediate Point is located between peer MEPs and
> can process OAM frames but does not initiate or terminate them.

- MIP: Maintenance Entity Intermediate Point is located between


Regards, Huub.

From ted.ietf@gmail.com  Fri Jan  4 09:24:48 2013
Return-Path: <ted.ietf@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8983C21F88C4 for <ietf@ietfa.amsl.com>; Fri,  4 Jan 2013 09:24:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.598
X-Spam-Level: 
X-Spam-Status: No, score=-3.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
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 Nc2NLPItC8ro for <ietf@ietfa.amsl.com>; Fri,  4 Jan 2013 09:24:47 -0800 (PST)
Received: from mail-ia0-f178.google.com (mail-ia0-f178.google.com [209.85.210.178]) by ietfa.amsl.com (Postfix) with ESMTP id 6D49721F88B4 for <ietf@ietf.org>; Fri,  4 Jan 2013 09:24:47 -0800 (PST)
Received: by mail-ia0-f178.google.com with SMTP id k25so13882418iah.37 for <ietf@ietf.org>; Fri, 04 Jan 2013 09:24:47 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=GfIt/biVORkrz+KiaLtDUmQo0qSwBQxZfR9LzrkAm/g=; b=WptCCQ2cMv81uHVVBwLb4rBFfZXga+GkvNBksB0WKwnIY3KZFsZcm8bHPCWOW3O4n9 eXSqOXSjnOEQLsiqSbNM6soHSouQqG/kstxGR4WJTpBjSk3tzXniPNlehrWCXEzCnJmg zJA/u6i7Dz3U6lFPUXrIVSM4mgEKVtzAoLpnTZ/doD2cW1HvOZF/zThmH1MssyO89rC3 RC55l5EEig4aIz/rYcVfNZETF19XrpWJgrlq6Yl3Koz5o1d1Mz5oGOX8TKeeEneuhz9d 9lRXolfjCIhfEpwczGMjW4P09jd7UTnG70UHR83xSpzqodRgleDjOq09m53pH/FPYTr0 ph+g==
MIME-Version: 1.0
Received: by 10.50.0.176 with SMTP id 16mr691539igf.70.1357320286969; Fri, 04 Jan 2013 09:24:46 -0800 (PST)
Received: by 10.43.94.5 with HTTP; Fri, 4 Jan 2013 09:24:46 -0800 (PST)
In-Reply-To: <00fd01cdea16$c956c720$5c045560$@tndh.net>
References: <CAMm+Lwh2cHRY+Dk2_SDtZZmUbPcgRpP89u3DHUcniJDrKrX_pw@mail.gmail.com> <CAMzo+1a0-90dnjnvs48a9DcNN9DY_edF5hH0__4XRuCaLHtL6Q@mail.gmail.com> <CAMm+LwjzjLc2-=4EdxwHOi21B3dOBUohYc5hhXZHL_Pk+iBBmQ@mail.gmail.com> <6.2.5.6.2.20121229192941.0aae33e8@resistor.net> <CAMm+LwiC0xtJU4vnGFPvAG4VKZdj7Tf3LfW0+pzwxKWTegRREw@mail.gmail.com> <a06240800cd074efd45b8@10.0.1.3> <CAMm+Lwiq+DCzXw572wKs78DG+XzYsJtwCVSPvNuVHSrT=Cr2nA@mail.gmail.com> <a06240809cd0799fee029@10.0.1.3> <50E29EE0.1080107@gmail.com> <50E32CAA.4040507@tana.it> <8C48B86A895913448548E6D15DA7553B72A8D6@xmb-rcd-x09.cisco.com> <00fd01cdea16$c956c720$5c045560$@tndh.net>
Date: Fri, 4 Jan 2013 09:24:46 -0800
Message-ID: <CA+9kkMBAm4S5s+sxXuVfp8vZMgZUvBG3YkOiCtegfpA+095_rA@mail.gmail.com>
Subject: Re: WCIT outcome?
From: Ted Hardie <ted.ietf@gmail.com>
To: Tony Hain <alh-ietf@tndh.net>
Content-Type: multipart/alternative; boundary=e89a8f5030ee8d1e4804d279c11c
Cc: ietf@ietf.org, lynn.st.amour@isoc.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 04 Jan 2013 17:24:48 -0000

--e89a8f5030ee8d1e4804d279c11c
Content-Type: text/plain; charset=ISO-8859-1

On Thu, Jan 3, 2013 at 4:59 PM, Tony Hain <alh-ietf@tndh.net> wrote:

> Like it or not, governments are fundamentally opposed to the open nature of
> 'the Internet', and they always will be (even the 'reasonable' ones).
> Managing information flow is how they derive and exercise power
>

Aside from the whole "consent of the governed" issue, this perspective
seems historically fairly short-sighted.  Fox's "History in Geographic
Perspective: the other France" lays out a fairly well-documented case for
modeling the trade networks of a country in geographic terms.  Some of
those are easily controlled by a nation states, river tolls being a great
example.  Others are not: the trade of ocean-going vessels left national
control then as now.  This set up an international network that had
enormous economic and cultural influences during the period he describes
(port city cultures in different trading nations often looked a lot closer
to each other than to the culture of the towns of the interior, for
example).

Yes, there were treaty-based efforts to set some common understandings.
Some of those were quite useful, but whenever they actually impinged on
workings of the real network you got smuggling.  In some cases, lots and
lots of it, with encouragement from some of the participating nations.   In
other words, some countries tried to control their participants in these
international networks very tightly.  Some were content to let their
merchants get fat off it instead.  There was no universal response.

I suspect someone much brighter than I am could write a similar analysis
for the Internet.  The network has changed what the boundaries are from the
traditional geographic boundaries of river basin, port, and railroad gauge
to a set of topologies instantiated in fiber networks and interconnects.
Where the network is entirely under the control of a nation-state, it will
find it easy to exercise sovereignty (whatever its reasons for doing so).
But it is very clear that this is not the only case.  *Whenever* the value
the network provides is derived from interconnects outside a single
nation's borders, that sovereignty is much harder to assert (or even
assess).  When the topology is relatively changeable, it is also hard to
use bilateral agreements to manage the relationship--when traffic from Den
Haag can move to Paris via the LINX instead of AMS-IX in an instant, a
Dutch-French bilateral agreement just doesn't do the trick.  It is even
trickier when the traffic from Den Haag to Haarlem goes via the LINX.

In this new effort at a multilateral framework, we are seeing a clash
between a desire for sovereign control of the Internet and a desire to reap
the benefits of open participation.  I think our role in that is to make
sure all involved understand:  the benefits of the Internet's network
effect; the risks in allowing nations through which traffic passes to
assert sovereignty over the flows, especially given both the pace and
chance of topological change; and the reality that entities outside of
governments control the paths that packets actual traverse.

That we already have some government who understand that is a good start,
but we have to keep working at it to avoid damage we can't route round.  I
personally want to thank Lynn and the Internet Society staff for all their
advocacy, as well as those IETF participants who were at WCIT with national
delegations.  It is, of necessity, arduous work, but well worth both the
effort and the thanks of our community.

regards,

Ted Hardie

--e89a8f5030ee8d1e4804d279c11c
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On Thu, Jan 3, 2013 at 4:59 PM, Tony Hain <span dir=3D"ltr">&lt;<a href=3D"=
mailto:alh-ietf@tndh.net" target=3D"_blank">alh-ietf@tndh.net</a>&gt;</span=
> wrote:<br><div class=3D"gmail_quote"><blockquote class=3D"gmail_quote" st=
yle=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">


Like it or not, governments are fundamentally opposed to the open nature of=
<br>
&#39;the Internet&#39;, and they always will be (even the &#39;reasonable&#=
39; ones).<br>
Managing information flow is how they derive and exercise power<br></blockq=
uote><div><br>Aside from the whole &quot;consent of the governed&quot; issu=
e, this perspective seems historically fairly short-sighted.=A0 Fox&#39;s &=
quot;History in Geographic Perspective: the other France&quot; lays out a f=
airly well-documented case for modeling the trade networks of a country in =
geographic terms.=A0 Some of those are easily controlled by a nation states=
, river tolls being a great example.=A0 Others are not: the trade of ocean-=
going vessels left national control then as now.=A0 This set up an internat=
ional network that had enormous economic and cultural influences during the=
 period he describes (port city cultures in different trading nations often=
 looked a lot closer to each other than to the culture of the towns of the =
interior, for example).=A0 <br>
<br>Yes, there were treaty-based efforts to set some common understandings.=
=A0 Some of those were quite useful, but whenever they actually impinged on=
 workings of the real network you got smuggling.=A0 In some cases, lots and=
 lots of it, with encouragement from some of the participating nations.=A0=
=A0 In other words, some countries tried to control their participants in t=
hese international networks very tightly.=A0 Some were content to let their=
 merchants get fat off it instead.=A0 There was no universal response.<br>
<br>
I suspect someone much brighter than I am could write a similar analysis fo=
r the Internet.=A0 The network has changed what the boundaries are from the=
 traditional geographic boundaries of river basin, port, and railroad gauge=
 to a set of topologies instantiated in fiber networks and interconnects.=
=A0 Where the network is entirely under the control of a nation-state, it w=
ill find it easy to exercise sovereignty (whatever its reasons for doing so=
).=A0 But it is very clear that this is not the only case.=A0 *Whenever* th=
e value the network provides is derived from interconnects outside a single=
 nation&#39;s borders, that sovereignty is much harder to assert (or even a=
ssess).=A0 When the topology is relatively changeable, it is also hard to u=
se bilateral agreements to manage the relationship--when traffic from Den H=
aag can move to Paris via the LINX instead of AMS-IX in an instant, a Dutch=
-French bilateral agreement just doesn&#39;t do the trick.=A0 It is even tr=
ickier when the traffic from Den Haag to Haarlem goes via the LINX.<br>

<br>In this new effort at a multilateral framework, we are seeing a clash b=
etween a desire for sovereign control of the Internet and a desire to reap =
the benefits of open participation.=A0 I think our role in that is to make =
sure all involved understand:=A0 the benefits of the Internet&#39;s network=
 effect; the risks in allowing nations through which traffic passes to asse=
rt sovereignty over the flows, especially given both the pace and chance of=
 topological change; and the reality that entities outside of governments c=
ontrol the paths that packets actual traverse.=A0 <br>
<br>That we already have some government who understand that is a good star=
t, but we have to keep working at it to avoid damage we can&#39;t route rou=
nd.=A0 I personally want to thank Lynn and the Internet Society staff for a=
ll their advocacy, as well as those IETF participants who were at WCIT with=
 national delegations.=A0 It is, of necessity, arduous work, but well worth=
 both the effort and the thanks of our community.<br>
<br>regards,<br><br>Ted Hardie<br></div></div>

--e89a8f5030ee8d1e4804d279c11c--

From braden@isi.edu  Fri Jan  4 09:57:20 2013
Return-Path: <braden@isi.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2B5BD21F857E for <ietf@ietfa.amsl.com>; Fri,  4 Jan 2013 09:57:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 NBgQtCsvYstZ for <ietf@ietfa.amsl.com>; Fri,  4 Jan 2013 09:57:19 -0800 (PST)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by ietfa.amsl.com (Postfix) with ESMTP id 0176921F857A for <ietf@ietf.org>; Fri,  4 Jan 2013 09:57:18 -0800 (PST)
Received: from [128.9.168.81] (rtb.isi.edu [128.9.168.81]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id r04Huep2006151 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 4 Jan 2013 09:56:40 -0800 (PST)
Message-ID: <50E717D8.50003@isi.edu>
Date: Fri, 04 Jan 2013 09:56:40 -0800
From: Bob Braden <braden@isi.edu>
Organization: USC/ISI
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: I'm struggling with 2219 language again
References: <7ED55FF1-3E1A-4DF7-918E-07790517B848@softarmor.com> <50E68CB5.4010107@gmail.com>
In-Reply-To: <50E68CB5.4010107@gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: braden@isi.edu
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: braden@isi.edu
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 04 Jan 2013 17:57:20 -0000

I believe that Brian's interpretation is exactly right. At least, it 
conforms to the Original Intent of the
applicability terms MUST, MAY, and SHOULD as defined in RFC 1122. And I 
sympathize with
Dean Willis whose head hurts; as one-time RFC Editor I was often 
confronted with wildly
inconsistent use of the applicability words. It often seemed that 
authors sprinkled them in
randomly, just enough seasoning to make a normative stew.

Bob Braden

. On 1/4/2013 12:03 AM, Brian E Carpenter wrote:
> On 04/01/2013 05:15, Dean Willis wrote:
> ...
>> Either way, I'd like to see some consensus. Because my head is throbbing and I want to know if it MUST hurt, SHOULD hurst, or just hurts. But I MUST proceed in accordance with consensus, because to do otherwise would undermine the clarity of our entire specification family.
> This Gen-ART reviewer believes that words like "must" have well defined meanings
> in the English language, so shouting is not needed at every use. There are
> standards track documents that don't use RFC 2119 at all, and I am not only
> referring to RFC 791.
>
> I think the upper case keywords should be used only when necessary to clarify
> points of potential non-interoperability or insecurity. I'm quite sure that
> I've broken that recommendation quite often, and it will always remain
> a judgment call. However, inserting a MUST in every sentence that describes
> behaviour is surely going too far. I guess the test is whether a reasonably
> careful reader might interpret a sentence incorrectly while writing code;
> and if so, would a normative keyword help?
>
>       Brian


From swb@internet2.edu  Fri Jan  4 10:05:23 2013
Return-Path: <swb@internet2.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4CA2821F8967 for <ietf@ietfa.amsl.com>; Fri,  4 Jan 2013 10:05:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 AS8stGVbqJll for <ietf@ietfa.amsl.com>; Fri,  4 Jan 2013 10:05:22 -0800 (PST)
Received: from va3outboundpool.messaging.microsoft.com (va3ehsobe010.messaging.microsoft.com [216.32.180.30]) by ietfa.amsl.com (Postfix) with ESMTP id 3B2AA21F8960 for <ietf@ietf.org>; Fri,  4 Jan 2013 10:05:22 -0800 (PST)
Received: from mail162-va3-R.bigfish.com (10.7.14.249) by VA3EHSOBE010.bigfish.com (10.7.40.12) with Microsoft SMTP Server id 14.1.225.23; Fri, 4 Jan 2013 18:05:19 +0000
Received: from mail162-va3 (localhost [127.0.0.1])	by mail162-va3-R.bigfish.com (Postfix) with ESMTP id 4A2F51602E1; Fri,  4 Jan 2013 18:05:19 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.232.53; KIP:(null); UIP:(null); IPV:NLI; H:BLUPRD0811HT003.namprd08.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: 3
X-BigFish: S3(zzzz1d77h1de0h1202h1e76h1d1ah1d2ah1082kzzz2dh2a8h668h839h947hd25he5bhf0ah1288h12a5h12a9h12bdh137ah13b6h1441h1504h1537h153bh162dh1631h1758h1765h1155h)
Received: from mail162-va3 (localhost.localdomain [127.0.0.1]) by mail162-va3 (MessageSwitch) id 1357322716739962_11961; Fri,  4 Jan 2013 18:05:16 +0000 (UTC)
Received: from VA3EHSMHS028.bigfish.com (unknown [10.7.14.247])	by mail162-va3.bigfish.com (Postfix) with ESMTP id A653710004B; Fri,  4 Jan 2013 18:05:16 +0000 (UTC)
Received: from BLUPRD0811HT003.namprd08.prod.outlook.com (157.56.232.53) by VA3EHSMHS028.bigfish.com (10.7.99.38) with Microsoft SMTP Server (TLS) id 14.1.225.23; Fri, 4 Jan 2013 18:05:16 +0000
Received: from swbi2mbp.local (67.241.75.185) by pod51019.outlook.com (10.255.123.38) with Microsoft SMTP Server (TLS) id 14.16.245.2; Fri, 4 Jan 2013 18:05:15 +0000
Message-ID: <50E719DA.1040709@internet2.edu>
Date: Fri, 4 Jan 2013 13:05:14 -0500
From: Scott Brim <swb@internet2.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: Dean Willis <dean.willis@softarmor.com>
Subject: Re: I'm struggling with 2219 language again
References: <7ED55FF1-3E1A-4DF7-918E-07790517B848@softarmor.com>
In-Reply-To: <7ED55FF1-3E1A-4DF7-918E-07790517B848@softarmor.com>
X-Enigmail-Version: 1.4.6
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
X-Originating-IP: [67.241.75.185]
X-OriginatorOrg: internet2.edu
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 04 Jan 2013 18:05:23 -0000

It's a communication problem.  If you want your audience to understand
exactly what you're saying, and implement along very specific lines, you
need to tell them in a way they understand.  Personally I prefer a
quieter approach, but I've been told that these days one MUST use MUST
or implementors just won't get it.  "Huh, that's a requirement?  But you
didn't say MUST."  I suggest turning this thread into a survey, and
finding out how people who actually write code look for in order to know
what's required.


From stpeter@stpeter.im  Fri Jan  4 10:15:14 2013
Return-Path: <stpeter@stpeter.im>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2DAA221F87D2 for <ietf@ietfa.amsl.com>; Fri,  4 Jan 2013 10:15:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 30RlVjX1h1cJ for <ietf@ietfa.amsl.com>; Fri,  4 Jan 2013 10:15:12 -0800 (PST)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id 5E05B21F87CC for <ietf@ietf.org>; Fri,  4 Jan 2013 10:15:03 -0800 (PST)
Received: from [10.129.24.89] (unknown [128.107.239.233]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id C87E34005D for <ietf@ietf.org>; Fri,  4 Jan 2013 11:19:56 -0700 (MST)
Message-ID: <50E71C24.1000701@stpeter.im>
Date: Fri, 04 Jan 2013 11:15:00 -0700
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: I'm struggling with 2219 language again
References: <7ED55FF1-3E1A-4DF7-918E-07790517B848@softarmor.com> <50E719DA.1040709@internet2.edu>
In-Reply-To: <50E719DA.1040709@internet2.edu>
X-Enigmail-Version: 1.4.6
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 04 Jan 2013 18:15:14 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Wonderful perennial topic. :)

As I always say when this comes up, when writing drafts I've settled
on using the 2119 keywords only in their uppercase form, and otherwise
using "need to", "ought to", "might" (etc.) to avoid all possible
confusion. Sure, it's a bit stilted, but we're not writing gorgeous
prose here, we're writing technical specifications that need to be
completely clear.

Peter

- --
Peter Saint-Andre
https://stpeter.im/

-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.18 (Darwin)
Comment: Using GnuPG with undefined - http://www.enigmail.net/

iEYEARECAAYFAlDnHCQACgkQNL8k5A2w/vxKmwCfXKjDtMqQiPp4a0udOB8Q9IbA
q9QAoNiXj2r/q4yRLp0B/13m6Xxg5YN4
=3PER
-----END PGP SIGNATURE-----

From hsantos@isdg.net  Fri Jan  4 10:37:03 2013
Return-Path: <hsantos@isdg.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2240321F872D for <ietf@ietfa.amsl.com>; Fri,  4 Jan 2013 10:37:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 0-xK+jTikU3u for <ietf@ietfa.amsl.com>; Fri,  4 Jan 2013 10:37:00 -0800 (PST)
Received: from listserv.winserver.com (news.winserver.com [208.247.131.9]) by ietfa.amsl.com (Postfix) with ESMTP id C721721F872C for <ietf@ietf.org>; Fri,  4 Jan 2013 10:36:59 -0800 (PST)
DKIM-Signature: v=1; d=isdg.net; s=tms1; a=rsa-sha1; c=simple/relaxed; l=5520; t=1357324614; h=Received:Received: Received:Received:Message-ID:Date:From:Organization:To:Subject: List-ID; bh=MODMgC2YzKMYZ4mI9ouzhZCEIy0=; b=DuFHwizevHZgYFBAP2GQ UvyUsZ8p4dR5XLGFMDhTgAQs8y7rjIkZJCMbQoFN0Y3Jc9uAj6ljdlCJaVy/zDGy UyVz37wUvEZRgUU1CNAG+eDnoIifYO3UM3OqLUBmUn+E9/qbHg4n2/NIdks7Lv0/ 5TievhKu6b9D+t07hxeMSvU=
Received: by winserver.com (Wildcat! SMTP Router v7.0.454.4) for ietf@ietf.org; Fri, 04 Jan 2013 13:36:54 -0500
Authentication-Results: dkim.winserver.com; dkim=pass header.d=beta.winserver.com header.s=tms1 header.i=beta.winserver.com;  adsp=pass policy=all author.d=isdg.net asl.d=beta.winserver.com;
Received: from beta.winserver.com ([208.247.131.23]) by winserver.com (Wildcat! SMTP v7.0.454.4) with ESMTP id 461376777.5411.4132; Fri, 04 Jan 2013 13:36:53 -0500
DKIM-Signature: v=1; d=beta.winserver.com; s=tms1; a=rsa-sha256; c=simple/relaxed; l=5520; t=1357324568; h=Received:Received: Message-ID:Date:From:Organization:To:Subject:List-ID; bh=tep9/J3 PgfV+U3osboFv4my82xy7OwlTzG4CD0ZAOWI=; b=Di0EdfVRN4VJI8zTERhmnU/ FwVWc5Qcs58l/h36HTRttx+TYByxKy/7UIjpJGG72Gf7OayRMgnRGWIC4mTwHphk qjFCnwKJx2iK8U+xRKIPEDrnPjyfq/XA1pjr8YEaxddjMrxR2WVCkCYeh49fM8rt 6oPex0VAOhO9DQRDuoFk=
Received: by beta.winserver.com (Wildcat! SMTP Router v7.0.454.4) for ietf@ietf.org; Fri, 04 Jan 2013 13:36:08 -0500
Received: from [192.168.1.101] ([99.3.147.93]) by beta.winserver.com (Wildcat! SMTP v7.0.454.4) with ESMTP id 1060083992.10.7172; Fri, 04 Jan 2013 13:36:07 -0500
Message-ID: <50E72161.1020101@isdg.net>
Date: Fri, 04 Jan 2013 13:37:21 -0500
From: Hector Santos <hsantos@isdg.net>
Organization: Santronics Software, Inc.
User-Agent: Thunderbird 2.0.0.24 (Windows/20100228)
MIME-Version: 1.0
To: Lou Berger <lberger@labn.net>
Subject: Re: I'm struggling with 2219 language again
References: <7ED55FF1-3E1A-4DF7-918E-07790517B848@softarmor.com> <50E6D7CB.6050905@labn.net>
In-Reply-To: <50E6D7CB.6050905@labn.net>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org, Dean Willis <dean.willis@softarmor.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 04 Jan 2013 18:37:03 -0000

+1.

I think it is important that we have communications tools for 
documenting strong minimum protocol requirements and we only have 
RFC2119 to make that possible.

Yet, we need to be careful where the lack of RFC2119 upper case 
wordings can be used to leverage an argument for relaxation of 
existing protocols where perhaps only lower case semantics were done.

IMO, where there are multiple protocol state choices or paths and 
where common sense engineering and security functionality is clear, 
upper vs lower should not matter.

I will like to use an example protocol logic I am currently concern 
with that could be altered due to 2119 related debates:

   For protocol state condition A, you may do action B or C.
   If action B is taken, you MUST do D.

So action B has 2119 language to do D.  Part of the 2219 debate is 
that doing action B or C are both optional.

C is not defined, although it could be said it was implied via other 
indirect protocol features:

   You SHOULD do E.

and in a protocol change proposal, it is now:

   You SHOULD do E1 instead of E.

Well, to do E or E1, you have to do C, not B.

Now the history of this is that original drafts/specs (ones some folks 
want us to ignore) did have 2119 language on whether you MAY do B or 
C, and in fact in an extended augmented RFC protocol, it only allowed 
for a MUST action B for protocol condition A.  C was not an option (or 
at least it wasn't stated) in the extended RFC technology.

The problem was the lack of an upper case MAY has provided the notion 
that none of this is normative thus making the action C more possible 
and action B less attractive.

By making C more possible, this makes E more plausible and now that E1 
is a new recommendation and preferred feature than E,  the idea of 
doing action B is now watered down.

The issue is sensitive and honestly, it got to a point where one says 
  "Who cares!?" If they want to watered down B, so be it.  You don't 
need to support it protocol changes nor the newer push to the E1 
recommendation.

The problem for me?

Is why is the security aspects of this do not make it obvious of what 
needs to be done?  We got into anal debate of 2119 language and I even 
recall a few years ago where another debate of the definition of 
SHOULD got a number of people labeled as 2219 illiterates by an AD.

In the example I cited, politics comes into play because you have two 
industry mindsets under protocol condition A:

   1) Those that believe in action B as the more secured action, and
   2) Those that DO NOT believe in action B and prefer C.

There is where a person like myself is left with the idea of waiting 
for WGLC to appeal changes to the protocol that will watered down 
action B.

This is all due because of the lack of 2119 language that many believe 
were naturally in place with just using lower case wordings.

No upper case, therefore action B is weak and that was unfair to 
current implementations that only do action B as its the most secured 
implementation (and less costly) action to protect users.   By 
allowing RFC2119 or stated arguments the protocol lacked 2119 
language, weakens the protocol and makes it more complex for 
implementations to consider action C which can be more harmful if 
certain forms of C making it functionality equivalent (security wise) 
to action B is not done (this is the added complexity).

I'm sure this is a dime a dozen story, but to me it is common to see 
WG chairs, AD and other key cogs throw the proverbial 2119 book at 
developers to help push specs.   IMO, we need it but we also need some 
common sense engineering and consideration to be done when we review 
current docs.  Ignoring existing implementations SHOULD not be one of 
them.

-- 
HLS


Lou Berger wrote:
> 
> On 1/4/2013 12:15 AM, Dean Willis wrote:
> ...
>> Are we deliberately evolving our language to use RFC 2119 terms as
>> the principle verbs  of a formal specification language?
> ...
> 
> My view on this has evolved over time.  I used to follow the practice of
> using 2219 language only for emphasis.  Over time, primarily motivated
> by reviewers comments and reader questions, I've migrated to the
> position that 2119 language should be used whenever and wherever a point
> of conformance is being made.  While this may be a bit of an extreme
> position, it ensures that authors, reviewers, readers, implementors,
> etc. are in sync as to what is expected from an interoperable
> implementation that conforms to a standard.  I think the importance of
> such unambiguity has increased over time as the number of implementors
> and non-native English speakers in our community have increased.
> 
> I also think it's important to follow section 6 of 2119, i.e., if it's
> not a point of interoperability or harmful behavior, there's no need to
> use 2119 conformance language.
> 
> So, my view is now:
> 
> a) lower case usage of 2119 key words *in RFCs* means the normal English
> meaning of such words, but does not place any requirement on
> implementations, i.e., is purely informative text.
> 
> b) upper case usage of 2119 key words *in RFCs*, as stated in [RFC2119],
> places "requirements in the specification", i.e., is conformance
> language with which an implementation must follow to ensure
> interoperability (or harm).  (And does not = shouting as would be the
> case in other contexts).
> 
> I take this view when writing and reviewing PS drafts...
> 
> Lou
> 
> 





From paf@frobbit.se  Fri Jan  4 10:55:50 2013
Return-Path: <paf@frobbit.se>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 670FA21F8809 for <ietf@ietfa.amsl.com>; Fri,  4 Jan 2013 10:55:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.891
X-Spam-Level: *
X-Spam-Status: No, score=1.891 tagged_above=-999 required=5 tests=[BAYES_50=0.001, HELO_EQ_SE=0.35, MIME_8BIT_HEADER=0.3, SARE_LWSHORTT=1.24]
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 nGT2VtV1K4hF for <ietf@ietfa.amsl.com>; Fri,  4 Jan 2013 10:55:49 -0800 (PST)
Received: from mail.frobbit.se (mail.frobbit.se [85.30.129.176]) by ietfa.amsl.com (Postfix) with ESMTP id 4487B21F87ED for <ietf@ietf.org>; Fri,  4 Jan 2013 10:55:49 -0800 (PST)
Received: from [IPv6:2a02:80:3ffc::14] (unknown [IPv6:2a02:80:3ffc::14]) by mail.frobbit.se (Postfix) with ESMTPSA id 090F120115; Fri,  4 Jan 2013 19:55:46 +0100 (CET)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Subject: Re: WCIT outcome?
From: =?windows-1252?Q?Patrik_F=E4ltstr=F6m?= <paf@frobbit.se>
In-Reply-To: <00fd01cdea16$c956c720$5c045560$@tndh.net>
Date: Fri, 4 Jan 2013 19:55:45 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <CA56BFA0-3CA1-499D-AD13-0406F9E48D63@frobbit.se>
References: <CAMm+Lwh2cHRY+Dk2_SDtZZmUbPcgRpP89u3DHUcniJDrKrX_pw@mail.gmail.com>	<CAMzo+1a0-90dnjnvs48a9DcNN9DY_edF5hH0__4XRuCaLHtL6Q@mail.gmail.com>	<CAMm+LwjzjLc2-=4EdxwHOi21B3dOBUohYc5hhXZHL_Pk+iBBmQ@mail.gmail.com>	<6.2.5.6.2.20121229192941.0aae33e8@resistor.net>	<CAMm+LwiC0xtJU4vnGFPvAG4VKZdj7Tf3LfW0+pzwxKWTegRREw@mail.gmail.com>	<a06240800cd074efd45b8@10.0.1.3>	<CAMm+Lwiq+DCzXw572wKs78DG+XzYsJtwCVSPvNuVHSrT=Cr2nA@mail.gmail.com>	<a06240809cd0799fee029@[10.0.1.3]> <50E29EE0.1080107@gmail.com>	<50E32CAA.4040507@tana.it> <8C48B86A895913448548E6D15DA7553B72A8D6@xmb-rcd-x09.cisco.com> <00fd01cdea16$c956c720$5c045560$@tndh.net>
To: "ietf@ietf.org Mailing List" <ietf@ietf.org>
X-Mailer: Apple Mail (2.1499)
Cc: lynn.st.amour@isoc.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 04 Jan 2013 18:55:50 -0000

On 4 jan 2013, at 01:59, Tony Hain <alh-ietf@tndh.net> wrote:

> Like it or not, governments are fundamentally opposed to the open =
nature of
> 'the Internet', and they always will be (even the 'reasonable' ones).

Because I do not think generalization is really a reasonable thing to =
do, and even dangerous when discussing governance issues, I disagree =
with this statement.

Governments want just like businesses success in whatever they do. That =
can in general be divided in two wishes. Short term, in the form of =
being re-elected (or not thrown out of their office) and long term, as =
in growth of the revenue of the country they govern.

They of course have pieces of their operation that belong to law =
enforcement agencies, but they also have those that are responsible of =
finding rules so that non-public sector can grow (to later increase for =
example tax revenue).

Because of this, I encourage people to not generalize per stakeholder =
group, but instead acknowledge that there are different *forces* that =
are orthogonal to each other, and calculating "the correct" balance =
between them is hard. Or rather, different people do for different =
reasons get different results when calculating what the for them proper =
balance is.

That is why I personally am against generalization that a stakeholder =
group have one specific view.

Specifically governments.

If when pushed to be forced to choose between two choices *all* =
governments wanted to have control, we would have had many more =
governments signing the proposed treaty that was on the table in Dubai.

Instead, when being forced to choose, they picked openness and multi =
stakeholder bottom up processes.

Just like what happened earlier during 2012 when in A/HRC/20/L.13 UN(*) =
concluded =
(<http://www.regeringen.se/content/1/c6/19/64/51/6999c512.pdf>:

> 1. Affirms that the same rights that people have offline must also be =
protected online, in particular freedom of expression, which is =
applicable regardless of frontiers and through any media of one=92s =
choice, in accordance with articles 19 of the Universal Declaration of =
Human Rights and the International Covenant on Civil and Political =
Rights;
>=20
> 2. Recognizes the global and open nature of the Internet as a driving =
force in accelerating progress towards development in its various forms;
>=20
> 3. Calls upon all States to promote and facilitate access to the =
Internet and international cooperation aimed at the development of media =
and information and communications facilities in all countries;
>=20
> 4. Encourages special procedures to take these issues into account =
within their existing mandates, as applicable;
>=20
> 5. Decides to continue its consideration of the promotion, protection =
and enjoyment of human rights, including the right to freedom of =
expression, on the Internet and in other technologies, as well as of how =
the Internet can be an important tool for development and for exercising =
human rights, in accordance with its programme of work.

   Patrik

(*) Algeria, Argentina, Australia, Austria, Azerbaijan, Belgium, Bolivia =
(Plurinational State of), Bosnia and Herzegovina, Brazil, Bulgaria, =
Canada, Chile, Costa Rica, C=F4te d=92Ivoire, Croatia, Cyprus, Czech =
Republic, Denmark, Djibouti, Egypt, Estonia, Finland, France, Georgia, =
Germany, Greece, Guatemala, Honduras, Hungary, Iceland, India, =
Indonesia, Ireland, Italy, Latvia, Libya, Liechtenstein, Lithuania, =
Luxembourg, Maldives, Malta, Mauritania, Mexico, Monaco, Montenegro, =
Morocco, Netherlands, Nigeria, Norway, Palestine, Peru, Poland, =
Portugal, Qatar, Republic of Moldova, Republic of Korea, Romania, =
Serbia, Slovakia, Slovenia, Somalia, Spain, Sweden, the former Yugoslav =
Republic of Macedonia, Timor-Leste, Tunisia, Turkey, Ukraine, United =
Kingdom of Great Britain and Northern Ireland, United States of America =
and Uruguay)


From rbarnes@bbn.com  Fri Jan  4 11:04:53 2013
Return-Path: <rbarnes@bbn.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3E14921F882B for <ietf@ietfa.amsl.com>; Fri,  4 Jan 2013 11:04:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 oJu0wWk3iYUW for <ietf@ietfa.amsl.com>; Fri,  4 Jan 2013 11:04:52 -0800 (PST)
Received: from smtp.bbn.com (smtp.bbn.com [128.33.0.80]) by ietfa.amsl.com (Postfix) with ESMTP id 9BE0C21F8753 for <ietf@ietf.org>; Fri,  4 Jan 2013 11:04:52 -0800 (PST)
Received: from ros-dhcp192-1-51-63.bbn.com ([192.1.51.63]:49448) by smtp.bbn.com with esmtps (TLSv1:AES128-SHA:128) (Exim 4.77 (FreeBSD)) (envelope-from <rbarnes@bbn.com>) id 1TrCZX-000CPl-KS; Fri, 04 Jan 2013 14:04:51 -0500
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Subject: Re: I'm struggling with 2219 language again
From: Richard Barnes <rbarnes@bbn.com>
In-Reply-To: <50E71C24.1000701@stpeter.im>
Date: Fri, 4 Jan 2013 14:04:51 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <156C25BD-1769-44C5-87B1-3BD670A1B2E0@bbn.com>
References: <7ED55FF1-3E1A-4DF7-918E-07790517B848@softarmor.com> <50E719DA.1040709@internet2.edu> <50E71C24.1000701@stpeter.im>
To: Peter Saint-Andre <stpeter@stpeter.im>
X-Mailer: Apple Mail (2.1499)
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 04 Jan 2013 19:04:53 -0000

Anecdotal data point number N+1...

As an occasional implementor of IETF specs, I have to say it's much =
easier to check my conformance if I can just grep for "MUST" and =
"SHOULD".  It's also easy for developers to get in the bad habit of ONLY =
doing those things that are clearly marked in that way.  So ISTM that if =
you're not tagging things you want done with RFC 2119 language, then =
you're risking people not implementing them.



On Jan 4, 2013, at 1:15 PM, Peter Saint-Andre <stpeter@stpeter.im> =
wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>=20
> Wonderful perennial topic. :)
>=20
> As I always say when this comes up, when writing drafts I've settled
> on using the 2119 keywords only in their uppercase form, and otherwise
> using "need to", "ought to", "might" (etc.) to avoid all possible
> confusion. Sure, it's a bit stilted, but we're not writing gorgeous
> prose here, we're writing technical specifications that need to be
> completely clear.
>=20
> Peter
>=20
> - --
> Peter Saint-Andre
> https://stpeter.im/
>=20
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG/MacGPG2 v2.0.18 (Darwin)
> Comment: Using GnuPG with undefined - http://www.enigmail.net/
>=20
> iEYEARECAAYFAlDnHCQACgkQNL8k5A2w/vxKmwCfXKjDtMqQiPp4a0udOB8Q9IbA
> q9QAoNiXj2r/q4yRLp0B/13m6Xxg5YN4
> =3D3PER
> -----END PGP SIGNATURE-----


From adrian@olddog.co.uk  Fri Jan  4 11:18:43 2013
Return-Path: <adrian@olddog.co.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AA01321F8880 for <ietf@ietfa.amsl.com>; Fri,  4 Jan 2013 11:18:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.842
X-Spam-Level: 
X-Spam-Status: No, score=-1.842 tagged_above=-999 required=5 tests=[AWL=0.757,  BAYES_00=-2.599]
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 Ml-xGDmCm2DP for <ietf@ietfa.amsl.com>; Fri,  4 Jan 2013 11:18:43 -0800 (PST)
Received: from asmtp2.iomartmail.com (asmtp2.iomartmail.com [62.128.201.249]) by ietfa.amsl.com (Postfix) with ESMTP id D548A21F88B2 for <ietf@ietf.org>; Fri,  4 Jan 2013 11:18:42 -0800 (PST)
Received: from asmtp2.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp2.iomartmail.com (8.13.8/8.13.8) with ESMTP id r04JIZRi029828;  Fri, 4 Jan 2013 19:18:41 GMT
Received: from 950129200 (089144192219.atnat0001.highway.a1.net [89.144.192.219]) (authenticated bits=0) by asmtp2.iomartmail.com (8.13.8/8.13.8) with ESMTP id r04JIUgf029777;  Fri, 4 Jan 2013 19:18:34 GMT
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "'Lou Berger'" <lberger@labn.net>, "'Dean Willis'" <dean.willis@softarmor.com>
References: <7ED55FF1-3E1A-4DF7-918E-07790517B848@softarmor.com> <50E6D7CB.6050905@labn.net>
In-Reply-To: <50E6D7CB.6050905@labn.net>
Subject: RE: I'm struggling with 2219 language again
Date: Fri, 4 Jan 2013 19:18:30 -0000
Message-ID: <06cd01cdeab0$4b5c8270$e2158750$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQJUvWn7iBQGZM1RkOakWodgojs72wGNIoRclx9osHA=
Content-Language: en-gb
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: adrian@olddog.co.uk
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 04 Jan 2013 19:18:43 -0000

Lou's view matches how I write and review documents.
I would add that there is sometimes value in using 2119-style language in
requirements documents ("The protocol solution MUST enable transmission of
data...") although, in my opinion, this requires a tweak to the normal2119
boilerplate.

Adrian

> -----Original Message-----
> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of Lou
> Berger
> Sent: 04 January 2013 13:23
> To: Dean Willis
> Cc: ietf@ietf.org
> Subject: Re: I'm struggling with 2219 language again
> 
> 
> 
> On 1/4/2013 12:15 AM, Dean Willis wrote:
> ...
> > Are we deliberately evolving our language to use RFC 2119 terms as
> > the principle verbs  of a formal specification language?
> ...
> 
> My view on this has evolved over time.  I used to follow the practice of
> using 2219 language only for emphasis.  Over time, primarily motivated
> by reviewers comments and reader questions, I've migrated to the
> position that 2119 language should be used whenever and wherever a point
> of conformance is being made.  While this may be a bit of an extreme
> position, it ensures that authors, reviewers, readers, implementors,
> etc. are in sync as to what is expected from an interoperable
> implementation that conforms to a standard.  I think the importance of
> such unambiguity has increased over time as the number of implementors
> and non-native English speakers in our community have increased.
> 
> I also think it's important to follow section 6 of 2119, i.e., if it's
> not a point of interoperability or harmful behavior, there's no need to
> use 2119 conformance language.
> 
> So, my view is now:
> 
> a) lower case usage of 2119 key words *in RFCs* means the normal English
> meaning of such words, but does not place any requirement on
> implementations, i.e., is purely informative text.
> 
> b) upper case usage of 2119 key words *in RFCs*, as stated in [RFC2119],
> places "requirements in the specification", i.e., is conformance
> language with which an implementation must follow to ensure
> interoperability (or harm).  (And does not = shouting as would be the
> case in other contexts).
> 
> I take this view when writing and reviewing PS drafts...
> 
> Lou


From kent@bbn.com  Thu Jan  3 10:20:45 2013
Return-Path: <kent@bbn.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 92B6E21F8CBE; Thu,  3 Jan 2013 10:20:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104
X-Spam-Level: 
X-Spam-Status: No, score=-104 tagged_above=-999 required=5 tests=[RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 yqyZmjw8J98o; Thu,  3 Jan 2013 10:20:45 -0800 (PST)
Received: from smtp.bbn.com (smtp.bbn.com [128.33.1.81]) by ietfa.amsl.com (Postfix) with ESMTP id 03C9021F8CBB; Thu,  3 Jan 2013 10:20:41 -0800 (PST)
Received: from dhcp89-089-242.bbn.com ([128.89.89.242]:52601) by smtp.bbn.com with esmtp (Exim 4.77 (FreeBSD)) (envelope-from <kent@bbn.com>) id 1TqpPD-000KWl-E3; Thu, 03 Jan 2013 13:20:39 -0500
Message-ID: <50E5CBF7.7040603@bbn.com>
Date: Thu, 03 Jan 2013 13:20:39 -0500
From: Stephen Kent <kent@bbn.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: ietf@ietf.org, sidr <sidr@ietf.org>
Subject: [sidr] Last Call: <draft-ietf-sidr-algorithm-agility-08.txt> (Algorithm Agility Procedure for RPKI.) to Proposed Standard
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Fri, 04 Jan 2013 11:19:51 -0800
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Jan 2013 18:20:45 -0000

The tech report cited in Eric's message is not a critique of the SIDR 
algorithm agility
document that is the subject if this last call. The tech report is a 
critique of the overall
SIDR repository system and object retrieval paradigm, with an emphasis 
on the speed with which
relying parties (principally ISPs) will be able to acquire RPKI data. 
The RPKI repository
system is defined in RFC 6481; the RP object retrieval approach is 
described in RFC 6480.
The tech report includes assumptions about the addition of many 
instances of additional objects
(router certs) to the RPKI repository system, but these assumptions are 
based on I-Ds that are in process in SIDR, and thus may be the more 
appropriate focus of the report, in terms of responses.

The tech report includes no specific criticisms of the algorithm agility 
mechanism described by the I-D in IETF LC, nor does it suggest any 
changes to this doc. An extensive discussion of the tech report took 
place on the SIDR list, in early December. That discussion also did not 
suggest any proposed changes to the algorithm agility doc. Thus the 
authors do not plan to make any changes as a result of this comment 
being posted during IETF LC.

Steve Kent (on behalf of Roque Gagliano and Sean Turner)


From abdussalambaryun@gmail.com  Fri Jan  4 12:25:57 2013
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EB4FA21F8842 for <ietf@ietfa.amsl.com>; Fri,  4 Jan 2013 12:25:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 ULYhUTpmZBa5 for <ietf@ietfa.amsl.com>; Fri,  4 Jan 2013 12:25:53 -0800 (PST)
Received: from mail-vb0-f43.google.com (mail-vb0-f43.google.com [209.85.212.43]) by ietfa.amsl.com (Postfix) with ESMTP id A3F2221F8804 for <ietf@ietf.org>; Fri,  4 Jan 2013 12:25:53 -0800 (PST)
Received: by mail-vb0-f43.google.com with SMTP id fs19so17161910vbb.30 for <ietf@ietf.org>; Fri, 04 Jan 2013 12:25:53 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:cc:content-type; bh=RZbfc5/Lmn+Mh0Rs3F7lh9XZlB/Fj0010GHkiuk+FcE=; b=bVf3T9IWCQ+q7lhM39FDPNB9+u9IQBaRqYhbFslln8onR0K96rIEihm90QafUXYH7e XTQCbl1kVJMNPchdXiOvkkhrZvH7Ik6IJ5PMwpcs+b3rrAaQMdCj2ukYz9K+6vI2Dhd7 oHfsoBGsgH+SWc6oQ2gFDPDDf8ODECXJKqCA8equf7s8GwnLUAJpz4QwJfkm8QWerGqc AkWc8h/LeJSqLco9VGxZf64Hfnc6W65VMtWaSStkQ1aQ75K+bTBnVK9BKi/l51r2I0Ja 3jKhEZrJWNPlBizd3H9tq6PMUv5d9tmnr2jY3vq8gWtN2BSRITYxnCQbHz4XNXwj3TAw F0ZQ==
MIME-Version: 1.0
Received: by 10.52.27.50 with SMTP id q18mr68133861vdg.20.1357331153075; Fri, 04 Jan 2013 12:25:53 -0800 (PST)
Received: by 10.220.145.5 with HTTP; Fri, 4 Jan 2013 12:25:52 -0800 (PST)
Date: Fri, 4 Jan 2013 21:25:52 +0100
Message-ID: <CADnDZ8_BPe-L4M=3nWE2k2Uj8bO11uRqCxunVN=22PYDDGOAQA@mail.gmail.com>
Subject: meaning RFC 2119 (was Re:I'm struggling with 2219 language again)
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: dean.willis@softarmor.com
Content-Type: text/plain; charset=ISO-8859-1
Cc: ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 04 Jan 2013 20:25:58 -0000

Hi Dean

I agree with you which I suggested before an update to the RFC [*], I
actually writing a work in progress ID, you may give me your
suggestion if you like. I recommend you use for your work IF, THEN
rather than MUST. Easier to read.

*  http://tools.ietf.org/id/draft-baryun-rfc2119-update-00.txt

AB

>
>
> I've always held to the idea that RFC 2119 language is for defining
> levels of compliance to requirements, and is best used very sparingly
> (as recommended in RFC 2119 itself). To me, RFC 2119 language doesn't
> make behavior normative -- rather, it describes the implications of
> doing something different than the defined behavior, from "will break
> the protocol if you change it" to "we have reason to think that there
> might be a reason we don't want to describe here that might influence
> you not to do this" to "here are some reasons that would cause you to
> do something different" and on to "doing something different might
> offend the sensibilities of the protocol author, but probably won't
> hurt anything else."
>
> But I'm ghost-editing a document right now whose gen-art review
> suggested replacing the vast majority of "is" "does" and "are" prose
> with MUST. The comments seem to indicate that protocol-defining text
> not using RFC 2119 language (specifically MUST) is "not normative".
>
> This makes me cringe. But my co-editor likes it a lot. And I see smart
> people like Ole also echoing the though that RFC 2119 language is what
> makes text normative.
>
> For example, the protocol under discussion uses TLS or DTLS for a
> plethora of security reasons. So, every time the draft discusses
> sending a response to a request, we would say "the node MUST send a
> response, and this response MUST be constructed by (insert some
> concatenation procedure here) and MUST be transmitted using TLS or
> DTLS.
>
> Or, a more specific example:
>
> For the text:
>
> In order to originate a message to a given Node-ID or
> Resource-ID, a node constructs an appropriate destination list.
>
>
> The Gen-ART comment here is:
> -First sentence: "a node constructs" -> "a node MUST construct"
>
>
> We'll literally end up with hundreds of RFC 2119 invocations (mostly
> MUST) in a protocol specification.
>
> Is this a good or bad thing? My co-editor and I disagree -- he likes
> formalization of the description language, and I like the English
> prose. But it raises process questions for the IETF as a whole:
>
> Are we deliberately evolving our language to use RFC 2119 terms as the
> principle verbs  of a formal specification language?
>
> Either way, I'd like to see some consensus. Because my head is
> throbbing and I want to know if it MUST hurt, SHOULD hurst, or just
> hurts. But I MUST proceed in accordance with consensus, because to do
> otherwise would undermine the clarity of our entire specification
> family.
>
> --
> Dean
>

From abdussalambaryun@gmail.com  Fri Jan  4 12:33:29 2013
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2886C21F8880 for <ietf@ietfa.amsl.com>; Fri,  4 Jan 2013 12:33:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 DDxxe-GENSJU for <ietf@ietfa.amsl.com>; Fri,  4 Jan 2013 12:33:25 -0800 (PST)
Received: from mail-vc0-f171.google.com (mail-vc0-f171.google.com [209.85.220.171]) by ietfa.amsl.com (Postfix) with ESMTP id E275E21F86EF for <ietf@ietf.org>; Fri,  4 Jan 2013 12:33:24 -0800 (PST)
Received: by mail-vc0-f171.google.com with SMTP id n11so17245374vch.30 for <ietf@ietf.org>; Fri, 04 Jan 2013 12:33:24 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=ELmN0z4H3s59ji8IN0A16nEmd02xwcBxit6CN0/A7dE=; b=LOmiW2kWuTuRASLYiA6Tjzewxjxy4M/UuBCPZWp+4I7ppCwuuLR/ywR0p3j7KNAwV+ MBxte+yRlP3Ve3WtZ28nm/lyIpII6PuvcLmMSOnf8ItO7JNeXVCywW9/ORvlM7dtfVKu 5IfoWAm0uNYWl0YzE3Loqj2lwdDE78KK0Wz/PvPtANhagq4A2XP8jqaaD350VPzxGWZH Ff8nCuhjrDa4uwP7Ba/m7qqlTN3atS6P/RVqpzzkgWaxFDbAzyJhao2fs/pRUYrHV7zf Gs/U2kK4KuEiCHxOdhGKGjphnC3EHa1Bx9DRWs9trsmH97bZ+lkJBm4Mv86NQpWMRaCg IAew==
MIME-Version: 1.0
Received: by 10.52.27.50 with SMTP id q18mr68152029vdg.20.1357331604174; Fri, 04 Jan 2013 12:33:24 -0800 (PST)
Received: by 10.220.145.5 with HTTP; Fri, 4 Jan 2013 12:33:24 -0800 (PST)
In-Reply-To: <CADnDZ8_BPe-L4M=3nWE2k2Uj8bO11uRqCxunVN=22PYDDGOAQA@mail.gmail.com>
References: <CADnDZ8_BPe-L4M=3nWE2k2Uj8bO11uRqCxunVN=22PYDDGOAQA@mail.gmail.com>
Date: Fri, 4 Jan 2013 21:33:24 +0100
Message-ID: <CADnDZ8_n7gP3mO72OCGusu07HN7Ew=eTLV22nDEJZ7yihnLhKw@mail.gmail.com>
Subject: Re: meaning RFC 2119 (was Re:I'm struggling with 2219 language again)
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: brian.e.carpenter@gmail.com
Content-Type: text/plain; charset=ISO-8859-1
Cc: ietf <ietf@ietf.org>, dean.willis@softarmor.com
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 04 Jan 2013 20:33:29 -0000

>I guess the test is whether a reasonably
careful reader might interpret a sentence incorrectly while writing code;
and if so, would a normative keyword help?

I think the best key word used/help is *IF, THEN, ELSE* the programmer
will never miss that key for running code and specification.

AB

> Hi Dean
>
> I agree with you which I suggested before an update to the RFC [*], I
> actually writing a work in progress ID, you may give me your
> suggestion if you like. I recommend you use for your work IF, THEN
> rather than MUST. Easier to read.
>
> *  http://tools.ietf.org/id/draft-baryun-rfc2119-update-00.txt
>
> AB
>
>>
>>
>> I've always held to the idea that RFC 2119 language is for defining
>> levels of compliance to requirements, and is best used very sparingly
>> (as recommended in RFC 2119 itself). To me, RFC 2119 language doesn't
>> make behavior normative -- rather, it describes the implications of
>> doing something different than the defined behavior, from "will break
>> the protocol if you change it" to "we have reason to think that there
>> might be a reason we don't want to describe here that might influence
>> you not to do this" to "here are some reasons that would cause you to
>> do something different" and on to "doing something different might
>> offend the sensibilities of the protocol author, but probably won't
>> hurt anything else."
>>
>> But I'm ghost-editing a document right now whose gen-art review
>> suggested replacing the vast majority of "is" "does" and "are" prose
>> with MUST. The comments seem to indicate that protocol-defining text
>> not using RFC 2119 language (specifically MUST) is "not normative".
>>
>> This makes me cringe. But my co-editor likes it a lot. And I see smart
>> people like Ole also echoing the though that RFC 2119 language is what
>> makes text normative.
>>
>> For example, the protocol under discussion uses TLS or DTLS for a
>> plethora of security reasons. So, every time the draft discusses
>> sending a response to a request, we would say "the node MUST send a
>> response, and this response MUST be constructed by (insert some
>> concatenation procedure here) and MUST be transmitted using TLS or
>> DTLS.
>>
>> Or, a more specific example:
>>
>> For the text:
>>
>> In order to originate a message to a given Node-ID or
>> Resource-ID, a node constructs an appropriate destination list.
>>
>>
>> The Gen-ART comment here is:
>> -First sentence: "a node constructs" -> "a node MUST construct"
>>
>>
>> We'll literally end up with hundreds of RFC 2119 invocations (mostly
>> MUST) in a protocol specification.
>>
>> Is this a good or bad thing? My co-editor and I disagree -- he likes
>> formalization of the description language, and I like the English
>> prose. But it raises process questions for the IETF as a whole:
>>
>> Are we deliberately evolving our language to use RFC 2119 terms as the
>> principle verbs  of a formal specification language?
>>
>> Either way, I'd like to see some consensus. Because my head is
>> throbbing and I want to know if it MUST hurt, SHOULD hurst, or just
>> hurts. But I MUST proceed in accordance with consensus, because to do
>> otherwise would undermine the clarity of our entire specification
>> family.
>>
>> --
>> Dean
>>
>

From abdussalambaryun@gmail.com  Fri Jan  4 12:51:08 2013
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 25DAF21F89E9 for <ietf@ietfa.amsl.com>; Fri,  4 Jan 2013 12:51:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 v7yKN6IKUbUd for <ietf@ietfa.amsl.com>; Fri,  4 Jan 2013 12:51:07 -0800 (PST)
Received: from mail-vb0-f49.google.com (mail-vb0-f49.google.com [209.85.212.49]) by ietfa.amsl.com (Postfix) with ESMTP id 4F23E21F890D for <ietf@ietf.org>; Fri,  4 Jan 2013 12:51:07 -0800 (PST)
Received: by mail-vb0-f49.google.com with SMTP id r6so16729444vbi.22 for <ietf@ietf.org>; Fri, 04 Jan 2013 12:51:06 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:cc:content-type; bh=WfJOi1zz8lJbHhisYgz2fUFyKYSYgifjhlUQ/XrQUZM=; b=ul7D7/s63uVAAmkipCKNkCyivafpegCuxCmPfiGmkcq2n/m3nRgHdehyxYwsgMdB3t ZEs2xh+Oz4o8zp/DSodoVAPSaLLlQ0W0+eRNsQjc4qbBPTcU0vceZuOE2/hD3qK9hxcc B9f74VN5M7ARdwm7Pow1sROO3fEdbVySiNJXyiuA3wLwd0rq9FVC/MEkhL+gqgyKYCSn So46PNi7z2BymBn1oyBGZJI8DeRLVYvLGtZm7+xM2DgmrkQ8CnQb0ETAmrMdU4IpyxTj 1pw4YEsqJIJVSh28uEzqMO87Oz1o1+eIbQ+C7ZvWY3Q/wLwgOdvlKf83w7sP0KRPFkVd XQvA==
MIME-Version: 1.0
Received: by 10.58.137.7 with SMTP id qe7mr79947585veb.23.1357332666665; Fri, 04 Jan 2013 12:51:06 -0800 (PST)
Received: by 10.220.145.5 with HTTP; Fri, 4 Jan 2013 12:51:06 -0800 (PST)
Date: Fri, 4 Jan 2013 21:51:06 +0100
Message-ID: <CADnDZ8-yCxUbrD9oFyQKkJuTgDZbamnV8K4GU+sAN5SekpyHAA@mail.gmail.com>
Subject: Making RFC2119 key language easier to Protocol Readers
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: dean.willis@softarmor.com
Content-Type: text/plain; charset=ISO-8859-1
Cc: ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 04 Jan 2013 20:51:08 -0000

>> formalization of the description language, and I like the English
>> prose. But it raises process questions for the IETF as a whole:
>>
>> Are we deliberately evolving our language to use RFC 2119 terms as the
>> principle verbs  of a formal specification language?

Is it *our language* or our specification language?

I agree that we use in IETF documents the English language but don't
think it is equal/close to all WORLD's language(s), so using RFC2119
will help programmers to read who may like the spoken language, but
like most the specification coding  language(s). However, the
specification/protocol language reader needs to be clear and in an
easy language. I think in the IETF the coding languages is OUR
language not only English.

AB

From alh-ietf@tndh.net  Fri Jan  4 13:45:23 2013
Return-Path: <alh-ietf@tndh.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C3D1C21F8923 for <ietf@ietfa.amsl.com>; Fri,  4 Jan 2013 13:45:23 -0800 (PST)
X-Quarantine-ID: <7p7ffsvBdzoz>
X-Virus-Scanned: amavisd-new at amsl.com
X-Amavis-Alert: BAD HEADER SECTION, Improper folded header field made up entirely of whitespace (char 20 hex): X-Spam-Report: ...that system for details.\n \n Content previ[...]
X-Spam-Flag: NO
X-Spam-Score: -0.68
X-Spam-Level: 
X-Spam-Status: No, score=-0.68 tagged_above=-999 required=5 tests=[AWL=0.680,  BAYES_00=-2.599, NO_RELAYS=-0.001, SARE_LWSHORTT=1.24]
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 7p7ffsvBdzoz for <ietf@ietfa.amsl.com>; Fri,  4 Jan 2013 13:45:22 -0800 (PST)
Received: from express.tndh.net (express.tndh.net [IPv6:2001:470:e930:1240:20d:56ff:fe04:4c0a]) by ietfa.amsl.com (Postfix) with ESMTP id 9364221F884A for <ietf@ietf.org>; Fri,  4 Jan 2013 13:45:22 -0800 (PST)
Received: from express.tndh.local ([2001:470:e930:1240:20d:56ff:fe04:4c0a] helo=eaglet) by express.tndh.net with esmtp (Exim 4.72 (FreeBSD)) (envelope-from <alh-ietf@tndh.net>) id 1TrF4U-00018V-O9; Fri, 04 Jan 2013 13:45:06 -0800
From: "Tony Hain" <alh-ietf@tndh.net>
To: <ietf@ietf.org>
References: <CAMm+Lwh2cHRY+Dk2_SDtZZmUbPcgRpP89u3DHUcniJDrKrX_pw@mail.gmail.com>	<CAMzo+1a0-90dnjnvs48a9DcNN9DY_edF5hH0__4XRuCaLHtL6Q@mail.gmail.com>	<CAMm+LwjzjLc2-=4EdxwHOi21B3dOBUohYc5hhXZHL_Pk+iBBmQ@mail.gmail.com>	<6.2.5.6.2.20121229192941.0aae33e8@resistor.net>	<CAMm+LwiC0xtJU4vnGFPvAG4VKZdj7Tf3LfW0+pzwxKWTegRREw@mail.gmail.com>	<a06240800cd074efd45b8@10.0.1.3>	<CAMm+Lwiq+DCzXw572wKs78DG+XzYsJtwCVSPvNuVHSrT=Cr2nA@mail.gmail.com>	<a06240809cd0799fee029@10.0.1.3>	<50E29EE0.1080107@gmail.com>	<50E32CAA.4040507@tana.it>	<8C48B86A895913448548E6D15DA7553B72A8D6@xmb-rcd-x09.cisco.com>	<00fd01cdea16$c956c720$5c045560$@tndh.net> <CA+9kkMBAm4S5s+sxXuVfp8vZMgZUvBG3YkOiCtegfpA+095_rA@mail.gmail.com>
In-Reply-To: <CA+9kkMBAm4S5s+sxXuVfp8vZMgZUvBG3YkOiCtegfpA+095_rA@mail.gmail.com>
Subject: RE: WCIT outcome?
Date: Fri, 4 Jan 2013 13:44:58 -0800
Message-ID: <015c01cdeac4$be33d550$3a9b7ff0$@tndh.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQLSnCD45NDVIWoUK8uGaD7jPXnB3gEvc1PuAjrLSsgB5a8deAKWQNdKAN2rb9oCXP2dawMSOZ2JAwUFfZ0BmckBbQJjEZ2iAjQP6OwDE2c4x5VcXBWA
Content-Language: en-us
X-SA-Exim-Connect-IP: 2001:470:e930:1240:20d:56ff:fe04:4c0a
X-SA-Exim-Mail-From: alh-ietf@tndh.net
X-SA-Exim-Scanned: No (on express.tndh.net); SAEximRunCond expanded to false
Cc: lynn.st.amour@isoc.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 04 Jan 2013 21:45:23 -0000

> Ted Hardie wrote:
> On Thu, Jan 3, 2013 at 4:59 PM, Tony Hain <alh-ietf@tndh.net> wrote:
> Like it or not, governments are fundamentally opposed to the open =
nature
of
> 'the Internet', and they always will be (even the 'reasonable' ones).
> Managing information flow is how they derive and exercise power
>=20
> Aside from the whole "consent of the governed" issue, this perspective
seems
> historically fairly short-sighted.=20

And that consent is based on information availability. Manage the
information, and you manage the consent.

> ...
> Yes, there were treaty-based efforts to set some common
> understandings.  Some of those were quite useful, but whenever they
actually
> impinged on workings of the real network you got smuggling.  In some
cases, lots
> and lots of it, with encouragement from some of the participating =
nations.
In
> other words, some countries tried to control their participants in =
these
> international networks very tightly.  Some were content to let their
merchants
> get fat off it instead.  There was no universal response.

Shipping Merchant / Harbor Master =3D=3D ISP    : As you see with the =
resolution
signatories, there is still no universal response.

> ...
> In this new effort at a multilateral framework, we are seeing a clash
between a
> desire for sovereign control of the Internet and a desire to reap the
benefits of
> open participation.  I think our role in that is to make sure all =
involved
> understand:  the benefits of the Internet's network effect; the risks =
in
allowing
> nations through which traffic passes to assert sovereignty over the =
flows,

As if professional information control practitioners do not understand =
the
risks of information control at a much deeper level than anyone in the =
IETF
could ever hope to ... =20

> especially given both the pace and chance of topological change; and =
the
reality
> that entities outside of governments control the paths that packets =
actual
> traverse.

The entities that operate and control the paths do so at the pleasure of =
the
governments, just as the merchants and harbor masters did in your =
example
above. As long as governments are pleased, the operators can live in a
fantasy land where they are outside government control. The Dubai
discussions show what happens when a collection of governments are no =
longer
pleased ... If that noise level gets high enough the non-signers will =
have
to respond just to maintain some degree of cooperation on other matters =
they
care about.

Our role is to recognize that there are much bigger issues than the =
simple
process of bit delivery. Yes bit delivery is important, and dynamic, but =
it
is equivalent to laying the tracks. Standards must be maintained for
consistent interworking, but it is not the path that matters; just as =
with
rail cars, it is the content that provides the value. Being highly =
dynamic
makes things harder to control, but not impossible. Even in the 'open'
countries, a few changes in something as apparently disconnected as tax =
laws
would dramatically change the decisions and behaviors of the operators =
that
are 'outside of government control'.=20
> ...


> Patrik F=E4ltstr=F6m wrote:
> On 4 jan 2013, at 01:59, Tony Hain <alh-ietf@tndh.net> wrote:
>=20
> > Like it or not, governments are fundamentally opposed to the open
> > nature of 'the Internet', and they always will be (even the =
'reasonable'
ones).
>=20
> Because I do not think generalization is really a reasonable thing to =
do,
and even
> dangerous when discussing governance issues, I disagree with this
statement.

I agree there is danger here, but I believe the greater danger is =
embodied
in this thread due to the lack of acknowledgement that governments =
always
have control, even if the control points are not obvious.

>=20
> Governments want just like businesses success in whatever they do. =
That
can in
> general be divided in two wishes. Short term, in the form of being
re-elected (or
> not thrown out of their office) and long term, as in growth of the =
revenue
of the
> country they govern.

The second point (restated as 'prosperity for their constituency') is =
really
just a continuation of the first point.

>=20
> They of course have pieces of their operation that belong to law
enforcement
> agencies, but they also have those that are responsible of finding =
rules
so that
> non-public sector can grow (to later increase for example tax =
revenue).
>=20
> Because of this, I encourage people to not generalize per stakeholder
group, but
> instead acknowledge that there are different *forces* that are =
orthogonal
to
> each other, and calculating "the correct" balance between them is =
hard. Or
> rather, different people do for different reasons get different =
results
when
> calculating what the for them proper balance is.
>=20
> That is why I personally am against generalization that a stakeholder
group have
> one specific view.

I would agree that they all demonstrate a different calculation for the
importance of various aspects of controlling information flow. My =
primary
point here is that the IETF has to accept this as a reality. So far the
position has been 'this is the technology, & governments need to adapt'. =
At
the end of the day though, it is the governments that are really in =
control,
and if the IETF does not want a 'forced adaptation', it need to evolve =
and
listen to the needs of a stakeholder group they have tried hard to =
ignore.

>=20
> Specifically governments.
>=20
> If when pushed to be forced to choose between two choices *all*
governments
> wanted to have control, we would have had many more governments =
signing
the
> proposed treaty that was on the table in Dubai.
>=20
> Instead, when being forced to choose, they picked openness and multi
> stakeholder bottom up processes.

As noted above, this is due to relative happiness, and limited noise. If =
the
noise level grows or they become unhappy, the independence of the =
standards
process is a minor pawn in the game, and will be sacrificed to protect
something more important.=20

> ...

Tony



From ben@nostrum.com  Fri Jan  4 13:58:44 2013
Return-Path: <ben@nostrum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 16BAA21F8877 for <ietf@ietfa.amsl.com>; Fri,  4 Jan 2013 13:58:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.6
X-Spam-Level: 
X-Spam-Status: No, score=-102.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, SPF_PASS=-0.001, USER_IN_WHITELIST=-100]
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 6uLmtOOSCQfs for <ietf@ietfa.amsl.com>; Fri,  4 Jan 2013 13:58:25 -0800 (PST)
Received: from shaman.nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id 4AFB421F8A71 for <ietf@ietf.org>; Fri,  4 Jan 2013 13:58:25 -0800 (PST)
Received: from [10.119.77.186] (173.234.16.19.rdns.ubiquityservers.com [173.234.16.19] (may be forged)) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id r04LwD6b092983 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 4 Jan 2013 15:58:17 -0600 (CST) (envelope-from ben@nostrum.com)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Subject: Re: I'm struggling with 2219 language again
From: Ben Campbell <ben@nostrum.com>
In-Reply-To: <156C25BD-1769-44C5-87B1-3BD670A1B2E0@bbn.com>
Date: Fri, 4 Jan 2013 15:58:11 -0600
Content-Transfer-Encoding: quoted-printable
Message-Id: <AB205837-7A8A-4FBE-B52E-82807ACF16CB@nostrum.com>
References: <7ED55FF1-3E1A-4DF7-918E-07790517B848@softarmor.com> <50E719DA.1040709@internet2.edu> <50E71C24.1000701@stpeter.im> <156C25BD-1769-44C5-87B1-3BD670A1B2E0@bbn.com>
To: Richard Barnes <rbarnes@bbn.com>
X-Mailer: Apple Mail (2.1499)
Received-SPF: pass (nostrum.com: 173.234.16.19 is authenticated by a trusted mechanism)
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 04 Jan 2013 21:58:44 -0000

I generally take (what I infer to be) Richard's view on the matter.  If =
not doing something will break interoperability or security, then make =
it normative. (I realize that's a gross oversimplification).

But that still doesn't mean you have to have a MUST for every step an =
implementation has to take. To take Dean's original example, I think it =
makes sense to say the implementation "... MUST send a response =
according to the following procedures..." then describe the procedure =
without peppering it with 2119 language,  except for special cases when =
needed for emphasis or clarity. This seems to cover the risk of people =
not implementing stuff, but still avoids an explosion of MUSTs (and the =
resulting requirements matrix).

Sticking with Dean's example, the use of TLS might qualify as one of the =
special cases needing additional normative emphasis, but you can always =
say something like "... MUST send all message over TLS" once, rather =
than restate it for every message.


On Jan 4, 2013, at 1:04 PM, Richard Barnes <rbarnes@bbn.com> wrote:

> Anecdotal data point number N+1...
>=20
> As an occasional implementor of IETF specs, I have to say it's much =
easier to check my conformance if I can just grep for "MUST" and =
"SHOULD".  It's also easy for developers to get in the bad habit of ONLY =
doing those things that are clearly marked in that way.  So ISTM that if =
you're not tagging things you want done with RFC 2119 language, then =
you're risking people not implementing them.
>=20
>=20
>=20
> On Jan 4, 2013, at 1:15 PM, Peter Saint-Andre <stpeter@stpeter.im> =
wrote:
>=20
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>=20
>> Wonderful perennial topic. :)
>>=20
>> As I always say when this comes up, when writing drafts I've settled
>> on using the 2119 keywords only in their uppercase form, and =
otherwise
>> using "need to", "ought to", "might" (etc.) to avoid all possible
>> confusion. Sure, it's a bit stilted, but we're not writing gorgeous
>> prose here, we're writing technical specifications that need to be
>> completely clear.
>>=20
>> Peter
>>=20
>> - --
>> Peter Saint-Andre
>> https://stpeter.im/
>>=20
>> -----BEGIN PGP SIGNATURE-----
>> Version: GnuPG/MacGPG2 v2.0.18 (Darwin)
>> Comment: Using GnuPG with undefined - http://www.enigmail.net/
>>=20
>> iEYEARECAAYFAlDnHCQACgkQNL8k5A2w/vxKmwCfXKjDtMqQiPp4a0udOB8Q9IbA
>> q9QAoNiXj2r/q4yRLp0B/13m6Xxg5YN4
>> =3D3PER
>> -----END PGP SIGNATURE-----
>=20


From sm@resistor.net  Fri Jan  4 14:12:54 2013
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9004F21F884C for <ietf@ietfa.amsl.com>; Fri,  4 Jan 2013 14:12:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.449
X-Spam-Level: 
X-Spam-Status: No, score=-102.449 tagged_above=-999 required=5 tests=[AWL=0.150, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 Xw7nusUgxlI2 for <ietf@ietfa.amsl.com>; Fri,  4 Jan 2013 14:12:52 -0800 (PST)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 1438321F8849 for <ietf@ietf.org>; Fri,  4 Jan 2013 14:12:52 -0800 (PST)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r04MChtw029934; Fri, 4 Jan 2013 14:12:46 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1357337569; bh=JhZo8TNVsTY0r2OKkYWj6/U2O3kkLgcQhChA490mr3o=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=IBf4eFarXUoZGbcK6N4SCTzSto8YejaSUCOhyTTQJWk21YxQqg7HdjmQkHKCAOpUV afpMvTFNSOjky60N4oTG+sbxQTRpHibROyi3+QUqhyGw0gJ9s4vsdJ9/WNpnYRMqr8 ae+A19gb9HZ8vX4EWnOI/sqIYQuiVtV54m7FP7DU=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1357337569; i=@resistor.net; bh=JhZo8TNVsTY0r2OKkYWj6/U2O3kkLgcQhChA490mr3o=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=Qd3JLz+EwcVwNqc1EdPK2xbDRVL0a2iPLefwZ9gBBCm7w6Kam2LmSbUZcphNtosCu NgjwgE5FPaB13XZ99r4vSs/J4mjfaVG8Z2x0k6M2lWmN24skwn2bUYzc5wYVDUTqf0 WI7oexSOgY8gYMXJ0280I8ZzzV1rvjr5xrUvUTPM=
Message-Id: <6.2.5.6.2.20130104112853.0ae65f30@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Fri, 04 Jan 2013 14:12:13 -0800
To: "Tony Hain" <alh-ietf@tndh.net>, Ted Hardie <ted.ietf@gmail.com>
From: SM <sm@resistor.net>
Subject: RE: WCIT outcome?
In-Reply-To: <00fd01cdea16$c956c720$5c045560$@tndh.net>
References: <CAMm+Lwh2cHRY+Dk2_SDtZZmUbPcgRpP89u3DHUcniJDrKrX_pw@mail.gmail.com> <CAMzo+1a0-90dnjnvs48a9DcNN9DY_edF5hH0__4XRuCaLHtL6Q@mail.gmail.com> <CAMm+LwjzjLc2-=4EdxwHOi21B3dOBUohYc5hhXZHL_Pk+iBBmQ@mail.gmail.com> <6.2.5.6.2.20121229192941.0aae33e8@resistor.net> <CAMm+LwiC0xtJU4vnGFPvAG4VKZdj7Tf3LfW0+pzwxKWTegRREw@mail.gmail.com> <a06240800cd074efd45b8@10.0.1.3> <CAMm+Lwiq+DCzXw572wKs78DG+XzYsJtwCVSPvNuVHSrT=Cr2nA@mail.gmail.com> <a06240809cd0799fee029@[10.0.1.3]> <50E29EE0.1080107@gmail.com> <50E32CAA.4040507@tana.it> <8C48B86A895913448548E6D15DA7553B72A8D6@xmb-rcd-x09.cisco.com> <00fd01cdea16$c956c720$5c045560$@tndh.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 04 Jan 2013 22:12:54 -0000

At 16:59 03-01-2013, Tony Hain wrote:
>other. How long the IETF gets to stay independent of that will depend on how
>responsive it is to meeting the needs of governments. If short-sighted
>attempts at political maneuvering are exposed in the IETF, it will lose its
>independence and finally bring that process under 'proper control'.

The IAB has a nominated a representative to the European 
Multi-Stakeholder Platform on ICT Standardisation.  It also commented 
on the (U.S) Federal Participation in the Development and Use of 
Voluntary Consensus Standards and in Conformity Assessment 
Activities.  The government interaction is basically between the IETF 
and the E.U. or the U.S.  I do not recall any cases (in recent times) 
where the E.U. or the U.S. has pressured the IETF to support or 
oppose a decision.

The IETF used to be set up in such a way that putting it under 
"proper control" would be quite an effort.

>It would be wise for the IETF participants to look at the countries that did
>sign, and why. What is it that they are not getting that they need, and how
>can that be resolved? To echo Day's point, it is the capability they
>want/need, not the historical implementation. Some things that are business

Yes.

At 09:24 04-01-2013, Ted Hardie wrote:
>In this new effort at a multilateral framework, we are seeing a 
>clash between a desire for sovereign control of the Internet and a 
>desire to reap the benefits of open participation.  I think our role 
>in that is to make sure all involved understand:  the benefits of 
>the Internet's network effect; the risks in allowing nations through 
>which traffic passes to assert sovereignty over the flows, 
>especially given both the pace and chance of topological change; and 
>the reality that entities outside of governments control the paths 
>that packets actual traverse.

A few years ago sourceforge.net blocked all users from a specific 
country from downloading files hosted on their site.  There was a 
case where a country had its say on one or more domain names through 
unusual means.  Some of that can be perceived as assertions of sovereignty.

Regards,
-sm 


From ynir@checkpoint.com  Fri Jan  4 14:14:56 2013
Return-Path: <ynir@checkpoint.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1840721F8864 for <ietf@ietfa.amsl.com>; Fri,  4 Jan 2013 14:14:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 V61dJBAwgEDZ for <ietf@ietfa.amsl.com>; Fri,  4 Jan 2013 14:14:55 -0800 (PST)
Received: from smtp.checkpoint.com (smtp.checkpoint.com [194.29.34.68]) by ietfa.amsl.com (Postfix) with ESMTP id 230C421F8849 for <ietf@ietf.org>; Fri,  4 Jan 2013 14:14:54 -0800 (PST)
Received: from IL-EX10.ad.checkpoint.com ([194.29.34.147]) by smtp.checkpoint.com (8.13.8/8.13.8) with ESMTP id r04MEpZ0004198; Sat, 5 Jan 2013 00:14:52 +0200
X-CheckPoint: {50E75280-0-1B221DC2-2FFFF}
Received: from IL-EX10.ad.checkpoint.com ([169.254.2.22]) by IL-EX10.ad.checkpoint.com ([169.254.2.238]) with mapi id 14.02.0318.004; Sat, 5 Jan 2013 00:14:51 +0200
From: Yoav Nir <ynir@checkpoint.com>
To: Michael Richardson <mcr@sandelman.ca>
Subject: Re: travel guide for the next IETF...
Thread-Topic: travel guide for the next IETF...
Thread-Index: AQHN5dfb0936cwl5eUu6Q6LVF7Mv7ZgzPAaAgAZomQA=
Date: Fri, 4 Jan 2013 22:14:51 +0000
Message-ID: <4613980CFC78314ABFD7F85CC30277210EE27C34@IL-EX10.ad.checkpoint.com>
References: <50DF09C7.1060009@dcrocker.net> <20200.1356985377@sandelman.ca>
In-Reply-To: <20200.1356985377@sandelman.ca>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [172.31.21.134]
x-kse-antivirus-interceptor-info: scan successful
x-kse-antivirus-info: Clean
Content-Type: text/plain; charset="us-ascii"
Content-ID: <8081191389A82348B895B3339B9CF5DA@ad.checkpoint.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 04 Jan 2013 22:14:56 -0000

On Dec 31, 2012, at 10:22 PM, Michael Richardson <mcr@sandelman.ca> wrote:

>=20
>>>>>> "Dave" =3D=3D Dave Crocker <dhc@dcrocker.net> writes:
>    Dave> "Quick, name five reasons to go to Orlando. Here are mine:
>    Dave> Puerto Rican=20
>    Dave> delicacies, alternative cinema, craft beer, African-American
>    Dave> history and=20
>    Dave> psychic readings..."
>=20
> Good... but how to get there?
>=20
> We appear to be stuck in the middle of a monster hotel with a single
> boulevard and nothing at all nearby (except that there is a shuttle
> to Disney)
>=20
> Shoping around for places to stay, there are some 3-star places for
> <$50/night.  =20

Looking in Google Earth, you'll still need a car. Even with those hotels th=
at are within walking distance, there are big stretches of road without any=
 sidewalks.=

From thegreatall@gmail.com  Fri Jan  4 14:18:49 2013
Return-Path: <thegreatall@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9FB3B21F8A74 for <ietf@ietfa.amsl.com>; Fri,  4 Jan 2013 14:18:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.415
X-Spam-Level: 
X-Spam-Status: No, score=-3.415 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, SARE_OBFU_SPLIT_HR2=0.183]
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 UIE+uXhYfnTU for <ietf@ietfa.amsl.com>; Fri,  4 Jan 2013 14:18:49 -0800 (PST)
Received: from mail-ob0-f180.google.com (mail-ob0-f180.google.com [209.85.214.180]) by ietfa.amsl.com (Postfix) with ESMTP id D00D021F846E for <ietf@ietf.org>; Fri,  4 Jan 2013 14:18:48 -0800 (PST)
Received: by mail-ob0-f180.google.com with SMTP id wd20so14910644obb.39 for <ietf@ietf.org>; Fri, 04 Jan 2013 14:18:48 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=U5QtJgp68U6fOeOnFD3/zwocbKua6BNSNcglKEwztIw=; b=kgZlLEHQotq2DLsyB11E6wFXg+WZfvTtY9i3rj7y5oAkV+7SFq3CnwesCVLbCl2Qvg Gco1P3KR7MpxDXFhGQyatRJA0i7IFv3YVHV15ae4lEzDocYYrmjkaDwONNU8ituW/h6w bgxvnOnMyQoQSpSYis5ChnFdQudNWpxDAKugYj72TA0JuPmmiBoLa92U3N+OiMHRGDP1 PRMW25dRxIIg0dkCKf6I25CvM7aUMv/278y7ur1KW0peKLa0JkBWWQTl+68B0uK4aOPa xBiT7PztQi0w6p6u21FXjoH7Xzg9s7dLfh8BdLdmA2pKUkBnYAKLqE1Tp0rthOoDQxCt REOQ==
MIME-Version: 1.0
Received: by 10.60.172.200 with SMTP id be8mr31533971oec.0.1357337928439; Fri, 04 Jan 2013 14:18:48 -0800 (PST)
Received: by 10.76.13.194 with HTTP; Fri, 4 Jan 2013 14:18:48 -0800 (PST)
Date: Fri, 4 Jan 2013 16:18:48 -0600
Message-ID: <CAMVzVHMeO6G6bxZ2qe6GVPVFEDJEeJXoAxMFTmmChaSQt89DWQ@mail.gmail.com>
Subject: More cache control for (X)HTML pages
From: Nathan <thegreatall@gmail.com>
To: ietf@ietf.org
Content-Type: multipart/alternative; boundary=bcaec54ee6d410978104d27ddd06
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 04 Jan 2013 22:20:46 -0000

--bcaec54ee6d410978104d27ddd06
Content-Type: text/plain; charset=ISO-8859-1

Hi, this is my first post so forgive me if I posted in the wrong spot.

I am contemplating writing an RFC on an HTML tag to be placed in the <head>
of a webpage which gives the browser instructions on a single location were
the page may obtain bulk cache information from the server instead of
having each time a new cache-able element is requested having the browser
create a new http request to the server to only have the server respond
with a 304 Not Modified.

I am not going into detail but a quick over view would look something like
(taken from google.com homepage's cache-able files):
<head>
    ...
    <cache src="/script-to-handle-bulk-cache-checking">
        <file href="images/srpr/logo3w.png" />
        <file href="
xjs/_/js/s/c,sb,cr,vm,cdos,jsa,sf,tbpr,tbui,rsn,ob,mb,lc,hv,cfm,klc,kat,aut,esp,erh,bihu,amcl,kp,lu,m,rtis,shb,sfa,hsm,j,p,pcc,csi/rt=j/ver=K-W_gw26Qd4.en_US./d=1/sv=1/rs=AItRSTP1F4RezC8aHlgXoNQaBhX3N9n9sQ"
/>
        <file href="extern_chrome/edf8435073bcf94.js" />
        <file href="
xjs/_/js/s/sy10,gf,sy45,sy46,sy81,sy44,sy39,sy82,sy8,sy34,sy50,sy48,sy80,sy99,sy105,sy108,sy9,sy15,mbtt,ssi,ifl/rt=j/ver=K-W_gw26Qd4.en_US./d=0/sv=1/rs=AItRSTP1F4RezC8aHlgXoNQaBhX3N9n9sQ"
/>
        <file href="textinputassistant/tia.png" />
        <file href="images/nav_logo114.png" />
    </cache>
    ...
</head>

The browser would then block until it cross references it's own cache with
the listed files and (if > 1) send a request to the location specified in
the "src" attribute in the "cache" tag with the cross referenced files list
and the associated "if-modified-since" date of each file. The server would
then respond telling the browser to use the cache for the files that can be
used for cache. Any other files need to be loaded load like normal.

The idea would be to have a page with many images, javascript, css, exc...
to do a single request in the hopes that the it could save any of those
cache-able files from needing their own request to the server to see if
they have been modified.

If there is already an RFC for this a link to it would be appreciated as I
looked for one and came up with only http header cache controls which does
not work the same way.

Thank you,
-Nathan Bruer

--bcaec54ee6d410978104d27ddd06
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi, this is my first post so forgive me if I posted in the=
 wrong spot.<div><br></div><div>I am contemplating writing an RFC on an HTM=
L tag=A0to be placed in the &lt;head&gt; of a webpage which gives the brows=
er instructions on a single location were the page may obtain bulk cache in=
formation from the server instead of having each time a new=A0cache-able=A0=
element is requested having the browser create a new http request to the se=
rver to only have the server respond with a 304 Not Modified.</div>

<div><br></div><div>I am not going into detail but a quick over view would =
look something like (taken from <a href=3D"http://google.com" target=3D"_bl=
ank">google.com</a>=A0homepage&#39;s cache-able files):</div><div>&lt;head&=
gt;</div>
<div>=A0 =A0 ...</div><div>=A0 =A0 &lt;cache src=3D&quot;/script-to-handle-=
bulk-cache-checking&quot;&gt;</div>
<div>=A0 =A0 =A0 =A0 &lt;file href=3D&quot;<span style=3D"font-size:12px;wh=
ite-space:pre-wrap;font-family:Consolas,&#39;Lucida Console&#39;,monospace"=
>images/srpr/logo3w.png</span>&quot; /&gt;</div><div>=A0 =A0 =A0 =A0 &lt;fi=
le href=3D&quot;<span style=3D"color:rgb(0,0,0);font-family:Consolas,&#39;L=
ucida Console&#39;,monospace;font-size:12px;white-space:pre-wrap">xjs/_/js/=
s/c,sb,cr,vm,cdos,jsa,sf,tbpr,tbui,rsn,ob,mb,lc,hv,cfm,klc,kat,aut,esp,erh,=
bihu,amcl,kp,lu,m,rtis,shb,sfa,hsm,j,p,pcc,csi/rt=3Dj/ver=3DK-W_gw26Qd4.en_=
US./d=3D1/sv=3D1/rs=3DAItRSTP1F4RezC8aHlgXoNQaBhX3N9n9sQ</span>&quot; /&gt;=
<br>

</div><div>=A0 =A0 =A0 =A0 &lt;file href=3D&quot;<span style=3D"color:rgb(0=
,0,0);font-family:Consolas,&#39;Lucida Console&#39;,monospace;font-size:12p=
x;white-space:pre-wrap">extern_chrome/edf8435073bcf94.js</span>&quot; /&gt;=
<br></div>
<div>=A0 =A0 =A0 =A0 &lt;file href=3D&quot;<span style=3D"color:rgb(0,0,0);=
font-family:Consolas,&#39;Lucida Console&#39;,monospace;font-size:12px;whit=
e-space:pre-wrap">xjs/_/js/s/sy10,gf,sy45,sy46,sy81,sy44,sy39,sy82,sy8,sy34=
,sy50,sy48,sy80,sy99,sy105,sy108,sy9,sy15,mbtt,ssi,ifl/rt=3Dj/ver=3DK-W_gw2=
6Qd4.en_US./d=3D0/sv=3D1/rs=3DAItRSTP1F4RezC8aHlgXoNQaBhX3N9n9sQ</span>&quo=
t; /&gt;<br>
</div><div>=A0 =A0 =A0 =A0=A0&lt;file href=3D&quot;<span style=3D"color:rgb=
(0,0,0);font-family:Consolas,&#39;Lucida Console&#39;,monospace;font-size:1=
2px;white-space:pre-wrap">textinputassistant/tia.png</span>&quot; /&gt;</di=
v><div>=A0 =A0 =A0 =A0=A0&lt;file href=3D&quot;<span style=3D"color:rgb(0,0=
,0);font-family:Consolas,&#39;Lucida Console&#39;,monospace;font-size:12px;=
white-space:pre-wrap">images/nav_logo114.png</span>&quot; /&gt;</div>
<div>=A0 =A0 &lt;/cache&gt;</div><div>=A0 =A0 ...</div><div style>&lt;/head=
&gt;</div><div><br></div><div style>The browser would then block until it c=
ross references it&#39;s own cache with the listed files and (if &gt; 1) se=
nd a request to the location specified in the &quot;src&quot; attribute in =
the &quot;cache&quot; tag with the cross referenced files list and the asso=
ciated &quot;if-modified-since&quot; date of each file. The server would th=
en respond telling the browser to use the cache for the files that can be u=
sed for cache. Any other files need to be loaded load like normal.</div>
<div style><br></div><div style>The idea would be to have a page with many =
images, javascript, css, exc... to do a single request in the hopes that th=
e it could save any of those cache-able files from needing their own reques=
t to the server to see if they have been modified.</div>
<div style><br></div><div style>If there is already an RFC for this a link =
to it would be=A0appreciated=A0as I looked for one and came up with only ht=
tp header cache controls which does not work the same way.</div><div style>
<br></div><div style>Thank you,</div><div style>-Nathan Bruer</div></div>

--bcaec54ee6d410978104d27ddd06--

From narten@us.ibm.com  Fri Jan  4 14:23:55 2013
Return-Path: <narten@us.ibm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CC0C921F87CE for <ietf@ietfa.amsl.com>; Fri,  4 Jan 2013 14:23:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.599
X-Spam-Level: 
X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
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 Z8ERQmUI1jFH for <ietf@ietfa.amsl.com>; Fri,  4 Jan 2013 14:23:55 -0800 (PST)
Received: from e33.co.us.ibm.com (e33.co.us.ibm.com [32.97.110.151]) by ietfa.amsl.com (Postfix) with ESMTP id 0AE9021F87AD for <ietf@ietf.org>; Fri,  4 Jan 2013 14:23:54 -0800 (PST)
Received: from /spool/local by e33.co.us.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for <ietf@ietf.org> from <narten@us.ibm.com>; Fri, 4 Jan 2013 15:23:53 -0700
Received: from d03dlp01.boulder.ibm.com (9.17.202.177) by e33.co.us.ibm.com (192.168.1.133) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted;  Fri, 4 Jan 2013 15:23:52 -0700
Received: from d03relay01.boulder.ibm.com (d03relay01.boulder.ibm.com [9.17.195.226]) by d03dlp01.boulder.ibm.com (Postfix) with ESMTP id D666F1FF003C for <ietf@ietf.org>; Fri,  4 Jan 2013 15:23:41 -0700 (MST)
Received: from d03av06.boulder.ibm.com (d03av06.boulder.ibm.com [9.17.195.245]) by d03relay01.boulder.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id r04MNoHd245426 for <ietf@ietf.org>; Fri, 4 Jan 2013 15:23:50 -0700
Received: from d03av06.boulder.ibm.com (loopback [127.0.0.1]) by d03av06.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP id r04MQ0wN016997 for <ietf@ietf.org>; Fri, 4 Jan 2013 15:26:00 -0700
Received: from cichlid.raleigh.ibm.com (sig-9-76-153-78.mts.ibm.com [9.76.153.78]) by d03av06.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVin) with ESMTP id r04MPwYb016917 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 4 Jan 2013 15:26:00 -0700
Received: from cichlid.raleigh.ibm.com (localhost.localdomain [127.0.0.1]) by cichlid.raleigh.ibm.com (8.14.5/8.12.5) with ESMTP id r04MNgRA020196; Fri, 4 Jan 2013 17:23:42 -0500
Message-Id: <201301042223.r04MNgRA020196@cichlid.raleigh.ibm.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: I'm struggling with 2219 language again
In-reply-to: <50E68CB5.4010107@gmail.com>
References: <7ED55FF1-3E1A-4DF7-918E-07790517B848@softarmor.com> <50E68CB5.4010107@gmail.com>
Comments: In-reply-to Brian E Carpenter <brian.e.carpenter@gmail.com> message dated "Fri, 04 Jan 2013 08:03:01 +0000."
Date: Fri, 04 Jan 2013 17:23:42 -0500
From: Thomas Narten <narten@us.ibm.com>
X-Content-Scanned: Fidelis XPS MAILER
x-cbid: 13010422-2398-0000-0000-00000FB5A16F
Cc: ietf@ietf.org, Dean Willis <dean.willis@softarmor.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 04 Jan 2013 22:23:55 -0000

+1 to Brian and others saying upper case should be used sparingly, and
only where it really matters. If even then.

The notion (that some have) that MUST means you have to do something
to be compliant and that a "must" (lower case) is optional is just
nuts.

If the ARP spec were to say, "upon receipt of an ARP request, the
recipient sends back an ARP response," does the lack of a MUST there
mean the response is optional? Surely not. And if we make it only a
SHOULD (e.g., to allow rate limiting of responses - a very reasonable
thing to do), does lack of MUST now make the feature optional from a
compliance/interoperability perspective?

The idea that upper case language can be used to identify all the
required parts of a specificition from a
compliance/conformance/interoperability perspective is just
wrong. This has never been the case (and would be exceeding painful to
do), though (again) some people seem to think this would be useful and
thus like lots of upper case language.

Where you want to use MUST is where an implementation might be tempted
to take a short cut -- to the detriment of the Internet -- but could
do so without actually breaking interoperability. A good example is
with retransmissions and exponential backoff. You can implement those
incorrectly (or not at all), and still get "interoperability". I.e.,
two machines can talk to each other. Maybe you don't get "good"
intereoperability and maybe not great performance under some
conditions, but you can still build an interoperabile implementation.

IMO, too many specs seriously overuse/misuse 2119 language, to the
detriment of readability, common sense, and reserving the terms to
bring attention to those cases where it really is important to
highlight an important point that may not be obvious to a casual
reader/implementor.

Thomas



From mnot@mnot.net  Fri Jan  4 14:47:34 2013
Return-Path: <mnot@mnot.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 912F821F8812 for <ietf@ietfa.amsl.com>; Fri,  4 Jan 2013 14:47:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 8EHmRQE16G46 for <ietf@ietfa.amsl.com>; Fri,  4 Jan 2013 14:47:33 -0800 (PST)
Received: from mxout-08.mxes.net (mxout-08.mxes.net [216.86.168.183]) by ietfa.amsl.com (Postfix) with ESMTP id 73F5E21F8815 for <ietf@ietf.org>; Fri,  4 Jan 2013 14:47:33 -0800 (PST)
Received: from [192.168.1.80] (unknown [118.209.230.64]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id CBC8C509BA; Fri,  4 Jan 2013 17:47:31 -0500 (EST)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Subject: Re: More cache control for (X)HTML pages
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <CAMVzVHMeO6G6bxZ2qe6GVPVFEDJEeJXoAxMFTmmChaSQt89DWQ@mail.gmail.com>
Date: Sat, 5 Jan 2013 09:47:26 +1100
Content-Transfer-Encoding: quoted-printable
Message-Id: <5D756BE9-8597-41C9-B268-1AA10022DB11@mnot.net>
References: <CAMVzVHMeO6G6bxZ2qe6GVPVFEDJEeJXoAxMFTmmChaSQt89DWQ@mail.gmail.com>
To: Nathan <thegreatall@gmail.com>
X-Mailer: Apple Mail (2.1499)
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 04 Jan 2013 22:47:34 -0000

Hi Nathan,

Have you looked at the HTML5 AppCache? It operates in a manner similar =
to what you're describing.

http://www.whatwg.org/specs/web-apps/current-work/multipage/offline.html

That said, most people seem to agree that AppCache is somewhat =
problematic; although some do use it, it's fairly fussy to work with, =
and adoption hasn't been wide. Also, note that it creates a cache that's =
separate to the "normal" HTTP cache.

If you want to propose this particular mechanism, I'd recommend talking =
to the WHAT WG <http://www.whatwg.org/> and making sure that the HTTPBIS =
WG <http://trac.tools.ietf.org/wg/httpbis/trac/wiki> is looped in; =
because it involves both HTML and HTTP caching, it touches both. =
However, I'd observe that what you're *really* trying to do is to =
overcome the limitations of HTTP's current use of TCP, and that's what =
we're trying to do with HTTP2 in HTTPBIS; if you wait a bit, this =
shouldn't be necessary.

Regards,


On 05/01/2013, at 9:18 AM, Nathan <thegreatall@gmail.com> wrote:

> Hi, this is my first post so forgive me if I posted in the wrong spot.
>=20
> I am contemplating writing an RFC on an HTML tag to be placed in the =
<head> of a webpage which gives the browser instructions on a single =
location were the page may obtain bulk cache information from the server =
instead of having each time a new cache-able element is requested having =
the browser create a new http request to the server to only have the =
server respond with a 304 Not Modified.
>=20
> I am not going into detail but a quick over view would look something =
like (taken from google.com homepage's cache-able files):
> <head>
>     ...
>     <cache src=3D"/script-to-handle-bulk-cache-checking">
>         <file href=3D"images/srpr/logo3w.png" />
>         <file =
href=3D"xjs/_/js/s/c,sb,cr,vm,cdos,jsa,sf,tbpr,tbui,rsn,ob,mb,lc,hv,cfm,kl=
c,kat,aut,esp,erh,bihu,amcl,kp,lu,m,rtis,shb,sfa,hsm,j,p,pcc,csi/rt=3Dj/ve=
r=3DK-W_gw26Qd4.en_US./d=3D1/sv=3D1/rs=3DAItRSTP1F4RezC8aHlgXoNQaBhX3N9n9s=
Q" />
>         <file href=3D"extern_chrome/edf8435073bcf94.js" />
>         <file =
href=3D"xjs/_/js/s/sy10,gf,sy45,sy46,sy81,sy44,sy39,sy82,sy8,sy34,sy50,sy4=
8,sy80,sy99,sy105,sy108,sy9,sy15,mbtt,ssi,ifl/rt=3Dj/ver=3DK-W_gw26Qd4.en_=
US./d=3D0/sv=3D1/rs=3DAItRSTP1F4RezC8aHlgXoNQaBhX3N9n9sQ" />
>         <file href=3D"textinputassistant/tia.png" />
>         <file href=3D"images/nav_logo114.png" />
>     </cache>
>     ...
> </head>
>=20
> The browser would then block until it cross references it's own cache =
with the listed files and (if > 1) send a request to the location =
specified in the "src" attribute in the "cache" tag with the cross =
referenced files list and the associated "if-modified-since" date of =
each file. The server would then respond telling the browser to use the =
cache for the files that can be used for cache. Any other files need to =
be loaded load like normal.
>=20
> The idea would be to have a page with many images, javascript, css, =
exc... to do a single request in the hopes that the it could save any of =
those cache-able files from needing their own request to the server to =
see if they have been modified.
>=20
> If there is already an RFC for this a link to it would be appreciated =
as I looked for one and came up with only http header cache controls =
which does not work the same way.
>=20
> Thank you,
> -Nathan Bruer

--
Mark Nottingham   http://www.mnot.net/




From mnot@mnot.net  Fri Jan  4 14:49:06 2013
Return-Path: <mnot@mnot.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EC0ED21F8A99 for <ietf@ietfa.amsl.com>; Fri,  4 Jan 2013 14:49:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 4bpNViL-k+mR for <ietf@ietfa.amsl.com>; Fri,  4 Jan 2013 14:49:06 -0800 (PST)
Received: from mxout-08.mxes.net (mxout-08.mxes.net [216.86.168.183]) by ietfa.amsl.com (Postfix) with ESMTP id 1FB4621F883F for <ietf@ietf.org>; Fri,  4 Jan 2013 14:49:05 -0800 (PST)
Received: from [192.168.1.80] (unknown [118.209.230.64]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id EAA03509B8; Fri,  4 Jan 2013 17:49:03 -0500 (EST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Subject: Re: I'm struggling with 2219 language again
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <50E71C24.1000701@stpeter.im>
Date: Sat, 5 Jan 2013 09:48:59 +1100
Content-Transfer-Encoding: 7bit
Message-Id: <4190731D-90CC-4D0D-94AF-FA2892466E54@mnot.net>
References: <7ED55FF1-3E1A-4DF7-918E-07790517B848@softarmor.com> <50E719DA.1040709@internet2.edu> <50E71C24.1000701@stpeter.im>
To: Peter Saint-Andre <stpeter@stpeter.im>
X-Mailer: Apple Mail (2.1499)
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 04 Jan 2013 22:49:07 -0000

+1; this is what we're doing in HTTPbis.


On 05/01/2013, at 5:15 AM, Peter Saint-Andre <stpeter@stpeter.im> wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Wonderful perennial topic. :)
> 
> As I always say when this comes up, when writing drafts I've settled
> on using the 2119 keywords only in their uppercase form, and otherwise
> using "need to", "ought to", "might" (etc.) to avoid all possible
> confusion. Sure, it's a bit stilted, but we're not writing gorgeous
> prose here, we're writing technical specifications that need to be
> completely clear.
> 
> Peter
> 
> - --
> Peter Saint-Andre
> https://stpeter.im/
> 
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG/MacGPG2 v2.0.18 (Darwin)
> Comment: Using GnuPG with undefined - http://www.enigmail.net/
> 
> iEYEARECAAYFAlDnHCQACgkQNL8k5A2w/vxKmwCfXKjDtMqQiPp4a0udOB8Q9IbA
> q9QAoNiXj2r/q4yRLp0B/13m6Xxg5YN4
> =3PER
> -----END PGP SIGNATURE-----

--
Mark Nottingham   http://www.mnot.net/




From mnot@mnot.net  Fri Jan  4 14:53:24 2013
Return-Path: <mnot@mnot.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8C5F621F86A2 for <ietf@ietfa.amsl.com>; Fri,  4 Jan 2013 14:53:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 VUcKHsAQG33j for <ietf@ietfa.amsl.com>; Fri,  4 Jan 2013 14:53:24 -0800 (PST)
Received: from mxout-08.mxes.net (mxout-08.mxes.net [216.86.168.183]) by ietfa.amsl.com (Postfix) with ESMTP id B4A8521F8881 for <ietf@ietf.org>; Fri,  4 Jan 2013 14:53:23 -0800 (PST)
Received: from [192.168.1.80] (unknown [118.209.230.64]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id AC82E509B6 for <ietf@ietf.org>; Fri,  4 Jan 2013 17:53:22 -0500 (EST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Subject: Re: travel guide for the next IETF...
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <4613980CFC78314ABFD7F85CC30277210EE27C34@IL-EX10.ad.checkpoint.com>
Date: Sat, 5 Jan 2013 09:53:18 +1100
Content-Transfer-Encoding: quoted-printable
Message-Id: <2C17B081-ECE7-4CD0-99AB-72324EA0BE27@mnot.net>
References: <50DF09C7.1060009@dcrocker.net> <20200.1356985377@sandelman.ca> <4613980CFC78314ABFD7F85CC30277210EE27C34@IL-EX10.ad.checkpoint.com>
To: IETF Discussion <ietf@ietf.org>
X-Mailer: Apple Mail (2.1499)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 04 Jan 2013 22:53:24 -0000

If the powers that be want to encourage us to come for the entire week, =
choosing places like this doesn't help. I don't need a tourist paradise, =
but I don't want to eat from the same hotel restaurant six days in a =
row. And needing a car is absurd.=20

</grumble>

P.S. I wonder how the "Stand Your Ground" laws will be interpreted by =
IETF participants... perhaps our discussions will be extra-civil this =
time. At least they're recorded...



On 05/01/2013, at 9:14 AM, Yoav Nir <ynir@checkpoint.com> wrote:

>=20
> On Dec 31, 2012, at 10:22 PM, Michael Richardson <mcr@sandelman.ca> =
wrote:
>=20
>>=20
>>>>>>> "Dave" =3D=3D Dave Crocker <dhc@dcrocker.net> writes:
>>   Dave> "Quick, name five reasons to go to Orlando. Here are mine:
>>   Dave> Puerto Rican=20
>>   Dave> delicacies, alternative cinema, craft beer, African-American
>>   Dave> history and=20
>>   Dave> psychic readings..."
>>=20
>> Good... but how to get there?
>>=20
>> We appear to be stuck in the middle of a monster hotel with a single
>> boulevard and nothing at all nearby (except that there is a shuttle
>> to Disney)
>>=20
>> Shoping around for places to stay, there are some 3-star places for
>> <$50/night.  =20
>=20
> Looking in Google Earth, you'll still need a car. Even with those =
hotels that are within walking distance, there are big stretches of road =
without any sidewalks.

--
Mark Nottingham   http://www.mnot.net/




From ole@cisco.com  Fri Jan  4 15:17:32 2013
Return-Path: <ole@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 59E3B21F8B0A for <ietf@ietfa.amsl.com>; Fri,  4 Jan 2013 15:17:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.599
X-Spam-Level: 
X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
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 9MAKU9b4ZvBC for <ietf@ietfa.amsl.com>; Fri,  4 Jan 2013 15:17:31 -0800 (PST)
Received: from mtv-iport-4.cisco.com (mtv-iport-4.cisco.com [173.36.130.15]) by ietfa.amsl.com (Postfix) with ESMTP id 9D73D21F843C for <ietf@ietf.org>; Fri,  4 Jan 2013 15:17:22 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=754; q=dns/txt; s=iport; t=1357341442; x=1358551042; h=date:from:reply-to:to:cc:subject:in-reply-to:message-id: references:mime-version; bh=HCDJ3NIofZ5EcrRM20EhM4jzhbWFGG9VxIZIGjdN3MM=; b=QdBTLsT0WiQuDsYgQLdpIsROz0t7Kc/Gy3bjXvmsZSIBe1UEIJqTMVYI 5sO/9hgn4V7zIwoLgyJn/WfkRWfHtZqnjtzSyFUfHXwpw2pCNMZFlfCaC n4b0q9dHewv1tvxTx11nUUpGAwOLDd09KSH+DH0GG+DXeFz4taGLaC/OL k=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av4EAGhi51CrRDoH/2dsb2JhbABFvU8Wc4IeAQEBAwE6PwULCw44VwaIIQW0J5EVA4hhkxWKXoMV
X-IronPort-AV: E=Sophos;i="4.84,412,1355097600"; d="scan'208";a="67931714"
Received: from mtv-core-2.cisco.com ([171.68.58.7]) by mtv-iport-4.cisco.com with ESMTP; 04 Jan 2013 23:17:22 +0000
Received: from [10.27.1.132] (sjc-ole-8913.cisco.com [10.27.1.132]) by mtv-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id r04NHL12015567 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 4 Jan 2013 23:17:22 GMT
Date: Fri, 4 Jan 2013 15:17:14 -0800 (PST)
From: Ole Jacobsen <ole@cisco.com>
To: Mark Nottingham <mnot@mnot.net>
Subject: Re: travel guide for the next IETF...
In-Reply-To: <2C17B081-ECE7-4CD0-99AB-72324EA0BE27@mnot.net>
Message-ID: <alpine.OSX.2.01.1301041514310.81626@173-11-110-132-sfba.hfc.comcastbusiness.net>
References: <50DF09C7.1060009@dcrocker.net> <20200.1356985377@sandelman.ca> <4613980CFC78314ABFD7F85CC30277210EE27C34@IL-EX10.ad.checkpoint.com> <2C17B081-ECE7-4CD0-99AB-72324EA0BE27@mnot.net>
User-Agent: Alpine 2.01 (OSX 1266 2009-07-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: Ole Jacobsen <ole@cisco.com>
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 04 Jan 2013 23:17:32 -0000

Mark,

This location was "dictated" (if that's the right word) by a desire to 
co-locate (back-to-back) with the IEEE.

As for transportation to restaurants etc, I believe shuttle options ar
being explored.

Ole

On Fri, 4 Jan 2013, Mark Nottingham wrote:

> If the powers that be want to encourage us to come for the entire 
> week, choosing places like this doesn't help. I don't need a tourist 
> paradise, but I don't want to eat from the same hotel restaurant six 
> days in a row. And needing a car is absurd.
> 
> </grumble>
> 
> P.S. I wonder how the "Stand Your Ground" laws will be interpreted 
> by IETF participants... perhaps our discussions will be extra-civil 
> this time. At least they're recorded...
> 
> 
> 

From ted.ietf@gmail.com  Fri Jan  4 16:03:27 2013
Return-Path: <ted.ietf@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CEC5821F86FA for <ietf@ietfa.amsl.com>; Fri,  4 Jan 2013 16:03:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.978
X-Spam-Level: 
X-Spam-Status: No, score=-1.978 tagged_above=-999 required=5 tests=[AWL=-1.620, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, SARE_LWSHORTT=1.24, SARE_RAND_1=2]
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 Lfex-sTQVzSM for <ietf@ietfa.amsl.com>; Fri,  4 Jan 2013 16:03:26 -0800 (PST)
Received: from mail-ia0-f172.google.com (mail-ia0-f172.google.com [209.85.210.172]) by ietfa.amsl.com (Postfix) with ESMTP id 8CBC021F86F8 for <ietf@ietf.org>; Fri,  4 Jan 2013 16:03:25 -0800 (PST)
Received: by mail-ia0-f172.google.com with SMTP id z13so14502089iaz.31 for <ietf@ietf.org>; Fri, 04 Jan 2013 16:03:24 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=enRUmdEQcA0K5LE9QaS7W6t7eYXS55Nf6RPlEBcmHLA=; b=QYvFj7Brog8s+QElgpWtCbzMcG3LD51AsawPWVkE76GJyU8fb9qfJWV0TOMHThUjVO aOembInlHQWHZ7a+x4KKkoL6qPH9GGA99p6/SpADYJhh+R8dBqq4hQ8vbf94Vv/BiGKT Q1UAdHZQ9bbCPlzRHEjQmrwg8MOcMmpqosM9kFcvp0hh//ZPS1CNh6+Kr7/r2Yess6jn /Q2Ejk/fidzxRRYHTM64U3yXIVhTRDYs0ZSq8DCq1CyL6w/fhK8vk3eHmVB6Eb2BDNle 5eGDoJXVziuhgffy4gvoxtgwe5uJNnADRvPCIFUCUNAliUetja/GBQ/9cX6ApfKXXCiQ 1eeQ==
MIME-Version: 1.0
Received: by 10.50.236.104 with SMTP id ut8mr196712igc.20.1357344204163; Fri, 04 Jan 2013 16:03:24 -0800 (PST)
Received: by 10.43.94.5 with HTTP; Fri, 4 Jan 2013 16:03:23 -0800 (PST)
In-Reply-To: <015c01cdeac4$be33d550$3a9b7ff0$@tndh.net>
References: <CAMm+Lwh2cHRY+Dk2_SDtZZmUbPcgRpP89u3DHUcniJDrKrX_pw@mail.gmail.com> <CAMzo+1a0-90dnjnvs48a9DcNN9DY_edF5hH0__4XRuCaLHtL6Q@mail.gmail.com> <CAMm+LwjzjLc2-=4EdxwHOi21B3dOBUohYc5hhXZHL_Pk+iBBmQ@mail.gmail.com> <6.2.5.6.2.20121229192941.0aae33e8@resistor.net> <CAMm+LwiC0xtJU4vnGFPvAG4VKZdj7Tf3LfW0+pzwxKWTegRREw@mail.gmail.com> <a06240800cd074efd45b8@10.0.1.3> <CAMm+Lwiq+DCzXw572wKs78DG+XzYsJtwCVSPvNuVHSrT=Cr2nA@mail.gmail.com> <a06240809cd0799fee029@10.0.1.3> <50E29EE0.1080107@gmail.com> <50E32CAA.4040507@tana.it> <8C48B86A895913448548E6D15DA7553B72A8D6@xmb-rcd-x09.cisco.com> <00fd01cdea16$c956c720$5c045560$@tndh.net> <CA+9kkMBAm4S5s+sxXuVfp8vZMgZUvBG3YkOiCtegfpA+095_rA@mail.gmail.com> <015c01cdeac4$be33d550$3a9b7ff0$@tndh.net>
Date: Fri, 4 Jan 2013 16:03:24 -0800
Message-ID: <CA+9kkMB9ZdLTAp=XO_KEtgJq6E_=eqCuoooL63ACLiPeLfC=Sg@mail.gmail.com>
Subject: Re: WCIT outcome?
From: Ted Hardie <ted.ietf@gmail.com>
To: Tony Hain <alh-ietf@tndh.net>
Content-Type: multipart/alternative; boundary=14dae9340343208be404d27f531e
Cc: ietf@ietf.org, lynn.st.amour@isoc.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 05 Jan 2013 00:03:28 -0000

--14dae9340343208be404d27f531e
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Fri, Jan 4, 2013 at 1:44 PM, Tony Hain <alh-ietf@tndh.net> wrote:

> > Ted Hardie wrote:
> > On Thu, Jan 3, 2013 at 4:59 PM, Tony Hain <alh-ietf@tndh.net> wrote:
> > Like it or not, governments are fundamentally opposed to the open natur=
e
> of
> > 'the Internet', and they always will be (even the 'reasonable' ones).
> > Managing information flow is how they derive and exercise power
> >
> > Aside from the whole "consent of the governed" issue, this perspective
> seems
> > historically fairly short-sighted.
>
> And that consent is based on information availability. Manage the
> information, and you manage the consent.
>
>
Possibly; the extent to which that management is obvious may, of course,
drive other behavior (cf. =D1=81=D0=B0=D0=BC=D0=B8=D0=B7=D0=B4=D0=B0=CC=81=
=D1=82 [Samizdat] and similar efforts).



> > ...
> > Yes, there were treaty-based efforts to set some common
> > understandings.  Some of those were quite useful, but whenever they
> actually
> > impinged on workings of the real network you got smuggling.  In some
> cases, lots
> > and lots of it, with encouragement from some of the participating
> nations.
> In
> > other words, some countries tried to control their participants in thes=
e
> > international networks very tightly.  Some were content to let their
> merchants
> > get fat off it instead.  There was no universal response.
>
> Shipping Merchant / Harbor Master =3D=3D ISP    : As you see with the
> resolution
> signatories, there is still no universal response.
>
>
Given this, I am somewhat confused why you said "Governments are
fundamentally opposed to the open nature of 'the Internet', and they always
will be (even the 'reasonable' ones)."  If some governments approve open
harbors for shipping and (and its Internet parallel), how are those
governments opposed to the open nature of the Internet?  Did you mean "Some
governments"?


> ...
> > In this new effort at a multilateral framework, we are seeing a clash
> between a
> > desire for sovereign control of the Internet and a desire to reap the
> benefits of
> > open participation.  I think our role in that is to make sure all
> involved
> > understand:  the benefits of the Internet's network effect; the risks i=
n
> allowing
> > nations through which traffic passes to assert sovereignty over the
> flows,
>
> As if professional information control practitioners do not understand th=
e
> risks of information control at a much deeper level than anyone in the IE=
TF
> could ever hope to ...
>
>
The pace and chance of topological change are pieces that are commonly
misunderstood outside the world of Internet engineering.  The amount of
surprise you get when you explain to someone why a routing announcement can
pull all the traffic for your company through $RANDOM_COUNTRY seems
perennial.



> > especially given both the pace and chance of topological change; and th=
e
> reality
> > that entities outside of governments control the paths that packets
> actual
> > traverse.
>
> The entities that operate and control the paths do so at the pleasure of
> the
> governments, just as the merchants and harbor masters did in your example
> above.


This is not the point I was making.  The operator of an infrastructure may
do so at the pleasure of the sovereign power in whose borders that
infrastructure sits, but that does not guarantee that packets will flow
over that infrastructure at the pleasure of that sovereign power.  If I do
not wish my packets from Den Haag to Paris to flow through the LINX, for
example, I can ensure that they do not.  That works because there are
multiple paths over which I might send the flow.  Internet routing is not
as open as sea-born trade; there are  paths that provide choke points.
But single points of failure are not an advantage to Internet engineering,
and providing them to engage well with specific governments both harms the
Internet and, at least in some lights, harms the governments' interests as
well.  We can make sure that's understood and build out the infrastructure
to minimize the choke points as best as we can.


> As long as governments are pleased, the operators can live in a
> fantasy land where they are outside government control.


I don't think that this is a realistic characterization of operators'
attitudes.


> The Dubai
> discussions show what happens when a collection of governments are no
> longer
> pleased ... If that noise level gets high enough the non-signers will hav=
e
> to respond just to maintain some degree of cooperation on other matters
> they
> care about.
>
> Our role is to recognize that there are much bigger issues than the simpl=
e
> process of bit delivery. Yes bit delivery is important, and dynamic, but =
it
> is equivalent to laying the tracks. Standards must be maintained for
> consistent interworking, but it is not the path that matters; just as wit=
h
> rail cars, it is the content that provides the value.


I certainly believe that the value is in the content; packets with no
payload aren't terribly interesting, but I don't see how your conclusion
changes the aims of the IETF in this regard.



> Being highly dynamic
> makes things harder to control, but not impossible. Even in the 'open'
> countries, a few changes in something as apparently disconnected as tax
> laws
> would dramatically change the decisions and behaviors of the operators th=
at
> are 'outside of government control'.
> > ...
>
>
> > Patrik F=C3=A4ltstr=C3=B6m wrote:
> > On 4 jan 2013, at 01:59, Tony Hain <alh-ietf@tndh.net> wrote:
> >
> > > Like it or not, governments are fundamentally opposed to the open
> > > nature of 'the Internet', and they always will be (even the
> 'reasonable'
> ones).
> >
> > Because I do not think generalization is really a reasonable thing to d=
o,
> and even
> > dangerous when discussing governance issues, I disagree with this
> statement.
>
> I agree there is danger here, but I believe the greater danger is embodie=
d
> in this thread due to the lack of acknowledgement that governments always
> have control, even if the control points are not obvious.
>
>
You've returned, though, to doing what Patrik noted was a problem: treating
all governments as if they were a homogeneous mass.  A government controls
a territory and has a set of interests.  They are not an homogeneous mass.


> >
> > Governments want just like businesses success in whatever they do. That
> can in
> > general be divided in two wishes. Short term, in the form of being
> re-elected (or
> > not thrown out of their office) and long term, as in growth of the
> revenue
> of the
> > country they govern.
>
> The second point (restated as 'prosperity for their constituency') is
> really
> just a continuation of the first point.
>
> >
> > They of course have pieces of their operation that belong to law
> enforcement
> > agencies, but they also have those that are responsible of finding rule=
s
> so that
> > non-public sector can grow (to later increase for example tax revenue).
> >
> > Because of this, I encourage people to not generalize per stakeholder
> group, but
> > instead acknowledge that there are different *forces* that are orthogon=
al
> to
> > each other, and calculating "the correct" balance between them is hard.
> Or
> > rather, different people do for different reasons get different results
> when
> > calculating what the for them proper balance is.
> >
> > That is why I personally am against generalization that a stakeholder
> group have
> > one specific view.
>
> I would agree that they all demonstrate a different calculation for the
> importance of various aspects of controlling information flow. My primary
> point here is that the IETF has to accept this as a reality. So far the
> position has been 'this is the technology, & governments need to adapt'. =
At
> the end of the day though, it is the governments that are really in
> control,
> and if the IETF does not want a 'forced adaptation', it need to evolve an=
d
> listen to the needs of a stakeholder group they have tried hard to ignore=
.
>
>
If I can re-state that as "engage with", I would agree; the IETF needs to
work with the Internet Society and others to engage in this process, or we
are pretty much guaranteed not to like the outcomes.  But this is not a
case where we need to lie back and think of England; we need to be active
parts of this process, rather than passively accepting what governments
want.  First and foremost because of the potential damage to the network
and its users, but also to avoid induced multiple personality disorder from
different governments saying different things.  Sweden is not Syria and
Chile is not China.



> >
> > Specifically governments.
> >
> > If when pushed to be forced to choose between two choices *all*
> governments
> > wanted to have control, we would have had many more governments signing
> the
> > proposed treaty that was on the table in Dubai.
> >
> > Instead, when being forced to choose, they picked openness and multi
> > stakeholder bottom up processes.
>
> As noted above, this is due to relative happiness, and limited noise. If
> the
> noise level grows or they become unhappy, the independence of the standar=
ds
> process is a minor pawn in the game, and will be sacrificed to protect
> something more important.
>
>
I believe we can maintain the IETF as independent.  Under some dire
outcomes, its output might cease to be called "standards" by the lights of
certain countries or treaty organizations, and there are certainly risks
there.  But good specs are good specs, and government mandates have changed
in favor of network effects before.

In the mean time, though, far better to thank those who are engaging in
this process, help them where we can, and keep our eyes on the real end
goal:  making the Internet work for everyone.

regards,

Ted


> > ...
>
> Tony
>
>
>

--14dae9340343208be404d27f531e
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Fri, Jan 4, 2013 at 1:44 PM, Tony Hain <span dir=3D"ltr">&lt;<a href=3D"=
mailto:alh-ietf@tndh.net" target=3D"_blank">alh-ietf@tndh.net</a>&gt;</span=
> wrote:<br><div class=3D"gmail_quote"><blockquote class=3D"gmail_quote" st=
yle=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class=3D"im">&gt; Ted Hardie wrote:<br>
&gt; On Thu, Jan 3, 2013 at 4:59 PM, Tony Hain &lt;<a href=3D"mailto:alh-ie=
tf@tndh.net">alh-ietf@tndh.net</a>&gt; wrote:<br>
&gt; Like it or not, governments are fundamentally opposed to the open natu=
re<br>
of<br>
&gt; &#39;the Internet&#39;, and they always will be (even the &#39;reasona=
ble&#39; ones).<br>
&gt; Managing information flow is how they derive and exercise power<br>
&gt;<br>
&gt; Aside from the whole &quot;consent of the governed&quot; issue, this p=
erspective<br>
seems<br>
&gt; historically fairly short-sighted.<br>
<br>
</div>And that consent is based on information availability. Manage the<br>
information, and you manage the consent.<br>
<br></blockquote><div><br>Possibly; the extent to which that management is =
obvious may, of course, drive other behavior (cf. <span lang=3D"ru">=D1=81=
=D0=B0=D0=BC=D0=B8=D0=B7=D0=B4=D0=B0=CC=81=D1=82 [</span>Samizdat] and simi=
lar efforts).<br><br>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D=
"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">

&gt; ...<br>
<div class=3D"im">&gt; Yes, there were treaty-based efforts to set some com=
mon<br>
&gt; understandings. =C2=A0Some of those were quite useful, but whenever th=
ey<br>
actually<br>
&gt; impinged on workings of the real network you got smuggling. =C2=A0In s=
ome<br>
cases, lots<br>
&gt; and lots of it, with encouragement from some of the participating nati=
ons.<br>
In<br>
&gt; other words, some countries tried to control their participants in the=
se<br>
&gt; international networks very tightly. =C2=A0Some were content to let th=
eir<br>
merchants<br>
&gt; get fat off it instead. =C2=A0There was no universal response.<br>
<br>
</div>Shipping Merchant / Harbor Master =3D=3D ISP =C2=A0 =C2=A0: As you se=
e with the resolution<br>
signatories, there is still no universal response.<br>
<br></blockquote><div><br>Given this, I am somewhat confused why you said &=
quot;Governments are fundamentally opposed to the open nature of &#39;the I=
nternet&#39;, and they always will be (even the &#39;reasonable&#39; ones).=
&quot;=C2=A0 If some governments approve open harbors for shipping and (and=
 its Internet parallel), how are those governments opposed to the open natu=
re of the Internet?=C2=A0 Did you mean &quot;Some governments&quot;?<br>
<br><br></div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;=
border-left:1px #ccc solid;padding-left:1ex">
&gt; ...<br>
<div class=3D"im">&gt; In this new effort at a multilateral framework, we a=
re seeing a clash<br>
between a<br>
&gt; desire for sovereign control of the Internet and a desire to reap the<=
br>
benefits of<br>
&gt; open participation. =C2=A0I think our role in that is to make sure all=
 involved<br>
&gt; understand: =C2=A0the benefits of the Internet&#39;s network effect; t=
he risks in<br>
allowing<br>
&gt; nations through which traffic passes to assert sovereignty over the fl=
ows,<br>
<br>
</div>As if professional information control practitioners do not understan=
d the<br>
risks of information control at a much deeper level than anyone in the IETF=
<br>
could ever hope to ...<br>
<div class=3D"im"><br></div></blockquote><div><br>The pace and chance of to=
pological change are pieces that are commonly misunderstood outside the wor=
ld of Internet engineering.=C2=A0 The amount of surprise you get when you e=
xplain to someone why a routing announcement can pull all the traffic for y=
our company through $RANDOM_COUNTRY seems perennial.=C2=A0 <br>
<br>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8e=
x;border-left:1px #ccc solid;padding-left:1ex"><div class=3D"im">
&gt; especially given both the pace and chance of topological change; and t=
he<br>
reality<br>
&gt; that entities outside of governments control the paths that packets ac=
tual<br>
&gt; traverse.<br>
<br>
</div>The entities that operate and control the paths do so at the pleasure=
 of the<br>
governments, just as the merchants and harbor masters did in your example<b=
r>
above. </blockquote><div><br>This is not the point I was making.=C2=A0 The =
operator of an infrastructure may do so at the pleasure of the sovereign po=
wer in whose borders that infrastructure sits, but that does not guarantee =
that packets will flow over that infrastructure at the pleasure of that sov=
ereign power.=C2=A0 If I do not wish my packets from Den Haag to Paris to f=
low through the LINX, for example, I can ensure that they do not.=C2=A0 Tha=
t works because there are multiple paths over which I might send the flow.=
=C2=A0 Internet routing is not as open as sea-born trade; there are=C2=A0 p=
aths that provide choke points.=C2=A0=C2=A0 But single points of failure ar=
e not an advantage to Internet engineering, and providing them to engage we=
ll with specific governments both harms the Internet and, at least in some =
lights, harms the governments&#39; interests as well.=C2=A0 We can make sur=
e that&#39;s understood and build out the infrastructure to minimize the ch=
oke points as best as we can.<br>
=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;bo=
rder-left:1px #ccc solid;padding-left:1ex">As long as governments are pleas=
ed, the operators can live in a<br>
fantasy land where they are outside government control. </blockquote><div><=
br>I don&#39;t think that this is a realistic characterization of operators=
&#39; attitudes.<br>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"=
margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
The Dubai<br>
discussions show what happens when a collection of governments are no longe=
r<br>
pleased ... If that noise level gets high enough the non-signers will have<=
br>
to respond just to maintain some degree of cooperation on other matters the=
y<br>
care about.<br>
<br>
Our role is to recognize that there are much bigger issues than the simple<=
br>
process of bit delivery. Yes bit delivery is important, and dynamic, but it=
<br>
is equivalent to laying the tracks. Standards must be maintained for<br>
consistent interworking, but it is not the path that matters; just as with<=
br>
rail cars, it is the content that provides the value.</blockquote><div><br>=
I certainly believe that the value is in the content; packets with no paylo=
ad aren&#39;t terribly interesting, but I don&#39;t see how your conclusion=
 changes the aims of the IETF in this regard.=C2=A0 <br>
<br>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8e=
x;border-left:1px #ccc solid;padding-left:1ex"> Being highly dynamic<br>
makes things harder to control, but not impossible. Even in the &#39;open&#=
39;<br>
countries, a few changes in something as apparently disconnected as tax law=
s<br>
would dramatically change the decisions and behaviors of the operators that=
<br>
are &#39;outside of government control&#39;.<br>
&gt; ...<br>
<br>
<br>
&gt; Patrik F=C3=A4ltstr=C3=B6m wrote:<br>
<div class=3D"im">&gt; On 4 jan 2013, at 01:59, Tony Hain &lt;<a href=3D"ma=
ilto:alh-ietf@tndh.net">alh-ietf@tndh.net</a>&gt; wrote:<br>
&gt;<br>
&gt; &gt; Like it or not, governments are fundamentally opposed to the open=
<br>
&gt; &gt; nature of &#39;the Internet&#39;, and they always will be (even t=
he &#39;reasonable&#39;<br>
ones).<br>
&gt;<br>
</div><div class=3D"im">&gt; Because I do not think generalization is reall=
y a reasonable thing to do,<br>
and even<br>
&gt; dangerous when discussing governance issues, I disagree with this<br>
statement.<br>
<br>
</div>I agree there is danger here, but I believe the greater danger is emb=
odied<br>
in this thread due to the lack of acknowledgement that governments always<b=
r>
have control, even if the control points are not obvious.<br>
<div class=3D"im"><br></div></blockquote><div><br>You&#39;ve returned, thou=
gh, to doing what Patrik noted was a problem: treating all governments as i=
f they were a homogeneous mass.=C2=A0 A government controls a territory and=
 has a set of interests.=C2=A0 They are not an homogeneous mass.<br>
=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;bo=
rder-left:1px #ccc solid;padding-left:1ex"><div class=3D"im">
&gt;<br>
&gt; Governments want just like businesses success in whatever they do. Tha=
t<br>
can in<br>
&gt; general be divided in two wishes. Short term, in the form of being<br>
re-elected (or<br>
&gt; not thrown out of their office) and long term, as in growth of the rev=
enue<br>
of the<br>
&gt; country they govern.<br>
<br>
</div>The second point (restated as &#39;prosperity for their constituency&=
#39;) is really<br>
just a continuation of the first point.<br>
<div class=3D"im"><br>
&gt;<br>
&gt; They of course have pieces of their operation that belong to law<br>
enforcement<br>
&gt; agencies, but they also have those that are responsible of finding rul=
es<br>
so that<br>
&gt; non-public sector can grow (to later increase for example tax revenue)=
.<br>
&gt;<br>
&gt; Because of this, I encourage people to not generalize per stakeholder<=
br>
group, but<br>
&gt; instead acknowledge that there are different *forces* that are orthogo=
nal<br>
to<br>
&gt; each other, and calculating &quot;the correct&quot; balance between th=
em is hard. Or<br>
&gt; rather, different people do for different reasons get different result=
s<br>
when<br>
&gt; calculating what the for them proper balance is.<br>
&gt;<br>
&gt; That is why I personally am against generalization that a stakeholder<=
br>
group have<br>
&gt; one specific view.<br>
<br>
</div>I would agree that they all demonstrate a different calculation for t=
he<br>
importance of various aspects of controlling information flow. My primary<b=
r>
point here is that the IETF has to accept this as a reality. So far the<br>
position has been &#39;this is the technology, &amp; governments need to ad=
apt&#39;. At<br>
the end of the day though, it is the governments that are really in control=
,<br>
and if the IETF does not want a &#39;forced adaptation&#39;, it need to evo=
lve and<br>
listen to the needs of a stakeholder group they have tried hard to ignore.<=
br>
<div class=3D"im"><br></div></blockquote><div><br>If I can re-state that as=
 &quot;engage with&quot;, I would agree; the IETF needs to work with the In=
ternet Society and others to engage in this process, or we are pretty much =
guaranteed not to like the outcomes.=C2=A0 But this is not a case where we =
need to lie back and think of England; we need to be active parts of this p=
rocess, rather than passively accepting what governments want.=C2=A0 First =
and foremost because of the potential damage to the network and its users, =
but also to avoid induced multiple personality disorder from different gove=
rnments saying different things.=C2=A0 Sweden is not Syria and Chile is not=
 China.<br>
<br>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8e=
x;border-left:1px #ccc solid;padding-left:1ex"><div class=3D"im">
&gt;<br>
&gt; Specifically governments.<br>
&gt;<br>
&gt; If when pushed to be forced to choose between two choices *all*<br>
governments<br>
&gt; wanted to have control, we would have had many more governments signin=
g<br>
the<br>
&gt; proposed treaty that was on the table in Dubai.<br>
&gt;<br>
&gt; Instead, when being forced to choose, they picked openness and multi<b=
r>
&gt; stakeholder bottom up processes.<br>
<br>
</div>As noted above, this is due to relative happiness, and limited noise.=
 If the<br>
noise level grows or they become unhappy, the independence of the standards=
<br>
process is a minor pawn in the game, and will be sacrificed to protect<br>
something more important.<br>
<br></blockquote><div><br>I believe we can maintain the IETF as independent=
.=C2=A0 Under some dire outcomes, its output might cease to be called &quot=
;standards&quot; by the lights of certain countries or treaty organizations=
, and there are certainly risks there.=C2=A0 But good specs are good specs,=
 and government mandates have changed in favor of network effects before.<b=
r>
<br>In the mean time, though, far better to thank those who are engaging in=
 this process, help them where we can, and keep our eyes on the real end go=
al:=C2=A0 making the Internet work for everyone.<br><br>regards,<br><br>Ted=
 <br>
=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;bo=
rder-left:1px #ccc solid;padding-left:1ex">
&gt; ...<br>
<span class=3D"HOEnZb"><font color=3D"#888888"><br>
Tony<br>
<br>
<br>
</font></span></blockquote></div><br>

--14dae9340343208be404d27f531e--

From worley@shell01.TheWorld.com  Fri Jan  4 16:42:03 2013
Return-Path: <worley@shell01.TheWorld.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 58B7D21F876E for <ietf@ietfa.amsl.com>; Fri,  4 Jan 2013 16:42:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.98
X-Spam-Level: 
X-Spam-Status: No, score=-2.98 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, RCVD_IN_SORBS_WEB=0.619]
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 KTk--L4LpeoJ for <ietf@ietfa.amsl.com>; Fri,  4 Jan 2013 16:42:02 -0800 (PST)
Received: from TheWorld.com (pcls5.std.com [192.74.137.145]) by ietfa.amsl.com (Postfix) with ESMTP id 9A7FE21F8765 for <ietf@ietf.org>; Fri,  4 Jan 2013 16:42:02 -0800 (PST)
Received: from shell.TheWorld.com (svani@shell01.theworld.com [192.74.137.71]) by TheWorld.com (8.14.5/8.14.5) with ESMTP id r050fp8t000416 for <ietf@ietf.org>; Fri, 4 Jan 2013 19:41:53 -0500
Received: from shell01.TheWorld.com (localhost.theworld.com [127.0.0.1]) by shell.TheWorld.com (8.13.6/8.12.8) with ESMTP id r050fpRM4514916 for <ietf@ietf.org>; Fri, 4 Jan 2013 19:41:51 -0500 (EST)
Received: (from worley@localhost) by shell01.TheWorld.com (8.13.6/8.13.6/Submit) id r050fpGh4501838; Fri, 4 Jan 2013 19:41:51 -0500 (EST)
Date: Fri, 4 Jan 2013 19:41:51 -0500 (EST)
Message-Id: <201301050041.r050fpGh4501838@shell01.TheWorld.com>
From: worley@ariadne.com (Dale R. Worley)
Sender: worley@ariadne.com (Dale R. Worley)
To: ietf@ietf.org
In-reply-to: <A2EB5895-E8D7-4CD2-921A-22082631D0B5@shinkuro.com> (steve@shinkuro.com)
Subject: Re: Acoustic couplers
References: <20130102175839.2DDAE18C0BB@mercury.lcs.mit.edu> <01OOIM6DH1HW00008S@mauve.mrochek.com> <50E4AFAF.4000506@dcrocker.net> <01OOIXYRHRN000008S@mauve.mrochek.com> <50E59B43.8000702@dcrocker.net> <2877F05C-BF25-42DE-BF77-1854CC955A54@shinkuro.com> <600960B19F7C535FA242D982@JcK-HP8200.jck.com> <A2EB5895-E8D7-4CD2-921A-22082631D0B5@shinkuro.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 05 Jan 2013 00:42:03 -0000

> From: Steve Crocker <steve@shinkuro.com>
> 
> I honestly don't remember whether the plugs were the clunky four pin
> or the then-modern RJ11.  I recall studying RJ11 and RJ45 plugs and
> sockets at some point and discovering that some plugs and sockets
> had six wires instead of only four or two.  I never did learn if
> they had a different number.  The form factor was the same.

Wikipedia has a long list:
http://en.wikipedia.org/wiki/Registered_jack It's probably not
complete.

Dale

From randy@psg.com  Fri Jan  4 16:46:52 2013
Return-Path: <randy@psg.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0EA7E21F84FD for <ietf@ietfa.amsl.com>; Fri,  4 Jan 2013 16:46:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.523
X-Spam-Level: 
X-Spam-Status: No, score=-2.523 tagged_above=-999 required=5 tests=[AWL=0.076,  BAYES_00=-2.599]
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 VP5frJFCwSTV for <ietf@ietfa.amsl.com>; Fri,  4 Jan 2013 16:46:45 -0800 (PST)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by ietfa.amsl.com (Postfix) with ESMTP id 70AFD21F8235 for <ietf@ietf.org>; Fri,  4 Jan 2013 16:46:44 -0800 (PST)
Received: from localhost ([127.0.0.1] helo=ryuu.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.80.1 (FreeBSD)) (envelope-from <randy@psg.com>) id 1TrHuM-0008uP-3H; Sat, 05 Jan 2013 00:46:42 +0000
Date: Sat, 05 Jan 2013 09:46:40 +0900
Message-ID: <m238ygqwwf.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Ted Hardie <ted.ietf@gmail.com>
Subject: Re: WCIT outcome?
In-Reply-To: <CA+9kkMB9ZdLTAp=XO_KEtgJq6E_=eqCuoooL63ACLiPeLfC=Sg@mail.gmail.com>
References: <CAMm+Lwh2cHRY+Dk2_SDtZZmUbPcgRpP89u3DHUcniJDrKrX_pw@mail.gmail.com> <CAMzo+1a0-90dnjnvs48a9DcNN9DY_edF5hH0__4XRuCaLHtL6Q@mail.gmail.com> <CAMm+LwjzjLc2-=4EdxwHOi21B3dOBUohYc5hhXZHL_Pk+iBBmQ@mail.gmail.com> <6.2.5.6.2.20121229192941.0aae33e8@resistor.net> <CAMm+LwiC0xtJU4vnGFPvAG4VKZdj7Tf3LfW0+pzwxKWTegRREw@mail.gmail.com> <a06240800cd074efd45b8@10.0.1.3> <CAMm+Lwiq+DCzXw572wKs78DG+XzYsJtwCVSPvNuVHSrT=Cr2nA@mail.gmail.com> <a06240809cd0799fee029@10.0.1.3> <50E29EE0.1080107@gmail.com> <50E32CAA.4040507@tana.it> <8C48B86A895913448548E6D15DA7553B72A8D6@xmb-rcd-x09.cisco.com> <00fd01cdea16$c956c720$5c045560$@tndh.net> <CA+9kkMBAm4S5s+sxXuVfp8vZMgZUvBG3YkOiCtegfpA+095_rA@mail.gmail.com> <015c01cdeac4$be33d550$3a9b7ff0$@tndh.net> <CA+9kkMB9ZdLTAp=XO_KEtgJq6E_=eqCuoooL63ACLiPeLfC=Sg@mail.gmail.com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.7 - "Harue")
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Cc: IETF Disgust <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 05 Jan 2013 00:46:52 -0000

>> And that consent is based on information availability. Manage the
>> information, and you manage the consent.
> Possibly; the extent to which that management is obvious may, of course,
> drive other behavior (cf. =D1=81=D0=B0=D0=BC=D0=B8=D0=B7=D0=B4=D0=B0=CC=
=81=D1=82 [Samizdat] and similar efforts).

or, in the states, wikileaks. =20

http://www.huffingtonpost.com/john-cusack/what-is-an-assange_b_2317824.html

randy

From ned+ietf@mauve.mrochek.com  Fri Jan  4 17:16:38 2013
Return-Path: <ned+ietf@mauve.mrochek.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A149F21F88E6 for <ietf@ietfa.amsl.com>; Fri,  4 Jan 2013 17:16:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 87NuRx+dwCuA for <ietf@ietfa.amsl.com>; Fri,  4 Jan 2013 17:16:38 -0800 (PST)
Received: from mauve.mrochek.com (mauve.mrochek.com [66.59.230.40]) by ietfa.amsl.com (Postfix) with ESMTP id 161CA21F872C for <ietf@ietf.org>; Fri,  4 Jan 2013 17:16:38 -0800 (PST)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01OOLLQ7DW1S004K1U@mauve.mrochek.com> for ietf@ietf.org; Fri, 4 Jan 2013 17:11:33 -0800 (PST)
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01OOJ8U2Q2U800008S@mauve.mrochek.com> (original mail from NED@mauve.mrochek.com) for ietf@ietf.org; Fri, 4 Jan 2013 17:11:28 -0800 (PST)
From: ned+ietf@mauve.mrochek.com
Message-id: <01OOLLQ4P2AE00008S@mauve.mrochek.com>
Date: Fri, 04 Jan 2013 17:05:16 -0800 (PST)
Subject: Re: I'm struggling with 2219 language again
In-reply-to: "Your message dated Fri, 04 Jan 2013 17:23:42 -0500" <201301042223.r04MNgRA020196@cichlid.raleigh.ibm.com>
MIME-version: 1.0
References: <7ED55FF1-3E1A-4DF7-918E-07790517B848@softarmor.com> <50E68CB5.4010107@gmail.com> <201301042223.r04MNgRA020196@cichlid.raleigh.ibm.com>
To: Thomas Narten <narten@us.ibm.com>
Cc: Dean Willis <dean.willis@softarmor.com>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 05 Jan 2013 01:16:38 -0000

> +1 to Brian and others saying upper case should be used sparingly, and
> only where it really matters. If even then.

That's the entire point: The terms provide additional information as to 
what the authors consider the important points of compliance to be.

> The notion (that some have) that MUST means you have to do something
> to be compliant and that a "must" (lower case) is optional is just
> nuts.

In some ways I find the use of SHOULD and SHOULD NOT be to be more useful
than MUST and MUST NOT. MUST and MUST NOT are usually obvious. SHOULD and
SHOULD NOT are things on the boundary, and how boundary cases are handled
is often what separated a good implementation from a mediocre or even poor
one.

> If the ARP spec were to say, "upon receipt of an ARP request, the
> recipient sends back an ARP response," does the lack of a MUST there
> mean the response is optional? Surely not. And if we make it only a
> SHOULD (e.g., to allow rate limiting of responses - a very reasonable
> thing to do), does lack of MUST now make the feature optional from a
> compliance/interoperability perspective?

> The idea that upper case language can be used to identify all the
> required parts of a specificition from a
> compliance/conformance/interoperability perspective is just
> wrong. This has never been the case (and would be exceeding painful to
> do), though (again) some people seem to think this would be useful and
> thus like lots of upper case language.

At most it provides the basis for a compliance checklist. But such checklists
never cover all the points involved in compliance. Heck, most specifications in
toto don't do that. Some amount of common sense is always required.

> Where you want to use MUST is where an implementation might be tempted
> to take a short cut -- to the detriment of the Internet -- but could
> do so without actually breaking interoperability. A good example is
> with retransmissions and exponential backoff. You can implement those
> incorrectly (or not at all), and still get "interoperability". I.e.,
> two machines can talk to each other. Maybe you don't get "good"
> intereoperability and maybe not great performance under some
> conditions, but you can still build an interoperabile implementation.

> IMO, too many specs seriously overuse/misuse 2119 language, to the
> detriment of readability, common sense, and reserving the terms to
> bring attention to those cases where it really is important to
> highlight an important point that may not be obvious to a casual
> reader/implementor.

Sadly true.

				Ned

From hsantos@isdg.net  Fri Jan  4 19:24:53 2013
Return-Path: <hsantos@isdg.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CCF3221F86BC for <ietf@ietfa.amsl.com>; Fri,  4 Jan 2013 19:24:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 PT9oCTZLRJOc for <ietf@ietfa.amsl.com>; Fri,  4 Jan 2013 19:24:52 -0800 (PST)
Received: from secure.winserver.com (secure.winserver.com [208.247.131.9]) by ietfa.amsl.com (Postfix) with ESMTP id A87CF21F86C2 for <ietf@ietf.org>; Fri,  4 Jan 2013 19:24:52 -0800 (PST)
DKIM-Signature: v=1; d=isdg.net; s=tms1; a=rsa-sha1; c=simple/relaxed; l=5497; t=1357356284; h=Received:Received: Received:Received:Message-ID:Date:From:Organization:To:Subject: List-ID; bh=Cqr67RPrdAXR6rOpV3Batt1D1U4=; b=YScUYzjaB/xV9H1R0vln yBLtH98tncMPXkNeoeDUVZuyoNlzFf1kc6BJ17PxAQyAuN+HyAvRDlhgnevtDkzJ T8ZKPfJo/PsdFWXHo5395sIM8fo1H6JBRWV8MgEpht11q5MF15u020PvEMNo4Cn2 vCbgiGun/+IbaRPHqSrjaHo=
Received: by winserver.com (Wildcat! SMTP Router v7.0.454.4) for ietf@ietf.org; Fri, 04 Jan 2013 22:24:44 -0500
Authentication-Results: dkim.winserver.com; dkim=pass header.d=beta.winserver.com header.s=tms1 header.i=beta.winserver.com;  adsp=pass policy=all author.d=isdg.net asl.d=beta.winserver.com;
Received: from beta.winserver.com ([208.247.131.23]) by winserver.com (Wildcat! SMTP v7.0.454.4) with ESMTP id 493047445.3.5724; Fri, 04 Jan 2013 22:24:44 -0500
DKIM-Signature: v=1; d=beta.winserver.com; s=tms1; a=rsa-sha256; c=simple/relaxed; l=5497; t=1357356235; h=Received:Received: Message-ID:Date:From:Organization:To:Subject:List-ID; bh=w3M9ZvA d/FNyo6Et9gXectiXWld5zwEtTr9+R6dh6n4=; b=h6Bvp2C2XuegXBIgMn7sC3O eHB2eN4UPcJ/HQ6B34kXCK6KcMTkBcqCQ2JNZNka3LpgUrHxNnWGV+B0Ep8pUQ+J 6LVnvf+30XvM+hfTj7Hy9BYGhdwd+Vl0t33OJcbWrCYpADdWz5eVnjbX/9yoRfdG A/TgXCiL8Y0PYfsHIb8E=
Received: by beta.winserver.com (Wildcat! SMTP Router v7.0.454.4) for ietf@ietf.org; Fri, 04 Jan 2013 22:23:55 -0500
Received: from [192.168.1.101] ([99.3.147.93]) by beta.winserver.com (Wildcat! SMTP v7.0.454.4) with ESMTP id 1091751632.10.5072; Fri, 04 Jan 2013 22:23:55 -0500
Message-ID: <50E79D02.5030000@isdg.net>
Date: Fri, 04 Jan 2013 22:24:50 -0500
From: Hector Santos <hsantos@isdg.net>
Organization: Santronics Software, Inc.
User-Agent: Thunderbird 2.0.0.24 (Windows/20100228)
MIME-Version: 1.0
To: Scott Brim <swb@internet2.edu>
Subject: Re: I'm struggling with 2219 language again
References: <7ED55FF1-3E1A-4DF7-918E-07790517B848@softarmor.com> <50E719DA.1040709@internet2.edu>
In-Reply-To: <50E719DA.1040709@internet2.edu>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org, Dean Willis <dean.willis@softarmor.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 05 Jan 2013 03:24:53 -0000

Scott Brim wrote:
> It's a communication problem.  If you want your audience to understand
> exactly what you're saying, and implement along very specific lines, you
> need to tell them in a way they understand.  

+1

> Personally I prefer a quieter approach, but I've been told that 
> these days one MUST use MUST or implementors just won't get it.  
> "Huh, that's a requirement?  But you didn't say MUST."  

I believe in the technical writing style of "Being specific is Terrific!"


>I suggest
> turning this thread into a survey, and
> finding out how people who actually write code look for in order to know
> what's required.

+1

We have implemented numerous protocols since the 80s. I have a 
specific method of approaching a new protocol implementation which 
allows for fastest implementation, testing proof of concept and above 
all minimum cost.  Why bother with the costly complexities of 
implementing SHOULDs and MAYs, if the minimum is not something you 
want in the end anyway?

A good data point is that for IP/Legal reasons, we do not use other 
people's code if we can help it and in the early days, open source was 
not as wide spread or even acceptable at the corporate level. In other 
words, it was all done in-house, purchased or nothing.  I also believe 
using other people's code has a high cost as well since you don't have 
an in-house expert understanding the inner workings of the externally 
developed software.

o Step 1 for Protocol Implementation:

Look for all the MUST protocol features.  This includes the explicit 
ones and watchful of semantics where its obviously required or things 
will break, perhaps it fell thru the crack.

An important consideration for a MUST is that operators are not given 
the opportunity to disable these protocol required features. So from a 
coding standpoint, this is one area you don't have to worry about 
designing configuration tools, the UI, nor including operation 
guidelines and documentation for these inherent protocol required 
features.

This is the minimum coding framework to allow for all inteop testing 
with other software and systems.

The better RFC spec is the one that has documented a checklist, a 
minimum requirement summary table, etc. Good example is RFC 1113 for 
the various internet hosting protocols. I considered RFC 1123 the "bible!"

Technical writing tip: Please stay away from verbosity especially of 
subjective concepts and please stop writing as if everyone is stupid.

     I always viewed the IETF RFC format as a blend of two steps
     of the SE process - functional and technical specifications.
     Functional specs tell us what we want and technical specs
     tell us how we do it.  So unless a specific functional requirements
     RFC was written, maybe some verbosity is needed but it should
     be minimized.

Generally, depending on the protocol, we can release code just on 
using MUST requirements - the bottom line framework for client/server 
communications.  Only when this is completely successfully, can your 
implementation consider moving on at extending the protocol 
implementation with additional SHOULD, MAY features and its optional 
complexities.

o Step 2

Look for the SHOULDs.  This is the candies of the protocol.  If the 
SHOULD is really simple to implement, it can be lumped in with step 1.

I know many believe a SHOULD are really a MUST as an alternative 
method perhaps - different version of MUST to be done nonetheless.

However, I believe these folks play down an important consideration 
for implementing SHOULD based protocol features:

    Developers need to offer these as options to deployment operators.

In other words, if the operator can not turn it off then a SHOULD was 
incorrectly used for a MUST which is required with no operator option 
to disable.

o Step 3

Look for the MAYs.   Very similar to SHOULD, a good way to consider a 
SHOULD is as a default enabled (ON out of the box) option and a MAY as 
a default disabled (OFF out of the box) option.

Summary:

   MUST   - required, no operator option to disabled. Of course,
            its possible to have a hidden, undocumented switch
            for questionable stuff.

   SHOULD - good idea, recommended. if implemented, enabled it
            out of the box.

   MAY    - similar to SHOULD, does not have to be enabled out
            of box.

In both cases for SHOULD and MAY, the operator can turn these protocol 
features off/on. For a MUST, the operator can not turn the MUST 
feature. These SHOULD/MAY features are documented for operators and 
support.

One last thing, I believe in a concept I call CoComp - Cooperative 
Competition, where all competitive implementators, including the 
protocol technology leader all share a common framework for a minimum 
protocol generic to all parties and the internet community. It is 
least required to solve the problem or provide a communication avenue. 
  All else, the SHOULDs, the MAYs, is added value for competing 
implementators.  It generally is what differentiate the various 
implementators software.

I personally believe it is doable to write a new RFC that describe a 
guideline for protocol development that will minimize conflicts at 
many levels.  Of course, a major part of that is good technical 
writing skills in principle and the ability to extract and describe 
what the protocol framework is, which brings it all back to the 
original issue using the proper communications verbiage to describe a 
protocol.

-- 
HLS



From glenzorn@gmail.com  Fri Jan  4 20:44:15 2013
Return-Path: <glenzorn@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EEEA021F86C9 for <ietf@ietfa.amsl.com>; Fri,  4 Jan 2013 20:44:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 dUKsJBdtB-wW for <ietf@ietfa.amsl.com>; Fri,  4 Jan 2013 20:44:15 -0800 (PST)
Received: from mail-pb0-f48.google.com (mail-pb0-f48.google.com [209.85.160.48]) by ietfa.amsl.com (Postfix) with ESMTP id 6090D21F86E7 for <ietf@ietf.org>; Fri,  4 Jan 2013 20:44:02 -0800 (PST)
Received: by mail-pb0-f48.google.com with SMTP id rq13so9568295pbb.21 for <ietf@ietf.org>; Fri, 04 Jan 2013 20:44:02 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=ouYA7KVleZ4OTUHIi6jo5tNKmjlScVRmhczu1VpSEAc=; b=ovtDOfKw2bCj9CAlR6CIe2lZeLKlpiRbatpiMHhEtkjq4sKFFA9ucPsqCZKT1w6Mb2 7bSBiu+7VJ/ydjfe/j26Rx6Sh0JrecUst1tlozHZY08jQr0fJOIg5gwemkqT6vFkoX0R /v6TK3/f54L3TDCyPIt8taQa/LZv170GQ/Rd+fsGeAOXuULMxkAxU7BjKYDlS+bWxjHn 7pszAKMmstlp2BwFP1tW2Pa3Pq+FyBASuozMP8b97jm+/WZhJVBF3qLYNw/6ew/tdoia uyUeuVjHqXqdUfSNGRydBTyfMBOilUIC2iBtE/YsMnEEeeLLlswpLh6GrRRR9Rtca8Vs bJJw==
X-Received: by 10.68.132.98 with SMTP id ot2mr167903773pbb.39.1357361042150; Fri, 04 Jan 2013 20:44:02 -0800 (PST)
Received: from [192.168.0.102] (ppp-58-11-142-173.revip2.asianet.co.th. [58.11.142.173]) by mx.google.com with ESMTPS id n10sm23727721pav.18.2013.01.04.20.43.59 (version=SSLv3 cipher=OTHER); Fri, 04 Jan 2013 20:44:00 -0800 (PST)
Message-ID: <50E7AF8D.9010603@gmail.com>
Date: Sat, 05 Jan 2013 11:43:57 +0700
From: Glen Zorn <glenzorn@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: Ole Jacobsen <ole@cisco.com>
Subject: Re: travel guide for the next IETF...
References: <50DF09C7.1060009@dcrocker.net> <20200.1356985377@sandelman.ca> <4613980CFC78314ABFD7F85CC30277210EE27C34@IL-EX10.ad.checkpoint.com> <2C17B081-ECE7-4CD0-99AB-72324EA0BE27@mnot.net> <alpine.OSX.2.01.1301041514310.81626@173-11-110-132-sfba.hfc.comcastbusiness.net>
In-Reply-To: <alpine.OSX.2.01.1301041514310.81626@173-11-110-132-sfba.hfc.comcastbusiness.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Mark Nottingham <mnot@mnot.net>, IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 05 Jan 2013 04:44:16 -0000

On 01/05/2013 06:17 AM, Ole Jacobsen wrote:

>
 > Mark,
 >
 > This location was "dictated" (if that's the right word) by a desire
 > to co-locate (back-to-back) with the IEEE.

So if you don't attend IEEE, quit your whining:  at least you won't have 
to eat he same hotel food for 2 weeks in a row...

...


From johnl@iecc.com  Fri Jan  4 20:52:08 2013
Return-Path: <johnl@iecc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C417821F8659 for <ietf@ietfa.amsl.com>; Fri,  4 Jan 2013 20:52:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -111.199
X-Spam-Level: 
X-Spam-Status: No, score=-111.199 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HABEAS_ACCREDITED_SOI=-4.3, RCVD_IN_BSP_TRUSTED=-4.3, USER_IN_WHITELIST=-100]
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 xWLxsxJU-3Rs for <ietf@ietfa.amsl.com>; Fri,  4 Jan 2013 20:52:07 -0800 (PST)
Received: from leila.iecc.com (leila6.iecc.com [IPv6:2001:470:1f07:1126:0:4c:6569:6c61]) by ietfa.amsl.com (Postfix) with ESMTP id 8B91121F85AC for <ietf@ietf.org>; Fri,  4 Jan 2013 20:52:07 -0800 (PST)
Received: (qmail 11028 invoked from network); 5 Jan 2013 04:52:04 -0000
Received: from leila.iecc.com (64.57.183.34) by mail1.iecc.com with QMQP; 5 Jan 2013 04:52:04 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:vbr-info; s=50e7b174.xn--3zv.k1301; i=johnl@user.iecc.com; bh=Rse2EjhTTaX71YSiwns4oibNVZJJmKv/IN0Fa5CrBcg=; b=VRI5n48kBJG93JuVW5avTa1MO6ZGznIXIN/r3eWm3Pgt20uFaqU5zsWQOZkO8xOPgSzz3eDYCHxNqiZ3ALMlDp2MBVJNdcyfSyT5lCha1mWG8ls5iB6UxlgzFHtEffGMYOIwhTmQ1w2MDqsNwxI7a4ByNbJJSYslW0Qq7su83S4=
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:vbr-info; s=50e7b174.xn--3zv.k1301; olt=johnl@user.iecc.com; bh=Rse2EjhTTaX71YSiwns4oibNVZJJmKv/IN0Fa5CrBcg=; b=Z+oe8gVVJj4e4+kry4RCiga5AZKIiOaEhLdriVewImvvuR8n3QORt18Y1ObYYZz01Iz9sWxKWAMi3gOaRx6aMi8JdzZslIh1Gfdm5k6P/C5EOcWwYHZ2oXMlxxcj78WKHd9MYDob0E3toxW7SstwbCzk96Py97tv6Fj5XfGd6tg=
VBR-Info: md=iecc.com; mc=all; mv=dwl.spamhaus.org
Date: 5 Jan 2013 04:51:41 -0000
Message-ID: <20130105045141.35864.qmail@joyce.lan>
From: "John Levine" <johnl@taugh.com>
To: ietf@ietf.org
Subject: Re: travel guide for the next IETF...
In-Reply-To: <50E7AF8D.9010603@gmail.com>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 05 Jan 2013 04:52:08 -0000

>So if you don't attend IEEE, quit your whining:  at least you won't have 
>to eat he same hotel food for 2 weeks in a row...

You don't have to eat there.  Check out the reviews of this restaurant
across the street:

https://plus.google.com/118141773512616354020/about


From glenzorn@gmail.com  Fri Jan  4 22:26:41 2013
Return-Path: <glenzorn@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B371021F874B for <ietf@ietfa.amsl.com>; Fri,  4 Jan 2013 22:26:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 9tzlgdrg7pMx for <ietf@ietfa.amsl.com>; Fri,  4 Jan 2013 22:26:41 -0800 (PST)
Received: from mail-pb0-f47.google.com (mail-pb0-f47.google.com [209.85.160.47]) by ietfa.amsl.com (Postfix) with ESMTP id 4B45B21F8201 for <ietf@ietf.org>; Fri,  4 Jan 2013 22:26:41 -0800 (PST)
Received: by mail-pb0-f47.google.com with SMTP id un1so9543006pbc.20 for <ietf@ietf.org>; Fri, 04 Jan 2013 22:26:41 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=DchqRL4WeFNfeI+GNeoXMw6gyfd4go9/wvQk8em5hOY=; b=fex7ZNlYuA28HDD+CLQ8YxCQTJYqcNvs8yX6xhYRWozRFifAxNYQ2vzMH54Fswq8Cl 04QXRF3tAdfWKkh4D5bFI3ZJ0f8+hJloh29nFpBFfJiiwQCNgXytW6MPzUorbBG4OTwz 7ceTgfIrXHakEoiJrM3W68W9ysK/3CIgh6r/LtqGJT02qiwfcfGaSol5tAVGobAxdBJr yCPSKyar2GZQC6QZ0AP3HVH1oLlQDBfx+lqyk8ewvzU17zx6bzSgs7rJFc+AVnI5ZiK0 NSfjzeQkKUj/mQGbzQUHZyBPNyWkLYLyGW9hJgzGxRp8dR4+0qYFZjy35NWsWtc781hs VY4g==
X-Received: by 10.68.213.233 with SMTP id nv9mr168380199pbc.155.1357367201064;  Fri, 04 Jan 2013 22:26:41 -0800 (PST)
Received: from [192.168.0.102] (ppp-58-11-142-173.revip2.asianet.co.th. [58.11.142.173]) by mx.google.com with ESMTPS id nm2sm33553564pbc.43.2013.01.04.22.26.38 (version=SSLv3 cipher=OTHER); Fri, 04 Jan 2013 22:26:40 -0800 (PST)
Message-ID: <50E7C79C.90004@gmail.com>
Date: Sat, 05 Jan 2013 13:26:36 +0700
From: Glen Zorn <glenzorn@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: John Levine <johnl@taugh.com>
Subject: Re: travel guide for the next IETF...
References: <20130105045141.35864.qmail@joyce.lan>
In-Reply-To: <20130105045141.35864.qmail@joyce.lan>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 05 Jan 2013 06:26:41 -0000

On 01/05/2013 11:51 AM, John Levine wrote:

>> So if you don't attend  IEEE, quit your whining: at least you won't
 >> have to eat he same hotel food for 2 weeks in a row...
 >
 > You don't have to eat there. Check out the reviews of this
 > restaurant across the street:
 >
 > https://plus.google.com/118141773512616354020/about

Splendid, sign me up!


From ynir@checkpoint.com  Sat Jan  5 00:13:58 2013
Return-Path: <ynir@checkpoint.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0697521F8599 for <ietf@ietfa.amsl.com>; Sat,  5 Jan 2013 00:13:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 5qg53lwPOJb0 for <ietf@ietfa.amsl.com>; Sat,  5 Jan 2013 00:13:57 -0800 (PST)
Received: from smtp.checkpoint.com (smtp.checkpoint.com [194.29.34.68]) by ietfa.amsl.com (Postfix) with ESMTP id 1AF3E21F8523 for <ietf@ietf.org>; Sat,  5 Jan 2013 00:13:56 -0800 (PST)
Received: from IL-EX10.ad.checkpoint.com ([194.29.34.147]) by smtp.checkpoint.com (8.13.8/8.13.8) with ESMTP id r058DsGB028173; Sat, 5 Jan 2013 10:13:54 +0200
X-CheckPoint: {50E7DEE1-0-1B221DC2-2FFFF}
Received: from IL-EX10.ad.checkpoint.com ([169.254.2.22]) by IL-EX10.ad.checkpoint.com ([169.254.2.238]) with mapi id 14.02.0318.004; Sat, 5 Jan 2013 10:13:53 +0200
From: Yoav Nir <ynir@checkpoint.com>
To: John Levine <johnl@taugh.com>
Subject: Re: travel guide for the next IETF...
Thread-Topic: travel guide for the next IETF...
Thread-Index: AQHN5dfb0936cwl5eUu6Q6LVF7Mv7ZgzPAaAgAZomQCAAAq9AIAABq8AgABbSYCAAAIpgIAAOHiA
Date: Sat, 5 Jan 2013 08:13:52 +0000
Message-ID: <4613980CFC78314ABFD7F85CC30277210EE27F65@IL-EX10.ad.checkpoint.com>
References: <20130105045141.35864.qmail@joyce.lan>
In-Reply-To: <20130105045141.35864.qmail@joyce.lan>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [172.31.20.211]
x-kse-antivirus-interceptor-info: scan successful
x-kse-antivirus-info: Clean
Content-Type: text/plain; charset="us-ascii"
Content-ID: <CBDFBB61FC09D344A27BA9B346DC8AEA@ad.checkpoint.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "<ietf@ietf.org>" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 05 Jan 2013 08:13:58 -0000

On Jan 5, 2013, at 6:51 AM, John Levine <johnl@taugh.com> wrote:

>> So if you don't attend IEEE, quit your whining:  at least you won't have=
=20
>> to eat he same hotel food for 2 weeks in a row...
>=20
> You don't have to eat there.  Check out the reviews of this restaurant
> across the street:
>=20
> https://plus.google.com/118141773512616354020/about

I wonder if you risk a jaywalking ticket for crossing that street without a=
 car.=

From abdussalambaryun@gmail.com  Sat Jan  5 00:22:42 2013
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6475921F866D for <ietf@ietfa.amsl.com>; Sat,  5 Jan 2013 00:22:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 7sd2mu8ZQfYN for <ietf@ietfa.amsl.com>; Sat,  5 Jan 2013 00:22:42 -0800 (PST)
Received: from mail-vc0-f169.google.com (mail-vc0-f169.google.com [209.85.220.169]) by ietfa.amsl.com (Postfix) with ESMTP id D657521F865B for <ietf@ietf.org>; Sat,  5 Jan 2013 00:22:41 -0800 (PST)
Received: by mail-vc0-f169.google.com with SMTP id gb23so17160161vcb.14 for <ietf@ietf.org>; Sat, 05 Jan 2013 00:22:41 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:cc:content-type; bh=4flQGMrkO+G7Es2ScegCf2GCNFjOn0RANiFC4nJHzNU=; b=bneA6Hy+cs4xQ2Uf61ExuHvIbwdLzeBPod7ffu+vFzYD7xklIFafmPVYCxCK9VFaFG 3xHEX7FuZOriM2d9apJdl1XtEG3aTqsO4u1DDGoVaPxO16rh7ZIkQp7vRGGqJO87McdU i9M82gZK8ZLvYJd9Rh7vwoG3Hiup0heiFiLCVtbaWD/czMKBpffWEVGwwFjZSBxDjQ61 ovEex96rdy5PgEBo+hbg9SrARCAcmwXN1qkU1ww/cBP7KfNhMgWAoTLlLhGrPmrTQ9QE SDtlKLYBOLP84pRDuUzf+NDPkxNdRNrkGuIm44H50PXqy/hcO3DaqDF4l/a9UEauz3gr fS1A==
MIME-Version: 1.0
Received: by 10.220.149.69 with SMTP id s5mr78972969vcv.23.1357374161277; Sat, 05 Jan 2013 00:22:41 -0800 (PST)
Received: by 10.220.145.5 with HTTP; Sat, 5 Jan 2013 00:22:41 -0800 (PST)
Date: Sat, 5 Jan 2013 09:22:41 +0100
Message-ID: <CADnDZ8-2ez_Hjb6rUMtJrB2ckfDXk6jek2x5PrXUvLyS5O_QYQ@mail.gmail.com>
Subject: Re: Hello ::Please I need to know LEACH protocol standard???
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: eng.mahmoudemam@yahoo.com
Content-Type: text/plain; charset=ISO-8859-1
Cc: ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 05 Jan 2013 08:22:42 -0000

Hi Mahmoud,

The LEACH is not a protocol worked on so far in IETF, not sure if it
standard yet elsewhere!

AB
-----

Hello everybody,

I am a researcher of Master's degree , working on LEACH routing
protocol for wireless sensor networks and i need to know for which
standard does LEACH , its family ,or even Layer 3 belong to.

Thank you

From ole@cisco.com  Sat Jan  5 00:25:29 2013
Return-Path: <ole@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0EF7E21F8716 for <ietf@ietfa.amsl.com>; Sat,  5 Jan 2013 00:25:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.599
X-Spam-Level: 
X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
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 kSYXaR3Ejimv for <ietf@ietfa.amsl.com>; Sat,  5 Jan 2013 00:25:28 -0800 (PST)
Received: from mtv-iport-4.cisco.com (mtv-iport-4.cisco.com [173.36.130.15]) by ietfa.amsl.com (Postfix) with ESMTP id 68BC521F8671 for <ietf@ietf.org>; Sat,  5 Jan 2013 00:25:28 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=271; q=dns/txt; s=iport; t=1357374328; x=1358583928; h=date:from:reply-to:to:cc:subject:in-reply-to:message-id: references:mime-version; bh=43cm23sEpxecJVy/FOMVWdOfprq4MGR7tcofQEpqDRg=; b=KZMhZQmocD6U8y7YK1+TOJyYJcCOuuu2RhTcXKQZ9Wnt/PWaVmzh3ijN uS9cqwau0CTFIfRZhRbrC0fViLPaTXnVBH97MxP5Jr8JPzogldCztl/qN KkrVuHrUsXRnHxWzbTjzUKIoZPRFW9Q+dPndQ/R3UKLhJkgE0xZOWr7Zs g=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AnkFAMvi51CrRDoG/2dsb2JhbABFhXK3ZBZzgh4BAQEDATo/EAsOOFcGiCQFDbQiBIx3hB4DiGGTFYpegxU
X-IronPort-AV: E=Sophos;i="4.84,415,1355097600"; d="scan'208";a="67955769"
Received: from mtv-core-1.cisco.com ([171.68.58.6]) by mtv-iport-4.cisco.com with ESMTP; 05 Jan 2013 08:25:28 +0000
Received: from [10.27.1.132] (sjc-ole-8913.cisco.com [10.27.1.132]) by mtv-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id r058PRED014590 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 5 Jan 2013 08:25:27 GMT
Date: Sat, 5 Jan 2013 00:25:19 -0800 (PST)
From: Ole Jacobsen <ole@cisco.com>
To: Yoav Nir <ynir@checkpoint.com>
Subject: Re: travel guide for the next IETF...
In-Reply-To: <4613980CFC78314ABFD7F85CC30277210EE27F65@IL-EX10.ad.checkpoint.com>
Message-ID: <alpine.OSX.2.01.1301050024000.94166@173-11-110-132-sfba.hfc.comcastbusiness.net>
References: <20130105045141.35864.qmail@joyce.lan> <4613980CFC78314ABFD7F85CC30277210EE27F65@IL-EX10.ad.checkpoint.com>
User-Agent: Alpine 2.01 (OSX 1266 2009-07-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Cc: John Levine <johnl@taugh.com>, "<ietf@ietf.org>" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: Ole Jacobsen <ole@cisco.com>
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 05 Jan 2013 08:25:29 -0000

On Sat, 5 Jan 2013, Yoav Nir wrote:

> 
> I wonder if you risk a jaywalking ticket for crossing that street without a car.

You did read the reviews, right? Sounds like you would risk more than 
a ticket...

https://plus.google.com/118141773512616354020/about

From abdussalambaryun@gmail.com  Sat Jan  5 00:31:09 2013
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F3CC221F8756 for <ietf@ietfa.amsl.com>; Sat,  5 Jan 2013 00:31:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 YUMWcYZdTReE for <ietf@ietfa.amsl.com>; Sat,  5 Jan 2013 00:31:08 -0800 (PST)
Received: from mail-vb0-f50.google.com (mail-vb0-f50.google.com [209.85.212.50]) by ietfa.amsl.com (Postfix) with ESMTP id D4DE321F8753 for <ietf@ietf.org>; Sat,  5 Jan 2013 00:31:07 -0800 (PST)
Received: by mail-vb0-f50.google.com with SMTP id ft2so5627259vbb.37 for <ietf@ietf.org>; Sat, 05 Jan 2013 00:31:07 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=iObeZlukI313WXZWgxBnlC52i0Pk5Bd7LqA1pdaY7GA=; b=mD6hUI/DNXnvi+tPp2B9y/2DshDiNm+DBjiI9wjZYS2PlQf4Ou1NarVoNAB7E+6OA3 naV0VppzRxP8xaKMCV+1USTO/88wsLuWY/7LdIdUdnrKfsBaQCGGxFjoaz9qEfbkLgEn vBaIeqpfZbWO+pUBVrTW9T7UGgRSgZKcBmidI9RTgWqrV6HbGjp2cSTfD7HGRFgERKNG o8bDAKL+zpPGUSrRDSn/elGh0jJkJn6TY3R4ITXP+px+jmPKtjqDpWRMOnjGnpAQ972G d+/5CwssYaAhEzqnX7fsmuazYt8EpEuAHiT4wkbths2kn+rc41mPjHTs2GkrNrqAxS9E JXSQ==
MIME-Version: 1.0
Received: by 10.58.143.12 with SMTP id sa12mr81240761veb.43.1357374667203; Sat, 05 Jan 2013 00:31:07 -0800 (PST)
Received: by 10.220.145.5 with HTTP; Sat, 5 Jan 2013 00:31:07 -0800 (PST)
In-Reply-To: <CADnDZ8-yCxUbrD9oFyQKkJuTgDZbamnV8K4GU+sAN5SekpyHAA@mail.gmail.com>
References: <CADnDZ8-yCxUbrD9oFyQKkJuTgDZbamnV8K4GU+sAN5SekpyHAA@mail.gmail.com>
Date: Sat, 5 Jan 2013 09:31:07 +0100
Message-ID: <CADnDZ8_a8cRSKrHzE4fZSrMNO6pGLa9vCcHzKUmHsVtCWRCf6g@mail.gmail.com>
Subject: Re: Making RFC2119 key language easier to Protocol Readers
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: hsantos@isdg.net
Content-Type: text/plain; charset=ISO-8859-1
Cc: ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 05 Jan 2013 08:31:09 -0000

Hi Hector,

I like your method, which beleive is the reason why the RFC2119 is
great help for implementors. As I mentioned before if the protocol
specification is long and complicated no doubt its language may make
it more difficult to readers or writters. Therefore, it will be nice
if the IETF surveys this matter as you and Scott suggested.

Thanking you
Abdussalam Baryun

+++++++++++++++++++++++++++
Date: Fri, 04 Jan 2013 22:24:50 -0500
From: Hector Santos <hsantos at isdg.net>
To: Scott Brim <swb at internet2.edu>
Sub:Re: I'm struggling with 2219 language again

We have implemented numerous protocols since the 80s. I have a
specific method of approaching a new protocol implementation which
allows for fastest implementation, testing proof of concept and above
all minimum cost. Why bother with the costly complexities of
implementing SHOULDs and MAYs, if the minimum is not something you
want in the end anyway?

A good data point is that for IP/Legal reasons, we do not use other
people's code if we can help it and in the early days, open source was
not as wide spread or even acceptable at the corporate level. In other
words, it was all done in-house, purchased or nothing. I also believe
using other people's code has a high cost as well since you don't have
an in-house expert understanding the inner workings of the externally
developed software.
o Step 1 for Protocol Implementation:


Look for all the MUST protocol features. This includes the explicit
ones and watchful of semantics where its obviously required or things
will break, perhaps it fell thru the crack.

An important consideration for a MUST is that operators are not given
the opportunity to disable these protocol required features. So from a
coding standpoint, this is one area you don't have to worry about
designing configuration tools, the UI, nor including operation
guidelines and documentation for these inherent protocol required
features.

This is the minimum coding framework to allow for all inteop testing
with other software and systems.

The better RFC spec is the one that has documented a checklist, a
minimum requirement summary table, etc. Good example is RFC 1113 for
the various internet hosting protocols. I considered RFC 1123 the
"bible!"

Technical writing tip: Please stay away from verbosity especially of
subjective concepts and please stop writing as if everyone is stupid.
    I always viewed the IETF RFC format as a blend of two steps
    of the SE process - functional and technical specifications.
    Functional specs tell us what we want and technical specs
    tell us how we do it.  So unless a specific functional requirements
    RFC was written, maybe some verbosity is needed but it should
    be minimized.


Generally, depending on the protocol, we can release code just on
using MUST requirements - the bottom line framework for client/server
communications. Only when this is completely successfully, can your
implementation consider moving on at extending the protocol
implementation with additional SHOULD, MAY features and its optional
complexities.
o Step 2


Look for the SHOULDs. This is the candies of the protocol. If the
SHOULD is really simple to implement, it can be lumped in with step 1.

I know many believe a SHOULD are really a MUST as an alternative
method perhaps - different version of MUST to be done nonetheless.

However, I believe these folks play down an important consideration
for implementing SHOULD based protocol features:
   Developers need to offer these as options to deployment operators.


In other words, if the operator can not turn it off then a SHOULD was
incorrectly used for a MUST which is required with no operator option
to disable.
o Step 3


Look for the MAYs. Very similar to SHOULD, a good way to consider a
SHOULD is as a default enabled (ON out of the box) option and a MAY as
a default disabled (OFF out of the box) option.
Summary:

  MUST   - required, no operator option to disabled. Of course,
           its possible to have a hidden, undocumented switch
           for questionable stuff.

  SHOULD - good idea, recommended. if implemented, enabled it
           out of the box.

  MAY    - similar to SHOULD, does not have to be enabled out
           of box.


In both cases for SHOULD and MAY, the operator can turn these protocol
features off/on. For a MUST, the operator can not turn the MUST
feature. These SHOULD/MAY features are documented for operators and
support.

One last thing, I believe in a concept I call CoComp - Cooperative
Competition, where all competitive implementators, including the
protocol technology leader all share a common framework for a minimum
protocol generic to all parties and the internet community. It is
least required to solve the problem or provide a communication avenue.
All else, the SHOULDs, the MAYs, is added value for competing
implementators. It generally is what differentiate the various
implementators software.

I personally believe it is doable to write a new RFC that describe a
guideline for protocol development that will minimize conflicts at
many levels. Of course, a major part of that is good technical writing
skills in principle and the ability to extract and describe what the
protocol framework is, which brings it all back to the original issue
using the proper communications verbiage to describe a protocol.
--
HLS

From abdussalambaryun@gmail.com  Sat Jan  5 00:36:57 2013
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0693821F8464 for <ietf@ietfa.amsl.com>; Sat,  5 Jan 2013 00:36:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 Ln2qZMM+9q3u for <ietf@ietfa.amsl.com>; Sat,  5 Jan 2013 00:36:56 -0800 (PST)
Received: from mail-vb0-f51.google.com (mail-vb0-f51.google.com [209.85.212.51]) by ietfa.amsl.com (Postfix) with ESMTP id E794421F8450 for <ietf@ietf.org>; Sat,  5 Jan 2013 00:36:55 -0800 (PST)
Received: by mail-vb0-f51.google.com with SMTP id fq11so17523083vbb.10 for <ietf@ietf.org>; Sat, 05 Jan 2013 00:36:55 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=WWFKDeMO1i34H4dv24WmXy8kKOTbC4hUfEiIiHdkITY=; b=V0sLh1xu2b8pmi/2Rl47caSWZ0nMJ4/I/ja2DRDsoOxmbey916rrBw0gNfYBWvLyba XGq5LjPAOkBnljVsbOR/pCo5ZWhm1kMOrC1L46lVJBvB+96KRhHRFwqSb4yl/DQYuquC UV+Jzn44Ue7Aapvh4UfzAtEUYY6E9v9zot/XJZMefXGAH58SNYuBrd/tOHfO/1KoZNPD YQMN2ERLOOgyTNlXiIpu8BnPOvH4HJ9Iem1WCesS3b/p7j2oQTPoex4q3j7QLOiG/w0n Rpbg9n+vHgGHAwG6ogczIE1SwYd7R22F8NZdyy0F8Yq9z8R7uqNHyPkuN0etLg9aa+KT IJCA==
MIME-Version: 1.0
Received: by 10.52.70.46 with SMTP id j14mr67766923vdu.99.1357375015406; Sat, 05 Jan 2013 00:36:55 -0800 (PST)
Received: by 10.220.145.5 with HTTP; Sat, 5 Jan 2013 00:36:55 -0800 (PST)
In-Reply-To: <CADnDZ8_a8cRSKrHzE4fZSrMNO6pGLa9vCcHzKUmHsVtCWRCf6g@mail.gmail.com>
References: <CADnDZ8-yCxUbrD9oFyQKkJuTgDZbamnV8K4GU+sAN5SekpyHAA@mail.gmail.com> <CADnDZ8_a8cRSKrHzE4fZSrMNO6pGLa9vCcHzKUmHsVtCWRCf6g@mail.gmail.com>
Date: Sat, 5 Jan 2013 09:36:55 +0100
Message-ID: <CADnDZ8_p-Ako98uwnQvq_hm4OOBXS1hSMFxkZvaPXgfXirFOdg@mail.gmail.com>
Subject: Re: Making RFC2119 key language easier to Protocol Readers
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: narten@us.ibm.com
Content-Type: text/plain; charset=ISO-8859-1
Cc: ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 05 Jan 2013 08:36:57 -0000

>IMO, too many specs seriously overuse/misuse 2119 language, to the
detriment of readability, common sense, and reserving the terms to
bring attention to those cases where it really is important to
highlight an important point that may not be obvious to a casual
reader/implementor.

also to highlight an important point that may not be obvious to
imlementors which are non-English speakers/writers.

AB

From swmike@swm.pp.se  Sat Jan  5 00:39:21 2013
Return-Path: <swmike@swm.pp.se>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 460CD21F8788 for <ietf@ietfa.amsl.com>; Sat,  5 Jan 2013 00:39:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 tjpbXvf6drVe for <ietf@ietfa.amsl.com>; Sat,  5 Jan 2013 00:39:20 -0800 (PST)
Received: from uplift.swm.pp.se (ipv6.swm.pp.se [IPv6:2a00:801::f]) by ietfa.amsl.com (Postfix) with ESMTP id 7C15A21F8780 for <ietf@ietf.org>; Sat,  5 Jan 2013 00:39:20 -0800 (PST)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id 789149C; Sat,  5 Jan 2013 09:39:18 +0100 (CET)
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id 726BE9A for <ietf@ietf.org>; Sat,  5 Jan 2013 09:39:18 +0100 (CET)
Date: Sat, 5 Jan 2013 09:39:18 +0100 (CET)
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: ietf <ietf@ietf.org>
Subject: Re: Making RFC2119 key language easier to Protocol Readers
In-Reply-To: <CADnDZ8_a8cRSKrHzE4fZSrMNO6pGLa9vCcHzKUmHsVtCWRCf6g@mail.gmail.com>
Message-ID: <alpine.DEB.2.00.1301050936060.26235@uplift.swm.pp.se>
References: <CADnDZ8-yCxUbrD9oFyQKkJuTgDZbamnV8K4GU+sAN5SekpyHAA@mail.gmail.com> <CADnDZ8_a8cRSKrHzE4fZSrMNO6pGLa9vCcHzKUmHsVtCWRCf6g@mail.gmail.com>
User-Agent: Alpine 2.00 (DEB 1167 2008-08-23)
Organization: People's Front Against WWW
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 05 Jan 2013 08:39:21 -0000

As an operator, I purchase equipment and need to write RFQs. I would like 
to able to ask more than "does the product implement RFC <whatever>", I 
want to also ask "Please document all instances where you did not follow 
all MUST and SHOULD, and why".

Otherwise I think there needs to be better definition of what it means to 
"implement" or "support" an RFC when it comes to completness and what this 
means as per following SHOULD and MAY.

-- 
Mikael Abrahamsson    email: swmike@swm.pp.se

From swmike@swm.pp.se  Sat Jan  5 00:43:32 2013
Return-Path: <swmike@swm.pp.se>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D634121F8788 for <ietf@ietfa.amsl.com>; Sat,  5 Jan 2013 00:43:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 N2YhodQ6ng8D for <ietf@ietfa.amsl.com>; Sat,  5 Jan 2013 00:43:32 -0800 (PST)
Received: from uplift.swm.pp.se (ipv6.swm.pp.se [IPv6:2a00:801::f]) by ietfa.amsl.com (Postfix) with ESMTP id 5099521F8780 for <ietf@ietf.org>; Sat,  5 Jan 2013 00:43:32 -0800 (PST)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id 885D29C; Sat,  5 Jan 2013 09:43:31 +0100 (CET)
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id 842F89A for <ietf@ietf.org>; Sat,  5 Jan 2013 09:43:31 +0100 (CET)
Date: Sat, 5 Jan 2013 09:43:31 +0100 (CET)
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: ietf <ietf@ietf.org>
Subject: Re: Making RFC2119 key language easier to Protocol Readers
In-Reply-To: <alpine.DEB.2.00.1301050936060.26235@uplift.swm.pp.se>
Message-ID: <alpine.DEB.2.00.1301050942480.26235@uplift.swm.pp.se>
References: <CADnDZ8-yCxUbrD9oFyQKkJuTgDZbamnV8K4GU+sAN5SekpyHAA@mail.gmail.com> <CADnDZ8_a8cRSKrHzE4fZSrMNO6pGLa9vCcHzKUmHsVtCWRCf6g@mail.gmail.com> <alpine.DEB.2.00.1301050936060.26235@uplift.swm.pp.se>
User-Agent: Alpine 2.00 (DEB 1167 2008-08-23)
Organization: People's Front Against WWW
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 05 Jan 2013 08:43:32 -0000

On Sat, 5 Jan 2013, Mikael Abrahamsson wrote:

> Otherwise I think there needs to be better definition of what it means 
> to "implement" or "support" an RFC when it comes to completness and what 
> this means as per following SHOULD and MAY.

Also what it means following things in it that is not RFC2119 language.

-- 
Mikael Abrahamsson    email: swmike@swm.pp.se

From abdussalambaryun@gmail.com  Sat Jan  5 00:54:47 2013
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2775F21F87D1 for <ietf@ietfa.amsl.com>; Sat,  5 Jan 2013 00:54:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 sbygNchFuJ9l for <ietf@ietfa.amsl.com>; Sat,  5 Jan 2013 00:54:46 -0800 (PST)
Received: from mail-vb0-f44.google.com (mail-vb0-f44.google.com [209.85.212.44]) by ietfa.amsl.com (Postfix) with ESMTP id 8F91121F87CD for <ietf@ietf.org>; Sat,  5 Jan 2013 00:54:46 -0800 (PST)
Received: by mail-vb0-f44.google.com with SMTP id fc26so17267409vbb.17 for <ietf@ietf.org>; Sat, 05 Jan 2013 00:54:45 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=7zJcTCWuGMIkLR3VtgIjpp2duxclgF3NVcsYDCe9zSI=; b=YGejuWaYt6QKcQtZLIBztK+a4OiQH5ni50cab7sOm6ycCslbxMtZspKIz6oZJ2U1GL zK7eqPaLj4f+Uh5Nkrhmc+Oe5hDIUu1PWXhc3XcdkAOJB5IG61CYOi19uz3SVKr+pPnp Nz3pRotlR28bvbAq+yrrb9DehowRiMbABfYIddu5lsyzsVCGHoyF8ZQ2A7hV4feNSyvZ Ux6Rr/szcgr6awaT3bP6dUfR7qMg7pNWiHHZqmuoFstx04Tw3TAmvYAEWbDFX4GG9BS/ W6bjvxiV8M0ke/WEklgmKo5UWgsENNWb4i3//TOJBXBM6RmM6QbC7HzoIPDeRur1Qhbg 6bGg==
MIME-Version: 1.0
Received: by 10.52.175.106 with SMTP id bz10mr67822460vdc.125.1357376085772; Sat, 05 Jan 2013 00:54:45 -0800 (PST)
Received: by 10.220.145.5 with HTTP; Sat, 5 Jan 2013 00:54:45 -0800 (PST)
In-Reply-To: <CADnDZ8-yCxUbrD9oFyQKkJuTgDZbamnV8K4GU+sAN5SekpyHAA@mail.gmail.com>
References: <CADnDZ8-yCxUbrD9oFyQKkJuTgDZbamnV8K4GU+sAN5SekpyHAA@mail.gmail.com>
Date: Sat, 5 Jan 2013 09:54:45 +0100
Message-ID: <CADnDZ8_jW_rCgYuLZ79h+aMfkiA5kN7QdTiHdGkavz-O55vyMQ@mail.gmail.com>
Subject: Re: Making RFC2119 key language easier to Protocol Readers
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: ned+ietf@mauve.mrochek.com
Content-Type: text/plain; charset=ISO-8859-1
Cc: narten@us.ibm.com, ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 05 Jan 2013 08:54:47 -0000

(was Re: I'm struggling with 2219 language again)

>> Where you want to use MUST is where an implementation might be tempted
>> to take a short cut -- to the detriment of the Internet -- but could
>> do so without actually breaking interoperability. A good example is
>> with retransmissions and exponential backoff. You can implement those
>> incorrectly (or not at all), and still get "interoperability". I.e.,
>> two machines can talk to each other. Maybe you don't get "good"
>> intereoperability and maybe not great performance under some
>> conditions, but you can still build an interoperabile implementation.

>> IMO, too many specs seriously overuse/misuse 2119 language, to the
>> detriment of readability, common sense, and reserving the terms to
>> bring attention to those cases where it really is important to
>> highlight an important point that may not be obvious to a casual
>> reader/implementor.

>Sadly true.

We can fix that, by discussing it further, or as Scott mentioned the survey [*]

>> two machines can talk to each other. Maybe you don't get "good"
>> intereoperability and maybe not great performance under some
>> conditions, but you can still build an interoperabile implementation.

As machines reads and writes may depend on conditions, I don't think
it is true that you can still interoperabile implementation by
ignoring using/documenting requirement keys language (i.e. all common
keys of all languages).

AB

From abdussalambaryun@gmail.com  Sat Jan  5 01:00:22 2013
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D547321F8673 for <ietf@ietfa.amsl.com>; Sat,  5 Jan 2013 01:00:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 gX-jzM1mPkKT for <ietf@ietfa.amsl.com>; Sat,  5 Jan 2013 01:00:22 -0800 (PST)
Received: from mail-vb0-f41.google.com (mail-vb0-f41.google.com [209.85.212.41]) by ietfa.amsl.com (Postfix) with ESMTP id 4866821F866D for <ietf@ietf.org>; Sat,  5 Jan 2013 01:00:22 -0800 (PST)
Received: by mail-vb0-f41.google.com with SMTP id l22so17111663vbn.14 for <ietf@ietf.org>; Sat, 05 Jan 2013 01:00:21 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=FcqdOIL4YZphJAN2Zbn3BA6XFg2KQeIxnQzyep9Wg/o=; b=vl9V23b08c3QniMYD/6PDB/mjhcevM4knVkvQsrJgGQuIAcUZsgotj0qXbSd9p5TwF lSy/6k4fja9YQeZD7zKdjvXwL5vfLqyoFO0SmwoEdk6OsbEMjvAItvFl2g6fjaC3zimt fMuVs/cB+j8WuhXYyjswNPBbeO9RzOKSHUkW5ZugNz+oKKoIWKMk5qY0V8hG4tqZwkXd hUTiR9J3Kv63c6h12zk9OYK4thOHDdBoPB7m4nqeNI6qdTUiEMJtFttv/HXiyLgP4L+1 c+6ULeJUVgzyJyZBsMSrT5nawgYao5NH9uQdwibP7OkNDP5VWr3zZAHyHAltgstMl9pu fINg==
MIME-Version: 1.0
Received: by 10.52.21.179 with SMTP id w19mr69192343vde.55.1357376421631; Sat, 05 Jan 2013 01:00:21 -0800 (PST)
Received: by 10.220.145.5 with HTTP; Sat, 5 Jan 2013 01:00:21 -0800 (PST)
In-Reply-To: <CADnDZ8_jW_rCgYuLZ79h+aMfkiA5kN7QdTiHdGkavz-O55vyMQ@mail.gmail.com>
References: <CADnDZ8-yCxUbrD9oFyQKkJuTgDZbamnV8K4GU+sAN5SekpyHAA@mail.gmail.com> <CADnDZ8_jW_rCgYuLZ79h+aMfkiA5kN7QdTiHdGkavz-O55vyMQ@mail.gmail.com>
Date: Sat, 5 Jan 2013 10:00:21 +0100
Message-ID: <CADnDZ8_k9XKQd6zNyoQWLRX0uFrb0Kb1nDw468drOBur877rAw@mail.gmail.com>
Subject: Re: Making RFC2119 key language easier to Protocol Readers
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: ietf <ietf@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 05 Jan 2013 09:00:22 -0000

We can fix that, by discussing it further, or as Scott mentioned make
a survey within IETF [*]

[*] http://www.ietf.org/mail-archive/web/ietf/current/msg76582.html

AB

On 1/5/13, Abdussalam Baryun <abdussalambaryun@gmail.com> wrote:
> (was Re: I'm struggling with 2219 language again)
>
>>> Where you want to use MUST is where an implementation might be tempted
>>> to take a short cut -- to the detriment of the Internet -- but could
>>> do so without actually breaking interoperability. A good example is
>>> with retransmissions and exponential backoff. You can implement those
>>> incorrectly (or not at all), and still get "interoperability". I.e.,
>>> two machines can talk to each other. Maybe you don't get "good"
>>> intereoperability and maybe not great performance under some
>>> conditions, but you can still build an interoperabile implementation.
>
>>> IMO, too many specs seriously overuse/misuse 2119 language, to the
>>> detriment of readability, common sense, and reserving the terms to
>>> bring attention to those cases where it really is important to
>>> highlight an important point that may not be obvious to a casual
>>> reader/implementor.
>
>>Sadly true.
>
> We can fix that, by discussing it further, or as Scott mentioned the survey
> [*]
>
>>> two machines can talk to each other. Maybe you don't get "good"
>>> intereoperability and maybe not great performance under some
>>> conditions, but you can still build an interoperabile implementation.
>
> As machines reads and writes may depend on conditions, I don't think
> it is true that you can still interoperabile implementation by
> ignoring using/documenting requirement keys language (i.e. all common
> keys of all languages).
>
> AB
>

From abdussalambaryun@gmail.com  Sat Jan  5 01:04:38 2013
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 02F5E21F87F5 for <ietf@ietfa.amsl.com>; Sat,  5 Jan 2013 01:04:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 Z-baewDlU3i9 for <ietf@ietfa.amsl.com>; Sat,  5 Jan 2013 01:04:37 -0800 (PST)
Received: from mail-vb0-f49.google.com (mail-vb0-f49.google.com [209.85.212.49]) by ietfa.amsl.com (Postfix) with ESMTP id 29A1721F8673 for <ietf@ietf.org>; Sat,  5 Jan 2013 01:04:37 -0800 (PST)
Received: by mail-vb0-f49.google.com with SMTP id r6so17098569vbi.8 for <ietf@ietf.org>; Sat, 05 Jan 2013 01:04:36 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=5qWSarzdKRHkrDtiFYYaoc84twgdWyBWvGXk37BJCcc=; b=UvlXjjMFRUtLmFa9Vkk50gaSF2ksicaMiDHtyPY552ozDbE6zmvq8agXv8csKR3C7t hNnczIvrlwFDwvqmGkOwaJ99e/ISRtHLRjgVDlKiSKIl++f+gGpsRLNDDawJPm/Mr4fU G0VbqHKGRJKtOzDrhkS8jeaHkpoieh95H71fH4VeG0TiaWA9iaUK6YyMuIN+eNOzJkrh 3O6y8UNpZoPac+qAHDOD/RvBJ/Q1xOK3zD2CfGBOg6boOi9Vi2IVUQb5dMr9cxLwRE1+ fiugkPm5eWYUTUYBewn+laAq30MbErCFEAKNwdKmc5I/0BbWWsug19PR6Q9vKe/b2BtU 3VlQ==
MIME-Version: 1.0
Received: by 10.220.107.5 with SMTP id z5mr79052677vco.22.1357376676661; Sat, 05 Jan 2013 01:04:36 -0800 (PST)
Received: by 10.220.145.5 with HTTP; Sat, 5 Jan 2013 01:04:36 -0800 (PST)
In-Reply-To: <CADnDZ8-yCxUbrD9oFyQKkJuTgDZbamnV8K4GU+sAN5SekpyHAA@mail.gmail.com>
References: <CADnDZ8-yCxUbrD9oFyQKkJuTgDZbamnV8K4GU+sAN5SekpyHAA@mail.gmail.com>
Date: Sat, 5 Jan 2013 10:04:36 +0100
Message-ID: <CADnDZ88XgyNXiu1fdK3WB7jrZTmfuvAc5U1XyAxjprZf6=7P4Q@mail.gmail.com>
Subject: Re: Making RFC2119 key language easier to Protocol Readers
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: swmike@swm.pp.se
Content-Type: text/plain; charset=ISO-8859-1
Cc: ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 05 Jan 2013 09:04:38 -0000

I totally agree with you,

AB

+++
As an operator, I purchase equipment and need to write RFQs. I would
like to able to ask more than "does the product implement RFC
<whatever>", I want to also ask "Please document all instances where
you did not follow all MUST and SHOULD, and why".

Otherwise I think there needs to be better definition of what it means
to "implement" or "support" an RFC when it comes to completness and
what this means as per following SHOULD and MAY.
--
Mikael Abrahamsson    email: swmike at swm.pp.se

From abdussalambaryun@gmail.com  Sat Jan  5 01:08:33 2013
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E808A21F863F for <ietf@ietfa.amsl.com>; Sat,  5 Jan 2013 01:08:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 0pJTw3kao3xd for <ietf@ietfa.amsl.com>; Sat,  5 Jan 2013 01:08:33 -0800 (PST)
Received: from mail-vb0-f52.google.com (mail-vb0-f52.google.com [209.85.212.52]) by ietfa.amsl.com (Postfix) with ESMTP id 3239721F8588 for <ietf@ietf.org>; Sat,  5 Jan 2013 01:08:33 -0800 (PST)
Received: by mail-vb0-f52.google.com with SMTP id ez10so17111363vbb.39 for <ietf@ietf.org>; Sat, 05 Jan 2013 01:08:32 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=GpfWqwfijJrkBgW/f1lymN1Fq1aGwjKFPZOMmOSgKWk=; b=YxxnPnVf1koZnHs5tIAlOjMr/3GRbS2T0w/BdFuoEBHYquEQCWR1mdptb28eGVPJva sZtu0c2PLS9FDtyB8TfvcU908QxXFRINKZcLyRMzrwrwjDoojeW12L8XBPv0qRZhZAVU sdFQPjWJXBt71SBD/yKR7Qx4o+8pQIIdfGfPjcY338qH/SInfSkecxn4KcpE4nWSXg7C D4z88HQvSbhOTADUYrjQyVnOSZ0vFuEIEqUPFaL21bSUsusisSNDqFFjCg4oZleWKmEo L+TJrjoRQYYA8NKKFGUPpKcjZPmXcWqJpePU4BgdJnbWs2HAmfGPIA5PDZfk3yHpoM9M KN6g==
MIME-Version: 1.0
Received: by 10.52.21.179 with SMTP id w19mr69198079vde.55.1357376912674; Sat, 05 Jan 2013 01:08:32 -0800 (PST)
Received: by 10.220.145.5 with HTTP; Sat, 5 Jan 2013 01:08:32 -0800 (PST)
In-Reply-To: <CADnDZ88XgyNXiu1fdK3WB7jrZTmfuvAc5U1XyAxjprZf6=7P4Q@mail.gmail.com>
References: <CADnDZ8-yCxUbrD9oFyQKkJuTgDZbamnV8K4GU+sAN5SekpyHAA@mail.gmail.com> <CADnDZ88XgyNXiu1fdK3WB7jrZTmfuvAc5U1XyAxjprZf6=7P4Q@mail.gmail.com>
Date: Sat, 5 Jan 2013 10:08:32 +0100
Message-ID: <CADnDZ8_pd5ZrnucZAoK5WDXUgK9gQhHm+GJe7PihDQzx1uUsaw@mail.gmail.com>
Subject: Re: Making RFC2119 key language easier to Protocol Readers
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: swmike@swm.pp.se
Content-Type: text/plain; charset=ISO-8859-1
Cc: ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 05 Jan 2013 09:08:34 -0000

Hi Mikael

>Also what it means following things in it that is not RFC2119 language.

It will mean, you should understand me/english/ietf/procedure even if
I don't have to explain, and you need to understand English well even
if you are a great implementor or great programming language speaker.

AB
===

On 1/5/13, Abdussalam Baryun <abdussalambaryun@gmail.com> wrote:
> I totally agree with you,
>
> AB
>
> +++
> As an operator, I purchase equipment and need to write RFQs. I would
> like to able to ask more than "does the product implement RFC
> <whatever>", I want to also ask "Please document all instances where
> you did not follow all MUST and SHOULD, and why".
>
> Otherwise I think there needs to be better definition of what it means
> to "implement" or "support" an RFC when it comes to completness and
> what this means as per following SHOULD and MAY.
> --
> Mikael Abrahamsson    email: swmike at swm.pp.se
>

From swmike@swm.pp.se  Sat Jan  5 01:13:11 2013
Return-Path: <swmike@swm.pp.se>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D541A21F8756 for <ietf@ietfa.amsl.com>; Sat,  5 Jan 2013 01:13:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599]
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 sN7VKNTdJYAJ for <ietf@ietfa.amsl.com>; Sat,  5 Jan 2013 01:13:11 -0800 (PST)
Received: from uplift.swm.pp.se (ipv6.swm.pp.se [IPv6:2a00:801::f]) by ietfa.amsl.com (Postfix) with ESMTP id F00E821F8433 for <ietf@ietf.org>; Sat,  5 Jan 2013 01:13:04 -0800 (PST)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id 08F1D9C; Sat,  5 Jan 2013 10:13:04 +0100 (CET)
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id 024F89A for <ietf@ietf.org>; Sat,  5 Jan 2013 10:13:04 +0100 (CET)
Date: Sat, 5 Jan 2013 10:13:03 +0100 (CET)
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: ietf <ietf@ietf.org>
Subject: Re: Making RFC2119 key language easier to Protocol Readers
In-Reply-To: <CADnDZ8_pd5ZrnucZAoK5WDXUgK9gQhHm+GJe7PihDQzx1uUsaw@mail.gmail.com>
Message-ID: <alpine.DEB.2.00.1301051010080.26235@uplift.swm.pp.se>
References: <CADnDZ8-yCxUbrD9oFyQKkJuTgDZbamnV8K4GU+sAN5SekpyHAA@mail.gmail.com> <CADnDZ88XgyNXiu1fdK3WB7jrZTmfuvAc5U1XyAxjprZf6=7P4Q@mail.gmail.com> <CADnDZ8_pd5ZrnucZAoK5WDXUgK9gQhHm+GJe7PihDQzx1uUsaw@mail.gmail.com>
User-Agent: Alpine 2.00 (DEB 1167 2008-08-23)
Organization: People's Front Against WWW
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 05 Jan 2013 09:13:12 -0000

On Sat, 5 Jan 2013, Abdussalam Baryun wrote:

> Hi Mikael
>
>> Also what it means following things in it that is not RFC2119 language.
>
> It will mean, you should understand me/english/ietf/procedure even if
> I don't have to explain, and you need to understand English well even
> if you are a great implementor or great programming language speaker.

The problem here is that I want them to pay back some of the money (or 
take back the equipment totally and give back all money) for breach of 
contract, when I discover that they haven't correctly (as in intention and 
interop) implemented the RFC they said they said they were compliant in 
supporting.

Ianal, but it feels that it should easier to do this if there are MUST and 
SHOULD in there and I asked them to document all deviations from these.

-- 
Mikael Abrahamsson    email: swmike@swm.pp.se

From lear@cisco.com  Sat Jan  5 06:31:56 2013
Return-Path: <lear@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 95DFF21F8444 for <ietf@ietfa.amsl.com>; Sat,  5 Jan 2013 06:31:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.599
X-Spam-Level: 
X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
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 1cPBTski2YbY for <ietf@ietfa.amsl.com>; Sat,  5 Jan 2013 06:31:55 -0800 (PST)
Received: from ams-iport-3.cisco.com (ams-iport-3.cisco.com [144.254.224.146]) by ietfa.amsl.com (Postfix) with ESMTP id 53CFA21F843D for <ietf@ietf.org>; Sat,  5 Jan 2013 06:31:55 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=5737; q=dns/txt; s=iport; t=1357396315; x=1358605915; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to; bh=Bb44ciSf/hmOUfcaSKCYsQHVcYUSr1yB6zgkJ3Y1cP0=; b=WxkS1I86E1jWH+ZfNUONxfKyuyNfbybAM6/LJiVri/ur69otJT4ZN4L5 LW9m9T0OSFzOOX4pASGgRCH9UoCHRg5fFtVMsrMYfluUzixlnpanrqjyU zbrCCmeUugE8crekz7xttYAJAlXlbhlV5DWj5jZT0iUux2B5mPVVMgdK7 Y=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AlcHAP036FCQ/khL/2dsb2JhbABFg0eCcoVesUAWc4IfAQEEI0gNARALBB0WCwICCQMCAQIBRQYNAQcBAYgTpSSCA403kAKBEwOWC5BJgnU
X-IronPort-AV: E=Sophos;i="4.84,415,1355097600"; d="scan'208,217";a="10881019"
Received: from ams-core-2.cisco.com ([144.254.72.75]) by ams-iport-3.cisco.com with ESMTP; 05 Jan 2013 14:31:54 +0000
Received: from ams3-vpn-dhcp6552.cisco.com (ams3-vpn-dhcp6552.cisco.com [10.61.89.151]) by ams-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id r05EVrO9011422 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 5 Jan 2013 14:31:53 GMT
Message-ID: <50E83959.3090100@cisco.com>
Date: Sat, 05 Jan 2013 15:31:53 +0100
From: Eliot Lear <lear@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: Ted Hardie <ted.ietf@gmail.com>
Subject: Re: WCIT outcome?
References: <CAMm+Lwh2cHRY+Dk2_SDtZZmUbPcgRpP89u3DHUcniJDrKrX_pw@mail.gmail.com> <CAMzo+1a0-90dnjnvs48a9DcNN9DY_edF5hH0__4XRuCaLHtL6Q@mail.gmail.com> <CAMm+LwjzjLc2-=4EdxwHOi21B3dOBUohYc5hhXZHL_Pk+iBBmQ@mail.gmail.com> <6.2.5.6.2.20121229192941.0aae33e8@resistor.net> <CAMm+LwiC0xtJU4vnGFPvAG4VKZdj7Tf3LfW0+pzwxKWTegRREw@mail.gmail.com> <a06240800cd074efd45b8@10.0.1.3> <CAMm+Lwiq+DCzXw572wKs78DG+XzYsJtwCVSPvNuVHSrT=Cr2nA@mail.gmail.com> <a06240809cd0799fee029@10.0.1.3> <50E29EE0.1080107@gmail.com> <50E32CAA.4040507@tana.it> <8C48B86A895913448548E6D15DA7553B72A8D6@xmb-rcd-x09.cisco.com> <00fd01cdea16$c956c720$5c045560$@tndh.net> <CA+9kkMBAm4S5s+sxXuVfp8vZMgZUvBG3YkOiCtegfpA+095_rA@mail.gmail.com> <015c01cdeac4$be33d550$3a9b7ff0$@tndh.net> <CA+9kkMB9ZdLTAp=XO_KEtgJq6E_=eqCuoooL63ACLiPeLfC=Sg@mail.gmail.com>
In-Reply-To: <CA+9kkMB9ZdLTAp=XO_KEtgJq6E_=eqCuoooL63ACLiPeLfC=Sg@mail.gmail.com>
X-Enigmail-Version: 1.4.6
Content-Type: multipart/alternative; boundary="------------090509090300010504080703"
Cc: ietf@ietf.org, lynn.st.amour@isoc.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 05 Jan 2013 14:31:56 -0000

This is a multi-part message in MIME format.
--------------090509090300010504080703
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

Hi,

At its core, the value of the IETF is technical.  We must always make
the best technical standards we can possibly make, adhering to the
values of rough consensus and running code.  Everything else is
secondary or nobody (government or otherwise) will want to implement
what we develop.  It's easy to lose sight of this in this conversation. 
It's an advantage we have over organizations who vote by country, and we
will always have it so long as such votes are allowed and where the
majority of expertise is found in a minority of countries, or where the
voice of expertise is silenced through "representation".  Because of
this approach, what happened at WCIT and at WTSA is likely to harm
developing countries more than anyone else, and that is truly unfortunate.

And so what do we need to do?

 1. Keep developing the best technical standards we can develop, based
    on rough consensus and running code.
 2. Do not get overly consumed by palace intrigue in other
    organizations.  It detracts from (1) above.
 3. While we cannot control others, we can and should occasionally
    remind them when they're going to do something that when implemented
    as specified would harm those who deploy the technology.
 4. Invite and encourage all to participate in our activities so that
    the best ideas flourish and all ideas are tested.

The other thing we need to understand is that the IETF doesn't live
without friends or in a vacuum.  The RIRs, NOGs, other standards bodies,
and ISOC all are working at many different levels, as are vendors.  If
WCIT shows anything, it is that these organizations are being listened
to, at least by many in the developed world.  Why?  Because over 2.5
billion people are connected, thanks to the collaboration of these and
other organizations.  That's moral authority that should not be
underestimated.  Nor should it be taken for granted.  See (1) above. 
And we also shouldn't try to boil the ocean by ourselves or it will
surely impact (1) above.

Can we do a better job on outreach to governments?  Yes.  I'd even
venture to say that the IETF should be held â€“ from time to time â€“ in a
developing country, so that people can more clearly see who we are and
what we do.  But not too often, lest it interfere with (1) above.  If we
keep building the best stuff, they will continue to come, even if there
are bumps along the road.

Eliot


--------------090509090300010504080703
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    Hi,<br>
    <br>
    At its core, the value of the IETF is technical.Â  We must always
    make the best technical standards we can possibly make, adhering to
    the values of rough consensus and running code.Â  Everything else is
    secondary or nobody (government or otherwise) will want to implement
    what we develop.Â  It's easy to lose sight of this in this
    conversation.Â  It's an advantage we have over organizations who vote
    by country, and we will always have it so long as such votes are
    allowed and where the majority of expertise is found in a minority
    of countries, or where the voice of expertise is silenced through
    "representation".Â  Because of this approach, what happened at WCIT
    and at WTSA is likely to harm developing countries more than anyone
    else, and that is truly unfortunate.<br>
    <br>
    And so what do we need to do?<br>
    <ol>
      <li>Keep developing the best technical standards we can develop,
        based on rough consensus and running code.</li>
      <li>Do not get overly consumed by palace intrigue in other
        organizations.Â  It detracts from (1) above.</li>
      <li>While we cannot control others, we can and should occasionally
        remind them when they're going to do something that when
        implemented as specified would harm those who deploy the
        technology. <br>
      </li>
      <li>Invite and encourage all to participate in our activities so
        that the best ideas flourish and all ideas are tested.<br>
      </li>
    </ol>
    <p>The other thing we need to understand is that the IETF doesn't
      live without friends or in a vacuum.Â  The RIRs, NOGs, other
      standards bodies, and ISOC all are working at many different
      levels, as are vendors.Â  If WCIT shows anything, it is that these
      organizations are being listened to, at least by many in the
      developed world.Â  Why?Â  Because over 2.5 billion people are
      connected, thanks to the collaboration of these and other
      organizations.Â  That's moral authority that should not be
      underestimated.Â  Nor should it be taken for granted.Â  See (1)
      above.Â  And we also shouldn't try to boil the ocean by ourselves
      or it will surely impact (1) above.<br>
    </p>
    <p>Can we do a better job on outreach to governments?Â  Yes.Â  I'd
      even venture to say that the IETF should be held â€“ from time to
      time â€“ in a developing country, so that people can more clearly
      see who we are and what we do.Â  But not too often, lest it
      interfere with (1) above.Â  If we keep building the best stuff,
      they will continue to come, even if there are bumps along the
      road.<br>
    </p>
    <p>Eliot<br>
    </p>
  </body>
</html>

--------------090509090300010504080703--

From john-ietf@jck.com  Sat Jan  5 08:03:13 2013
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 17DFC21F85BF for <ietf@ietfa.amsl.com>; Sat,  5 Jan 2013 08:03:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 Y6D2FkK6cFDv for <ietf@ietfa.amsl.com>; Sat,  5 Jan 2013 08:03:12 -0800 (PST)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 35A4421F85B3 for <ietf@ietf.org>; Sat,  5 Jan 2013 08:03:12 -0800 (PST)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1TrWDG-000MIo-Ka; Sat, 05 Jan 2013 11:03:10 -0500
Date: Sat, 05 Jan 2013 11:03:05 -0500
From: John C Klensin <john-ietf@jck.com>
To: Mikael Abrahamsson <swmike@swm.pp.se>, ietf <ietf@ietf.org>
Subject: Re: Making RFC2119 key language easier to Protocol Readers
Message-ID: <1D12E3A12F3C30D3066A13E6@JcK-HP8200.jck.com>
In-Reply-To: <alpine.DEB.2.00.1301051010080.26235@uplift.swm.pp.se>
References: <CADnDZ8-yCxUbrD9oFyQKkJuTgDZbamnV8K4GU+sAN5SekpyHAA@mail.gmail.com> <CADnDZ88XgyNXiu1fdK3WB7jrZTmfuvAc5U1XyAxjprZf6=7P4Q@mail.gmail.com> <CADnDZ8_pd5ZrnucZAoK5WDXUgK9gQhHm+GJe7PihDQzx1uUsaw@mail.gmail.com> <alpine.DEB.2.00.1301051010080.26235@uplift.swm.pp.se>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 05 Jan 2013 16:03:13 -0000

--On Saturday, January 05, 2013 10:13 +0100 Mikael Abrahamsson
<swmike@swm.pp.se> wrote:

> The problem here is that I want them to pay back some of the
> money (or take back the equipment totally and give back all
> money) for breach of contract, when I discover that they
> haven't correctly (as in intention and interop) implemented
> the RFC they said they said they were compliant in supporting.
> 
> Ianal, but it feels that it should easier to do this if there
> are MUST and SHOULD in there and I asked them to document all
> deviations from these.

Folks, there is a long-term tension in almost every standards
body (at least those who notice) between

	-- a specification whose primary purpose is guidance for
	implementers and, in particular, implementers who intend
	to do the best job possible to make things work together.
	
	-- a specification whose primary purpose is to set
	boundaries for what constitutes a conforming
	implementation so that, as Mikael suggests, one can hold
	those whose implementations do not fall within those
	boundaries can be help accountable legally and/or
	financially.

The traditional position of the IETF is not only that the first
is much more important than the second, but that the test of a
successful specification is interoperable implementations.   If
a pair of implementations do not interoperate, our assumption is
that something is broken, be it implementation 1, implementation
2, or the spec.  Indeed, our old "Draft Standard" requirements
took it as at least a default that the problem lay in the spec,
in part because we weren't very worried about bad-faith
implementations.

Similarly, if there are a half-dozen implementations, all of
which are widely deployed and interoperate smoothly but disagree
with the spec, we usually look on the spec with suspicion and
fix it to conform to those implementations.   In an organization
following the second model, the spec is paramount and all six of
those implementations are wrong (and can be held accountable by
third parties for being wrong).

In the IETF, that tension shows up in many ways.  There are not
just arguments about the use of 2119 terms, but statements like
"the audience for IETF Standards and the RFC Series is
implementers".  Those statements are hotly debated because,
among other things, our documents -- like it or not-- are used
in procurements and, if there are problems, in precisely the way
Mikael describes.   Some of them work better in those contexts
than others.

Another tension is that, while "interoperability" is a good
criterion for some specs, it is less so for others.  "If you do
X, things won't interoperate" can be a valid and important
statement, but so can "If you do Y, things may interoperate
perfectly well in the 'they work together' sense, but there will
be one operational mess after another".  A very narrow reading
of 2119 would permit a MUST NOT for the first case, but not even
a SHOULD NOT for the second because the problem has nothing to
do with a narrow reading of "interoperability".  This is the
reason why some of us have never particularly liked the
interoperability-linked language of 2119.  Its intent, I think,
is to shift the concern toward the first model above and away
from the second but the side-effect of the language chosen has
been to create arguments against strong requirements for
operational quality and minimum implementation quality --
requirements that are perfectly consistent with the first model
above (and possibly even helpful for the second).  

It is also why some of us have argued for years that invocation
of 2119 and its definitions should be optional.  But "optional"
has often morphed in practice -- and with IESGs were were, IMO,
more interested in rules and their rigid interpretation than in
sensible and flexible understanding of particular situations and
needs -- into "optional only in theory" or "optional only if one
can prove to the satisfaction of the most rigid AD that it is
absolutely necessary".

And, again, that is further complicated by the observation that
IETF Standards are used for procurement and even for litigation
about product quality.   We either need to accept that fact and,
where necessary, adjust our specification style to match or we
run the risk of bodies springing up who will profile our
Standards, write procurement-quality conformance statements for
their profiles, and become, de facto, the real standards-setter
for the marketplace (and obviously do so without any element of
IETF consensus).  

Aside but really, IMO, at the core of these sorts of
discussions: Telling people what the IETF says they can't do is
pretty useless, at least until we organize the Protocol Police
to enforce our positions and, ideally, the Protocol Army and
Gallows to make the Protocol Police credible.  If people think
they need to do something, they will do it without allowing us
to comment.  And, if they think they need to standardize
whatever they are doing that we've told them they can't, they
will just find another forum.  We then end up complaining about
how all those nasty people are modifying or extending our
standards without our permission and that is another activity
that may be satisfying but is rarely productive.

    best.
     john


From hsantos@isdg.net  Sat Jan  5 08:37:16 2013
Return-Path: <hsantos@isdg.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E05FB21F855A for <ietf@ietfa.amsl.com>; Sat,  5 Jan 2013 08:37:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.138
X-Spam-Level: 
X-Spam-Status: No, score=-102.138 tagged_above=-999 required=5 tests=[AWL=-0.461, BAYES_00=-2.599, HELO_MISMATCH_NET=0.611, HOST_MISMATCH_COM=0.311, USER_IN_WHITELIST=-100]
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 XrOgW7Hofw3r for <ietf@ietfa.amsl.com>; Sat,  5 Jan 2013 08:37:16 -0800 (PST)
Received: from catinthebox.net (listserv.winserver.com [208.247.131.9]) by ietfa.amsl.com (Postfix) with ESMTP id 0532021F8548 for <ietf@ietf.org>; Sat,  5 Jan 2013 08:37:15 -0800 (PST)
DKIM-Signature: v=1; d=isdg.net; s=tms1; a=rsa-sha1; c=simple/relaxed; l=1504; t=1357403830; h=Received:Received: Received:Received:Message-ID:Date:From:Organization:To:Subject: List-ID; bh=4DDJM0rsgGfPpWAzVfAyPC8IeVI=; b=XB4qJMl4RRIB/Yk8rpzR 9Ilfe3JdXrqMNoYEBPI2ONf2IDcpW6wCPquM4pOwC4/PO7e3F/aBoE5oDXz/TOme A9Soy1PAFmiB4MQPYdmUcoR5BfDpOaB+AO3K5IDZHEzzCLYbyHAV5xbEdAcFUXMU xcH62ZC83EUYFKWIUr5nTEk=
Received: by winserver.com (Wildcat! SMTP Router v7.0.454.4) for ietf@ietf.org; Sat, 05 Jan 2013 11:37:10 -0500
Authentication-Results: dkim.winserver.com; dkim=pass header.d=beta.winserver.com header.s=tms1 header.i=beta.winserver.com;  adsp=pass policy=all author.d=isdg.net asl.d=beta.winserver.com;
Received: from opensite.winserver.com ([208.247.131.23]) by winserver.com (Wildcat! SMTP v7.0.454.4) with ESMTP id 540593024.340.3180; Sat, 05 Jan 2013 11:37:10 -0500
DKIM-Signature: v=1; d=beta.winserver.com; s=tms1; a=rsa-sha256; c=simple/relaxed; l=1504; t=1357403780; h=Received:Received: Message-ID:Date:From:Organization:To:Subject:List-ID; bh=9bc/KAQ qeIqoaR4JSL7uNT9Sur1VXyrej+oyd0m34+g=; b=eNeW2Zqwbzp25gFrw9aCr3k UUn7mCJTJSgBtFSdB8x054PYYIqi8Txf8kS1GjvOCEX0Z3rVQo9nFy2EfvjRyjiW eVDhPt4Nz6UvelzviXdhOUpZUUIIf1EARQ1CEMbQTl5IQwWxb/xR/kdxEnOALXc+ OVuKkmYq4UBQegmJ1w98=
Received: by beta.winserver.com (Wildcat! SMTP Router v7.0.454.4) for ietf@ietf.org; Sat, 05 Jan 2013 11:36:20 -0500
Received: from [192.168.1.101] ([99.3.147.93]) by beta.winserver.com (Wildcat! SMTP v7.0.454.4) with ESMTP id 1139296164.10.4692; Sat, 05 Jan 2013 11:36:19 -0500
Message-ID: <50E856DA.6020900@isdg.net>
Date: Sat, 05 Jan 2013 11:37:46 -0500
From: Hector Santos <hsantos@isdg.net>
Organization: Santronics Software, Inc.
User-Agent: Thunderbird 2.0.0.24 (Windows/20100228)
MIME-Version: 1.0
To: Mikael Abrahamsson <swmike@swm.pp.se>
Subject: Re: Making RFC2119 key language easier to Protocol Readers
References: <CADnDZ8-yCxUbrD9oFyQKkJuTgDZbamnV8K4GU+sAN5SekpyHAA@mail.gmail.com>	<CADnDZ88XgyNXiu1fdK3WB7jrZTmfuvAc5U1XyAxjprZf6=7P4Q@mail.gmail.com>	<CADnDZ8_pd5ZrnucZAoK5WDXUgK9gQhHm+GJe7PihDQzx1uUsaw@mail.gmail.com> <alpine.DEB.2.00.1301051010080.26235@uplift.swm.pp.se>
In-Reply-To: <alpine.DEB.2.00.1301051010080.26235@uplift.swm.pp.se>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Cc: ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 05 Jan 2013 16:37:17 -0000

Keep in mind only a STD is a "real" standard. A RFC is still only a 
recommendation,  a guideline.  What makes it a "pseudo-standard" is 
the # of implementations, how wide spread it is and foremost IMO, how 
much embedded it is so that a change has a negative impact.  At that 
point, an RFC not having a STD status probably doesn't matter any more.

At best, you might be able to sue for malpractice (failing to do what 
most experts in field would be doing) in cases where there is provable 
harm caused by the neglect to implement a well known practice. But 
only maybe getting your money back is realistic. :)

ikael Abrahamsson wrote:
> On Sat, 5 Jan 2013, Abdussalam Baryun wrote:
> 
>> Hi Mikael
>>
>>> Also what it means following things in it that is not RFC2119 language.
>>
>> It will mean, you should understand me/english/ietf/procedure even if
>> I don't have to explain, and you need to understand English well even
>> if you are a great implementor or great programming language speaker.
> 
> The problem here is that I want them to pay back some of the money (or 
> take back the equipment totally and give back all money) for breach of 
> contract, when I discover that they haven't correctly (as in intention 
> and interop) implemented the RFC they said they said they were compliant 
> in supporting.
> 
> Ianal, but it feels that it should easier to do this if there are MUST 
> and SHOULD in there and I asked them to document all deviations from these.
> 

-- 
HLS



From petithug@acm.org  Sat Jan  5 11:13:56 2013
Return-Path: <petithug@acm.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 69A2E21F8554 for <ietf@ietfa.amsl.com>; Sat,  5 Jan 2013 11:13:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.308
X-Spam-Level: 
X-Spam-Status: No, score=-101.308 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MISSING_HEADERS=1.292, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
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 BT4TAUW3Cn-l for <ietf@ietfa.amsl.com>; Sat,  5 Jan 2013 11:13:55 -0800 (PST)
Received: from implementers.org (implementers.org [IPv6:2604:3400:dc1:41:216:3eff:fe5b:8240]) by ietfa.amsl.com (Postfix) with ESMTP id 279F221F8546 for <ietf@ietf.org>; Sat,  5 Jan 2013 11:13:55 -0800 (PST)
Received: from [IPv6:2601:9:4b80:32:5de6:df9d:4864:4f45] (unknown [IPv6:2601:9:4b80:32:5de6:df9d:4864:4f45]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (Client CN "Marc Petit-Huguenin", Issuer "implementers.org" (verified OK)) by implementers.org (Postfix) with ESMTPS id 5A0262049D for <ietf@ietf.org>; Sat,  5 Jan 2013 19:13:53 +0000 (UTC)
Message-ID: <50E87B7B.5070605@acm.org>
Date: Sat, 05 Jan 2013 11:14:03 -0800
From: Marc Petit-Huguenin <petithug@acm.org>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.11) Gecko/20121122 Icedove/10.0.11
MIME-Version: 1.0
CC: ietf@ietf.org
Subject: A proposal for a scientific approach to this question [was Re: I'm struggling with 2219 language again]
References: <7ED55FF1-3E1A-4DF7-918E-07790517B848@softarmor.com>
In-Reply-To: <7ED55FF1-3E1A-4DF7-918E-07790517B848@softarmor.com>
X-Enigmail-Version: 1.4.1
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 05 Jan 2013 19:13:56 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

I read the responses so far, and what can be said today is that there is 2
philosophies, with supporters in both camps.  The goal of the IETF is to make
the Internet work better, and I do believe that RFC 2119 is one of the
fundamental tool to reach this goal, but having two ways to use it does not
help this goal.

One way to find out would be to measure which philosophy results in the best
implementations.  Let's say that we can associate with each Standard Track RFC
one of these two philosophy.  If we had statistics on implementations then it
would be a simple matter of counting which one produce the less
interoperability problems, security issues and congestion problems (is there
other criteria?).  But as far as I know, there is no such data available -
maybe we should start collecting these, but that does not help for our current
problem.

Another way to look at it would be to run the following experiment:

1. Someone design a new protocol, something simple but not obvious, and write
in a formal language and keep it secret.

2. The same protocol is rewritten in RFC language but in two different
variants according to the two philosophies.  These also are kept secret.

3. The two variants are distributed randomly to a set of volunteer
implementers, who all implement the spec they received the best they can and
submit the result back, keeping their implementation secret.

4.  A test harness is written from the formal description, and all
implementations are run against each other, collecting stats related to the
criteria listed above (some criterion may be tricky to automatically assess,
we'll see).

5. Results are published, together with the protocol in formal form, the
specs, the results and the recommendation for one or the other philosophy.


That could be an interesting research project, and could even find some
funding from interested parties.


On 01/03/2013 09:15 PM, Dean Willis wrote:
> 
> I've always held to the idea that RFC 2119 language is for defining levels
> of compliance to requirements, and is best used very sparingly (as
> recommended in RFC 2119 itself). To me, RFC 2119 language doesn't make
> behavior normative -- rather, it describes the implications of doing
> something different than the defined behavior, from "will break the
> protocol if you change it" to "we have reason to think that there might be
> a reason we don't want to describe here that might influence you not to do
> this" to "here are some reasons that would cause you to do something
> different" and on to "doing something different might offend the
> sensibilities of the protocol author, but probably won't hurt anything
> else."
> 
> But I'm ghost-editing a document right now whose gen-art review suggested 
> replacing the vast majority of "is" "does" and "are" prose with MUST. The 
> comments seem to indicate that protocol-defining text not using RFC 2119 
> language (specifically MUST) is "not normative".
> 
> This makes me cringe. But my co-editor likes it a lot. And I see smart
> people like Ole also echoing the though that RFC 2119 language is what
> makes text normative.
> 
> For example, the protocol under discussion uses TLS or DTLS for a plethora
> of security reasons. So, every time the draft discusses sending a response
> to a request, we would say "the node MUST send a response, and this
> response MUST be constructed by (insert some concatenation procedure here)
> and MUST be transmitted using TLS or DTLS.
> 
> Or, a more specific example:
> 
> For the text:
> 
> In order to originate a message to a given Node-ID or Resource-ID, a node 
> constructs an appropriate destination list.
> 
> 
> The Gen-ART comment here is: -First sentence: "a node constructs" -> "a
> node MUST construct"
> 
> 
> We'll literally end up with hundreds of RFC 2119 invocations (mostly MUST)
> in a protocol specification.
> 
> Is this a good or bad thing? My co-editor and I disagree -- he likes 
> formalization of the description language, and I like the English prose.
> But it raises process questions for the IETF as a whole:
> 
> Are we deliberately evolving our language to use RFC 2119 terms as the 
> principle verbs  of a formal specification language?
> 
> Either way, I'd like to see some consensus. Because my head is throbbing
> and I want to know if it MUST hurt, SHOULD hurst, or just hurts. But I
> MUST proceed in accordance with consensus, because to do otherwise would
> undermine the clarity of our entire specification family.
> 

- -- 
Marc Petit-Huguenin
Email: marc@petit-huguenin.org
Blog: http://blog.marc.petit-huguenin.org
Profile: http://www.linkedin.com/in/petithug
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iQIcBAEBCAAGBQJQ6Ht3AAoJECnERZXWan7ETHwP/1MwWKyX4ZoTqS2AZr5VdCwx
jGO/0+tbHppplfippPlJRR6cV5rfrrtkKp9j3Xbr477Jeuaaadjv3y0CfkGF+DUb
fDhcB/GQLiN1oC6s3cjiib46Rnd18Ela6xUAZleiLjKKoo0TJKfQ8oAt3tYonokK
onb95NAsF0FsbiqBzoUi23aEf/SFoKOg3a67DAt5XmntnNh5K6jVOmT4GFYtF3LB
vW6d1x0hI0INUSXzjypD+MaqzCgHvdxAjqx44qlrFjFYz7GLcRAR3Z5ynOCCfeBi
fM4xxGhytTYolrXdOQK1BgtUIewdCHMqPFZjclB2DiEITkUzxRrGKI5MizQEModB
8vwmJQJ0E98veMvBP5ce9eKPZP0gHMxEWMu2zgGulb2mLVxyfSfBIy2dIuqpHsUM
dWuvLzx1HJouZ4sFfCGMarpLvoYwYu1grL+oaJiPXd1TI26BCyI703gdQE1dBRhK
XrfIEgmP1VG1QhhBA6otLQlWfB0IGG2c80y0KOZ4x9rQ8Wn+Cxz4vQg6CvHPys+z
ClvFH4r/v3CpavSpugcD7sJAssfp9wbe9Jjw1pCPiXgs0fN+yQtQRIVDCSCQHNJ4
iWFtwExIDQyh/lKmJNlf8P3qBSmhzqvAG1B9bAZY9JroJoqY84kkgWKHRodAQ/HM
DqC0PVCig1bKYwZpT1Ov
=oOlZ
-----END PGP SIGNATURE-----

From melinda.shore@gmail.com  Sat Jan  5 14:53:43 2013
Return-Path: <melinda.shore@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 010F421F8583 for <ietf@ietfa.amsl.com>; Sat,  5 Jan 2013 14:53:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 PN7X8S+IXPWF for <ietf@ietfa.amsl.com>; Sat,  5 Jan 2013 14:53:42 -0800 (PST)
Received: from mail-pb0-f47.google.com (mail-pb0-f47.google.com [209.85.160.47]) by ietfa.amsl.com (Postfix) with ESMTP id 84EAD21F8526 for <ietf@ietf.org>; Sat,  5 Jan 2013 14:53:42 -0800 (PST)
Received: by mail-pb0-f47.google.com with SMTP id un1so9827974pbc.34 for <ietf@ietf.org>; Sat, 05 Jan 2013 14:53:42 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=q6pZ8QGLv3V0SrlEco8wj32JUxvGFcwoTQh/p6W03Hk=; b=EZMtM/KsKm3KN7KGSHVhSAFX7qbkw5DCYuRBVZWSISNwu3BtVApdttFyHgDlVrDkvZ +RcYPzaL9dOqj6UP/D+c1xOLGSVAqB73A5JXfKHEAycvVlfGTRc6sV8yILYW3OZ2MCLD 1GcZQmwr4uwNB6VLa15/WSd2idkIc9BIEH4gwPIFdLIM//9yB2B9Vxajn7wlhOWehm0u EJucpBBPz/Hcbv/lg8ksf1Nf0lwAM25CKFdYcWSRrozeS9BCw2Jkj01aTDsPvRG+eou2 m68ZinHMcYQX1iOE7Tfe6YDXKedufNrAoozddo/aGNa+p6uAlp5tFuTkpMP2At7l5oVR MP6g==
X-Received: by 10.66.77.38 with SMTP id p6mr165729974paw.47.1357426422332; Sat, 05 Jan 2013 14:53:42 -0800 (PST)
Received: from spandex.local (66-230-84-20-rb1.fai.dsl.dynamic.acsalaska.net. [66.230.84.20]) by mx.google.com with ESMTPS id v2sm35733468paz.36.2013.01.05.14.53.39 (version=TLSv1/SSLv3 cipher=OTHER); Sat, 05 Jan 2013 14:53:40 -0800 (PST)
Message-ID: <50E8AEF2.4090103@gmail.com>
Date: Sat, 05 Jan 2013 13:53:38 -0900
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Making RFC2119 key language easier to Protocol Readers
References: <CADnDZ8-yCxUbrD9oFyQKkJuTgDZbamnV8K4GU+sAN5SekpyHAA@mail.gmail.com> <CADnDZ8_a8cRSKrHzE4fZSrMNO6pGLa9vCcHzKUmHsVtCWRCf6g@mail.gmail.com> <alpine.DEB.2.00.1301050936060.26235@uplift.swm.pp.se>
In-Reply-To: <alpine.DEB.2.00.1301050936060.26235@uplift.swm.pp.se>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 05 Jan 2013 22:53:43 -0000

On 1/4/13 11:39 PM, Mikael Abrahamsson wrote:
> As an operator, I purchase equipment and need to write RFQs. I would
> like to able to ask more than "does the product implement RFC
> <whatever>", I want to also ask "Please document all instances where you
> did not follow all MUST and SHOULD, and why".
> 
> Otherwise I think there needs to be better definition of what it means
> to "implement" or "support" an RFC when it comes to completness and what
> this means as per following SHOULD and MAY.

I think being clear about who our constituencies are and what they
need is probably key to coming to any sort of agreement on any of this.
We've often complained about the lack of operator participation and
Mikael's comments may be an example the consequences of that - that we
don't fully understand how our documents are being used.

That said, frankly I've tended to assume that language in standards
documents is normative unless otherwise specified, and that highly
legalistic language is difficult to read.  On a third hand it wouldn't
be a small thing if non-native English speakers had an easier time with
our documents if every single normative thing in document is flagged
through the use of 2119 language.

So, basically where that leaves me is: 1) language in standards-track
documents is already normative by default; 2) however, if inserting
2119 language in all standards-track documents will make documents more
useful to people who actually run networks and/or clearer to people
whose first language is not English, it's probably worth tightening up
our language.

Melinda


From sayrer@gmail.com  Sat Jan  5 16:19:06 2013
Return-Path: <sayrer@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 57C4821F85CC; Sat,  5 Jan 2013 16:19:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 gmxHkQx7R+OC; Sat,  5 Jan 2013 16:19:05 -0800 (PST)
Received: from mail-wg0-f51.google.com (mail-wg0-f51.google.com [74.125.82.51]) by ietfa.amsl.com (Postfix) with ESMTP id 6672121F8583; Sat,  5 Jan 2013 16:19:04 -0800 (PST)
Received: by mail-wg0-f51.google.com with SMTP id gg4so8355552wgb.6 for <multiple recipients>; Sat, 05 Jan 2013 16:19:03 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=HVAx443GPdwtmDGTz6qFnYEBfwUvdzwqj5kBQd02Pok=; b=QgkEu8+UVYFZhoOp/hE4Ggvf+YdtCiMyJKtgcFApyHAFXvuZX+yRzv3oqIW8EeNeR8 waJPt5v/N8n4Ebz1Di9eRe0EHNS69GcVlcW6OWexHYzvG2TDJHt5XdlaDy/40ClCGHhk ++idcD+5ktH2sxwt94ngVbMzI7uGq3toPVdxWQelkRgzQWu0D4CoklAmvTd6T/ZoxggC eyCGVzpANeEQzTbTqi7IM1ZBv12d0GDIkNFDKMWpq+8mr5lAoSqGjKSyigaUV2kQ9Pfi pR5jPD8F+/oN55vrgHPAWHY9ZfKlh8h4D10+EWjuZZUEV2XRvsslMRtG6XrJyQCsNG0Q gOxQ==
MIME-Version: 1.0
Received: by 10.194.23.37 with SMTP id j5mr89600518wjf.28.1357431543500; Sat, 05 Jan 2013 16:19:03 -0800 (PST)
Received: by 10.194.1.101 with HTTP; Sat, 5 Jan 2013 16:19:03 -0800 (PST)
In-Reply-To: <EABB8F51-C3B4-49F5-8672-5C2ABAC7043A@mnot.net>
References: <20121211150057.28223.93310.idtracker@ietfa.amsl.com> <50cb04b9.86df440a.72fe.1e20SMTPIN_ADDED_BROKEN@mx.google.com> <CABP7RbeNsZ_rBWRjou=VG+hBhUKaOz+y1a0sSChwWiHte9znnQ@mail.gmail.com> <50cb5f3c.694c420a.38fb.39afSMTPIN_ADDED_BROKEN@mx.google.com> <CAChr6SxZRc3B_HCbw76kLe2dsRSr43r-gLpfMVnCUfJTrZdTLA@mail.gmail.com> <CABP7RbfA33huBFadMeXTTEt=MkjW8-d4DFH7+GLXGurnm9sSRw@mail.gmail.com> <CAOXDeqpPE4eNy_qJpDPdPHbCQakG9-hDcNZ3Sj9r4kWedByVzQ@mail.gmail.com> <CAChr6SwtS_=iS-k4mJm1vHjEvvGVzay5jDYeGheqsPZqO-89CQ@mail.gmail.com> <EABB8F51-C3B4-49F5-8672-5C2ABAC7043A@mnot.net>
Date: Sat, 5 Jan 2013 16:19:03 -0800
Message-ID: <CAChr6Sx7JdKM91EwJaSZ0Ra_F4FSqkuc3vzTY1LM=F_8sWho+Q@mail.gmail.com>
Subject: Re: [apps-discuss] Last Call: <draft-ietf-appsawg-json-pointer-07.txt> (JSON Pointer) to Proposed Standard
From: Robert Sayre <sayrer@gmail.com>
To: Mark Nottingham <mnot@mnot.net>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable
Cc: IETF Discussion <ietf@ietf.org>, IETF Apps Discuss <apps-discuss@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 06 Jan 2013 00:19:06 -0000

Mark,

The WG's reasoning, as stated in your message below, seems flawed.
Messages since your last communication on this matter have shown:

1) The ambiguity around arrays makes the patch format unsuitable for
common concurrent editing algorithms.
2) The ambiguity is likely to occur in the real world, for a couple of
different reasons.
3) It's not possible to tell whether a JSON Pointer document is
syntactically correct in isolation.

Additionally, you raised this point in your message below:
>
> the patch author already has to understand the semantics of the document =
they're patching

That claim does not seem to be well-justified, and it could be
meaningless to the person implementing patch software (for example:
https://github.com/sayrer/json-sync).

This issue is a problem in practice, and it's a problem in theory as
well. JSON-Patch messages aren't sufficiently self-descriptive, so
they aren't appropriate for use in a RESTful system.

A response containing technical reasoning seems in order, since the
points raised by myself and others on this issue are unrelated to the
WG's previous thinking.

- Rob

On Sun, Dec 16, 2012 at 9:41 PM, Mark Nottingham <mnot@mnot.net> wrote:
> Robert,
>
> This was discussed extensively in the Working Group.
>
> The root of the issue was that some people reflexively felt that this was=
 necessary, but upon reflection, we decided it wasn't; although it seems "n=
atural" to some, especially those coming from a static language background,=
 it didn't provide any utility.
>
> You might argue that someone who (for example) adds to "/foo/1" in the mi=
staken belief that it's an array, when in fact it's an object, will get sur=
prising results. That's true, but if we were to solve this problem, that pe=
rson would still need to understand the underlying semantics of "foo" to do=
 anything useful to it -- and I'm not hearing anyone complain about that (I=
 hope).
>
> Put another way -- do you really think that people PATCHing something as =
if it's an array (when in fact it's an object) is a significant, real-world=
 problem, given that the patch author already has to understand the semanti=
cs of the document they're patching? I don't, and the WG didn't either.
>
> Regards,
>
>
> On 17/12/2012, at 3:36 PM, Robert Sayre <sayrer@gmail.com> wrote:
>
>> The cost of fixing it seems low, either by changing the path syntax of
>> JSON pointer or changing the names of operations applied to arrays.
>> Array-like objects are common enough in JavaScript to make this a
>> worry. The other suggestions either assume a particular policy for
>> concurrent edits or require more machinery (test operation etc).
>> Wouldn't it be simpler to make the patch format more precise?
>>
>> - Rob
>>
>> On Sun, Dec 16, 2012 at 4:33 PM, Matthew Morley <matt@mpcm.com> wrote:
>>> I am usually lurking and struggling to keep up with these posts. But, I
>>> concur with James, this really is a non-issue in practice.
>>>
>>> The JSON Pointer expresses a path down a JSON object to a specific cont=
ext.
>>> The Patch expresses a change within or to that context.
>>> Everything about the both standards is about that end context.
>>>
>>> If you want to confirm the type of the context before applying a patch,=
 this
>>> should probably be part of a test operation. I'm not sure if this is
>>> possible at this point (?), but that is where the logic should exist.
>>>
>>>
>>>
>>> On Sun, Dec 16, 2012 at 12:22 AM, James M Snell <jasnell@gmail.com> wro=
te:
>>>>
>>>>
>>>>
>>>>
>>>> On Sat, Dec 15, 2012 at 8:36 PM, Robert Sayre <sayrer@gmail.com> wrote=
:
>>>>>
>>>>> On Fri, Dec 14, 2012 at 9:17 AM, Markus Lanthaler
>>>>> <markus.lanthaler@gmx.net> wrote:
>>>>>>
>>>>>> Hmm.. I think that=92s quite problematic. Especially considering how=
 JSON
>>>>>> Pointer is used in JSON Patch.
>>>>>
>>>>> I agree--I provided the same feedback privately. It seems
>>>>> straightforwardly unsound.
>>>>>
>>>>
>>>> In practice it doesn't seem to be much of an issue.
>>>>
>>>> Specifically, if I GET an existing document and get an etag with the J=
SON,
>>>> then make some changes and send a PATCH with If-Match, the fact that a=
ny
>>>> given pointer could point to an array or object member doesn't really =
matter
>>>> much.
>>>>
>>>> For example:
>>>>
>>>>> GET /the/doc HTTP/1.1
>>>>
>>>>  <  HTTP/1.1 200 OK
>>>>     ETag: "my-document-tag"
>>>>     Content-Type: application/json
>>>>
>>>>     {"1":"foo"}
>>>>
>>>>> PATCH /the/doc HTTP/1.1
>>>>     If-Match: "my-document-etag"
>>>>     Content-Type: application/json-patch
>>>>
>>>>     [{"op":"add","path":"/2","value":"bar"}]
>>>>
>>>> Generally speaking, someone should not be using PATCH to perform a par=
tial
>>>> modification if they don't already have some knowledge in advance what=
 they
>>>> are modifying. The only time the apparent ambiguity becomes an issue i=
s when
>>>> a client is blindly sending a patch to an unknown endpoint... in which=
 case,
>>>> you get whatever you end up with.
>>>>
>>>> - James
>>>>
>>>>
>>>>>
>>>>> - Rob
>>>>>
>>>>>
>>>>>>
>>>>>> --
>>>>>>
>>>>>> Markus Lanthaler
>>>>>>
>>>>>> @markuslanthaler
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> From: James M Snell [mailto:jasnell@gmail.com]
>>>>>> Sent: Friday, December 14, 2012 5:41 PM
>>>>>> To: Markus Lanthaler
>>>>>> Cc: IETF Discussion; IETF Apps Discuss
>>>>>> Subject: Re: [apps-discuss] Last Call:
>>>>>> <draft-ietf-appsawg-json-pointer-07.txt> (JSON Pointer) to Proposed =
Standard
>>>>>>
>>>>>>
>>>>>>
>>>>>> JSON Pointer does not distinguish between objects and arrays. That i=
s
>>>>>> not determined until the pointer is applied to an actual object inst=
ance...
>>>>>> the pointer "/1" is valid against {"1":"a"} or ["a","b"]
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Fri, Dec 14, 2012 at 2:51 AM, Markus Lanthaler
>>>>>> <markus.lanthaler@gmx.net> wrote:
>>>>>>
>>>>>> I've asked that before but didn't get an answer. So let me ask again
>>>>>> (even
>>>>>> though I'm quite sure it has already been asked by somebody else).
>>>>>>
>>>>>> How does JSON Pointer distinguish between objects and arrays? E.g.
>>>>>> consider
>>>>>> the following JSON document:
>>>>>>
>>>>>> {
>>>>>>  "foo": "bar",
>>>>>>  "1": "baz"
>>>>>> }
>>>>>>
>>>>>> As I read the draft, the JSON Pointer "/1" would evaluate to "baz" e=
ven
>>>>>> though that's probably not what the author intended. Is there a way =
to
>>>>>> avoid
>>>>>> that?
>>>>>>
>>>>>>
>>>>>> Thanks,
>>>>>> Markus
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Markus Lanthaler
>>>>>> @markuslanthaler
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>> -----Original Message-----
>>>>>>> From: apps-discuss-bounces@ietf.org [mailto:apps-discuss-
>>>>>>> bounces@ietf.org] On Behalf Of The IESG
>>>>>>> Sent: Tuesday, December 11, 2012 4:01 PM
>>>>>>> To: IETF-Announce
>>>>>>> Cc: apps-discuss@ietf.org
>>>>>>> Subject: [apps-discuss] Last Call: <draft-ietf-appsawg-json-pointer=
-
>>>>>>> 07.txt> (JSON Pointer) to Proposed Standard
>>>>>>>
>>>>>>>
>>>>>>> The IESG has received a request from the Applications Area Working
>>>>>>> Group
>>>>>>> WG (appsawg) to consider the following document:
>>>>>>> - 'JSON Pointer'
>>>>>>>  <draft-ietf-appsawg-json-pointer-07.txt> as Proposed Standard
>>>>>>>
>>>>>>> The IESG plans to make a decision in the next few weeks, and solici=
ts
>>>>>>> final comments on this action. Please send substantive comments to
>>>>>>> the
>>>>>>> ietf@ietf.org mailing lists by 2012-12-25. Exceptionally, comments
>>>>>>> may
>>>>>>> be
>>>>>>> sent to iesg@ietf.org instead. In either case, please retain the
>>>>>>> beginning of the Subject line to allow automated sorting.
>>>>>>>
>>>>>>> Abstract
>>>>>>>
>>>>>>>
>>>>>>>   JSON Pointer defines a string syntax for identifying a specific
>>>>>>> value
>>>>>>>   within a JSON document.
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> The file can be obtained via
>>>>>>> http://datatracker.ietf.org/doc/draft-ietf-appsawg-json-pointer/
>>>>>>>
>>>>>>> IESG discussion can be tracked via
>>>>>>>
>>>>>>> http://datatracker.ietf.org/doc/draft-ietf-appsawg-json-pointer/bal=
lot/
>>>>>>>
>>>>>>>
>>>>>>> No IPR declarations have been submitted directly on this I-D.
>>>>>>>
>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> apps-discuss mailing list
>>>>>>> apps-discuss@ietf.org
>>>>>>> https://www.ietf.org/mailman/listinfo/apps-discuss
>>>>>>
>>>>>> _______________________________________________
>>>>>> apps-discuss mailing list
>>>>>> apps-discuss@ietf.org
>>>>>> https://www.ietf.org/mailman/listinfo/apps-discuss
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> apps-discuss mailing list
>>>>>> apps-discuss@ietf.org
>>>>>> https://www.ietf.org/mailman/listinfo/apps-discuss
>>>>>>
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> apps-discuss mailing list
>>>> apps-discuss@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/apps-discuss
>>>>
>>>
>>>
>>>
>>> --
>>> Matthew P. C. Morley
>> _______________________________________________
>> apps-discuss mailing list
>> apps-discuss@ietf.org
>> https://www.ietf.org/mailman/listinfo/apps-discuss
>
> --
> Mark Nottingham   http://www.mnot.net/
>
>
>

From jasnell@gmail.com  Sat Jan  5 17:31:26 2013
Return-Path: <jasnell@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CB19A21F8514; Sat,  5 Jan 2013 17:31:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.598
X-Spam-Level: 
X-Spam-Status: No, score=-3.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
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 krnL8HJnp3Yj; Sat,  5 Jan 2013 17:31:25 -0800 (PST)
Received: from mail-oa0-f53.google.com (mail-oa0-f53.google.com [209.85.219.53]) by ietfa.amsl.com (Postfix) with ESMTP id DEAE421F8510; Sat,  5 Jan 2013 17:31:24 -0800 (PST)
Received: by mail-oa0-f53.google.com with SMTP id j6so16289220oag.26 for <multiple recipients>; Sat, 05 Jan 2013 17:31:24 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=R1QGDaBtObbigb7511+EgX674huTEsank8svzI2EHcg=; b=WstZq2KqGnlWv8DP8r2bDF8B2imaVg0KPR/k1bruL9z1xhbE+hqq7K9Usdgbm0U2zR H0bwLhvEcxDxCxynlh9OssrqnM3nyy4sJjTMBHRI44hQGRcQiH44PDrc76U2ZUc+J5M0 l9FHYOgSNOkMa8k9q6TIB3IEtbUYoL/KolnK4q98KSZkr98xw6yEe/kWCAJY2nCNslKa SVNl1rm+dG2dBcDhWX4jil9xybYt4Ya8942EfcNDTCqaflbQWDMS707yj0GvS0xupAhO kfOJXHKAbaNBRSQSeENlQ2K7xPt/v69ETje5GjnGfAJKFZ7bdVKEbj0WJLeBPuF9WAw7 41IA==
Received: by 10.182.0.68 with SMTP id 4mr42070525obc.80.1357435884336; Sat, 05 Jan 2013 17:31:24 -0800 (PST)
MIME-Version: 1.0
Received: by 10.76.86.9 with HTTP; Sat, 5 Jan 2013 17:31:04 -0800 (PST)
In-Reply-To: <CAChr6Sx7JdKM91EwJaSZ0Ra_F4FSqkuc3vzTY1LM=F_8sWho+Q@mail.gmail.com>
References: <20121211150057.28223.93310.idtracker@ietfa.amsl.com> <50cb04b9.86df440a.72fe.1e20SMTPIN_ADDED_BROKEN@mx.google.com> <CABP7RbeNsZ_rBWRjou=VG+hBhUKaOz+y1a0sSChwWiHte9znnQ@mail.gmail.com> <50cb5f3c.694c420a.38fb.39afSMTPIN_ADDED_BROKEN@mx.google.com> <CAChr6SxZRc3B_HCbw76kLe2dsRSr43r-gLpfMVnCUfJTrZdTLA@mail.gmail.com> <CABP7RbfA33huBFadMeXTTEt=MkjW8-d4DFH7+GLXGurnm9sSRw@mail.gmail.com> <CAOXDeqpPE4eNy_qJpDPdPHbCQakG9-hDcNZ3Sj9r4kWedByVzQ@mail.gmail.com> <CAChr6SwtS_=iS-k4mJm1vHjEvvGVzay5jDYeGheqsPZqO-89CQ@mail.gmail.com> <EABB8F51-C3B4-49F5-8672-5C2ABAC7043A@mnot.net> <CAChr6Sx7JdKM91EwJaSZ0Ra_F4FSqkuc3vzTY1LM=F_8sWho+Q@mail.gmail.com>
From: James M Snell <jasnell@gmail.com>
Date: Sat, 5 Jan 2013 17:31:04 -0800
Message-ID: <CABP7RbfRRuc=n6V4S4E7hLM8xEEuhi_R+YzEhC1Shy+ZK7dYqA@mail.gmail.com>
Subject: Re: [apps-discuss] Last Call: <draft-ietf-appsawg-json-pointer-07.txt> (JSON Pointer) to Proposed Standard
To: Robert Sayre <sayrer@gmail.com>
Content-Type: multipart/alternative; boundary=f46d043c7f88b0f73f04d294ab99
Cc: Mark Nottingham <mnot@mnot.net>, IETF Discussion <ietf@ietf.org>, IETF Apps Discuss <apps-discuss@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 06 Jan 2013 01:31:26 -0000

--f46d043c7f88b0f73f04d294ab99
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Robert,

I may have missed it, but can you provide a non-theoretical example of this
problem that you're suggesting exists in practice?

On Sat, Jan 5, 2013 at 4:19 PM, Robert Sayre <sayrer@gmail.com> wrote:

> Mark,
>
> The WG's reasoning, as stated in your message below, seems flawed.
> Messages since your last communication on this matter have shown:
>
> 1) The ambiguity around arrays makes the patch format unsuitable for
> common concurrent editing algorithms.
>

Why? I'm still not seeing how it's unsuitable. Again, a non-theoretical
example would be helpful.



> 2) The ambiguity is likely to occur in the real world, for a couple of
> different reasons.
>

Such as? What are the reasons?


> 3) It's not possible to tell whether a JSON Pointer document is
> syntactically correct in isolation.
>

There is no such thing as a "JSON Pointer document" and I have absolutely
no idea what "syntactically correct in isolation" means with regards to
this problem you're suggesting. If I see "/a/b/1", that is a syntactically
correct JSON Pointer... whether or not it points to anything specific
depends entirely on the specific JSON structure it is applied to. If I had
to guess, you're saying that it's not possible to tell if "/a/b/01" is a
valid JSON Pointer or not given nothing but the pointer? If so, who cares
really? The JSON Pointer is not useful unless it's applied to an actual
JSON structure, it's only at that point that we really ought to care about
validity.

Still not seeing the problem.


>
> Additionally, you raised this point in your message below:
> >
> > the patch author already has to understand the semantics of the documen=
t
> they're patching
>
> That claim does not seem to be well-justified, and it could be
> meaningless to the person implementing patch software (for example:
> https://github.com/sayrer/json-sync).
>
> This issue is a problem in practice, and it's a problem in theory as
> well. JSON-Patch messages aren't sufficiently self-descriptive, so
> they aren't appropriate for use in a RESTful system.
>
>
What would be "sufficiently self-descriptive" ? Again, a non-theoretical
example and suggested alternative that we can compare would be helpful for
context.

It is possible that I missed a couple of posts on this over the holiday so
if you already provided an example, please do let me know and I'll go
hunting through the archives.

- James


> A response containing technical reasoning seems in order, since the
> points raised by myself and others on this issue are unrelated to the
> WG's previous thinking.



>
> - Rob
>
> On Sun, Dec 16, 2012 at 9:41 PM, Mark Nottingham <mnot@mnot.net> wrote:
> > Robert,
> >
> > This was discussed extensively in the Working Group.
> >
> > The root of the issue was that some people reflexively felt that this
> was necessary, but upon reflection, we decided it wasn't; although it see=
ms
> "natural" to some, especially those coming from a static language
> background, it didn't provide any utility.
> >
> > You might argue that someone who (for example) adds to "/foo/1" in the
> mistaken belief that it's an array, when in fact it's an object, will get
> surprising results. That's true, but if we were to solve this problem, th=
at
> person would still need to understand the underlying semantics of "foo" t=
o
> do anything useful to it -- and I'm not hearing anyone complain about tha=
t
> (I hope).
> >
> > Put another way -- do you really think that people PATCHing something a=
s
> if it's an array (when in fact it's an object) is a significant, real-wor=
ld
> problem, given that the patch author already has to understand the
> semantics of the document they're patching? I don't, and the WG didn't
> either.
> >
> > Regards,
> >
> >
> > On 17/12/2012, at 3:36 PM, Robert Sayre <sayrer@gmail.com> wrote:
> >
> >> The cost of fixing it seems low, either by changing the path syntax of
> >> JSON pointer or changing the names of operations applied to arrays.
> >> Array-like objects are common enough in JavaScript to make this a
> >> worry. The other suggestions either assume a particular policy for
> >> concurrent edits or require more machinery (test operation etc).
> >> Wouldn't it be simpler to make the patch format more precise?
> >>
> >> - Rob
> >>
> >> On Sun, Dec 16, 2012 at 4:33 PM, Matthew Morley <matt@mpcm.com> wrote:
> >>> I am usually lurking and struggling to keep up with these posts. But,=
 I
> >>> concur with James, this really is a non-issue in practice.
> >>>
> >>> The JSON Pointer expresses a path down a JSON object to a specific
> context.
> >>> The Patch expresses a change within or to that context.
> >>> Everything about the both standards is about that end context.
> >>>
> >>> If you want to confirm the type of the context before applying a
> patch, this
> >>> should probably be part of a test operation. I'm not sure if this is
> >>> possible at this point (?), but that is where the logic should exist.
> >>>
> >>>
> >>>
> >>> On Sun, Dec 16, 2012 at 12:22 AM, James M Snell <jasnell@gmail.com>
> wrote:
> >>>>
> >>>>
> >>>>
> >>>>
> >>>> On Sat, Dec 15, 2012 at 8:36 PM, Robert Sayre <sayrer@gmail.com>
> wrote:
> >>>>>
> >>>>> On Fri, Dec 14, 2012 at 9:17 AM, Markus Lanthaler
> >>>>> <markus.lanthaler@gmx.net> wrote:
> >>>>>>
> >>>>>> Hmm.. I think that=E2=80=99s quite problematic. Especially conside=
ring how
> JSON
> >>>>>> Pointer is used in JSON Patch.
> >>>>>
> >>>>> I agree--I provided the same feedback privately. It seems
> >>>>> straightforwardly unsound.
> >>>>>
> >>>>
> >>>> In practice it doesn't seem to be much of an issue.
> >>>>
> >>>> Specifically, if I GET an existing document and get an etag with the
> JSON,
> >>>> then make some changes and send a PATCH with If-Match, the fact that
> any
> >>>> given pointer could point to an array or object member doesn't reall=
y
> matter
> >>>> much.
> >>>>
> >>>> For example:
> >>>>
> >>>>> GET /the/doc HTTP/1.1
> >>>>
> >>>>  <  HTTP/1.1 200 OK
> >>>>     ETag: "my-document-tag"
> >>>>     Content-Type: application/json
> >>>>
> >>>>     {"1":"foo"}
> >>>>
> >>>>> PATCH /the/doc HTTP/1.1
> >>>>     If-Match: "my-document-etag"
> >>>>     Content-Type: application/json-patch
> >>>>
> >>>>     [{"op":"add","path":"/2","value":"bar"}]
> >>>>
> >>>> Generally speaking, someone should not be using PATCH to perform a
> partial
> >>>> modification if they don't already have some knowledge in advance
> what they
> >>>> are modifying. The only time the apparent ambiguity becomes an issue
> is when
> >>>> a client is blindly sending a patch to an unknown endpoint... in
> which case,
> >>>> you get whatever you end up with.
> >>>>
> >>>> - James
> >>>>
> >>>>
> >>>>>
> >>>>> - Rob
> >>>>>
> >>>>>
> >>>>>>
> >>>>>> --
> >>>>>>
> >>>>>> Markus Lanthaler
> >>>>>>
> >>>>>> @markuslanthaler
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>> From: James M Snell [mailto:jasnell@gmail.com]
> >>>>>> Sent: Friday, December 14, 2012 5:41 PM
> >>>>>> To: Markus Lanthaler
> >>>>>> Cc: IETF Discussion; IETF Apps Discuss
> >>>>>> Subject: Re: [apps-discuss] Last Call:
> >>>>>> <draft-ietf-appsawg-json-pointer-07.txt> (JSON Pointer) to Propose=
d
> Standard
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>> JSON Pointer does not distinguish between objects and arrays. That
> is
> >>>>>> not determined until the pointer is applied to an actual object
> instance...
> >>>>>> the pointer "/1" is valid against {"1":"a"} or ["a","b"]
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>> On Fri, Dec 14, 2012 at 2:51 AM, Markus Lanthaler
> >>>>>> <markus.lanthaler@gmx.net> wrote:
> >>>>>>
> >>>>>> I've asked that before but didn't get an answer. So let me ask aga=
in
> >>>>>> (even
> >>>>>> though I'm quite sure it has already been asked by somebody else).
> >>>>>>
> >>>>>> How does JSON Pointer distinguish between objects and arrays? E.g.
> >>>>>> consider
> >>>>>> the following JSON document:
> >>>>>>
> >>>>>> {
> >>>>>>  "foo": "bar",
> >>>>>>  "1": "baz"
> >>>>>> }
> >>>>>>
> >>>>>> As I read the draft, the JSON Pointer "/1" would evaluate to "baz"
> even
> >>>>>> though that's probably not what the author intended. Is there a wa=
y
> to
> >>>>>> avoid
> >>>>>> that?
> >>>>>>
> >>>>>>
> >>>>>> Thanks,
> >>>>>> Markus
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>> --
> >>>>>> Markus Lanthaler
> >>>>>> @markuslanthaler
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>> -----Original Message-----
> >>>>>>> From: apps-discuss-bounces@ietf.org [mailto:apps-discuss-
> >>>>>>> bounces@ietf.org] On Behalf Of The IESG
> >>>>>>> Sent: Tuesday, December 11, 2012 4:01 PM
> >>>>>>> To: IETF-Announce
> >>>>>>> Cc: apps-discuss@ietf.org
> >>>>>>> Subject: [apps-discuss] Last Call:
> <draft-ietf-appsawg-json-pointer-
> >>>>>>> 07.txt> (JSON Pointer) to Proposed Standard
> >>>>>>>
> >>>>>>>
> >>>>>>> The IESG has received a request from the Applications Area Workin=
g
> >>>>>>> Group
> >>>>>>> WG (appsawg) to consider the following document:
> >>>>>>> - 'JSON Pointer'
> >>>>>>>  <draft-ietf-appsawg-json-pointer-07.txt> as Proposed Standard
> >>>>>>>
> >>>>>>> The IESG plans to make a decision in the next few weeks, and
> solicits
> >>>>>>> final comments on this action. Please send substantive comments t=
o
> >>>>>>> the
> >>>>>>> ietf@ietf.org mailing lists by 2012-12-25. Exceptionally, comment=
s
> >>>>>>> may
> >>>>>>> be
> >>>>>>> sent to iesg@ietf.org instead. In either case, please retain the
> >>>>>>> beginning of the Subject line to allow automated sorting.
> >>>>>>>
> >>>>>>> Abstract
> >>>>>>>
> >>>>>>>
> >>>>>>>   JSON Pointer defines a string syntax for identifying a specific
> >>>>>>> value
> >>>>>>>   within a JSON document.
> >>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>> The file can be obtained via
> >>>>>>> http://datatracker.ietf.org/doc/draft-ietf-appsawg-json-pointer/
> >>>>>>>
> >>>>>>> IESG discussion can be tracked via
> >>>>>>>
> >>>>>>>
> http://datatracker.ietf.org/doc/draft-ietf-appsawg-json-pointer/ballot/
> >>>>>>>
> >>>>>>>
> >>>>>>> No IPR declarations have been submitted directly on this I-D.
> >>>>>>>
> >>>>>>>
> >>>>>>> _______________________________________________
> >>>>>>> apps-discuss mailing list
> >>>>>>> apps-discuss@ietf.org
> >>>>>>> https://www.ietf.org/mailman/listinfo/apps-discuss
> >>>>>>
> >>>>>> _______________________________________________
> >>>>>> apps-discuss mailing list
> >>>>>> apps-discuss@ietf.org
> >>>>>> https://www.ietf.org/mailman/listinfo/apps-discuss
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>> _______________________________________________
> >>>>>> apps-discuss mailing list
> >>>>>> apps-discuss@ietf.org
> >>>>>> https://www.ietf.org/mailman/listinfo/apps-discuss
> >>>>>>
> >>>>
> >>>>
> >>>>
> >>>> _______________________________________________
> >>>> apps-discuss mailing list
> >>>> apps-discuss@ietf.org
> >>>> https://www.ietf.org/mailman/listinfo/apps-discuss
> >>>>
> >>>
> >>>
> >>>
> >>> --
> >>> Matthew P. C. Morley
> >> _______________________________________________
> >> apps-discuss mailing list
> >> apps-discuss@ietf.org
> >> https://www.ietf.org/mailman/listinfo/apps-discuss
> >
> > --
> > Mark Nottingham   http://www.mnot.net/
> >
> >
> >
> _______________________________________________
> apps-discuss mailing list
> apps-discuss@ietf.org
> https://www.ietf.org/mailman/listinfo/apps-discuss
>

--f46d043c7f88b0f73f04d294ab99
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><font face=3D"courier new,monospace">Robert,</font><div><f=
ont face=3D"courier new,monospace"><br></font></div><div style><font face=
=3D"courier new,monospace">I may have missed it, but can you provide a non-=
theoretical example of this problem that you&#39;re suggesting exists in pr=
actice?=C2=A0</font></div>

<div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Sat, Jan 5, 20=
13 at 4:19 PM, Robert Sayre <span dir=3D"ltr">&lt;<a href=3D"mailto:sayrer@=
gmail.com" target=3D"_blank">sayrer@gmail.com</a>&gt;</span> wrote:<br><blo=
ckquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left=
-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;paddi=
ng-left:1ex">

Mark,<br>
<br>
The WG&#39;s reasoning, as stated in your message below, seems flawed.<br>
Messages since your last communication on this matter have shown:<br>
<br>
1) The ambiguity around arrays makes the patch format unsuitable for<br>
common concurrent editing algorithms.<br></blockquote><div><br></div><div s=
tyle><font face=3D"courier new, monospace">Why? I&#39;m still not seeing ho=
w it&#39;s unsuitable. Again, a non-theoretical example would be helpful.</=
font></div>

<div><br></div><div>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"=
margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,20=
4,204);border-left-style:solid;padding-left:1ex">
2) The ambiguity is likely to occur in the real world, for a couple of<br>
different reasons.<br></blockquote><div><br></div><div style><font face=3D"=
courier new, monospace">Such as? What are the reasons?=C2=A0</font></div><d=
iv>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0p=
x 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-lef=
t-style:solid;padding-left:1ex">


3) It&#39;s not possible to tell whether a JSON Pointer document is<br>
syntactically correct in isolation.<br></blockquote><div><br></div><div sty=
le><font face=3D"courier new, monospace">There is no such thing as a &quot;=
JSON Pointer document&quot; and I have absolutely no idea what &quot;syntac=
tically correct in isolation&quot; means with regards to this problem you&#=
39;re suggesting. If I see &quot;/a/b/1&quot;, that is a syntactically corr=
ect JSON Pointer... whether or not it points to anything specific depends e=
ntirely on the specific JSON structure it is applied to. If I had to guess,=
 you&#39;re saying that it&#39;s not possible to tell if &quot;/a/b/01&quot=
; is a valid JSON Pointer or not given nothing but the pointer? If so, who =
cares really? The JSON Pointer is not useful unless it&#39;s applied to an =
actual JSON structure, it&#39;s only at that point that we really ought to =
care about validity.</font></div>

<div style><font face=3D"courier new, monospace"><br></font></div><div styl=
e><font face=3D"courier new, monospace">Still not seeing the problem.</font=
></div><div>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0=
px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);b=
order-left-style:solid;padding-left:1ex">


<br>
Additionally, you raised this point in your message below:<br>
<div class=3D"im">&gt;<br>
&gt; the patch author already has to understand the semantics of the docume=
nt they&#39;re patching<br>
<br>
</div>That claim does not seem to be well-justified, and it could be<br>
meaningless to the person implementing patch software (for example:<br>
<a href=3D"https://github.com/sayrer/json-sync" target=3D"_blank">https://g=
ithub.com/sayrer/json-sync</a>).<br>
<br>
This issue is a problem in practice, and it&#39;s a problem in theory as<br=
>
well. JSON-Patch messages aren&#39;t sufficiently self-descriptive, so<br>
they aren&#39;t appropriate for use in a RESTful system.<br>
<br></blockquote><div><br></div><div style><font face=3D"courier new, monos=
pace">What would be &quot;sufficiently self-descriptive&quot; ? Again, a no=
n-theoretical example and suggested alternative that we can compare would b=
e helpful for context.</font></div>

<div style><br></div><div style><font face=3D"courier new, monospace">It is=
 possible that I missed a couple of posts on this over the holiday so if yo=
u already provided an example, please do let me know and I&#39;ll go huntin=
g through the archives.</font></div>

<div style><font face=3D"courier new, monospace"><br></font></div><div styl=
e><font face=3D"courier new, monospace">- James</font></div><div>=C2=A0</di=
v><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;borde=
r-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid=
;padding-left:1ex">


A response containing technical reasoning seems in order, since the<br>
points raised by myself and others on this issue are unrelated to the<br>
WG&#39;s previous thinking.</blockquote><div>=C2=A0</div><blockquote class=
=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left-width:1px;bo=
rder-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<br>
- Rob<br>
<div class=3D"im"><br>
On Sun, Dec 16, 2012 at 9:41 PM, Mark Nottingham &lt;<a href=3D"mailto:mnot=
@mnot.net">mnot@mnot.net</a>&gt; wrote:<br>
</div><div class=3D""><div class=3D"h5">&gt; Robert,<br>
&gt;<br>
&gt; This was discussed extensively in the Working Group.<br>
&gt;<br>
&gt; The root of the issue was that some people reflexively felt that this =
was necessary, but upon reflection, we decided it wasn&#39;t; although it s=
eems &quot;natural&quot; to some, especially those coming from a static lan=
guage background, it didn&#39;t provide any utility.<br>


&gt;<br>
&gt; You might argue that someone who (for example) adds to &quot;/foo/1&qu=
ot; in the mistaken belief that it&#39;s an array, when in fact it&#39;s an=
 object, will get surprising results. That&#39;s true, but if we were to so=
lve this problem, that person would still need to understand the underlying=
 semantics of &quot;foo&quot; to do anything useful to it -- and I&#39;m no=
t hearing anyone complain about that (I hope).<br>


&gt;<br>
&gt; Put another way -- do you really think that people PATCHing something =
as if it&#39;s an array (when in fact it&#39;s an object) is a significant,=
 real-world problem, given that the patch author already has to understand =
the semantics of the document they&#39;re patching? I don&#39;t, and the WG=
 didn&#39;t either.<br>


&gt;<br>
&gt; Regards,<br>
&gt;<br>
&gt;<br>
&gt; On 17/12/2012, at 3:36 PM, Robert Sayre &lt;<a href=3D"mailto:sayrer@g=
mail.com">sayrer@gmail.com</a>&gt; wrote:<br>
&gt;<br>
&gt;&gt; The cost of fixing it seems low, either by changing the path synta=
x of<br>
&gt;&gt; JSON pointer or changing the names of operations applied to arrays=
.<br>
&gt;&gt; Array-like objects are common enough in JavaScript to make this a<=
br>
&gt;&gt; worry. The other suggestions either assume a particular policy for=
<br>
&gt;&gt; concurrent edits or require more machinery (test operation etc).<b=
r>
&gt;&gt; Wouldn&#39;t it be simpler to make the patch format more precise?<=
br>
&gt;&gt;<br>
&gt;&gt; - Rob<br>
&gt;&gt;<br>
&gt;&gt; On Sun, Dec 16, 2012 at 4:33 PM, Matthew Morley &lt;<a href=3D"mai=
lto:matt@mpcm.com">matt@mpcm.com</a>&gt; wrote:<br>
&gt;&gt;&gt; I am usually lurking and struggling to keep up with these post=
s. But, I<br>
&gt;&gt;&gt; concur with James, this really is a non-issue in practice.<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; The JSON Pointer expresses a path down a JSON object to a spec=
ific context.<br>
&gt;&gt;&gt; The Patch expresses a change within or to that context.<br>
&gt;&gt;&gt; Everything about the both standards is about that end context.=
<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; If you want to confirm the type of the context before applying=
 a patch, this<br>
&gt;&gt;&gt; should probably be part of a test operation. I&#39;m not sure =
if this is<br>
&gt;&gt;&gt; possible at this point (?), but that is where the logic should=
 exist.<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; On Sun, Dec 16, 2012 at 12:22 AM, James M Snell &lt;<a href=3D=
"mailto:jasnell@gmail.com">jasnell@gmail.com</a>&gt; wrote:<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; On Sat, Dec 15, 2012 at 8:36 PM, Robert Sayre &lt;<a href=
=3D"mailto:sayrer@gmail.com">sayrer@gmail.com</a>&gt; wrote:<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; On Fri, Dec 14, 2012 at 9:17 AM, Markus Lanthaler<br>
&gt;&gt;&gt;&gt;&gt; &lt;<a href=3D"mailto:markus.lanthaler@gmx.net">markus=
.lanthaler@gmx.net</a>&gt; wrote:<br>
&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt; Hmm.. I think that=E2=80=99s quite problematic. Es=
pecially considering how JSON<br>
&gt;&gt;&gt;&gt;&gt;&gt; Pointer is used in JSON Patch.<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; I agree--I provided the same feedback privately. It se=
ems<br>
&gt;&gt;&gt;&gt;&gt; straightforwardly unsound.<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; In practice it doesn&#39;t seem to be much of an issue.<br=
>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; Specifically, if I GET an existing document and get an eta=
g with the JSON,<br>
&gt;&gt;&gt;&gt; then make some changes and send a PATCH with If-Match, the=
 fact that any<br>
&gt;&gt;&gt;&gt; given pointer could point to an array or object member doe=
sn&#39;t really matter<br>
&gt;&gt;&gt;&gt; much.<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; For example:<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; GET /the/doc HTTP/1.1<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; =C2=A0&lt; =C2=A0HTTP/1.1 200 OK<br>
&gt;&gt;&gt;&gt; =C2=A0 =C2=A0 ETag: &quot;my-document-tag&quot;<br>
&gt;&gt;&gt;&gt; =C2=A0 =C2=A0 Content-Type: application/json<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; =C2=A0 =C2=A0 {&quot;1&quot;:&quot;foo&quot;}<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; PATCH /the/doc HTTP/1.1<br>
&gt;&gt;&gt;&gt; =C2=A0 =C2=A0 If-Match: &quot;my-document-etag&quot;<br>
&gt;&gt;&gt;&gt; =C2=A0 =C2=A0 Content-Type: application/json-patch<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; =C2=A0 =C2=A0 [{&quot;op&quot;:&quot;add&quot;,&quot;path&=
quot;:&quot;/2&quot;,&quot;value&quot;:&quot;bar&quot;}]<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; Generally speaking, someone should not be using PATCH to p=
erform a partial<br>
&gt;&gt;&gt;&gt; modification if they don&#39;t already have some knowledge=
 in advance what they<br>
&gt;&gt;&gt;&gt; are modifying. The only time the apparent ambiguity become=
s an issue is when<br>
&gt;&gt;&gt;&gt; a client is blindly sending a patch to an unknown endpoint=
... in which case,<br>
&gt;&gt;&gt;&gt; you get whatever you end up with.<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; - James<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; - Rob<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt; --<br>
&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt; Markus Lanthaler<br>
&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt; @markuslanthaler<br>
&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt; From: James M Snell [mailto:<a href=3D"mailto:jasn=
ell@gmail.com">jasnell@gmail.com</a>]<br>
&gt;&gt;&gt;&gt;&gt;&gt; Sent: Friday, December 14, 2012 5:41 PM<br>
&gt;&gt;&gt;&gt;&gt;&gt; To: Markus Lanthaler<br>
&gt;&gt;&gt;&gt;&gt;&gt; Cc: IETF Discussion; IETF Apps Discuss<br>
&gt;&gt;&gt;&gt;&gt;&gt; Subject: Re: [apps-discuss] Last Call:<br>
&gt;&gt;&gt;&gt;&gt;&gt; &lt;draft-ietf-appsawg-json-pointer-07.txt&gt; (JS=
ON Pointer) to Proposed Standard<br>
&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt; JSON Pointer does not distinguish between objects =
and arrays. That is<br>
&gt;&gt;&gt;&gt;&gt;&gt; not determined until the pointer is applied to an =
actual object instance...<br>
&gt;&gt;&gt;&gt;&gt;&gt; the pointer &quot;/1&quot; is valid against {&quot=
;1&quot;:&quot;a&quot;} or [&quot;a&quot;,&quot;b&quot;]<br>
&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt; On Fri, Dec 14, 2012 at 2:51 AM, Markus Lanthaler<=
br>
&gt;&gt;&gt;&gt;&gt;&gt; &lt;<a href=3D"mailto:markus.lanthaler@gmx.net">ma=
rkus.lanthaler@gmx.net</a>&gt; wrote:<br>
&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt; I&#39;ve asked that before but didn&#39;t get an a=
nswer. So let me ask again<br>
&gt;&gt;&gt;&gt;&gt;&gt; (even<br>
&gt;&gt;&gt;&gt;&gt;&gt; though I&#39;m quite sure it has already been aske=
d by somebody else).<br>
&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt; How does JSON Pointer distinguish between objects =
and arrays? E.g.<br>
&gt;&gt;&gt;&gt;&gt;&gt; consider<br>
&gt;&gt;&gt;&gt;&gt;&gt; the following JSON document:<br>
&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt; {<br>
&gt;&gt;&gt;&gt;&gt;&gt; =C2=A0&quot;foo&quot;: &quot;bar&quot;,<br>
&gt;&gt;&gt;&gt;&gt;&gt; =C2=A0&quot;1&quot;: &quot;baz&quot;<br>
&gt;&gt;&gt;&gt;&gt;&gt; }<br>
&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt; As I read the draft, the JSON Pointer &quot;/1&quo=
t; would evaluate to &quot;baz&quot; even<br>
&gt;&gt;&gt;&gt;&gt;&gt; though that&#39;s probably not what the author int=
ended. Is there a way to<br>
&gt;&gt;&gt;&gt;&gt;&gt; avoid<br>
&gt;&gt;&gt;&gt;&gt;&gt; that?<br>
&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt; Thanks,<br>
&gt;&gt;&gt;&gt;&gt;&gt; Markus<br>
&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt; --<br>
&gt;&gt;&gt;&gt;&gt;&gt; Markus Lanthaler<br>
&gt;&gt;&gt;&gt;&gt;&gt; @markuslanthaler<br>
&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; -----Original Message-----<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; From: <a href=3D"mailto:apps-discuss-bounces@i=
etf.org">apps-discuss-bounces@ietf.org</a> [mailto:<a href=3D"mailto:apps-d=
iscuss-">apps-discuss-</a><br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; <a href=3D"mailto:bounces@ietf.org">bounces@ie=
tf.org</a>] On Behalf Of The IESG<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; Sent: Tuesday, December 11, 2012 4:01 PM<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; To: IETF-Announce<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; Cc: <a href=3D"mailto:apps-discuss@ietf.org">a=
pps-discuss@ietf.org</a><br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; Subject: [apps-discuss] Last Call: &lt;draft-i=
etf-appsawg-json-pointer-<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; 07.txt&gt; (JSON Pointer) to Proposed Standard=
<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; The IESG has received a request from the Appli=
cations Area Working<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; Group<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; WG (appsawg) to consider the following documen=
t:<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; - &#39;JSON Pointer&#39;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; =C2=A0&lt;draft-ietf-appsawg-json-pointer-07.t=
xt&gt; as Proposed Standard<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; The IESG plans to make a decision in the next =
few weeks, and solicits<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; final comments on this action. Please send sub=
stantive comments to<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; the<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; <a href=3D"mailto:ietf@ietf.org">ietf@ietf.org=
</a> mailing lists by 2012-12-25. Exceptionally, comments<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; may<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; be<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; sent to <a href=3D"mailto:iesg@ietf.org">iesg@=
ietf.org</a> instead. In either case, please retain the<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; beginning of the Subject line to allow automat=
ed sorting.<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; Abstract<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; =C2=A0 JSON Pointer defines a string syntax fo=
r identifying a specific<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; value<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; =C2=A0 within a JSON document.<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; The file can be obtained via<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; <a href=3D"http://datatracker.ietf.org/doc/dra=
ft-ietf-appsawg-json-pointer/" target=3D"_blank">http://datatracker.ietf.or=
g/doc/draft-ietf-appsawg-json-pointer/</a><br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; IESG discussion can be tracked via<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; <a href=3D"http://datatracker.ietf.org/doc/dra=
ft-ietf-appsawg-json-pointer/ballot/" target=3D"_blank">http://datatracker.=
ietf.org/doc/draft-ietf-appsawg-json-pointer/ballot/</a><br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; No IPR declarations have been submitted direct=
ly on this I-D.<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; ______________________________________________=
_<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; apps-discuss mailing list<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; <a href=3D"mailto:apps-discuss@ietf.org">apps-=
discuss@ietf.org</a><br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; <a href=3D"https://www.ietf.org/mailman/listin=
fo/apps-discuss" target=3D"_blank">https://www.ietf.org/mailman/listinfo/ap=
ps-discuss</a><br>
&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt; _______________________________________________<br=
>
&gt;&gt;&gt;&gt;&gt;&gt; apps-discuss mailing list<br>
&gt;&gt;&gt;&gt;&gt;&gt; <a href=3D"mailto:apps-discuss@ietf.org">apps-disc=
uss@ietf.org</a><br>
&gt;&gt;&gt;&gt;&gt;&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/a=
pps-discuss" target=3D"_blank">https://www.ietf.org/mailman/listinfo/apps-d=
iscuss</a><br>
&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt; _______________________________________________<br=
>
&gt;&gt;&gt;&gt;&gt;&gt; apps-discuss mailing list<br>
&gt;&gt;&gt;&gt;&gt;&gt; <a href=3D"mailto:apps-discuss@ietf.org">apps-disc=
uss@ietf.org</a><br>
&gt;&gt;&gt;&gt;&gt;&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/a=
pps-discuss" target=3D"_blank">https://www.ietf.org/mailman/listinfo/apps-d=
iscuss</a><br>
&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; _______________________________________________<br>
&gt;&gt;&gt;&gt; apps-discuss mailing list<br>
&gt;&gt;&gt;&gt; <a href=3D"mailto:apps-discuss@ietf.org">apps-discuss@ietf=
.org</a><br>
&gt;&gt;&gt;&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/apps-disc=
uss" target=3D"_blank">https://www.ietf.org/mailman/listinfo/apps-discuss</=
a><br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; --<br>
&gt;&gt;&gt; Matthew P. C. Morley<br>
&gt;&gt; _______________________________________________<br>
&gt;&gt; apps-discuss mailing list<br>
&gt;&gt; <a href=3D"mailto:apps-discuss@ietf.org">apps-discuss@ietf.org</a>=
<br>
&gt;&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/apps-discuss" tar=
get=3D"_blank">https://www.ietf.org/mailman/listinfo/apps-discuss</a><br>
&gt;<br>
&gt; --<br>
&gt; Mark Nottingham =C2=A0 <a href=3D"http://www.mnot.net/" target=3D"_bla=
nk">http://www.mnot.net/</a><br>
&gt;<br>
&gt;<br>
&gt;<br>
_______________________________________________<br>
apps-discuss mailing list<br>
<a href=3D"mailto:apps-discuss@ietf.org">apps-discuss@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/apps-discuss" target=3D"_b=
lank">https://www.ietf.org/mailman/listinfo/apps-discuss</a><br>
</div></div></blockquote></div><br></div></div>

--f46d043c7f88b0f73f04d294ab99--

From mnot@mnot.net  Sat Jan  5 17:48:22 2013
Return-Path: <mnot@mnot.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7203D21F8583; Sat,  5 Jan 2013 17:48:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 m7iO9rn1IByk; Sat,  5 Jan 2013 17:48:21 -0800 (PST)
Received: from mxout-08.mxes.net (mxout-08.mxes.net [216.86.168.183]) by ietfa.amsl.com (Postfix) with ESMTP id D9F2A21F8574; Sat,  5 Jan 2013 17:48:20 -0800 (PST)
Received: from [192.168.1.80] (unknown [118.209.230.64]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id 68975509B8; Sat,  5 Jan 2013 20:48:14 -0500 (EST)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Subject: Re: [apps-discuss] Last Call: <draft-ietf-appsawg-json-pointer-07.txt> (JSON Pointer) to Proposed Standard
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <CAChr6Sx7JdKM91EwJaSZ0Ra_F4FSqkuc3vzTY1LM=F_8sWho+Q@mail.gmail.com>
Date: Sun, 6 Jan 2013 12:48:10 +1100
Content-Transfer-Encoding: quoted-printable
Message-Id: <263BA4B0-6401-4391-A369-A90863D9A4BC@mnot.net>
References: <20121211150057.28223.93310.idtracker@ietfa.amsl.com> <50cb04b9.86df440a.72fe.1e20SMTPIN_ADDED_BROKEN@mx.google.com> <CABP7RbeNsZ_rBWRjou=VG+hBhUKaOz+y1a0sSChwWiHte9znnQ@mail.gmail.com> <50cb5f3c.694c420a.38fb.39afSMTPIN_ADDED_BROKEN@mx.google.com> <CAChr6SxZRc3B_HCbw76kLe2dsRSr43r-gLpfMVnCUfJTrZdTLA@mail.gmail.com> <CABP7RbfA33huBFadMeXTTEt=MkjW8-d4DFH7+GLXGurnm9sSRw@mail.gmail.com> <CAOXDeqpPE4eNy_qJpDPdPHbCQakG9-hDcNZ3Sj9r4kWedByVzQ@mail.gmail.com> <CAChr6SwtS_=iS-k4mJm1vHjEvvGVzay5jDYeGheqsPZqO-89CQ@mail.gmail.com> <EABB8F51-C3B4-49F5-8672-5C2ABAC7043A@mnot.net> <CAChr6Sx7JdKM91EwJaSZ0Ra_F4FSqkuc3vzTY1LM=F_8sWho+Q@mail.gmail.com>
To: Robert Sayre <sayrer@gmail.com>
X-Mailer: Apple Mail (2.1499)
Cc: IETF Discussion <ietf@ietf.org>, IETF Apps Discuss <apps-discuss@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 06 Jan 2013 01:48:22 -0000

Robert,

I neither represent the WG (except in as far as I attempt to do so as =
document editor), nor do I judge consensus in the WG (the Chairs do, =
although at this late date, the IESG are making the decisions).

That said, if we were starting this from scratch, I *personally* could =
see adding some syntax to distinguish intent, as I don't see it causing =
any huge amount of harm (besides leading some to believe that JSON =
Pointer is a proto-schema language).=20

However, at this point, doing so really a judgement call; we have =
multiple implementations, and we shouldn't force them to change =
arbitrarily. As far as I can see, you haven't convinced anyone that this =
is a serious enough problem to do so (and I don't appear to be the only =
one to hold that opinion, by any means). Furthermore, it's not clear =
that the use cases you have in mind (since you have brought up JSON =
Sync) are in-scope for these specifications.

Soon, the IESG will make its determination, so you'd likely be much more =
productive by laying out your argument cogently to them, rather than =
focusing on me.

If we were to open up to further changes, I'd like to see us discuss =
things like allowing header modifications in the format, and specifying =
the target's intended media type (which was already discussed and =
rejected in the WG).=20

However, I'm even more interested in getting this format published, in =
the knowledge that HTTP PATCH has been defined for some time, but is =
effectively useless (at least against JSON) without any defined, stable =
patch format. If we find serious deficiencies, nothing stops us, or you, =
or anyone else from defining a new patch format (as James is already =
doing).

Cheers,


On 06/01/2013, at 11:19 AM, Robert Sayre <sayrer@gmail.com> wrote:

> Mark,
>=20
> The WG's reasoning, as stated in your message below, seems flawed.
> Messages since your last communication on this matter have shown:
>=20
> 1) The ambiguity around arrays makes the patch format unsuitable for
> common concurrent editing algorithms.
> 2) The ambiguity is likely to occur in the real world, for a couple of
> different reasons.
> 3) It's not possible to tell whether a JSON Pointer document is
> syntactically correct in isolation.
>=20
> Additionally, you raised this point in your message below:
>>=20
>> the patch author already has to understand the semantics of the =
document they're patching
>=20
> That claim does not seem to be well-justified, and it could be
> meaningless to the person implementing patch software (for example:
> https://github.com/sayrer/json-sync).
>=20
> This issue is a problem in practice, and it's a problem in theory as
> well. JSON-Patch messages aren't sufficiently self-descriptive, so
> they aren't appropriate for use in a RESTful system.
>=20
> A response containing technical reasoning seems in order, since the
> points raised by myself and others on this issue are unrelated to the
> WG's previous thinking.
>=20
> - Rob
>=20
> On Sun, Dec 16, 2012 at 9:41 PM, Mark Nottingham <mnot@mnot.net> =
wrote:
>> Robert,
>>=20
>> This was discussed extensively in the Working Group.
>>=20
>> The root of the issue was that some people reflexively felt that this =
was necessary, but upon reflection, we decided it wasn't; although it =
seems "natural" to some, especially those coming from a static language =
background, it didn't provide any utility.
>>=20
>> You might argue that someone who (for example) adds to "/foo/1" in =
the mistaken belief that it's an array, when in fact it's an object, =
will get surprising results. That's true, but if we were to solve this =
problem, that person would still need to understand the underlying =
semantics of "foo" to do anything useful to it -- and I'm not hearing =
anyone complain about that (I hope).
>>=20
>> Put another way -- do you really think that people PATCHing something =
as if it's an array (when in fact it's an object) is a significant, =
real-world problem, given that the patch author already has to =
understand the semantics of the document they're patching? I don't, and =
the WG didn't either.
>>=20
>> Regards,
>>=20
>>=20
>> On 17/12/2012, at 3:36 PM, Robert Sayre <sayrer@gmail.com> wrote:
>>=20
>>> The cost of fixing it seems low, either by changing the path syntax =
of
>>> JSON pointer or changing the names of operations applied to arrays.
>>> Array-like objects are common enough in JavaScript to make this a
>>> worry. The other suggestions either assume a particular policy for
>>> concurrent edits or require more machinery (test operation etc).
>>> Wouldn't it be simpler to make the patch format more precise?
>>>=20
>>> - Rob
>>>=20
>>> On Sun, Dec 16, 2012 at 4:33 PM, Matthew Morley <matt@mpcm.com> =
wrote:
>>>> I am usually lurking and struggling to keep up with these posts. =
But, I
>>>> concur with James, this really is a non-issue in practice.
>>>>=20
>>>> The JSON Pointer expresses a path down a JSON object to a specific =
context.
>>>> The Patch expresses a change within or to that context.
>>>> Everything about the both standards is about that end context.
>>>>=20
>>>> If you want to confirm the type of the context before applying a =
patch, this
>>>> should probably be part of a test operation. I'm not sure if this =
is
>>>> possible at this point (?), but that is where the logic should =
exist.
>>>>=20
>>>>=20
>>>>=20
>>>> On Sun, Dec 16, 2012 at 12:22 AM, James M Snell <jasnell@gmail.com> =
wrote:
>>>>>=20
>>>>>=20
>>>>>=20
>>>>>=20
>>>>> On Sat, Dec 15, 2012 at 8:36 PM, Robert Sayre <sayrer@gmail.com> =
wrote:
>>>>>>=20
>>>>>> On Fri, Dec 14, 2012 at 9:17 AM, Markus Lanthaler
>>>>>> <markus.lanthaler@gmx.net> wrote:
>>>>>>>=20
>>>>>>> Hmm.. I think that=92s quite problematic. Especially considering =
how JSON
>>>>>>> Pointer is used in JSON Patch.
>>>>>>=20
>>>>>> I agree--I provided the same feedback privately. It seems
>>>>>> straightforwardly unsound.
>>>>>>=20
>>>>>=20
>>>>> In practice it doesn't seem to be much of an issue.
>>>>>=20
>>>>> Specifically, if I GET an existing document and get an etag with =
the JSON,
>>>>> then make some changes and send a PATCH with If-Match, the fact =
that any
>>>>> given pointer could point to an array or object member doesn't =
really matter
>>>>> much.
>>>>>=20
>>>>> For example:
>>>>>=20
>>>>>> GET /the/doc HTTP/1.1
>>>>>=20
>>>>> <  HTTP/1.1 200 OK
>>>>>    ETag: "my-document-tag"
>>>>>    Content-Type: application/json
>>>>>=20
>>>>>    {"1":"foo"}
>>>>>=20
>>>>>> PATCH /the/doc HTTP/1.1
>>>>>    If-Match: "my-document-etag"
>>>>>    Content-Type: application/json-patch
>>>>>=20
>>>>>    [{"op":"add","path":"/2","value":"bar"}]
>>>>>=20
>>>>> Generally speaking, someone should not be using PATCH to perform a =
partial
>>>>> modification if they don't already have some knowledge in advance =
what they
>>>>> are modifying. The only time the apparent ambiguity becomes an =
issue is when
>>>>> a client is blindly sending a patch to an unknown endpoint... in =
which case,
>>>>> you get whatever you end up with.
>>>>>=20
>>>>> - James
>>>>>=20
>>>>>=20
>>>>>>=20
>>>>>> - Rob
>>>>>>=20
>>>>>>=20
>>>>>>>=20
>>>>>>> --
>>>>>>>=20
>>>>>>> Markus Lanthaler
>>>>>>>=20
>>>>>>> @markuslanthaler
>>>>>>>=20
>>>>>>>=20
>>>>>>>=20
>>>>>>>=20
>>>>>>>=20
>>>>>>>=20
>>>>>>>=20
>>>>>>> From: James M Snell [mailto:jasnell@gmail.com]
>>>>>>> Sent: Friday, December 14, 2012 5:41 PM
>>>>>>> To: Markus Lanthaler
>>>>>>> Cc: IETF Discussion; IETF Apps Discuss
>>>>>>> Subject: Re: [apps-discuss] Last Call:
>>>>>>> <draft-ietf-appsawg-json-pointer-07.txt> (JSON Pointer) to =
Proposed Standard
>>>>>>>=20
>>>>>>>=20
>>>>>>>=20
>>>>>>> JSON Pointer does not distinguish between objects and arrays. =
That is
>>>>>>> not determined until the pointer is applied to an actual object =
instance...
>>>>>>> the pointer "/1" is valid against {"1":"a"} or ["a","b"]
>>>>>>>=20
>>>>>>>=20
>>>>>>>=20
>>>>>>> On Fri, Dec 14, 2012 at 2:51 AM, Markus Lanthaler
>>>>>>> <markus.lanthaler@gmx.net> wrote:
>>>>>>>=20
>>>>>>> I've asked that before but didn't get an answer. So let me ask =
again
>>>>>>> (even
>>>>>>> though I'm quite sure it has already been asked by somebody =
else).
>>>>>>>=20
>>>>>>> How does JSON Pointer distinguish between objects and arrays? =
E.g.
>>>>>>> consider
>>>>>>> the following JSON document:
>>>>>>>=20
>>>>>>> {
>>>>>>> "foo": "bar",
>>>>>>> "1": "baz"
>>>>>>> }
>>>>>>>=20
>>>>>>> As I read the draft, the JSON Pointer "/1" would evaluate to =
"baz" even
>>>>>>> though that's probably not what the author intended. Is there a =
way to
>>>>>>> avoid
>>>>>>> that?
>>>>>>>=20
>>>>>>>=20
>>>>>>> Thanks,
>>>>>>> Markus
>>>>>>>=20
>>>>>>>=20
>>>>>>>=20
>>>>>>> --
>>>>>>> Markus Lanthaler
>>>>>>> @markuslanthaler
>>>>>>>=20
>>>>>>>=20
>>>>>>>=20
>>>>>>>=20
>>>>>>>=20
>>>>>>>> -----Original Message-----
>>>>>>>> From: apps-discuss-bounces@ietf.org [mailto:apps-discuss-
>>>>>>>> bounces@ietf.org] On Behalf Of The IESG
>>>>>>>> Sent: Tuesday, December 11, 2012 4:01 PM
>>>>>>>> To: IETF-Announce
>>>>>>>> Cc: apps-discuss@ietf.org
>>>>>>>> Subject: [apps-discuss] Last Call: =
<draft-ietf-appsawg-json-pointer-
>>>>>>>> 07.txt> (JSON Pointer) to Proposed Standard
>>>>>>>>=20
>>>>>>>>=20
>>>>>>>> The IESG has received a request from the Applications Area =
Working
>>>>>>>> Group
>>>>>>>> WG (appsawg) to consider the following document:
>>>>>>>> - 'JSON Pointer'
>>>>>>>> <draft-ietf-appsawg-json-pointer-07.txt> as Proposed Standard
>>>>>>>>=20
>>>>>>>> The IESG plans to make a decision in the next few weeks, and =
solicits
>>>>>>>> final comments on this action. Please send substantive comments =
to
>>>>>>>> the
>>>>>>>> ietf@ietf.org mailing lists by 2012-12-25. Exceptionally, =
comments
>>>>>>>> may
>>>>>>>> be
>>>>>>>> sent to iesg@ietf.org instead. In either case, please retain =
the
>>>>>>>> beginning of the Subject line to allow automated sorting.
>>>>>>>>=20
>>>>>>>> Abstract
>>>>>>>>=20
>>>>>>>>=20
>>>>>>>>  JSON Pointer defines a string syntax for identifying a =
specific
>>>>>>>> value
>>>>>>>>  within a JSON document.
>>>>>>>>=20
>>>>>>>>=20
>>>>>>>>=20
>>>>>>>>=20
>>>>>>>> The file can be obtained via
>>>>>>>> =
http://datatracker.ietf.org/doc/draft-ietf-appsawg-json-pointer/
>>>>>>>>=20
>>>>>>>> IESG discussion can be tracked via
>>>>>>>>=20
>>>>>>>> =
http://datatracker.ietf.org/doc/draft-ietf-appsawg-json-pointer/ballot/
>>>>>>>>=20
>>>>>>>>=20
>>>>>>>> No IPR declarations have been submitted directly on this I-D.
>>>>>>>>=20
>>>>>>>>=20
>>>>>>>> _______________________________________________
>>>>>>>> apps-discuss mailing list
>>>>>>>> apps-discuss@ietf.org
>>>>>>>> https://www.ietf.org/mailman/listinfo/apps-discuss
>>>>>>>=20
>>>>>>> _______________________________________________
>>>>>>> apps-discuss mailing list
>>>>>>> apps-discuss@ietf.org
>>>>>>> https://www.ietf.org/mailman/listinfo/apps-discuss
>>>>>>>=20
>>>>>>>=20
>>>>>>>=20
>>>>>>>=20
>>>>>>> _______________________________________________
>>>>>>> apps-discuss mailing list
>>>>>>> apps-discuss@ietf.org
>>>>>>> https://www.ietf.org/mailman/listinfo/apps-discuss
>>>>>>>=20
>>>>>=20
>>>>>=20
>>>>>=20
>>>>> _______________________________________________
>>>>> apps-discuss mailing list
>>>>> apps-discuss@ietf.org
>>>>> https://www.ietf.org/mailman/listinfo/apps-discuss
>>>>>=20
>>>>=20
>>>>=20
>>>>=20
>>>> --
>>>> Matthew P. C. Morley
>>> _______________________________________________
>>> apps-discuss mailing list
>>> apps-discuss@ietf.org
>>> https://www.ietf.org/mailman/listinfo/apps-discuss
>>=20
>> --
>> Mark Nottingham   http://www.mnot.net/
>>=20
>>=20
>>=20

--
Mark Nottingham   http://www.mnot.net/




From sayrer@gmail.com  Sat Jan  5 18:29:50 2013
Return-Path: <sayrer@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BCC8E21F852C; Sat,  5 Jan 2013 18:29:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 xnEZwV6-vVSf; Sat,  5 Jan 2013 18:29:49 -0800 (PST)
Received: from mail-wg0-f54.google.com (mail-wg0-f54.google.com [74.125.82.54]) by ietfa.amsl.com (Postfix) with ESMTP id 10AC721F8526; Sat,  5 Jan 2013 18:29:48 -0800 (PST)
Received: by mail-wg0-f54.google.com with SMTP id fg15so8393529wgb.21 for <multiple recipients>; Sat, 05 Jan 2013 18:29:48 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=iSxaa8cOyR01s6YTFdOlGc89BTjz+V+x23RWLU92LaQ=; b=wBQqPY7n8fwiJDbk+nleXsOAAHDydLYeD5ejwoV3iax7N1vUUaBPKiQlCOcxsIKbA1 HCY/tPaYY505T6bRDKufdyERMK9j3hizcC8WYl/0FBvL6g/OTdgw++uoo7+gxlZKphrQ 59T5gGEW+m8lAzECBQIolzp3jce7OFjWcvpPqiLM9ZKiV0nPj0z7mXwbSAi/Vygm9+Qy mgjLG+XP3K7ADd6T0WwdHY+B22h/Nu2dImt3NF1xD48RSoz5hug12GBmOqa4cd+1C2Gm 9XHVtG67eTlEi86xJvE5ZCcv7aFAOZ20IFi0wOz0L/3O1PGqcIkvGcAKRuaiMfG00Dfl ABTQ==
MIME-Version: 1.0
Received: by 10.194.78.162 with SMTP id c2mr89570783wjx.46.1357439388168; Sat, 05 Jan 2013 18:29:48 -0800 (PST)
Received: by 10.194.1.101 with HTTP; Sat, 5 Jan 2013 18:29:48 -0800 (PST)
In-Reply-To: <263BA4B0-6401-4391-A369-A90863D9A4BC@mnot.net>
References: <20121211150057.28223.93310.idtracker@ietfa.amsl.com> <50cb04b9.86df440a.72fe.1e20SMTPIN_ADDED_BROKEN@mx.google.com> <CABP7RbeNsZ_rBWRjou=VG+hBhUKaOz+y1a0sSChwWiHte9znnQ@mail.gmail.com> <50cb5f3c.694c420a.38fb.39afSMTPIN_ADDED_BROKEN@mx.google.com> <CAChr6SxZRc3B_HCbw76kLe2dsRSr43r-gLpfMVnCUfJTrZdTLA@mail.gmail.com> <CABP7RbfA33huBFadMeXTTEt=MkjW8-d4DFH7+GLXGurnm9sSRw@mail.gmail.com> <CAOXDeqpPE4eNy_qJpDPdPHbCQakG9-hDcNZ3Sj9r4kWedByVzQ@mail.gmail.com> <CAChr6SwtS_=iS-k4mJm1vHjEvvGVzay5jDYeGheqsPZqO-89CQ@mail.gmail.com> <EABB8F51-C3B4-49F5-8672-5C2ABAC7043A@mnot.net> <CAChr6Sx7JdKM91EwJaSZ0Ra_F4FSqkuc3vzTY1LM=F_8sWho+Q@mail.gmail.com> <263BA4B0-6401-4391-A369-A90863D9A4BC@mnot.net>
Date: Sat, 5 Jan 2013 18:29:48 -0800
Message-ID: <CAChr6Sw-hZwzB423qvkqyGfq8Aw6Jry-=B9zSzgp2GwbX6gQQg@mail.gmail.com>
Subject: Re: [apps-discuss] Last Call: <draft-ietf-appsawg-json-pointer-07.txt> (JSON Pointer) to Proposed Standard
From: Robert Sayre <sayrer@gmail.com>
To: Mark Nottingham <mnot@mnot.net>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable
Cc: IETF Discussion <ietf@ietf.org>, IETF Apps Discuss <apps-discuss@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 06 Jan 2013 02:29:50 -0000

On Sat, Jan 5, 2013 at 5:48 PM, Mark Nottingham <mnot@mnot.net> wrote:
>
> However, at this point, doing so really a judgement call; we have multipl=
e implementations, and we shouldn't
> force them to change arbitrarily.

The word "arbitrarily" seems inappropriate here. I raised at least
four technical issues and your message addresses none of them.

> As far as I can see, you haven't convinced anyone that this is a serious =
enough problem to do so (and I don't
> appear to be the only one to hold that opinion, by any means).

Did you read this thread? Markus Lanthaler and Conal Tuohy raised
similar points.

> Furthermore, it's not clear that the use cases you have in mind (since yo=
u have brought up JSON Sync)
> are in-scope for these specifications.

That assertion is both unsubstantiated and incorrect. json-sync has
identical primitive operations to JSON Patch (create/edit/remove vs
add/replace/remove). The JSON Patch document defines Copy and Move in
terms of the add/replace, so those are mostly syntactic sugar. The
only meaningful delta is the "test" operation, and I do plan to add
that to json-sync, since it's a good way to make application-specific
assertions.

> However, I'm even more interested in getting this format published,

Well, I guess someone has something they want to ship...

- Rob

> Cheers,
>
>
> On 06/01/2013, at 11:19 AM, Robert Sayre <sayrer@gmail.com> wrote:
>
>> Mark,
>>
>> The WG's reasoning, as stated in your message below, seems flawed.
>> Messages since your last communication on this matter have shown:
>>
>> 1) The ambiguity around arrays makes the patch format unsuitable for
>> common concurrent editing algorithms.
>> 2) The ambiguity is likely to occur in the real world, for a couple of
>> different reasons.
>> 3) It's not possible to tell whether a JSON Pointer document is
>> syntactically correct in isolation.
>>
>> Additionally, you raised this point in your message below:
>>>
>>> the patch author already has to understand the semantics of the documen=
t they're patching
>>
>> That claim does not seem to be well-justified, and it could be
>> meaningless to the person implementing patch software (for example:
>> https://github.com/sayrer/json-sync).
>>
>> This issue is a problem in practice, and it's a problem in theory as
>> well. JSON-Patch messages aren't sufficiently self-descriptive, so
>> they aren't appropriate for use in a RESTful system.
>>
>> A response containing technical reasoning seems in order, since the
>> points raised by myself and others on this issue are unrelated to the
>> WG's previous thinking.
>>
>> - Rob
>>
>> On Sun, Dec 16, 2012 at 9:41 PM, Mark Nottingham <mnot@mnot.net> wrote:
>>> Robert,
>>>
>>> This was discussed extensively in the Working Group.
>>>
>>> The root of the issue was that some people reflexively felt that this w=
as necessary, but upon reflection, we decided it wasn't; although it seems =
"natural" to some, especially those coming from a static language backgroun=
d, it didn't provide any utility.
>>>
>>> You might argue that someone who (for example) adds to "/foo/1" in the =
mistaken belief that it's an array, when in fact it's an object, will get s=
urprising results. That's true, but if we were to solve this problem, that =
person would still need to understand the underlying semantics of "foo" to =
do anything useful to it -- and I'm not hearing anyone complain about that =
(I hope).
>>>
>>> Put another way -- do you really think that people PATCHing something a=
s if it's an array (when in fact it's an object) is a significant, real-wor=
ld problem, given that the patch author already has to understand the seman=
tics of the document they're patching? I don't, and the WG didn't either.
>>>
>>> Regards,
>>>
>>>
>>> On 17/12/2012, at 3:36 PM, Robert Sayre <sayrer@gmail.com> wrote:
>>>
>>>> The cost of fixing it seems low, either by changing the path syntax of
>>>> JSON pointer or changing the names of operations applied to arrays.
>>>> Array-like objects are common enough in JavaScript to make this a
>>>> worry. The other suggestions either assume a particular policy for
>>>> concurrent edits or require more machinery (test operation etc).
>>>> Wouldn't it be simpler to make the patch format more precise?
>>>>
>>>> - Rob
>>>>
>>>> On Sun, Dec 16, 2012 at 4:33 PM, Matthew Morley <matt@mpcm.com> wrote:
>>>>> I am usually lurking and struggling to keep up with these posts. But,=
 I
>>>>> concur with James, this really is a non-issue in practice.
>>>>>
>>>>> The JSON Pointer expresses a path down a JSON object to a specific co=
ntext.
>>>>> The Patch expresses a change within or to that context.
>>>>> Everything about the both standards is about that end context.
>>>>>
>>>>> If you want to confirm the type of the context before applying a patc=
h, this
>>>>> should probably be part of a test operation. I'm not sure if this is
>>>>> possible at this point (?), but that is where the logic should exist.
>>>>>
>>>>>
>>>>>
>>>>> On Sun, Dec 16, 2012 at 12:22 AM, James M Snell <jasnell@gmail.com> w=
rote:
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Sat, Dec 15, 2012 at 8:36 PM, Robert Sayre <sayrer@gmail.com> wro=
te:
>>>>>>>
>>>>>>> On Fri, Dec 14, 2012 at 9:17 AM, Markus Lanthaler
>>>>>>> <markus.lanthaler@gmx.net> wrote:
>>>>>>>>
>>>>>>>> Hmm.. I think that=92s quite problematic. Especially considering h=
ow JSON
>>>>>>>> Pointer is used in JSON Patch.
>>>>>>>
>>>>>>> I agree--I provided the same feedback privately. It seems
>>>>>>> straightforwardly unsound.
>>>>>>>
>>>>>>
>>>>>> In practice it doesn't seem to be much of an issue.
>>>>>>
>>>>>> Specifically, if I GET an existing document and get an etag with the=
 JSON,
>>>>>> then make some changes and send a PATCH with If-Match, the fact that=
 any
>>>>>> given pointer could point to an array or object member doesn't reall=
y matter
>>>>>> much.
>>>>>>
>>>>>> For example:
>>>>>>
>>>>>>> GET /the/doc HTTP/1.1
>>>>>>
>>>>>> <  HTTP/1.1 200 OK
>>>>>>    ETag: "my-document-tag"
>>>>>>    Content-Type: application/json
>>>>>>
>>>>>>    {"1":"foo"}
>>>>>>
>>>>>>> PATCH /the/doc HTTP/1.1
>>>>>>    If-Match: "my-document-etag"
>>>>>>    Content-Type: application/json-patch
>>>>>>
>>>>>>    [{"op":"add","path":"/2","value":"bar"}]
>>>>>>
>>>>>> Generally speaking, someone should not be using PATCH to perform a p=
artial
>>>>>> modification if they don't already have some knowledge in advance wh=
at they
>>>>>> are modifying. The only time the apparent ambiguity becomes an issue=
 is when
>>>>>> a client is blindly sending a patch to an unknown endpoint... in whi=
ch case,
>>>>>> you get whatever you end up with.
>>>>>>
>>>>>> - James
>>>>>>
>>>>>>
>>>>>>>
>>>>>>> - Rob
>>>>>>>
>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>>
>>>>>>>> Markus Lanthaler
>>>>>>>>
>>>>>>>> @markuslanthaler
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> From: James M Snell [mailto:jasnell@gmail.com]
>>>>>>>> Sent: Friday, December 14, 2012 5:41 PM
>>>>>>>> To: Markus Lanthaler
>>>>>>>> Cc: IETF Discussion; IETF Apps Discuss
>>>>>>>> Subject: Re: [apps-discuss] Last Call:
>>>>>>>> <draft-ietf-appsawg-json-pointer-07.txt> (JSON Pointer) to Propose=
d Standard
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> JSON Pointer does not distinguish between objects and arrays. That=
 is
>>>>>>>> not determined until the pointer is applied to an actual object in=
stance...
>>>>>>>> the pointer "/1" is valid against {"1":"a"} or ["a","b"]
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> On Fri, Dec 14, 2012 at 2:51 AM, Markus Lanthaler
>>>>>>>> <markus.lanthaler@gmx.net> wrote:
>>>>>>>>
>>>>>>>> I've asked that before but didn't get an answer. So let me ask aga=
in
>>>>>>>> (even
>>>>>>>> though I'm quite sure it has already been asked by somebody else).
>>>>>>>>
>>>>>>>> How does JSON Pointer distinguish between objects and arrays? E.g.
>>>>>>>> consider
>>>>>>>> the following JSON document:
>>>>>>>>
>>>>>>>> {
>>>>>>>> "foo": "bar",
>>>>>>>> "1": "baz"
>>>>>>>> }
>>>>>>>>
>>>>>>>> As I read the draft, the JSON Pointer "/1" would evaluate to "baz"=
 even
>>>>>>>> though that's probably not what the author intended. Is there a wa=
y to
>>>>>>>> avoid
>>>>>>>> that?
>>>>>>>>
>>>>>>>>
>>>>>>>> Thanks,
>>>>>>>> Markus
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> Markus Lanthaler
>>>>>>>> @markuslanthaler
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>> -----Original Message-----
>>>>>>>>> From: apps-discuss-bounces@ietf.org [mailto:apps-discuss-
>>>>>>>>> bounces@ietf.org] On Behalf Of The IESG
>>>>>>>>> Sent: Tuesday, December 11, 2012 4:01 PM
>>>>>>>>> To: IETF-Announce
>>>>>>>>> Cc: apps-discuss@ietf.org
>>>>>>>>> Subject: [apps-discuss] Last Call: <draft-ietf-appsawg-json-point=
er-
>>>>>>>>> 07.txt> (JSON Pointer) to Proposed Standard
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> The IESG has received a request from the Applications Area Workin=
g
>>>>>>>>> Group
>>>>>>>>> WG (appsawg) to consider the following document:
>>>>>>>>> - 'JSON Pointer'
>>>>>>>>> <draft-ietf-appsawg-json-pointer-07.txt> as Proposed Standard
>>>>>>>>>
>>>>>>>>> The IESG plans to make a decision in the next few weeks, and soli=
cits
>>>>>>>>> final comments on this action. Please send substantive comments t=
o
>>>>>>>>> the
>>>>>>>>> ietf@ietf.org mailing lists by 2012-12-25. Exceptionally, comment=
s
>>>>>>>>> may
>>>>>>>>> be
>>>>>>>>> sent to iesg@ietf.org instead. In either case, please retain the
>>>>>>>>> beginning of the Subject line to allow automated sorting.
>>>>>>>>>
>>>>>>>>> Abstract
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>  JSON Pointer defines a string syntax for identifying a specific
>>>>>>>>> value
>>>>>>>>>  within a JSON document.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> The file can be obtained via
>>>>>>>>> http://datatracker.ietf.org/doc/draft-ietf-appsawg-json-pointer/
>>>>>>>>>
>>>>>>>>> IESG discussion can be tracked via
>>>>>>>>>
>>>>>>>>> http://datatracker.ietf.org/doc/draft-ietf-appsawg-json-pointer/b=
allot/
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> No IPR declarations have been submitted directly on this I-D.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> _______________________________________________
>>>>>>>>> apps-discuss mailing list
>>>>>>>>> apps-discuss@ietf.org
>>>>>>>>> https://www.ietf.org/mailman/listinfo/apps-discuss
>>>>>>>>
>>>>>>>> _______________________________________________
>>>>>>>> apps-discuss mailing list
>>>>>>>> apps-discuss@ietf.org
>>>>>>>> https://www.ietf.org/mailman/listinfo/apps-discuss
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> _______________________________________________
>>>>>>>> apps-discuss mailing list
>>>>>>>> apps-discuss@ietf.org
>>>>>>>> https://www.ietf.org/mailman/listinfo/apps-discuss
>>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> apps-discuss mailing list
>>>>>> apps-discuss@ietf.org
>>>>>> https://www.ietf.org/mailman/listinfo/apps-discuss
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Matthew P. C. Morley
>>>> _______________________________________________
>>>> apps-discuss mailing list
>>>> apps-discuss@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/apps-discuss
>>>
>>> --
>>> Mark Nottingham   http://www.mnot.net/
>>>
>>>
>>>
>
> --
> Mark Nottingham   http://www.mnot.net/
>
>
>

From mnot@mnot.net  Sat Jan  5 18:59:56 2013
Return-Path: <mnot@mnot.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 496ED21F87C3; Sat,  5 Jan 2013 18:59:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 UF40DjJXo7PK; Sat,  5 Jan 2013 18:59:55 -0800 (PST)
Received: from mxout-08.mxes.net (mxout-08.mxes.net [216.86.168.183]) by ietfa.amsl.com (Postfix) with ESMTP id A636D21F8717; Sat,  5 Jan 2013 18:59:54 -0800 (PST)
Received: from [192.168.1.80] (unknown [118.209.230.64]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id 5CB29509B8; Sat,  5 Jan 2013 21:59:51 -0500 (EST)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Subject: Re: [apps-discuss] Last Call: <draft-ietf-appsawg-json-pointer-07.txt> (JSON Pointer) to Proposed Standard
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <CAChr6Sw-hZwzB423qvkqyGfq8Aw6Jry-=B9zSzgp2GwbX6gQQg@mail.gmail.com>
Date: Sun, 6 Jan 2013 13:59:46 +1100
Content-Transfer-Encoding: quoted-printable
Message-Id: <E17FB936-BB87-4711-BEFB-21714B746B71@mnot.net>
References: <20121211150057.28223.93310.idtracker@ietfa.amsl.com> <50cb04b9.86df440a.72fe.1e20SMTPIN_ADDED_BROKEN@mx.google.com> <CABP7RbeNsZ_rBWRjou=VG+hBhUKaOz+y1a0sSChwWiHte9znnQ@mail.gmail.com> <50cb5f3c.694c420a.38fb.39afSMTPIN_ADDED_BROKEN@mx.google.com> <CAChr6SxZRc3B_HCbw76kLe2dsRSr43r-gLpfMVnCUfJTrZdTLA@mail.gmail.com> <CABP7RbfA33huBFadMeXTTEt=MkjW8-d4DFH7+GLXGurnm9sSRw@mail.gmail.com> <CAOXDeqpPE4eNy_qJpDPdPHbCQakG9-hDcNZ3Sj9r4kWedByVzQ@mail.gmail.com> <CAChr6SwtS_=iS-k4mJm1vHjEvvGVzay5jDYeGheqsPZqO-89CQ@mail.gmail.com> <EABB8F51-C3B4-49F5-8672-5C2ABAC7043A@mnot.net> <CAChr6Sx7JdKM91EwJaSZ0Ra_F4FSqkuc3vzTY1LM=F_8sWho+Q@mail.gmail.com> <263BA4B0-6401-4391-A369-A90863D9A4BC@mnot.net> <CAChr6Sw-hZwzB423qvkqyGfq8Aw6Jry-=B9zSzgp2GwbX6gQQg@mail.gmail.com>
To: Robert Sayre <sayrer@gmail.com>
X-Mailer: Apple Mail (2.1499)
Cc: IETF Discussion <ietf@ietf.org>, IETF Apps Discuss <apps-discuss@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 06 Jan 2013 02:59:56 -0000

On 06/01/2013, at 1:29 PM, Robert Sayre <sayrer@gmail.com> wrote:

> On Sat, Jan 5, 2013 at 5:48 PM, Mark Nottingham <mnot@mnot.net> wrote:
>>=20
>> However, at this point, doing so really a judgement call; we have =
multiple implementations, and we shouldn't
>> force them to change arbitrarily.
>=20
> The word "arbitrarily" seems inappropriate here. I raised at least
> four technical issues and your message addresses none of them.

... and I explained why.=20


>> As far as I can see, you haven't convinced anyone that this is a =
serious enough problem to do so (and I don't
>> appear to be the only one to hold that opinion, by any means).
>=20
> Did you read this thread? Markus Lanthaler and Conal Tuohy raised
> similar points.

Yes.=20


>> Furthermore, it's not clear that the use cases you have in mind =
(since you have brought up JSON Sync)
>> are in-scope for these specifications.
>=20
> That assertion is both unsubstantiated and incorrect. json-sync has
> identical primitive operations to JSON Patch (create/edit/remove vs
> add/replace/remove). The JSON Patch document defines Copy and Move in
> terms of the add/replace, so those are mostly syntactic sugar. The
> only meaningful delta is the "test" operation, and I do plan to add
> that to json-sync, since it's a good way to make application-specific
> assertions.

Yes, you've brought that to our attention several times. If you wanted =
this spec to align with your software, it would have been much easier if =
you'd got involved before Last Call.


>> However, I'm even more interested in getting this format published,
>=20
> Well, I guess someone has something they want to ship...

Right. I'll let that statement stand on its own; I think anyone who's =
been participating or watching the WG can assess how justified it is.

Always a pleasure, Rob.


>=20
> - Rob
>=20
>> Cheers,
>>=20
>>=20
>> On 06/01/2013, at 11:19 AM, Robert Sayre <sayrer@gmail.com> wrote:
>>=20
>>> Mark,
>>>=20
>>> The WG's reasoning, as stated in your message below, seems flawed.
>>> Messages since your last communication on this matter have shown:
>>>=20
>>> 1) The ambiguity around arrays makes the patch format unsuitable for
>>> common concurrent editing algorithms.
>>> 2) The ambiguity is likely to occur in the real world, for a couple =
of
>>> different reasons.
>>> 3) It's not possible to tell whether a JSON Pointer document is
>>> syntactically correct in isolation.
>>>=20
>>> Additionally, you raised this point in your message below:
>>>>=20
>>>> the patch author already has to understand the semantics of the =
document they're patching
>>>=20
>>> That claim does not seem to be well-justified, and it could be
>>> meaningless to the person implementing patch software (for example:
>>> https://github.com/sayrer/json-sync).
>>>=20
>>> This issue is a problem in practice, and it's a problem in theory as
>>> well. JSON-Patch messages aren't sufficiently self-descriptive, so
>>> they aren't appropriate for use in a RESTful system.
>>>=20
>>> A response containing technical reasoning seems in order, since the
>>> points raised by myself and others on this issue are unrelated to =
the
>>> WG's previous thinking.
>>>=20
>>> - Rob
>>>=20
>>> On Sun, Dec 16, 2012 at 9:41 PM, Mark Nottingham <mnot@mnot.net> =
wrote:
>>>> Robert,
>>>>=20
>>>> This was discussed extensively in the Working Group.
>>>>=20
>>>> The root of the issue was that some people reflexively felt that =
this was necessary, but upon reflection, we decided it wasn't; although =
it seems "natural" to some, especially those coming from a static =
language background, it didn't provide any utility.
>>>>=20
>>>> You might argue that someone who (for example) adds to "/foo/1" in =
the mistaken belief that it's an array, when in fact it's an object, =
will get surprising results. That's true, but if we were to solve this =
problem, that person would still need to understand the underlying =
semantics of "foo" to do anything useful to it -- and I'm not hearing =
anyone complain about that (I hope).
>>>>=20
>>>> Put another way -- do you really think that people PATCHing =
something as if it's an array (when in fact it's an object) is a =
significant, real-world problem, given that the patch author already has =
to understand the semantics of the document they're patching? I don't, =
and the WG didn't either.
>>>>=20
>>>> Regards,
>>>>=20
>>>>=20
>>>> On 17/12/2012, at 3:36 PM, Robert Sayre <sayrer@gmail.com> wrote:
>>>>=20
>>>>> The cost of fixing it seems low, either by changing the path =
syntax of
>>>>> JSON pointer or changing the names of operations applied to =
arrays.
>>>>> Array-like objects are common enough in JavaScript to make this a
>>>>> worry. The other suggestions either assume a particular policy for
>>>>> concurrent edits or require more machinery (test operation etc).
>>>>> Wouldn't it be simpler to make the patch format more precise?
>>>>>=20
>>>>> - Rob
>>>>>=20
>>>>> On Sun, Dec 16, 2012 at 4:33 PM, Matthew Morley <matt@mpcm.com> =
wrote:
>>>>>> I am usually lurking and struggling to keep up with these posts. =
But, I
>>>>>> concur with James, this really is a non-issue in practice.
>>>>>>=20
>>>>>> The JSON Pointer expresses a path down a JSON object to a =
specific context.
>>>>>> The Patch expresses a change within or to that context.
>>>>>> Everything about the both standards is about that end context.
>>>>>>=20
>>>>>> If you want to confirm the type of the context before applying a =
patch, this
>>>>>> should probably be part of a test operation. I'm not sure if this =
is
>>>>>> possible at this point (?), but that is where the logic should =
exist.
>>>>>>=20
>>>>>>=20
>>>>>>=20
>>>>>> On Sun, Dec 16, 2012 at 12:22 AM, James M Snell =
<jasnell@gmail.com> wrote:
>>>>>>>=20
>>>>>>>=20
>>>>>>>=20
>>>>>>>=20
>>>>>>> On Sat, Dec 15, 2012 at 8:36 PM, Robert Sayre <sayrer@gmail.com> =
wrote:
>>>>>>>>=20
>>>>>>>> On Fri, Dec 14, 2012 at 9:17 AM, Markus Lanthaler
>>>>>>>> <markus.lanthaler@gmx.net> wrote:
>>>>>>>>>=20
>>>>>>>>> Hmm.. I think that=92s quite problematic. Especially =
considering how JSON
>>>>>>>>> Pointer is used in JSON Patch.
>>>>>>>>=20
>>>>>>>> I agree--I provided the same feedback privately. It seems
>>>>>>>> straightforwardly unsound.
>>>>>>>>=20
>>>>>>>=20
>>>>>>> In practice it doesn't seem to be much of an issue.
>>>>>>>=20
>>>>>>> Specifically, if I GET an existing document and get an etag with =
the JSON,
>>>>>>> then make some changes and send a PATCH with If-Match, the fact =
that any
>>>>>>> given pointer could point to an array or object member doesn't =
really matter
>>>>>>> much.
>>>>>>>=20
>>>>>>> For example:
>>>>>>>=20
>>>>>>>> GET /the/doc HTTP/1.1
>>>>>>>=20
>>>>>>> <  HTTP/1.1 200 OK
>>>>>>>   ETag: "my-document-tag"
>>>>>>>   Content-Type: application/json
>>>>>>>=20
>>>>>>>   {"1":"foo"}
>>>>>>>=20
>>>>>>>> PATCH /the/doc HTTP/1.1
>>>>>>>   If-Match: "my-document-etag"
>>>>>>>   Content-Type: application/json-patch
>>>>>>>=20
>>>>>>>   [{"op":"add","path":"/2","value":"bar"}]
>>>>>>>=20
>>>>>>> Generally speaking, someone should not be using PATCH to perform =
a partial
>>>>>>> modification if they don't already have some knowledge in =
advance what they
>>>>>>> are modifying. The only time the apparent ambiguity becomes an =
issue is when
>>>>>>> a client is blindly sending a patch to an unknown endpoint... in =
which case,
>>>>>>> you get whatever you end up with.
>>>>>>>=20
>>>>>>> - James
>>>>>>>=20
>>>>>>>=20
>>>>>>>>=20
>>>>>>>> - Rob
>>>>>>>>=20
>>>>>>>>=20
>>>>>>>>>=20
>>>>>>>>> --
>>>>>>>>>=20
>>>>>>>>> Markus Lanthaler
>>>>>>>>>=20
>>>>>>>>> @markuslanthaler
>>>>>>>>>=20
>>>>>>>>>=20
>>>>>>>>>=20
>>>>>>>>>=20
>>>>>>>>>=20
>>>>>>>>>=20
>>>>>>>>>=20
>>>>>>>>> From: James M Snell [mailto:jasnell@gmail.com]
>>>>>>>>> Sent: Friday, December 14, 2012 5:41 PM
>>>>>>>>> To: Markus Lanthaler
>>>>>>>>> Cc: IETF Discussion; IETF Apps Discuss
>>>>>>>>> Subject: Re: [apps-discuss] Last Call:
>>>>>>>>> <draft-ietf-appsawg-json-pointer-07.txt> (JSON Pointer) to =
Proposed Standard
>>>>>>>>>=20
>>>>>>>>>=20
>>>>>>>>>=20
>>>>>>>>> JSON Pointer does not distinguish between objects and arrays. =
That is
>>>>>>>>> not determined until the pointer is applied to an actual =
object instance...
>>>>>>>>> the pointer "/1" is valid against {"1":"a"} or ["a","b"]
>>>>>>>>>=20
>>>>>>>>>=20
>>>>>>>>>=20
>>>>>>>>> On Fri, Dec 14, 2012 at 2:51 AM, Markus Lanthaler
>>>>>>>>> <markus.lanthaler@gmx.net> wrote:
>>>>>>>>>=20
>>>>>>>>> I've asked that before but didn't get an answer. So let me ask =
again
>>>>>>>>> (even
>>>>>>>>> though I'm quite sure it has already been asked by somebody =
else).
>>>>>>>>>=20
>>>>>>>>> How does JSON Pointer distinguish between objects and arrays? =
E.g.
>>>>>>>>> consider
>>>>>>>>> the following JSON document:
>>>>>>>>>=20
>>>>>>>>> {
>>>>>>>>> "foo": "bar",
>>>>>>>>> "1": "baz"
>>>>>>>>> }
>>>>>>>>>=20
>>>>>>>>> As I read the draft, the JSON Pointer "/1" would evaluate to =
"baz" even
>>>>>>>>> though that's probably not what the author intended. Is there =
a way to
>>>>>>>>> avoid
>>>>>>>>> that?
>>>>>>>>>=20
>>>>>>>>>=20
>>>>>>>>> Thanks,
>>>>>>>>> Markus
>>>>>>>>>=20
>>>>>>>>>=20
>>>>>>>>>=20
>>>>>>>>> --
>>>>>>>>> Markus Lanthaler
>>>>>>>>> @markuslanthaler
>>>>>>>>>=20
>>>>>>>>>=20
>>>>>>>>>=20
>>>>>>>>>=20
>>>>>>>>>=20
>>>>>>>>>> -----Original Message-----
>>>>>>>>>> From: apps-discuss-bounces@ietf.org [mailto:apps-discuss-
>>>>>>>>>> bounces@ietf.org] On Behalf Of The IESG
>>>>>>>>>> Sent: Tuesday, December 11, 2012 4:01 PM
>>>>>>>>>> To: IETF-Announce
>>>>>>>>>> Cc: apps-discuss@ietf.org
>>>>>>>>>> Subject: [apps-discuss] Last Call: =
<draft-ietf-appsawg-json-pointer-
>>>>>>>>>> 07.txt> (JSON Pointer) to Proposed Standard
>>>>>>>>>>=20
>>>>>>>>>>=20
>>>>>>>>>> The IESG has received a request from the Applications Area =
Working
>>>>>>>>>> Group
>>>>>>>>>> WG (appsawg) to consider the following document:
>>>>>>>>>> - 'JSON Pointer'
>>>>>>>>>> <draft-ietf-appsawg-json-pointer-07.txt> as Proposed Standard
>>>>>>>>>>=20
>>>>>>>>>> The IESG plans to make a decision in the next few weeks, and =
solicits
>>>>>>>>>> final comments on this action. Please send substantive =
comments to
>>>>>>>>>> the
>>>>>>>>>> ietf@ietf.org mailing lists by 2012-12-25. Exceptionally, =
comments
>>>>>>>>>> may
>>>>>>>>>> be
>>>>>>>>>> sent to iesg@ietf.org instead. In either case, please retain =
the
>>>>>>>>>> beginning of the Subject line to allow automated sorting.
>>>>>>>>>>=20
>>>>>>>>>> Abstract
>>>>>>>>>>=20
>>>>>>>>>>=20
>>>>>>>>>> JSON Pointer defines a string syntax for identifying a =
specific
>>>>>>>>>> value
>>>>>>>>>> within a JSON document.
>>>>>>>>>>=20
>>>>>>>>>>=20
>>>>>>>>>>=20
>>>>>>>>>>=20
>>>>>>>>>> The file can be obtained via
>>>>>>>>>> =
http://datatracker.ietf.org/doc/draft-ietf-appsawg-json-pointer/
>>>>>>>>>>=20
>>>>>>>>>> IESG discussion can be tracked via
>>>>>>>>>>=20
>>>>>>>>>> =
http://datatracker.ietf.org/doc/draft-ietf-appsawg-json-pointer/ballot/
>>>>>>>>>>=20
>>>>>>>>>>=20
>>>>>>>>>> No IPR declarations have been submitted directly on this I-D.
>>>>>>>>>>=20
>>>>>>>>>>=20
>>>>>>>>>> _______________________________________________
>>>>>>>>>> apps-discuss mailing list
>>>>>>>>>> apps-discuss@ietf.org
>>>>>>>>>> https://www.ietf.org/mailman/listinfo/apps-discuss
>>>>>>>>>=20
>>>>>>>>> _______________________________________________
>>>>>>>>> apps-discuss mailing list
>>>>>>>>> apps-discuss@ietf.org
>>>>>>>>> https://www.ietf.org/mailman/listinfo/apps-discuss
>>>>>>>>>=20
>>>>>>>>>=20
>>>>>>>>>=20
>>>>>>>>>=20
>>>>>>>>> _______________________________________________
>>>>>>>>> apps-discuss mailing list
>>>>>>>>> apps-discuss@ietf.org
>>>>>>>>> https://www.ietf.org/mailman/listinfo/apps-discuss
>>>>>>>>>=20
>>>>>>>=20
>>>>>>>=20
>>>>>>>=20
>>>>>>> _______________________________________________
>>>>>>> apps-discuss mailing list
>>>>>>> apps-discuss@ietf.org
>>>>>>> https://www.ietf.org/mailman/listinfo/apps-discuss
>>>>>>>=20
>>>>>>=20
>>>>>>=20
>>>>>>=20
>>>>>> --
>>>>>> Matthew P. C. Morley
>>>>> _______________________________________________
>>>>> apps-discuss mailing list
>>>>> apps-discuss@ietf.org
>>>>> https://www.ietf.org/mailman/listinfo/apps-discuss
>>>>=20
>>>> --
>>>> Mark Nottingham   http://www.mnot.net/
>>>>=20
>>>>=20
>>>>=20
>>=20
>> --
>> Mark Nottingham   http://www.mnot.net/
>>=20
>>=20
>>=20

--
Mark Nottingham   http://www.mnot.net/




From sayrer@gmail.com  Sat Jan  5 20:20:22 2013
Return-Path: <sayrer@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7084221F889A; Sat,  5 Jan 2013 20:20:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 lP0EABJFvl7N; Sat,  5 Jan 2013 20:20:20 -0800 (PST)
Received: from mail-we0-f171.google.com (mail-we0-f171.google.com [74.125.82.171]) by ietfa.amsl.com (Postfix) with ESMTP id 54C9321F86D2; Sat,  5 Jan 2013 20:20:20 -0800 (PST)
Received: by mail-we0-f171.google.com with SMTP id u3so8590697wey.2 for <multiple recipients>; Sat, 05 Jan 2013 20:20:19 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=u1BsyZimtWLoOOmBKOLEKpqVQ3ZNJbjzgTOYlEhX4Pc=; b=mgr03Yxq3oci2e0OpTCuwnyDwe/APllCjQdiRbhSaC+xB9ZlbQrAOIdslgCjDCRBJS ylSwuh0MbWcYAcrJ1aWgKZf3INcz26RaOgDHVN30yafBjfvgkDacm/ymMpjSJz9ZeP/g UDg6igmg3bskt1E7cb5lPKQH6Ocx8/b/zcsdlAG+HkHR3DuhbPUWzXgFvFAPBYWiza0R MIOoANZ6KPAEMLnX5nUzcQLX8mluvMp/XDhe1aHeVnBnWfl2pDi9CJxO07k3wxwx9C9U EDnAyrx8SF6ibXHaabYTQYy7OugBLJYSebbNk8aU8Leewr1i3QDdWE492fhTudRNDiLT AWuQ==
MIME-Version: 1.0
Received: by 10.180.88.40 with SMTP id bd8mr3777178wib.33.1357446019252; Sat, 05 Jan 2013 20:20:19 -0800 (PST)
Received: by 10.194.1.101 with HTTP; Sat, 5 Jan 2013 20:20:19 -0800 (PST)
In-Reply-To: <E17FB936-BB87-4711-BEFB-21714B746B71@mnot.net>
References: <20121211150057.28223.93310.idtracker@ietfa.amsl.com> <50cb04b9.86df440a.72fe.1e20SMTPIN_ADDED_BROKEN@mx.google.com> <CABP7RbeNsZ_rBWRjou=VG+hBhUKaOz+y1a0sSChwWiHte9znnQ@mail.gmail.com> <50cb5f3c.694c420a.38fb.39afSMTPIN_ADDED_BROKEN@mx.google.com> <CAChr6SxZRc3B_HCbw76kLe2dsRSr43r-gLpfMVnCUfJTrZdTLA@mail.gmail.com> <CABP7RbfA33huBFadMeXTTEt=MkjW8-d4DFH7+GLXGurnm9sSRw@mail.gmail.com> <CAOXDeqpPE4eNy_qJpDPdPHbCQakG9-hDcNZ3Sj9r4kWedByVzQ@mail.gmail.com> <CAChr6SwtS_=iS-k4mJm1vHjEvvGVzay5jDYeGheqsPZqO-89CQ@mail.gmail.com> <EABB8F51-C3B4-49F5-8672-5C2ABAC7043A@mnot.net> <CAChr6Sx7JdKM91EwJaSZ0Ra_F4FSqkuc3vzTY1LM=F_8sWho+Q@mail.gmail.com> <263BA4B0-6401-4391-A369-A90863D9A4BC@mnot.net> <CAChr6Sw-hZwzB423qvkqyGfq8Aw6Jry-=B9zSzgp2GwbX6gQQg@mail.gmail.com> <E17FB936-BB87-4711-BEFB-21714B746B71@mnot.net>
Date: Sat, 5 Jan 2013 20:20:19 -0800
Message-ID: <CAChr6Sw_GJUE715G_E9DBSz57OvtVjzpU69nk9WwJzz3NPg8AA@mail.gmail.com>
Subject: Re: [apps-discuss] Last Call: <draft-ietf-appsawg-json-pointer-07.txt> (JSON Pointer) to Proposed Standard
From: Robert Sayre <sayrer@gmail.com>
To: Mark Nottingham <mnot@mnot.net>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable
Cc: IETF Discussion <ietf@ietf.org>, IETF Apps Discuss <apps-discuss@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 06 Jan 2013 04:20:22 -0000

On Sat, Jan 5, 2013 at 6:59 PM, Mark Nottingham <mnot@mnot.net> wrote:
>
> Yes, you've brought that to our attention several times. If you wanted
> this spec to align with your software, it would have been much easier
> if you'd got involved before Last Call.

Well, there shouldn't be any big adjustments to my software at all,
and the document generally looks good. This is just a bug: two parties
can apply the same patch and get different results, without
encountering an error.

>>> However, I'm even more interested in getting this format published,
>>
>> Well, I guess someone has something they want to ship...
>
> Right. I'll let that statement stand on its own; I think anyone who's bee=
n
> participating or watching the WG can assess how justified it is.

Ah. I meant that the WG seems to be favoring "running code" a little
too heavily in the presence of a bug. It's an old argument, and it's
boring: "We can't change it now, there are already twelve users!"

>
> Always a pleasure, Rob.

That tone leaves something to be desired, but no matter. This is a bug
and the WG should fix it. I don't think more process emails are
necessary.

- Rob

On Sat, Jan 5, 2013 at 6:59 PM, Mark Nottingham <mnot@mnot.net> wrote:
> On 06/01/2013, at 1:29 PM, Robert Sayre <sayrer@gmail.com> wrote:
>
>> On Sat, Jan 5, 2013 at 5:48 PM, Mark Nottingham <mnot@mnot.net> wrote:
>>>
>>> However, at this point, doing so really a judgement call; we have multi=
ple implementations, and we shouldn't
>>> force them to change arbitrarily.
>>
>> The word "arbitrarily" seems inappropriate here. I raised at least
>> four technical issues and your message addresses none of them.
>
> ... and I explained why.
>
>
>>> As far as I can see, you haven't convinced anyone that this is a seriou=
s enough problem to do so (and I don't
>>> appear to be the only one to hold that opinion, by any means).
>>
>> Did you read this thread? Markus Lanthaler and Conal Tuohy raised
>> similar points.
>
> Yes.
>
>
>>> Furthermore, it's not clear that the use cases you have in mind (since =
you have brought up JSON Sync)
>>> are in-scope for these specifications.
>>
>> That assertion is both unsubstantiated and incorrect. json-sync has
>> identical primitive operations to JSON Patch (create/edit/remove vs
>> add/replace/remove). The JSON Patch document defines Copy and Move in
>> terms of the add/replace, so those are mostly syntactic sugar. The
>> only meaningful delta is the "test" operation, and I do plan to add
>> that to json-sync, since it's a good way to make application-specific
>> assertions.
>
> Yes, you've brought that to our attention several times. If you wanted th=
is spec to align with your software, it would have been much easier if you'=
d got involved before Last Call.
>
>
>>> However, I'm even more interested in getting this format published,
>>
>> Well, I guess someone has something they want to ship...
>
> Right. I'll let that statement stand on its own; I think anyone who's bee=
n participating or watching the WG can assess how justified it is.
>
> Always a pleasure, Rob.
>
>
>>
>> - Rob
>>
>>> Cheers,
>>>
>>>
>>> On 06/01/2013, at 11:19 AM, Robert Sayre <sayrer@gmail.com> wrote:
>>>
>>>> Mark,
>>>>
>>>> The WG's reasoning, as stated in your message below, seems flawed.
>>>> Messages since your last communication on this matter have shown:
>>>>
>>>> 1) The ambiguity around arrays makes the patch format unsuitable for
>>>> common concurrent editing algorithms.
>>>> 2) The ambiguity is likely to occur in the real world, for a couple of
>>>> different reasons.
>>>> 3) It's not possible to tell whether a JSON Pointer document is
>>>> syntactically correct in isolation.
>>>>
>>>> Additionally, you raised this point in your message below:
>>>>>
>>>>> the patch author already has to understand the semantics of the docum=
ent they're patching
>>>>
>>>> That claim does not seem to be well-justified, and it could be
>>>> meaningless to the person implementing patch software (for example:
>>>> https://github.com/sayrer/json-sync).
>>>>
>>>> This issue is a problem in practice, and it's a problem in theory as
>>>> well. JSON-Patch messages aren't sufficiently self-descriptive, so
>>>> they aren't appropriate for use in a RESTful system.
>>>>
>>>> A response containing technical reasoning seems in order, since the
>>>> points raised by myself and others on this issue are unrelated to the
>>>> WG's previous thinking.
>>>>
>>>> - Rob
>>>>
>>>> On Sun, Dec 16, 2012 at 9:41 PM, Mark Nottingham <mnot@mnot.net> wrote=
:
>>>>> Robert,
>>>>>
>>>>> This was discussed extensively in the Working Group.
>>>>>
>>>>> The root of the issue was that some people reflexively felt that this=
 was necessary, but upon reflection, we decided it wasn't; although it seem=
s "natural" to some, especially those coming from a static language backgro=
und, it didn't provide any utility.
>>>>>
>>>>> You might argue that someone who (for example) adds to "/foo/1" in th=
e mistaken belief that it's an array, when in fact it's an object, will get=
 surprising results. That's true, but if we were to solve this problem, tha=
t person would still need to understand the underlying semantics of "foo" t=
o do anything useful to it -- and I'm not hearing anyone complain about tha=
t (I hope).
>>>>>
>>>>> Put another way -- do you really think that people PATCHing something=
 as if it's an array (when in fact it's an object) is a significant, real-w=
orld problem, given that the patch author already has to understand the sem=
antics of the document they're patching? I don't, and the WG didn't either.
>>>>>
>>>>> Regards,
>>>>>
>>>>>
>>>>> On 17/12/2012, at 3:36 PM, Robert Sayre <sayrer@gmail.com> wrote:
>>>>>
>>>>>> The cost of fixing it seems low, either by changing the path syntax =
of
>>>>>> JSON pointer or changing the names of operations applied to arrays.
>>>>>> Array-like objects are common enough in JavaScript to make this a
>>>>>> worry. The other suggestions either assume a particular policy for
>>>>>> concurrent edits or require more machinery (test operation etc).
>>>>>> Wouldn't it be simpler to make the patch format more precise?
>>>>>>
>>>>>> - Rob
>>>>>>
>>>>>> On Sun, Dec 16, 2012 at 4:33 PM, Matthew Morley <matt@mpcm.com> wrot=
e:
>>>>>>> I am usually lurking and struggling to keep up with these posts. Bu=
t, I
>>>>>>> concur with James, this really is a non-issue in practice.
>>>>>>>
>>>>>>> The JSON Pointer expresses a path down a JSON object to a specific =
context.
>>>>>>> The Patch expresses a change within or to that context.
>>>>>>> Everything about the both standards is about that end context.
>>>>>>>
>>>>>>> If you want to confirm the type of the context before applying a pa=
tch, this
>>>>>>> should probably be part of a test operation. I'm not sure if this i=
s
>>>>>>> possible at this point (?), but that is where the logic should exis=
t.
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On Sun, Dec 16, 2012 at 12:22 AM, James M Snell <jasnell@gmail.com>=
 wrote:
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> On Sat, Dec 15, 2012 at 8:36 PM, Robert Sayre <sayrer@gmail.com> w=
rote:
>>>>>>>>>
>>>>>>>>> On Fri, Dec 14, 2012 at 9:17 AM, Markus Lanthaler
>>>>>>>>> <markus.lanthaler@gmx.net> wrote:
>>>>>>>>>>
>>>>>>>>>> Hmm.. I think that=92s quite problematic. Especially considering=
 how JSON
>>>>>>>>>> Pointer is used in JSON Patch.
>>>>>>>>>
>>>>>>>>> I agree--I provided the same feedback privately. It seems
>>>>>>>>> straightforwardly unsound.
>>>>>>>>>
>>>>>>>>
>>>>>>>> In practice it doesn't seem to be much of an issue.
>>>>>>>>
>>>>>>>> Specifically, if I GET an existing document and get an etag with t=
he JSON,
>>>>>>>> then make some changes and send a PATCH with If-Match, the fact th=
at any
>>>>>>>> given pointer could point to an array or object member doesn't rea=
lly matter
>>>>>>>> much.
>>>>>>>>
>>>>>>>> For example:
>>>>>>>>
>>>>>>>>> GET /the/doc HTTP/1.1
>>>>>>>>
>>>>>>>> <  HTTP/1.1 200 OK
>>>>>>>>   ETag: "my-document-tag"
>>>>>>>>   Content-Type: application/json
>>>>>>>>
>>>>>>>>   {"1":"foo"}
>>>>>>>>
>>>>>>>>> PATCH /the/doc HTTP/1.1
>>>>>>>>   If-Match: "my-document-etag"
>>>>>>>>   Content-Type: application/json-patch
>>>>>>>>
>>>>>>>>   [{"op":"add","path":"/2","value":"bar"}]
>>>>>>>>
>>>>>>>> Generally speaking, someone should not be using PATCH to perform a=
 partial
>>>>>>>> modification if they don't already have some knowledge in advance =
what they
>>>>>>>> are modifying. The only time the apparent ambiguity becomes an iss=
ue is when
>>>>>>>> a client is blindly sending a patch to an unknown endpoint... in w=
hich case,
>>>>>>>> you get whatever you end up with.
>>>>>>>>
>>>>>>>> - James
>>>>>>>>
>>>>>>>>
>>>>>>>>>
>>>>>>>>> - Rob
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> --
>>>>>>>>>>
>>>>>>>>>> Markus Lanthaler
>>>>>>>>>>
>>>>>>>>>> @markuslanthaler
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> From: James M Snell [mailto:jasnell@gmail.com]
>>>>>>>>>> Sent: Friday, December 14, 2012 5:41 PM
>>>>>>>>>> To: Markus Lanthaler
>>>>>>>>>> Cc: IETF Discussion; IETF Apps Discuss
>>>>>>>>>> Subject: Re: [apps-discuss] Last Call:
>>>>>>>>>> <draft-ietf-appsawg-json-pointer-07.txt> (JSON Pointer) to Propo=
sed Standard
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> JSON Pointer does not distinguish between objects and arrays. Th=
at is
>>>>>>>>>> not determined until the pointer is applied to an actual object =
instance...
>>>>>>>>>> the pointer "/1" is valid against {"1":"a"} or ["a","b"]
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> On Fri, Dec 14, 2012 at 2:51 AM, Markus Lanthaler
>>>>>>>>>> <markus.lanthaler@gmx.net> wrote:
>>>>>>>>>>
>>>>>>>>>> I've asked that before but didn't get an answer. So let me ask a=
gain
>>>>>>>>>> (even
>>>>>>>>>> though I'm quite sure it has already been asked by somebody else=
).
>>>>>>>>>>
>>>>>>>>>> How does JSON Pointer distinguish between objects and arrays? E.=
g.
>>>>>>>>>> consider
>>>>>>>>>> the following JSON document:
>>>>>>>>>>
>>>>>>>>>> {
>>>>>>>>>> "foo": "bar",
>>>>>>>>>> "1": "baz"
>>>>>>>>>> }
>>>>>>>>>>
>>>>>>>>>> As I read the draft, the JSON Pointer "/1" would evaluate to "ba=
z" even
>>>>>>>>>> though that's probably not what the author intended. Is there a =
way to
>>>>>>>>>> avoid
>>>>>>>>>> that?
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Thanks,
>>>>>>>>>> Markus
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> --
>>>>>>>>>> Markus Lanthaler
>>>>>>>>>> @markuslanthaler
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>> -----Original Message-----
>>>>>>>>>>> From: apps-discuss-bounces@ietf.org [mailto:apps-discuss-
>>>>>>>>>>> bounces@ietf.org] On Behalf Of The IESG
>>>>>>>>>>> Sent: Tuesday, December 11, 2012 4:01 PM
>>>>>>>>>>> To: IETF-Announce
>>>>>>>>>>> Cc: apps-discuss@ietf.org
>>>>>>>>>>> Subject: [apps-discuss] Last Call: <draft-ietf-appsawg-json-poi=
nter-
>>>>>>>>>>> 07.txt> (JSON Pointer) to Proposed Standard
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> The IESG has received a request from the Applications Area Work=
ing
>>>>>>>>>>> Group
>>>>>>>>>>> WG (appsawg) to consider the following document:
>>>>>>>>>>> - 'JSON Pointer'
>>>>>>>>>>> <draft-ietf-appsawg-json-pointer-07.txt> as Proposed Standard
>>>>>>>>>>>
>>>>>>>>>>> The IESG plans to make a decision in the next few weeks, and so=
licits
>>>>>>>>>>> final comments on this action. Please send substantive comments=
 to
>>>>>>>>>>> the
>>>>>>>>>>> ietf@ietf.org mailing lists by 2012-12-25. Exceptionally, comme=
nts
>>>>>>>>>>> may
>>>>>>>>>>> be
>>>>>>>>>>> sent to iesg@ietf.org instead. In either case, please retain th=
e
>>>>>>>>>>> beginning of the Subject line to allow automated sorting.
>>>>>>>>>>>
>>>>>>>>>>> Abstract
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> JSON Pointer defines a string syntax for identifying a specific
>>>>>>>>>>> value
>>>>>>>>>>> within a JSON document.
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> The file can be obtained via
>>>>>>>>>>> http://datatracker.ietf.org/doc/draft-ietf-appsawg-json-pointer=
/
>>>>>>>>>>>
>>>>>>>>>>> IESG discussion can be tracked via
>>>>>>>>>>>
>>>>>>>>>>> http://datatracker.ietf.org/doc/draft-ietf-appsawg-json-pointer=
/ballot/
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> No IPR declarations have been submitted directly on this I-D.
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> _______________________________________________
>>>>>>>>>>> apps-discuss mailing list
>>>>>>>>>>> apps-discuss@ietf.org
>>>>>>>>>>> https://www.ietf.org/mailman/listinfo/apps-discuss
>>>>>>>>>>
>>>>>>>>>> _______________________________________________
>>>>>>>>>> apps-discuss mailing list
>>>>>>>>>> apps-discuss@ietf.org
>>>>>>>>>> https://www.ietf.org/mailman/listinfo/apps-discuss
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> _______________________________________________
>>>>>>>>>> apps-discuss mailing list
>>>>>>>>>> apps-discuss@ietf.org
>>>>>>>>>> https://www.ietf.org/mailman/listinfo/apps-discuss
>>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> _______________________________________________
>>>>>>>> apps-discuss mailing list
>>>>>>>> apps-discuss@ietf.org
>>>>>>>> https://www.ietf.org/mailman/listinfo/apps-discuss
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Matthew P. C. Morley
>>>>>> _______________________________________________
>>>>>> apps-discuss mailing list
>>>>>> apps-discuss@ietf.org
>>>>>> https://www.ietf.org/mailman/listinfo/apps-discuss
>>>>>
>>>>> --
>>>>> Mark Nottingham   http://www.mnot.net/
>>>>>
>>>>>
>>>>>
>>>
>>> --
>>> Mark Nottingham   http://www.mnot.net/
>>>
>>>
>>>
>
> --
> Mark Nottingham   http://www.mnot.net/
>
>
>

From jasnell@gmail.com  Sat Jan  5 20:55:55 2013
Return-Path: <jasnell@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C84D521F86C4; Sat,  5 Jan 2013 20:55:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.598
X-Spam-Level: 
X-Spam-Status: No, score=-3.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
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 DRtl7gQwfgIO; Sat,  5 Jan 2013 20:55:53 -0800 (PST)
Received: from mail-ia0-f171.google.com (mail-ia0-f171.google.com [209.85.210.171]) by ietfa.amsl.com (Postfix) with ESMTP id 7209521F86C2; Sat,  5 Jan 2013 20:55:53 -0800 (PST)
Received: by mail-ia0-f171.google.com with SMTP id k27so15146355iad.16 for <multiple recipients>; Sat, 05 Jan 2013 20:55:53 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=/JERQDQf9uDDkvBq41BVGCG4CD7+NP7w3V0emDQU7Uw=; b=Wp0CM3kstpkPa0/WhRKXWUZCytcBqCt/Fd10arLafkZ7GUxmaTO+tbt8ZnfgNGYcCU ryeEIDp0nZWYaXel5YsbhZ2MXkG1vnOXmyV9aDSKxZfQx5Q5d1Paknm1tAGbnytAH9Tk 4XJ8XbBakI3DZX8iVOF4rHpCMVih9XIhmSiIHgibFik24Jjt0EAJqufkeTrfjwHZlDqz DDA0MiJoP2NblMCy8EyIUQnKhltGvJ9heUDUuAfJ+hkk5PndnJhSnfJ+aeXLesEtUtKx X3ldVsj3RG8zsmJHB/cXjpPcYEg8Lprv+gzUVgy+uhSTC3OlXHixZQ8gXVQC9NebuA0+ FtQg==
MIME-Version: 1.0
X-Received: by 10.50.178.10 with SMTP id cu10mr2721943igc.75.1357448152974; Sat, 05 Jan 2013 20:55:52 -0800 (PST)
Received: by 10.64.7.19 with HTTP; Sat, 5 Jan 2013 20:55:52 -0800 (PST)
Received: by 10.64.7.19 with HTTP; Sat, 5 Jan 2013 20:55:52 -0800 (PST)
In-Reply-To: <CAChr6Sw_GJUE715G_E9DBSz57OvtVjzpU69nk9WwJzz3NPg8AA@mail.gmail.com>
References: <20121211150057.28223.93310.idtracker@ietfa.amsl.com> <50cb04b9.86df440a.72fe.1e20SMTPIN_ADDED_BROKEN@mx.google.com> <CABP7RbeNsZ_rBWRjou=VG+hBhUKaOz+y1a0sSChwWiHte9znnQ@mail.gmail.com> <50cb5f3c.694c420a.38fb.39afSMTPIN_ADDED_BROKEN@mx.google.com> <CAChr6SxZRc3B_HCbw76kLe2dsRSr43r-gLpfMVnCUfJTrZdTLA@mail.gmail.com> <CABP7RbfA33huBFadMeXTTEt=MkjW8-d4DFH7+GLXGurnm9sSRw@mail.gmail.com> <CAOXDeqpPE4eNy_qJpDPdPHbCQakG9-hDcNZ3Sj9r4kWedByVzQ@mail.gmail.com> <CAChr6SwtS_=iS-k4mJm1vHjEvvGVzay5jDYeGheqsPZqO-89CQ@mail.gmail.com> <EABB8F51-C3B4-49F5-8672-5C2ABAC7043A@mnot.net> <CAChr6Sx7JdKM91EwJaSZ0Ra_F4FSqkuc3vzTY1LM=F_8sWho+Q@mail.gmail.com> <263BA4B0-6401-4391-A369-A90863D9A4BC@mnot.net> <CAChr6Sw-hZwzB423qvkqyGfq8Aw6Jry-=B9zSzgp2GwbX6gQQg@mail.gmail.com> <E17FB936-BB87-4711-BEFB-21714B746B71@mnot.net> <CAChr6Sw_GJUE715G_E9DBSz57OvtVjzpU69nk9WwJzz3NPg8AA@mail.gmail.com>
Date: Sat, 5 Jan 2013 20:55:52 -0800
Message-ID: <CABP7RbcQARMAvisv4zUPX7+t97MQ_vwizBCiUBt6Nc7y7CapYQ@mail.gmail.com>
Subject: Re: [apps-discuss] Last Call: <draft-ietf-appsawg-json-pointer-07.txt> (JSON Pointer) to Proposed Standard
From: James M Snell <jasnell@gmail.com>
To: Rob Sayre <sayrer@gmail.com>
Content-Type: multipart/alternative; boundary=e89a8f839ca1f5860704d2978658
Cc: Mark Nottingham <mnot@mnot.net>, IETF Discussion <ietf@ietf.org>, IETF Apps Discuss <apps-discuss@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 06 Jan 2013 04:55:56 -0000

--e89a8f839ca1f5860704d2978658
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Jan 5, 2013 8:20 PM, "Robert Sayre" <sayrer@gmail.com> wrote:
>
> On Sat, Jan 5, 2013 at 6:59 PM, Mark Nottingham <mnot@mnot.net> wrote:
> >
> > Yes, you've brought that to our attention several times. If you wanted
> > this spec to align with your software, it would have been much easier
> > if you'd got involved before Last Call.
>
> Well, there shouldn't be any big adjustments to my software at all,
> and the document generally looks good. This is just a bug: two parties
> can apply the same patch and get different results, without
> encountering an error.
>

Not seeing the bug... applying the same patch to different resources that
have different states ought to have different results. #worksasintended
#wontfix #moveonthereisnothingmoretoseehere

- james

> >>> However, I'm even more interested in getting this format published,
> >>
> >> Well, I guess someone has something they want to ship...
> >
> > Right. I'll let that statement stand on its own; I think anyone who's
been
> > participating or watching the WG can assess how justified it is.
>
> Ah. I meant that the WG seems to be favoring "running code" a little
> too heavily in the presence of a bug. It's an old argument, and it's
> boring: "We can't change it now, there are already twelve users!"
>
> >
> > Always a pleasure, Rob.
>
> That tone leaves something to be desired, but no matter. This is a bug
> and the WG should fix it. I don't think more process emails are
> necessary.
>
> - Rob
>
> On Sat, Jan 5, 2013 at 6:59 PM, Mark Nottingham <mnot@mnot.net> wrote:
> > On 06/01/2013, at 1:29 PM, Robert Sayre <sayrer@gmail.com> wrote:
> >
> >> On Sat, Jan 5, 2013 at 5:48 PM, Mark Nottingham <mnot@mnot.net> wrote:
> >>>
> >>> However, at this point, doing so really a judgement call; we have
multiple implementations, and we shouldn't
> >>> force them to change arbitrarily.
> >>
> >> The word "arbitrarily" seems inappropriate here. I raised at least
> >> four technical issues and your message addresses none of them.
> >
> > ... and I explained why.
> >
> >
> >>> As far as I can see, you haven't convinced anyone that this is a
serious enough problem to do so (and I don't
> >>> appear to be the only one to hold that opinion, by any means).
> >>
> >> Did you read this thread? Markus Lanthaler and Conal Tuohy raised
> >> similar points.
> >
> > Yes.
> >
> >
> >>> Furthermore, it's not clear that the use cases you have in mind
(since you have brought up JSON Sync)
> >>> are in-scope for these specifications.
> >>
> >> That assertion is both unsubstantiated and incorrect. json-sync has
> >> identical primitive operations to JSON Patch (create/edit/remove vs
> >> add/replace/remove). The JSON Patch document defines Copy and Move in
> >> terms of the add/replace, so those are mostly syntactic sugar. The
> >> only meaningful delta is the "test" operation, and I do plan to add
> >> that to json-sync, since it's a good way to make application-specific
> >> assertions.
> >
> > Yes, you've brought that to our attention several times. If you wanted
this spec to align with your software, it would have been much easier if
you'd got involved before Last Call.
> >
> >
> >>> However, I'm even more interested in getting this format published,
> >>
> >> Well, I guess someone has something they want to ship...
> >
> > Right. I'll let that statement stand on its own; I think anyone who's
been participating or watching the WG can assess how justified it is.
> >
> > Always a pleasure, Rob.
> >
> >
> >>
> >> - Rob
> >>
> >>> Cheers,
> >>>
> >>>
> >>> On 06/01/2013, at 11:19 AM, Robert Sayre <sayrer@gmail.com> wrote:
> >>>
> >>>> Mark,
> >>>>
> >>>> The WG's reasoning, as stated in your message below, seems flawed.
> >>>> Messages since your last communication on this matter have shown:
> >>>>
> >>>> 1) The ambiguity around arrays makes the patch format unsuitable for
> >>>> common concurrent editing algorithms.
> >>>> 2) The ambiguity is likely to occur in the real world, for a couple
of
> >>>> different reasons.
> >>>> 3) It's not possible to tell whether a JSON Pointer document is
> >>>> syntactically correct in isolation.
> >>>>
> >>>> Additionally, you raised this point in your message below:
> >>>>>
> >>>>> the patch author already has to understand the semantics of the
document they're patching
> >>>>
> >>>> That claim does not seem to be well-justified, and it could be
> >>>> meaningless to the person implementing patch software (for example:
> >>>> https://github.com/sayrer/json-sync).
> >>>>
> >>>> This issue is a problem in practice, and it's a problem in theory as
> >>>> well. JSON-Patch messages aren't sufficiently self-descriptive, so
> >>>> they aren't appropriate for use in a RESTful system.
> >>>>
> >>>> A response containing technical reasoning seems in order, since the
> >>>> points raised by myself and others on this issue are unrelated to th=
e
> >>>> WG's previous thinking.
> >>>>
> >>>> - Rob
> >>>>
> >>>> On Sun, Dec 16, 2012 at 9:41 PM, Mark Nottingham <mnot@mnot.net>
wrote:
> >>>>> Robert,
> >>>>>
> >>>>> This was discussed extensively in the Working Group.
> >>>>>
> >>>>> The root of the issue was that some people reflexively felt that
this was necessary, but upon reflection, we decided it wasn't; although it
seems "natural" to some, especially those coming from a static language
background, it didn't provide any utility.
> >>>>>
> >>>>> You might argue that someone who (for example) adds to "/foo/1" in
the mistaken belief that it's an array, when in fact it's an object, will
get surprising results. That's true, but if we were to solve this problem,
that person would still need to understand the underlying semantics of
"foo" to do anything useful to it -- and I'm not hearing anyone complain
about that (I hope).
> >>>>>
> >>>>> Put another way -- do you really think that people PATCHing
something as if it's an array (when in fact it's an object) is a
significant, real-world problem, given that the patch author already has to
understand the semantics of the document they're patching? I don't, and the
WG didn't either.
> >>>>>
> >>>>> Regards,
> >>>>>
> >>>>>
> >>>>> On 17/12/2012, at 3:36 PM, Robert Sayre <sayrer@gmail.com> wrote:
> >>>>>
> >>>>>> The cost of fixing it seems low, either by changing the path
syntax of
> >>>>>> JSON pointer or changing the names of operations applied to arrays=
.
> >>>>>> Array-like objects are common enough in JavaScript to make this a
> >>>>>> worry. The other suggestions either assume a particular policy for
> >>>>>> concurrent edits or require more machinery (test operation etc).
> >>>>>> Wouldn't it be simpler to make the patch format more precise?
> >>>>>>
> >>>>>> - Rob
> >>>>>>
> >>>>>> On Sun, Dec 16, 2012 at 4:33 PM, Matthew Morley <matt@mpcm.com>
wrote:
> >>>>>>> I am usually lurking and struggling to keep up with these posts.
But, I
> >>>>>>> concur with James, this really is a non-issue in practice.
> >>>>>>>
> >>>>>>> The JSON Pointer expresses a path down a JSON object to a
specific context.
> >>>>>>> The Patch expresses a change within or to that context.
> >>>>>>> Everything about the both standards is about that end context.
> >>>>>>>
> >>>>>>> If you want to confirm the type of the context before applying a
patch, this
> >>>>>>> should probably be part of a test operation. I'm not sure if this
is
> >>>>>>> possible at this point (?), but that is where the logic should
exist.
> >>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>> On Sun, Dec 16, 2012 at 12:22 AM, James M Snell <jasnell@gmail.co=
m>
wrote:
> >>>>>>>>
> >>>>>>>>
> >>>>>>>>
> >>>>>>>>
> >>>>>>>> On Sat, Dec 15, 2012 at 8:36 PM, Robert Sayre <sayrer@gmail.com>
wrote:
> >>>>>>>>>
> >>>>>>>>> On Fri, Dec 14, 2012 at 9:17 AM, Markus Lanthaler
> >>>>>>>>> <markus.lanthaler@gmx.net> wrote:
> >>>>>>>>>>
> >>>>>>>>>> Hmm.. I think that=E2=80=99s quite problematic. Especially con=
sidering
how JSON
> >>>>>>>>>> Pointer is used in JSON Patch.
> >>>>>>>>>
> >>>>>>>>> I agree--I provided the same feedback privately. It seems
> >>>>>>>>> straightforwardly unsound.
> >>>>>>>>>
> >>>>>>>>
> >>>>>>>> In practice it doesn't seem to be much of an issue.
> >>>>>>>>
> >>>>>>>> Specifically, if I GET an existing document and get an etag with
the JSON,
> >>>>>>>> then make some changes and send a PATCH with If-Match, the fact
that any
> >>>>>>>> given pointer could point to an array or object member doesn't
really matter
> >>>>>>>> much.
> >>>>>>>>
> >>>>>>>> For example:
> >>>>>>>>
> >>>>>>>>> GET /the/doc HTTP/1.1
> >>>>>>>>
> >>>>>>>> <  HTTP/1.1 200 OK
> >>>>>>>>   ETag: "my-document-tag"
> >>>>>>>>   Content-Type: application/json
> >>>>>>>>
> >>>>>>>>   {"1":"foo"}
> >>>>>>>>
> >>>>>>>>> PATCH /the/doc HTTP/1.1
> >>>>>>>>   If-Match: "my-document-etag"
> >>>>>>>>   Content-Type: application/json-patch
> >>>>>>>>
> >>>>>>>>   [{"op":"add","path":"/2","value":"bar"}]
> >>>>>>>>
> >>>>>>>> Generally speaking, someone should not be using PATCH to perform
a partial
> >>>>>>>> modification if they don't already have some knowledge in
advance what they
> >>>>>>>> are modifying. The only time the apparent ambiguity becomes an
issue is when
> >>>>>>>> a client is blindly sending a patch to an unknown endpoint... in
which case,
> >>>>>>>> you get whatever you end up with.
> >>>>>>>>
> >>>>>>>> - James
> >>>>>>>>
> >>>>>>>>
> >>>>>>>>>
> >>>>>>>>> - Rob
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>> --
> >>>>>>>>>>
> >>>>>>>>>> Markus Lanthaler
> >>>>>>>>>>
> >>>>>>>>>> @markuslanthaler
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>> From: James M Snell [mailto:jasnell@gmail.com]
> >>>>>>>>>> Sent: Friday, December 14, 2012 5:41 PM
> >>>>>>>>>> To: Markus Lanthaler
> >>>>>>>>>> Cc: IETF Discussion; IETF Apps Discuss
> >>>>>>>>>> Subject: Re: [apps-discuss] Last Call:
> >>>>>>>>>> <draft-ietf-appsawg-json-pointer-07.txt> (JSON Pointer) to
Proposed Standard
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>> JSON Pointer does not distinguish between objects and arrays.
That is
> >>>>>>>>>> not determined until the pointer is applied to an actual
object instance...
> >>>>>>>>>> the pointer "/1" is valid against {"1":"a"} or ["a","b"]
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>> On Fri, Dec 14, 2012 at 2:51 AM, Markus Lanthaler
> >>>>>>>>>> <markus.lanthaler@gmx.net> wrote:
> >>>>>>>>>>
> >>>>>>>>>> I've asked that before but didn't get an answer. So let me ask
again
> >>>>>>>>>> (even
> >>>>>>>>>> though I'm quite sure it has already been asked by somebody
else).
> >>>>>>>>>>
> >>>>>>>>>> How does JSON Pointer distinguish between objects and arrays?
E.g.
> >>>>>>>>>> consider
> >>>>>>>>>> the following JSON document:
> >>>>>>>>>>
> >>>>>>>>>> {
> >>>>>>>>>> "foo": "bar",
> >>>>>>>>>> "1": "baz"
> >>>>>>>>>> }
> >>>>>>>>>>
> >>>>>>>>>> As I read the draft, the JSON Pointer "/1" would evaluate to
"baz" even
> >>>>>>>>>> though that's probably not what the author intended. Is there
a way to
> >>>>>>>>>> avoid
> >>>>>>>>>> that?
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>> Thanks,
> >>>>>>>>>> Markus
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>> --
> >>>>>>>>>> Markus Lanthaler
> >>>>>>>>>> @markuslanthaler
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>> -----Original Message-----
> >>>>>>>>>>> From: apps-discuss-bounces@ietf.org [mailto:apps-discuss-
> >>>>>>>>>>> bounces@ietf.org] On Behalf Of The IESG
> >>>>>>>>>>> Sent: Tuesday, December 11, 2012 4:01 PM
> >>>>>>>>>>> To: IETF-Announce
> >>>>>>>>>>> Cc: apps-discuss@ietf.org
> >>>>>>>>>>> Subject: [apps-discuss] Last Call:
<draft-ietf-appsawg-json-pointer-
> >>>>>>>>>>> 07.txt> (JSON Pointer) to Proposed Standard
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>> The IESG has received a request from the Applications Area
Working
> >>>>>>>>>>> Group
> >>>>>>>>>>> WG (appsawg) to consider the following document:
> >>>>>>>>>>> - 'JSON Pointer'
> >>>>>>>>>>> <draft-ietf-appsawg-json-pointer-07.txt> as Proposed Standard
> >>>>>>>>>>>
> >>>>>>>>>>> The IESG plans to make a decision in the next few weeks, and
solicits
> >>>>>>>>>>> final comments on this action. Please send substantive
comments to
> >>>>>>>>>>> the
> >>>>>>>>>>> ietf@ietf.org mailing lists by 2012-12-25. Exceptionally,
comments
> >>>>>>>>>>> may
> >>>>>>>>>>> be
> >>>>>>>>>>> sent to iesg@ietf.org instead. In either case, please retain
the
> >>>>>>>>>>> beginning of the Subject line to allow automated sorting.
> >>>>>>>>>>>
> >>>>>>>>>>> Abstract
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>> JSON Pointer defines a string syntax for identifying a
specific
> >>>>>>>>>>> value
> >>>>>>>>>>> within a JSON document.
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>> The file can be obtained via
> >>>>>>>>>>>
http://datatracker.ietf.org/doc/draft-ietf-appsawg-json-pointer/
> >>>>>>>>>>>
> >>>>>>>>>>> IESG discussion can be tracked via
> >>>>>>>>>>>
> >>>>>>>>>>>
http://datatracker.ietf.org/doc/draft-ietf-appsawg-json-pointer/ballot/
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>> No IPR declarations have been submitted directly on this I-D.
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>> _______________________________________________
> >>>>>>>>>>> apps-discuss mailing list
> >>>>>>>>>>> apps-discuss@ietf.org
> >>>>>>>>>>> https://www.ietf.org/mailman/listinfo/apps-discuss
> >>>>>>>>>>
> >>>>>>>>>> _______________________________________________
> >>>>>>>>>> apps-discuss mailing list
> >>>>>>>>>> apps-discuss@ietf.org
> >>>>>>>>>> https://www.ietf.org/mailman/listinfo/apps-discuss
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>> _______________________________________________
> >>>>>>>>>> apps-discuss mailing list
> >>>>>>>>>> apps-discuss@ietf.org
> >>>>>>>>>> https://www.ietf.org/mailman/listinfo/apps-discuss
> >>>>>>>>>>
> >>>>>>>>
> >>>>>>>>
> >>>>>>>>
> >>>>>>>> _______________________________________________
> >>>>>>>> apps-discuss mailing list
> >>>>>>>> apps-discuss@ietf.org
> >>>>>>>> https://www.ietf.org/mailman/listinfo/apps-discuss
> >>>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>> --
> >>>>>>> Matthew P. C. Morley
> >>>>>> _______________________________________________
> >>>>>> apps-discuss mailing list
> >>>>>> apps-discuss@ietf.org
> >>>>>> https://www.ietf.org/mailman/listinfo/apps-discuss
> >>>>>
> >>>>> --
> >>>>> Mark Nottingham   http://www.mnot.net/
> >>>>>
> >>>>>
> >>>>>
> >>>
> >>> --
> >>> Mark Nottingham   http://www.mnot.net/
> >>>
> >>>
> >>>
> >
> > --
> > Mark Nottingham   http://www.mnot.net/
> >
> >
> >
> _______________________________________________
> apps-discuss mailing list
> apps-discuss@ietf.org
> https://www.ietf.org/mailman/listinfo/apps-discuss

--e89a8f839ca1f5860704d2978658
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<p dir=3D"ltr"><br>
On Jan 5, 2013 8:20 PM, &quot;Robert Sayre&quot; &lt;<a href=3D"mailto:sayr=
er@gmail.com">sayrer@gmail.com</a>&gt; wrote:<br>
&gt;<br>
&gt; On Sat, Jan 5, 2013 at 6:59 PM, Mark Nottingham &lt;<a href=3D"mailto:=
mnot@mnot.net">mnot@mnot.net</a>&gt; wrote:<br>
&gt; &gt;<br>
&gt; &gt; Yes, you&#39;ve brought that to our attention several times. If y=
ou wanted<br>
&gt; &gt; this spec to align with your software, it would have been much ea=
sier<br>
&gt; &gt; if you&#39;d got involved before Last Call.<br>
&gt;<br>
&gt; Well, there shouldn&#39;t be any big adjustments to my software at all=
,<br>
&gt; and the document generally looks good. This is just a bug: two parties=
<br>
&gt; can apply the same patch and get different results, without<br>
&gt; encountering an error.<br>
&gt;</p>
<p dir=3D"ltr">Not seeing the bug... applying the same patch to different r=
esources that have different states ought to have different results. #works=
asintended #wontfix #moveonthereisnothingmoretoseehere</p>
<p dir=3D"ltr">- james</p>
<p dir=3D"ltr">&gt; &gt;&gt;&gt; However, I&#39;m even more interested in g=
etting this format published,<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt; Well, I guess someone has something they want to ship...<br>
&gt; &gt;<br>
&gt; &gt; Right. I&#39;ll let that statement stand on its own; I think anyo=
ne who&#39;s been<br>
&gt; &gt; participating or watching the WG can assess how justified it is.<=
br>
&gt;<br>
&gt; Ah. I meant that the WG seems to be favoring &quot;running code&quot; =
a little<br>
&gt; too heavily in the presence of a bug. It&#39;s an old argument, and it=
&#39;s<br>
&gt; boring: &quot;We can&#39;t change it now, there are already twelve use=
rs!&quot;<br>
&gt;<br>
&gt; &gt;<br>
&gt; &gt; Always a pleasure, Rob.<br>
&gt;<br>
&gt; That tone leaves something to be desired, but no matter. This is a bug=
<br>
&gt; and the WG should fix it. I don&#39;t think more process emails are<br=
>
&gt; necessary.<br>
&gt;<br>
&gt; - Rob<br>
&gt;<br>
&gt; On Sat, Jan 5, 2013 at 6:59 PM, Mark Nottingham &lt;<a href=3D"mailto:=
mnot@mnot.net">mnot@mnot.net</a>&gt; wrote:<br>
&gt; &gt; On 06/01/2013, at 1:29 PM, Robert Sayre &lt;<a href=3D"mailto:say=
rer@gmail.com">sayrer@gmail.com</a>&gt; wrote:<br>
&gt; &gt;<br>
&gt; &gt;&gt; On Sat, Jan 5, 2013 at 5:48 PM, Mark Nottingham &lt;<a href=
=3D"mailto:mnot@mnot.net">mnot@mnot.net</a>&gt; wrote:<br>
&gt; &gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt; However, at this point, doing so really a judgement call;=
 we have multiple implementations, and we shouldn&#39;t<br>
&gt; &gt;&gt;&gt; force them to change arbitrarily.<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt; The word &quot;arbitrarily&quot; seems inappropriate here. I =
raised at least<br>
&gt; &gt;&gt; four technical issues and your message addresses none of them=
.<br>
&gt; &gt;<br>
&gt; &gt; ... and I explained why.<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt;&gt;&gt; As far as I can see, you haven&#39;t convinced anyone tha=
t this is a serious enough problem to do so (and I don&#39;t<br>
&gt; &gt;&gt;&gt; appear to be the only one to hold that opinion, by any me=
ans).<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt; Did you read this thread? Markus Lanthaler and Conal Tuohy ra=
ised<br>
&gt; &gt;&gt; similar points.<br>
&gt; &gt;<br>
&gt; &gt; Yes.<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt;&gt;&gt; Furthermore, it&#39;s not clear that the use cases you ha=
ve in mind (since you have brought up JSON Sync)<br>
&gt; &gt;&gt;&gt; are in-scope for these specifications.<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt; That assertion is both unsubstantiated and incorrect. json-sy=
nc has<br>
&gt; &gt;&gt; identical primitive operations to JSON Patch (create/edit/rem=
ove vs<br>
&gt; &gt;&gt; add/replace/remove). The JSON Patch document defines Copy and=
 Move in<br>
&gt; &gt;&gt; terms of the add/replace, so those are mostly syntactic sugar=
. The<br>
&gt; &gt;&gt; only meaningful delta is the &quot;test&quot; operation, and =
I do plan to add<br>
&gt; &gt;&gt; that to json-sync, since it&#39;s a good way to make applicat=
ion-specific<br>
&gt; &gt;&gt; assertions.<br>
&gt; &gt;<br>
&gt; &gt; Yes, you&#39;ve brought that to our attention several times. If y=
ou wanted this spec to align with your software, it would have been much ea=
sier if you&#39;d got involved before Last Call.<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt;&gt;&gt; However, I&#39;m even more interested in getting this for=
mat published,<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt; Well, I guess someone has something they want to ship...<br>
&gt; &gt;<br>
&gt; &gt; Right. I&#39;ll let that statement stand on its own; I think anyo=
ne who&#39;s been participating or watching the WG can assess how justified=
 it is.<br>
&gt; &gt;<br>
&gt; &gt; Always a pleasure, Rob.<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt; - Rob<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt;&gt; Cheers,<br>
&gt; &gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt; On 06/01/2013, at 11:19 AM, Robert Sayre &lt;<a href=3D"m=
ailto:sayrer@gmail.com">sayrer@gmail.com</a>&gt; wrote:<br>
&gt; &gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt; Mark,<br>
&gt; &gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt; The WG&#39;s reasoning, as stated in your message bel=
ow, seems flawed.<br>
&gt; &gt;&gt;&gt;&gt; Messages since your last communication on this matter=
 have shown:<br>
&gt; &gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt; 1) The ambiguity around arrays makes the patch format=
 unsuitable for<br>
&gt; &gt;&gt;&gt;&gt; common concurrent editing algorithms.<br>
&gt; &gt;&gt;&gt;&gt; 2) The ambiguity is likely to occur in the real world=
, for a couple of<br>
&gt; &gt;&gt;&gt;&gt; different reasons.<br>
&gt; &gt;&gt;&gt;&gt; 3) It&#39;s not possible to tell whether a JSON Point=
er document is<br>
&gt; &gt;&gt;&gt;&gt; syntactically correct in isolation.<br>
&gt; &gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt; Additionally, you raised this point in your message b=
elow:<br>
&gt; &gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt; the patch author already has to understand the se=
mantics of the document they&#39;re patching<br>
&gt; &gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt; That claim does not seem to be well-justified, and it=
 could be<br>
&gt; &gt;&gt;&gt;&gt; meaningless to the person implementing patch software=
 (for example:<br>
&gt; &gt;&gt;&gt;&gt; <a href=3D"https://github.com/sayrer/json-sync">https=
://github.com/sayrer/json-sync</a>).<br>
&gt; &gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt; This issue is a problem in practice, and it&#39;s a p=
roblem in theory as<br>
&gt; &gt;&gt;&gt;&gt; well. JSON-Patch messages aren&#39;t sufficiently sel=
f-descriptive, so<br>
&gt; &gt;&gt;&gt;&gt; they aren&#39;t appropriate for use in a RESTful syst=
em.<br>
&gt; &gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt; A response containing technical reasoning seems in or=
der, since the<br>
&gt; &gt;&gt;&gt;&gt; points raised by myself and others on this issue are =
unrelated to the<br>
&gt; &gt;&gt;&gt;&gt; WG&#39;s previous thinking.<br>
&gt; &gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt; - Rob<br>
&gt; &gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt; On Sun, Dec 16, 2012 at 9:41 PM, Mark Nottingham &lt;=
<a href=3D"mailto:mnot@mnot.net">mnot@mnot.net</a>&gt; wrote:<br>
&gt; &gt;&gt;&gt;&gt;&gt; Robert,<br>
&gt; &gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt; This was discussed extensively in the Working Gro=
up.<br>
&gt; &gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt; The root of the issue was that some people reflex=
ively felt that this was necessary, but upon reflection, we decided it wasn=
&#39;t; although it seems &quot;natural&quot; to some, especially those com=
ing from a static language background, it didn&#39;t provide any utility.<b=
r>

&gt; &gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt; You might argue that someone who (for example) ad=
ds to &quot;/foo/1&quot; in the mistaken belief that it&#39;s an array, whe=
n in fact it&#39;s an object, will get surprising results. That&#39;s true,=
 but if we were to solve this problem, that person would still need to unde=
rstand the underlying semantics of &quot;foo&quot; to do anything useful to=
 it -- and I&#39;m not hearing anyone complain about that (I hope).<br>

&gt; &gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt; Put another way -- do you really think that peopl=
e PATCHing something as if it&#39;s an array (when in fact it&#39;s an obje=
ct) is a significant, real-world problem, given that the patch author alrea=
dy has to understand the semantics of the document they&#39;re patching? I =
don&#39;t, and the WG didn&#39;t either.<br>

&gt; &gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt; Regards,<br>
&gt; &gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt; On 17/12/2012, at 3:36 PM, Robert Sayre &lt;<a hr=
ef=3D"mailto:sayrer@gmail.com">sayrer@gmail.com</a>&gt; wrote:<br>
&gt; &gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt; The cost of fixing it seems low, either by ch=
anging the path syntax of<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt; JSON pointer or changing the names of operati=
ons applied to arrays.<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt; Array-like objects are common enough in JavaS=
cript to make this a<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt; worry. The other suggestions either assume a =
particular policy for<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt; concurrent edits or require more machinery (t=
est operation etc).<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt; Wouldn&#39;t it be simpler to make the patch =
format more precise?<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt; - Rob<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt; On Sun, Dec 16, 2012 at 4:33 PM, Matthew Morl=
ey &lt;<a href=3D"mailto:matt@mpcm.com">matt@mpcm.com</a>&gt; wrote:<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt; I am usually lurking and struggling to ke=
ep up with these posts. But, I<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt; concur with James, this really is a non-i=
ssue in practice.<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt; The JSON Pointer expresses a path down a =
JSON object to a specific context.<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt; The Patch expresses a change within or to=
 that context.<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt; Everything about the both standards is ab=
out that end context.<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt; If you want to confirm the type of the co=
ntext before applying a patch, this<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt; should probably be part of a test operati=
on. I&#39;m not sure if this is<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt; possible at this point (?), but that is w=
here the logic should exist.<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt; On Sun, Dec 16, 2012 at 12:22 AM, James M=
 Snell &lt;<a href=3D"mailto:jasnell@gmail.com">jasnell@gmail.com</a>&gt; w=
rote:<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; On Sat, Dec 15, 2012 at 8:36 PM, Robe=
rt Sayre &lt;<a href=3D"mailto:sayrer@gmail.com">sayrer@gmail.com</a>&gt; w=
rote:<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; On Fri, Dec 14, 2012 at 9:17 AM, =
Markus Lanthaler<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; &lt;<a href=3D"mailto:markus.lant=
haler@gmx.net">markus.lanthaler@gmx.net</a>&gt; wrote:<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; Hmm.. I think that=E2=80=99s =
quite problematic. Especially considering how JSON<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; Pointer is used in JSON Patch=
.<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; I agree--I provided the same feed=
back privately. It seems<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; straightforwardly unsound.<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; In practice it doesn&#39;t seem to be=
 much of an issue.<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; Specifically, if I GET an existing do=
cument and get an etag with the JSON,<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; then make some changes and send a PAT=
CH with If-Match, the fact that any<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; given pointer could point to an array=
 or object member doesn&#39;t really matter<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; much.<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; For example:<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; GET /the/doc HTTP/1.1<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; &lt; =C2=A0HTTP/1.1 200 OK<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; =C2=A0 ETag: &quot;my-document-tag&qu=
ot;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; =C2=A0 Content-Type: application/json=
<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; =C2=A0 {&quot;1&quot;:&quot;foo&quot;=
}<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; PATCH /the/doc HTTP/1.1<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; =C2=A0 If-Match: &quot;my-document-et=
ag&quot;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; =C2=A0 Content-Type: application/json=
-patch<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; =C2=A0 [{&quot;op&quot;:&quot;add&quo=
t;,&quot;path&quot;:&quot;/2&quot;,&quot;value&quot;:&quot;bar&quot;}]<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; Generally speaking, someone should no=
t be using PATCH to perform a partial<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; modification if they don&#39;t alread=
y have some knowledge in advance what they<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; are modifying. The only time the appa=
rent ambiguity becomes an issue is when<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; a client is blindly sending a patch t=
o an unknown endpoint... in which case,<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; you get whatever you end up with.<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; - James<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; - Rob<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; --<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; Markus Lanthaler<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; @markuslanthaler<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; From: James M Snell [mailto:<=
a href=3D"mailto:jasnell@gmail.com">jasnell@gmail.com</a>]<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; Sent: Friday, December 14, 20=
12 5:41 PM<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; To: Markus Lanthaler<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; Cc: IETF Discussion; IETF App=
s Discuss<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; Subject: Re: [apps-discuss] L=
ast Call:<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; &lt;draft-ietf-appsawg-json-p=
ointer-07.txt&gt; (JSON Pointer) to Proposed Standard<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; JSON Pointer does not disting=
uish between objects and arrays. That is<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; not determined until the poin=
ter is applied to an actual object instance...<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; the pointer &quot;/1&quot; is=
 valid against {&quot;1&quot;:&quot;a&quot;} or [&quot;a&quot;,&quot;b&quot=
;]<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; On Fri, Dec 14, 2012 at 2:51 =
AM, Markus Lanthaler<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; &lt;<a href=3D"mailto:markus.=
lanthaler@gmx.net">markus.lanthaler@gmx.net</a>&gt; wrote:<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; I&#39;ve asked that before bu=
t didn&#39;t get an answer. So let me ask again<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; (even<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; though I&#39;m quite sure it =
has already been asked by somebody else).<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; How does JSON Pointer disting=
uish between objects and arrays? E.g.<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; consider<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; the following JSON document:<=
br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; {<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; &quot;foo&quot;: &quot;bar&qu=
ot;,<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; &quot;1&quot;: &quot;baz&quot=
;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; }<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; As I read the draft, the JSON=
 Pointer &quot;/1&quot; would evaluate to &quot;baz&quot; even<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; though that&#39;s probably no=
t what the author intended. Is there a way to<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; avoid<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; that?<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; Thanks,<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; Markus<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; --<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; Markus Lanthaler<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; @markuslanthaler<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; -----Original Message----=
-<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; From: <a href=3D"mailto:a=
pps-discuss-bounces@ietf.org">apps-discuss-bounces@ietf.org</a> [mailto:<a =
href=3D"mailto:apps-discuss-">apps-discuss-</a><br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; <a href=3D"mailto:bounces=
@ietf.org">bounces@ietf.org</a>] On Behalf Of The IESG<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; Sent: Tuesday, December 1=
1, 2012 4:01 PM<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; To: IETF-Announce<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; Cc: <a href=3D"mailto:app=
s-discuss@ietf.org">apps-discuss@ietf.org</a><br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; Subject: [apps-discuss] L=
ast Call: &lt;draft-ietf-appsawg-json-pointer-<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; 07.txt&gt; (JSON Pointer)=
 to Proposed Standard<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; The IESG has received a r=
equest from the Applications Area Working<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; Group<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; WG (appsawg) to consider =
the following document:<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; - &#39;JSON Pointer&#39;<=
br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; &lt;draft-ietf-appsawg-js=
on-pointer-07.txt&gt; as Proposed Standard<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; The IESG plans to make a =
decision in the next few weeks, and solicits<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; final comments on this ac=
tion. Please send substantive comments to<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; the<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; <a href=3D"mailto:ietf@ie=
tf.org">ietf@ietf.org</a> mailing lists by 2012-12-25. Exceptionally, comme=
nts<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; may<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; be<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; sent to <a href=3D"mailto=
:iesg@ietf.org">iesg@ietf.org</a> instead. In either case, please retain th=
e<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; beginning of the Subject =
line to allow automated sorting.<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; Abstract<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; JSON Pointer defines a st=
ring syntax for identifying a specific<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; value<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; within a JSON document.<b=
r>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; The file can be obtained =
via<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; <a href=3D"http://datatra=
cker.ietf.org/doc/draft-ietf-appsawg-json-pointer/">http://datatracker.ietf=
.org/doc/draft-ietf-appsawg-json-pointer/</a><br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; IESG discussion can be tr=
acked via<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; <a href=3D"http://datatra=
cker.ietf.org/doc/draft-ietf-appsawg-json-pointer/ballot/">http://datatrack=
er.ietf.org/doc/draft-ietf-appsawg-json-pointer/ballot/</a><br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; No IPR declarations have =
been submitted directly on this I-D.<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; _________________________=
______________________<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; apps-discuss mailing list=
<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; <a href=3D"mailto:apps-di=
scuss@ietf.org">apps-discuss@ietf.org</a><br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; <a href=3D"https://www.ie=
tf.org/mailman/listinfo/apps-discuss">https://www.ietf.org/mailman/listinfo=
/apps-discuss</a><br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; _____________________________=
__________________<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; apps-discuss mailing list<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; <a href=3D"mailto:apps-discus=
s@ietf.org">apps-discuss@ietf.org</a><br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; <a href=3D"https://www.ietf.o=
rg/mailman/listinfo/apps-discuss">https://www.ietf.org/mailman/listinfo/app=
s-discuss</a><br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; _____________________________=
__________________<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; apps-discuss mailing list<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; <a href=3D"mailto:apps-discus=
s@ietf.org">apps-discuss@ietf.org</a><br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; <a href=3D"https://www.ietf.o=
rg/mailman/listinfo/apps-discuss">https://www.ietf.org/mailman/listinfo/app=
s-discuss</a><br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; _____________________________________=
__________<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; apps-discuss mailing list<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; <a href=3D"mailto:apps-discuss@ietf.o=
rg">apps-discuss@ietf.org</a><br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; <a href=3D"https://www.ietf.org/mailm=
an/listinfo/apps-discuss">https://www.ietf.org/mailman/listinfo/apps-discus=
s</a><br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt; --<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt; Matthew P. C. Morley<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt; _____________________________________________=
__<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt; apps-discuss mailing list<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt; <a href=3D"mailto:apps-discuss@ietf.org">apps=
-discuss@ietf.org</a><br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt; <a href=3D"https://www.ietf.org/mailman/listi=
nfo/apps-discuss">https://www.ietf.org/mailman/listinfo/apps-discuss</a><br=
>
&gt; &gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt; --<br>
&gt; &gt;&gt;&gt;&gt;&gt; Mark Nottingham =C2=A0 <a href=3D"http://www.mnot=
.net/">http://www.mnot.net/</a><br>
&gt; &gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt; --<br>
&gt; &gt;&gt;&gt; Mark Nottingham =C2=A0 <a href=3D"http://www.mnot.net/">h=
ttp://www.mnot.net/</a><br>
&gt; &gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;<br>
&gt; &gt;<br>
&gt; &gt; --<br>
&gt; &gt; Mark Nottingham =C2=A0 <a href=3D"http://www.mnot.net/">http://ww=
w.mnot.net/</a><br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; _______________________________________________<br>
&gt; apps-discuss mailing list<br>
&gt; <a href=3D"mailto:apps-discuss@ietf.org">apps-discuss@ietf.org</a><br>
&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/apps-discuss">https:/=
/www.ietf.org/mailman/listinfo/apps-discuss</a><br>
</p>

--e89a8f839ca1f5860704d2978658--

From sayrer@gmail.com  Sat Jan  5 21:25:41 2013
Return-Path: <sayrer@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C2AC021F8753; Sat,  5 Jan 2013 21:25:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 IvHT6tDIrukH; Sat,  5 Jan 2013 21:25:41 -0800 (PST)
Received: from mail-we0-f171.google.com (mail-we0-f171.google.com [74.125.82.171]) by ietfa.amsl.com (Postfix) with ESMTP id D330D21F873C; Sat,  5 Jan 2013 21:25:40 -0800 (PST)
Received: by mail-we0-f171.google.com with SMTP id u3so9065471wey.30 for <multiple recipients>; Sat, 05 Jan 2013 21:25:40 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=65iawI3jB5FxP+ZcgrYq6XU0Ocp9ArB1mf44MYln13c=; b=fzdavCgh9eyvwZZGfIsj75/dnRlVUjmj9RbwEYIjgoIHhu1xUKksEgYlk6D0hoedmG nBW8uulRS5ohZRFDN9Q41GGqHJvBfy1EiB22kln1omTkqqwnaz/BGQnGwCgbprQBa0h4 lJG4nV7li0w45fREiUiA5FiopNtuUUMyKEceA1ktIv7zNQ5XL5YoP/j28VIvkafzxFuS LBp+WnCZ5sDMJEpGcgGg8OazK/DJ9zGH+t2Sf3TOF0j8I5O9IvKip1IhXFuTl2Y6E0M1 bvXIsqhWaPodtor4pdHb7xSKMT1E8jdNsburipVvYtdUvfWfbtAI6SB3BQXuawJDT/TV fH1Q==
MIME-Version: 1.0
Received: by 10.194.76.99 with SMTP id j3mr90845663wjw.47.1357449940101; Sat, 05 Jan 2013 21:25:40 -0800 (PST)
Received: by 10.194.1.101 with HTTP; Sat, 5 Jan 2013 21:25:40 -0800 (PST)
In-Reply-To: <CABP7RbcQARMAvisv4zUPX7+t97MQ_vwizBCiUBt6Nc7y7CapYQ@mail.gmail.com>
References: <20121211150057.28223.93310.idtracker@ietfa.amsl.com> <50cb04b9.86df440a.72fe.1e20SMTPIN_ADDED_BROKEN@mx.google.com> <CABP7RbeNsZ_rBWRjou=VG+hBhUKaOz+y1a0sSChwWiHte9znnQ@mail.gmail.com> <50cb5f3c.694c420a.38fb.39afSMTPIN_ADDED_BROKEN@mx.google.com> <CAChr6SxZRc3B_HCbw76kLe2dsRSr43r-gLpfMVnCUfJTrZdTLA@mail.gmail.com> <CABP7RbfA33huBFadMeXTTEt=MkjW8-d4DFH7+GLXGurnm9sSRw@mail.gmail.com> <CAOXDeqpPE4eNy_qJpDPdPHbCQakG9-hDcNZ3Sj9r4kWedByVzQ@mail.gmail.com> <CAChr6SwtS_=iS-k4mJm1vHjEvvGVzay5jDYeGheqsPZqO-89CQ@mail.gmail.com> <EABB8F51-C3B4-49F5-8672-5C2ABAC7043A@mnot.net> <CAChr6Sx7JdKM91EwJaSZ0Ra_F4FSqkuc3vzTY1LM=F_8sWho+Q@mail.gmail.com> <263BA4B0-6401-4391-A369-A90863D9A4BC@mnot.net> <CAChr6Sw-hZwzB423qvkqyGfq8Aw6Jry-=B9zSzgp2GwbX6gQQg@mail.gmail.com> <E17FB936-BB87-4711-BEFB-21714B746B71@mnot.net> <CAChr6Sw_GJUE715G_E9DBSz57OvtVjzpU69nk9WwJzz3NPg8AA@mail.gmail.com> <CABP7RbcQARMAvisv4zUPX7+t97MQ_vwizBCiUBt6Nc7y7CapYQ@mail.gmail.com>
Date: Sat, 5 Jan 2013 21:25:40 -0800
Message-ID: <CAChr6Sxn1WXHb5cesUk8fa6=A6bxh8xhJW_WQ8mABPWbSZgtew@mail.gmail.com>
Subject: Re: [apps-discuss] Last Call: <draft-ietf-appsawg-json-pointer-07.txt> (JSON Pointer) to Proposed Standard
From: Robert Sayre <sayrer@gmail.com>
To: James M Snell <jasnell@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: Mark Nottingham <mnot@mnot.net>, IETF Discussion <ietf@ietf.org>, IETF Apps Discuss <apps-discuss@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 06 Jan 2013 05:25:41 -0000

On Sat, Jan 5, 2013 at 8:55 PM, James M Snell <jasnell@gmail.com> wrote:
>
> On Jan 5, 2013 8:20 PM, "Robert Sayre" <sayrer@gmail.com> wrote:
>>
>> On Sat, Jan 5, 2013 at 6:59 PM, Mark Nottingham <mnot@mnot.net> wrote:
>> >
>> > Yes, you've brought that to our attention several times. If you wanted
>> > this spec to align with your software, it would have been much easier
>> > if you'd got involved before Last Call.
>>
>> Well, there shouldn't be any big adjustments to my software at all,
>> and the document generally looks good. This is just a bug: two parties
>> can apply the same patch and get different results, without
>> encountering an error.
>>
>
> Not seeing the bug... applying the same patch to different resources that
> have different states ought to have different results.

This argument is fallacious. Consider this JSON patch:

{ "op": "remove", "path": "/1" }

This patch can be generated by removing a key from a hashtable by the
sender, and then applied to an array by the recipient (which may
result in array shifts etc). A good quality patch format would not
permit such an obvious ambiguity, because applying that patch can fail
all parties. The resulting document does not reflect the intent of any
author.

I have obviously said my piece. And, fwiw, I don't think the IESG
should contradict the WG.

- Rob

From jasnell@gmail.com  Sat Jan  5 21:58:56 2013
Return-Path: <jasnell@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A9E1B21F8756; Sat,  5 Jan 2013 21:58:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.598
X-Spam-Level: 
X-Spam-Status: No, score=-3.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
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 HpckNnA7+mE7; Sat,  5 Jan 2013 21:58:56 -0800 (PST)
Received: from mail-ia0-f174.google.com (mail-ia0-f174.google.com [209.85.210.174]) by ietfa.amsl.com (Postfix) with ESMTP id E65DD21F8732; Sat,  5 Jan 2013 21:58:55 -0800 (PST)
Received: by mail-ia0-f174.google.com with SMTP id y25so14908766iay.5 for <multiple recipients>; Sat, 05 Jan 2013 21:58:55 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=kZAtZHaF12CbwG28Kw5Lfr7sTXTN1zEibcbShC+7+EA=; b=aBpf/KB4fDPQhSvRkJ8b2ZGF9tptJlUP3EdL4PCGyU3xki8UAtbOyX99SD1kKtimfp ZxIri9HO3x30mY40pB1DJ5Lq3Z0ApnB2eYk+16kSlQxHftt6uve0GYriH7yQoR8LjxK6 qN2zzPGnvYVyIAOSkVqY3ScS/L54eGpGb39ZSdhA/x65l46p9xmE0pkc9HN8urIiTWaZ DT5g63bepR5NWo5H8bWL14DGuX5uclDgPQATZf8cXK2EzY8KCcg7yGKGgRKvDV67naov +W9kSQK7DgHiK5SwworSzkKnlIo8EHPa7+SrigfQob5/vxtnP3RzaB4lVPUqcGATs30h lyFQ==
MIME-Version: 1.0
X-Received: by 10.50.219.233 with SMTP id pr9mr2746714igc.19.1357451935539; Sat, 05 Jan 2013 21:58:55 -0800 (PST)
Received: by 10.64.7.19 with HTTP; Sat, 5 Jan 2013 21:58:55 -0800 (PST)
Received: by 10.64.7.19 with HTTP; Sat, 5 Jan 2013 21:58:55 -0800 (PST)
In-Reply-To: <CAChr6Sxn1WXHb5cesUk8fa6=A6bxh8xhJW_WQ8mABPWbSZgtew@mail.gmail.com>
References: <20121211150057.28223.93310.idtracker@ietfa.amsl.com> <50cb04b9.86df440a.72fe.1e20SMTPIN_ADDED_BROKEN@mx.google.com> <CABP7RbeNsZ_rBWRjou=VG+hBhUKaOz+y1a0sSChwWiHte9znnQ@mail.gmail.com> <50cb5f3c.694c420a.38fb.39afSMTPIN_ADDED_BROKEN@mx.google.com> <CAChr6SxZRc3B_HCbw76kLe2dsRSr43r-gLpfMVnCUfJTrZdTLA@mail.gmail.com> <CABP7RbfA33huBFadMeXTTEt=MkjW8-d4DFH7+GLXGurnm9sSRw@mail.gmail.com> <CAOXDeqpPE4eNy_qJpDPdPHbCQakG9-hDcNZ3Sj9r4kWedByVzQ@mail.gmail.com> <CAChr6SwtS_=iS-k4mJm1vHjEvvGVzay5jDYeGheqsPZqO-89CQ@mail.gmail.com> <EABB8F51-C3B4-49F5-8672-5C2ABAC7043A@mnot.net> <CAChr6Sx7JdKM91EwJaSZ0Ra_F4FSqkuc3vzTY1LM=F_8sWho+Q@mail.gmail.com> <263BA4B0-6401-4391-A369-A90863D9A4BC@mnot.net> <CAChr6Sw-hZwzB423qvkqyGfq8Aw6Jry-=B9zSzgp2GwbX6gQQg@mail.gmail.com> <E17FB936-BB87-4711-BEFB-21714B746B71@mnot.net> <CAChr6Sw_GJUE715G_E9DBSz57OvtVjzpU69nk9WwJzz3NPg8AA@mail.gmail.com> <CABP7RbcQARMAvisv4zUPX7+t97MQ_vwizBCiUBt6Nc7y7CapYQ@mail.gmail.com> <CAChr6Sxn1WXHb5cesUk8fa6=A6bxh8xhJW_WQ8mABPWbSZgtew@mail.gmail.com>
Date: Sat, 5 Jan 2013 21:58:55 -0800
Message-ID: <CABP7Rbc2MyFtr9LWKZHfFzsa7Efd8syfJ+9kAksuFOyztLdoLA@mail.gmail.com>
Subject: Re: [apps-discuss] Last Call: <draft-ietf-appsawg-json-pointer-07.txt> (JSON Pointer) to Proposed Standard
From: James M Snell <jasnell@gmail.com>
To: Rob Sayre <sayrer@gmail.com>
Content-Type: multipart/alternative; boundary=14dae934120f6ae03304d2986821
Cc: Mark Nottingham <mnot@mnot.net>, IETF Discussion <ietf@ietf.org>, IETF Apps Discuss <apps-discuss@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 06 Jan 2013 05:58:56 -0000

--14dae934120f6ae03304d2986821
Content-Type: text/plain; charset=UTF-8

[{"op":"type","path":"","value":"array"},{"op":"remove","path":"/1"}]

Problem solved. Still no bug, and still nothing I can see that needs
fixing.

I've said my piece on it to. Afaic, this spec is done and ready to go.

- James
 On Jan 5, 2013 9:25 PM, "Robert Sayre" <sayrer@gmail.com> wrote:

> On Sat, Jan 5, 2013 at 8:55 PM, James M Snell <jasnell@gmail.com> wrote:
> >
> > On Jan 5, 2013 8:20 PM, "Robert Sayre" <sayrer@gmail.com> wrote:
> >>
> >> On Sat, Jan 5, 2013 at 6:59 PM, Mark Nottingham <mnot@mnot.net> wrote:
> >> >
> >> > Yes, you've brought that to our attention several times. If you wanted
> >> > this spec to align with your software, it would have been much easier
> >> > if you'd got involved before Last Call.
> >>
> >> Well, there shouldn't be any big adjustments to my software at all,
> >> and the document generally looks good. This is just a bug: two parties
> >> can apply the same patch and get different results, without
> >> encountering an error.
> >>
> >
> > Not seeing the bug... applying the same patch to different resources that
> > have different states ought to have different results.
>
> This argument is fallacious. Consider this JSON patch:
>
> { "op": "remove", "path": "/1" }
>
> This patch can be generated by removing a key from a hashtable by the
> sender, and then applied to an array by the recipient (which may
> result in array shifts etc). A good quality patch format would not
> permit such an obvious ambiguity, because applying that patch can fail
> all parties. The resulting document does not reflect the intent of any
> author.
>
> I have obviously said my piece. And, fwiw, I don't think the IESG
> should contradict the WG.
>
> - Rob
>

--14dae934120f6ae03304d2986821
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<p dir=3D"ltr">[{&quot;op&quot;:&quot;type&quot;,&quot;path&quot;:&quot;&qu=
ot;,&quot;value&quot;:&quot;array&quot;},{&quot;op&quot;:&quot;remove&quot;=
,&quot;path&quot;:&quot;/1&quot;}]</p>
<p dir=3D"ltr">Problem solved. Still no bug, and still nothing I can see th=
at needs fixing. </p>
<p dir=3D"ltr">I&#39;ve said my piece on it to. Afaic, this spec is done an=
d ready to go. </p>
<p dir=3D"ltr">- James<br>
</p>
<div class=3D"gmail_quote">On Jan 5, 2013 9:25 PM, &quot;Robert Sayre&quot;=
 &lt;<a href=3D"mailto:sayrer@gmail.com">sayrer@gmail.com</a>&gt; wrote:<br=
 type=3D"attribution"><blockquote class=3D"gmail_quote" style=3D"margin:0 0=
 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On Sat, Jan 5, 2013 at 8:55 PM, James M Snell &lt;<a href=3D"mailto:jasnell=
@gmail.com">jasnell@gmail.com</a>&gt; wrote:<br>
&gt;<br>
&gt; On Jan 5, 2013 8:20 PM, &quot;Robert Sayre&quot; &lt;<a href=3D"mailto=
:sayrer@gmail.com">sayrer@gmail.com</a>&gt; wrote:<br>
&gt;&gt;<br>
&gt;&gt; On Sat, Jan 5, 2013 at 6:59 PM, Mark Nottingham &lt;<a href=3D"mai=
lto:mnot@mnot.net">mnot@mnot.net</a>&gt; wrote:<br>
&gt;&gt; &gt;<br>
&gt;&gt; &gt; Yes, you&#39;ve brought that to our attention several times. =
If you wanted<br>
&gt;&gt; &gt; this spec to align with your software, it would have been muc=
h easier<br>
&gt;&gt; &gt; if you&#39;d got involved before Last Call.<br>
&gt;&gt;<br>
&gt;&gt; Well, there shouldn&#39;t be any big adjustments to my software at=
 all,<br>
&gt;&gt; and the document generally looks good. This is just a bug: two par=
ties<br>
&gt;&gt; can apply the same patch and get different results, without<br>
&gt;&gt; encountering an error.<br>
&gt;&gt;<br>
&gt;<br>
&gt; Not seeing the bug... applying the same patch to different resources t=
hat<br>
&gt; have different states ought to have different results.<br>
<br>
This argument is fallacious. Consider this JSON patch:<br>
<br>
{ &quot;op&quot;: &quot;remove&quot;, &quot;path&quot;: &quot;/1&quot; }<br=
>
<br>
This patch can be generated by removing a key from a hashtable by the<br>
sender, and then applied to an array by the recipient (which may<br>
result in array shifts etc). A good quality patch format would not<br>
permit such an obvious ambiguity, because applying that patch can fail<br>
all parties. The resulting document does not reflect the intent of any<br>
author.<br>
<br>
I have obviously said my piece. And, fwiw, I don&#39;t think the IESG<br>
should contradict the WG.<br>
<br>
- Rob<br>
</blockquote></div>

--14dae934120f6ae03304d2986821--

From abdussalambaryun@gmail.com  Sun Jan  6 00:41:04 2013
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A6A8B21F8797 for <ietf@ietfa.amsl.com>; Sun,  6 Jan 2013 00:41:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 AIoeTdtb6-W4 for <ietf@ietfa.amsl.com>; Sun,  6 Jan 2013 00:41:04 -0800 (PST)
Received: from mail-vc0-f169.google.com (mail-vc0-f169.google.com [209.85.220.169]) by ietfa.amsl.com (Postfix) with ESMTP id E848421F87AB for <ietf@ietf.org>; Sun,  6 Jan 2013 00:41:03 -0800 (PST)
Received: by mail-vc0-f169.google.com with SMTP id gb23so17963879vcb.14 for <ietf@ietf.org>; Sun, 06 Jan 2013 00:41:03 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:cc:content-type; bh=U5gyhwPrbjYAzxSjahPu/itdTEceYwX2cexLjDWpevw=; b=rwzoZyjReAXK+HZu/r++RWEcayiLovb+EGr/4oQLRBDIIM822omtDj8DgmNmcUL6t3 1m8iHozbEfsTs0GaSIQibMUbchIOwAvwjK+M+J+R8G07EKDsi3QssfUUIHxy/mlhneJ8 I34v1veENFp80UrqeSzT4ICEMvHiP/hyFpC8wLlBOKjvuzgNDxjeSqeRLULNGUCzEhqj yGf4zJ2Ghk2d0OySpTKESa1KZqzg8AKvF0Xtdsy1is9nn6DJ98Z9E56u0lAb76uH3qWf oAlxO3VqxQYWJCkTu12jCiAQPxmRNzsfKU1Ptdz4OJgdIks9+wJ+yg5ORCHGO5mf6X+m GVGA==
MIME-Version: 1.0
Received: by 10.58.252.72 with SMTP id zq8mr83419911vec.20.1357461663384; Sun, 06 Jan 2013 00:41:03 -0800 (PST)
Received: by 10.220.145.5 with HTTP; Sun, 6 Jan 2013 00:41:03 -0800 (PST)
Date: Sun, 6 Jan 2013 09:41:03 +0100
Message-ID: <CADnDZ8_GgVeapUKefFMqOvwOo00X8_rFDWMR0vb-Zvu_p=yT3A@mail.gmail.com>
Subject: Re: A proposal for a scientific approach to this question [was Re: I'm struggling with 2219 language again]
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: petithug@acm.org
Content-Type: text/plain; charset=ISO-8859-1
Cc: ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 06 Jan 2013 08:41:04 -0000

Hi Marc Petit-Huguenin ,

>I read the responses so far, and what can be said today is that there is 2
philosophies, with supporters in both camps.  The goal of the IETF is to make
the Internet work better, and I do believe that RFC 2119 is one of the
fundamental tool to reach this goal, but having two ways to use it does not
help this goal.

I like the approach, and agree with you that we need a solution in
IETF which still is not solved or ignored by participants fo some
reasons. However, I agree of a survey or an experiment what ever we
call it, that makes IETF reflects to the RFC2119 performance on the
end-user of such product implementation of RFC protocols. I think many
old participants already have good experience to inform us of some
reality of IETF standards' end-user production.

AB

From abdussalambaryun@gmail.com  Sun Jan  6 00:59:47 2013
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BBABC21F880E for <ietf@ietfa.amsl.com>; Sun,  6 Jan 2013 00:59:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 PbdZtyWkhynF for <ietf@ietfa.amsl.com>; Sun,  6 Jan 2013 00:59:47 -0800 (PST)
Received: from mail-vc0-f172.google.com (mail-vc0-f172.google.com [209.85.220.172]) by ietfa.amsl.com (Postfix) with ESMTP id 38ABE21F8758 for <ietf@ietf.org>; Sun,  6 Jan 2013 00:59:47 -0800 (PST)
Received: by mail-vc0-f172.google.com with SMTP id fw7so18574008vcb.3 for <ietf@ietf.org>; Sun, 06 Jan 2013 00:59:46 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:cc:content-type; bh=YYhh5km5j7kE9zJr4pzCwScH4m4Oz6f799oypO21Af0=; b=zERSaEiftsN5VTh1KDSjbp+kOIrYhE4vCCOln6T2pbDFhteJmuIg6dhinCXvrpBSiH xsSmrLXHyYIhH11RHkWfocAYce4aZ9sYbkfhOC0Y/aw8dv9srFGK+WkAmp+lI8ff01uf yMxpdrzL77waqnPbeqV56g7WxU6o40JKzTgHgVt7I+1+hPN4D5Oj4v06kfJJI5F2lPZs sBe6CCrKCUBvnZc+rmJaM92uZvSueOG7SZfwyKU2nRnyfEgkzTWdVa4OxAS3j9TSkvLC gf4VcLWsKU7qIEQw9mlcgs2WHCC0gHrx9GwYR72CuuiAOsOpW2f6pi+4UKK0OaT8MjcJ SppA==
MIME-Version: 1.0
Received: by 10.52.21.179 with SMTP id w19mr70681196vde.55.1357462786488; Sun, 06 Jan 2013 00:59:46 -0800 (PST)
Received: by 10.220.145.5 with HTTP; Sun, 6 Jan 2013 00:59:46 -0800 (PST)
Date: Sun, 6 Jan 2013 09:59:46 +0100
Message-ID: <CADnDZ896FUhWJQyGVu54tv=hvC5FZDxKMowhdxk0GM1C9LrrNw@mail.gmail.com>
Subject: Re: [apps-discuss] Last Call: <draft-ietf-appsawg-json-pointer-07.txt> (JSON Pointer) to Proposed Standard
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: mnot@mnot.net
Content-Type: text/plain; charset=ISO-8859-1
Cc: ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 06 Jan 2013 08:59:47 -0000

>Yes, you've brought that to our attention several times. If you wanted this spec to align with your software, it would have been much easier if you'd got involved before Last Call.

Why is it called <Last Call> if we don't accept any new input (e.g.,
draft-ietf-appsawg-json-pointer-07) . Why do we call RFC <Request For
Comment> if we don't want people to comment on (e.g. RFC2119).

We SHOULD discuss any input any time, thank the participant, and
accept only consensus on each input at any phase of time.

AB

From sayrer@gmail.com  Sun Jan  6 04:09:13 2013
Return-Path: <sayrer@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 447C421F8788 for <ietf@ietfa.amsl.com>; Sun,  6 Jan 2013 04:09:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 sBCMGbKI2B2K for <ietf@ietfa.amsl.com>; Sun,  6 Jan 2013 04:09:12 -0800 (PST)
Received: from mail-we0-f181.google.com (mail-we0-f181.google.com [74.125.82.181]) by ietfa.amsl.com (Postfix) with ESMTP id 5E7E121F8778 for <ietf@ietf.org>; Sun,  6 Jan 2013 04:09:11 -0800 (PST)
Received: by mail-we0-f181.google.com with SMTP id t11so8846895wey.26 for <ietf@ietf.org>; Sun, 06 Jan 2013 04:09:11 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=sSQ/1BsCJEFXefeYrYoAhrSWoKsezj0YZWurytYQky0=; b=QQWFfBdZ1DWgpbe3RYf4AFP6NuS9Kb3PWXaZfT9f8sazYX+Asd8qM/XeV2pk10jaJk JkK8JzllNV8/n7qlSlsINcCJRMDCPH0UEia+tJHSNyuqs+DNHRyiMObVWqxYkBVNqw9R qaawe2Hp3npj4G6IoJB/zHky7yPS7wxPEIlUVivhJ87fMZ+YB+kseAwnqNU60sZhRw3P QMZfTP8ejzMr0/hJmJJ7lUckUM355myqwpZ07BGY0ZBpzgeG2CAS2LibFxzJZym2FOTA y4Y1NmFlIngsrH6QngqFh3gMO5OLyKU05aEoBAr+lB763zUF3ogIFELv7I7YlYiuB2f+ 99Fg==
MIME-Version: 1.0
Received: by 10.180.73.80 with SMTP id j16mr4844285wiv.5.1357474151160; Sun, 06 Jan 2013 04:09:11 -0800 (PST)
Received: by 10.194.1.101 with HTTP; Sun, 6 Jan 2013 04:09:11 -0800 (PST)
In-Reply-To: <CADnDZ896FUhWJQyGVu54tv=hvC5FZDxKMowhdxk0GM1C9LrrNw@mail.gmail.com>
References: <CADnDZ896FUhWJQyGVu54tv=hvC5FZDxKMowhdxk0GM1C9LrrNw@mail.gmail.com>
Date: Sun, 6 Jan 2013 04:09:11 -0800
Message-ID: <CAChr6SxibLyp1WBskouGEH6G8ki_xt=7fex3Wg_6z8DExP89Kw@mail.gmail.com>
Subject: Re: [apps-discuss] Last Call: <draft-ietf-appsawg-json-pointer-07.txt> (JSON Pointer) to Proposed Standard
From: Robert Sayre <sayrer@gmail.com>
To: Abdussalam Baryun <abdussalambaryun@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: mnot@mnot.net, ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 06 Jan 2013 12:09:13 -0000

On Sun, Jan 6, 2013 at 12:59 AM, Abdussalam Baryun
<abdussalambaryun@gmail.com> wrote:
>>Yes, you've brought that to our attention several times. If you wanted this spec to align with your software, it would have been much easier if you'd got involved before Last Call.
>
> Why is it called <Last Call> if we don't accept any new input (e.g.,
> draft-ietf-appsawg-json-pointer-07) . Why do we call RFC <Request For
> Comment> if we don't want people to comment on (e.g. RFC2119).
>
> We SHOULD discuss any input any time, thank the participant, and
> accept only consensus on each input at any phase of time.

This is true, and a timing objection is a pretty low-quality response
to a substantive issue. This particular timing objection is also
somewhat misleading, since it looks like more than one person provided
this feedback prior to IETF Last Call without receiving a response:
<http://www.ietf.org/mail-archive/web/apps-discuss/current/msg08531.html>.
My message on the matter was sent on December 3rd, 2012.

- Rob

From abdussalambaryun@gmail.com  Sun Jan  6 13:07:38 2013
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3BAF021F854E for <ietf@ietfa.amsl.com>; Sun,  6 Jan 2013 13:07:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 jQylz1a3mzZ0 for <ietf@ietfa.amsl.com>; Sun,  6 Jan 2013 13:07:37 -0800 (PST)
Received: from mail-vc0-f171.google.com (mail-vc0-f171.google.com [209.85.220.171]) by ietfa.amsl.com (Postfix) with ESMTP id 78B5921F8B0E for <ietf@ietf.org>; Sun,  6 Jan 2013 13:07:36 -0800 (PST)
Received: by mail-vc0-f171.google.com with SMTP id n11so18498861vch.2 for <ietf@ietf.org>; Sun, 06 Jan 2013 13:07:36 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=ibUufZoJNlMK4FeeqenLo33FP5svWsMBWCdV4QbSy1U=; b=I6Wc3E4wQeIt842q8CKgnMDmf/OB0Ka/f2eaw4gA1n1gPZ6rPlFpSCMFKgzTYQHifq l8p1HFYFuIjeysBJ4GprkuSWkIRZbEPGxEfddbdzuZds8vzbV0H5pk/SpTldFHkYwrj+ lfR3X2f2ZYTxtLPax+QeK8Z+OQQXetYtQeLOwJHqmVwpW5x1bIqXnM+9vGlYAguzRVO5 1Nn6x76fZEV+e3RKVwAG+CyQEFPFv/HubIkdQ3JFVXOnZ2oN6372f4o4+1TPDmlzCu0y 0362Anz9NvNpKO4IBKj57XozFh2AsEZqBy3HBeLccVxStHXal161n26y/FB3yLCVNApj d3DQ==
MIME-Version: 1.0
Received: by 10.220.115.20 with SMTP id g20mr81489011vcq.31.1357506455892; Sun, 06 Jan 2013 13:07:35 -0800 (PST)
Received: by 10.220.145.5 with HTTP; Sun, 6 Jan 2013 13:07:35 -0800 (PST)
In-Reply-To: <CAChr6SxibLyp1WBskouGEH6G8ki_xt=7fex3Wg_6z8DExP89Kw@mail.gmail.com>
References: <CADnDZ896FUhWJQyGVu54tv=hvC5FZDxKMowhdxk0GM1C9LrrNw@mail.gmail.com> <CAChr6SxibLyp1WBskouGEH6G8ki_xt=7fex3Wg_6z8DExP89Kw@mail.gmail.com>
Date: Sun, 6 Jan 2013 22:07:35 +0100
Message-ID: <CADnDZ8_J+L-ZXRR1dvb6Thd2sPob+OxVJfqaRV7FawZKhtYgtA@mail.gmail.com>
Subject: Re: [apps-discuss] Last Call: <draft-ietf-appsawg-json-pointer-07.txt> (JSON Pointer) to Proposed Standard
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: Robert Sayre <sayrer@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 06 Jan 2013 21:07:38 -0000

The same thing happend to me on one work last call, the WG chair and
authors didn't want to take my input or any minor change in the
document.  The good thing is that if the IESG request a change they
will be welling to change, so don't worry if the comments are
reasonable to IESG it is already heard (i.e. but just in case not
seen, send your comments again to iesg address).... :-)

AB

On 1/6/13, Robert Sayre <sayrer@gmail.com> wrote:
> On Sun, Jan 6, 2013 at 12:59 AM, Abdussalam Baryun
> <abdussalambaryun@gmail.com> wrote:
>>>Yes, you've brought that to our attention several times. If you wanted
>>> this spec to align with your software, it would have been much easier if
>>> you'd got involved before Last Call.
>>
>> Why is it called <Last Call> if we don't accept any new input (e.g.,
>> draft-ietf-appsawg-json-pointer-07) . Why do we call RFC <Request For
>> Comment> if we don't want people to comment on (e.g. RFC2119).
>>
>> We SHOULD discuss any input any time, thank the participant, and
>> accept only consensus on each input at any phase of time.
>
> This is true, and a timing objection is a pretty low-quality response
> to a substantive issue. This particular timing objection is also
> somewhat misleading, since it looks like more than one person provided
> this feedback prior to IETF Last Call without receiving a response:
> <http://www.ietf.org/mail-archive/web/apps-discuss/current/msg08531.html>.
> My message on the matter was sent on December 3rd, 2012.
>
> - Rob
>

From mcr@sandelman.ca  Sun Jan  6 14:13:53 2013
Return-Path: <mcr@sandelman.ca>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C828421F863C for <ietf@ietfa.amsl.com>; Sun,  6 Jan 2013 14:13:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.299
X-Spam-Level: 
X-Spam-Status: No, score=-2.299 tagged_above=-999 required=5 tests=[AWL=0.300,  BAYES_00=-2.599]
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 NwUzRnQWPHvh for <ietf@ietfa.amsl.com>; Sun,  6 Jan 2013 14:13:52 -0800 (PST)
Received: from tuna.sandelman.ca (unknown [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) by ietfa.amsl.com (Postfix) with ESMTP id 5069821F851E for <ietf@ietf.org>; Sun,  6 Jan 2013 14:13:52 -0800 (PST)
Received: from sandelman.ca (unknown [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 08B4E2016D; Sun,  6 Jan 2013 17:17:47 -0500 (EST)
Received: by sandelman.ca (Postfix, from userid 179) id 9EFC2636C7; Sun,  6 Jan 2013 17:12:51 -0500 (EST)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id 7C8C8636C4; Sun,  6 Jan 2013 17:12:51 -0500 (EST)
From: Michael Richardson <mcr@sandelman.ca>
To: Ole Jacobsen <ole@cisco.com>
Subject: Re: travel guide for the next IETF...
In-Reply-To: <alpine.OSX.2.01.1301041514310.81626@173-11-110-132-sfba.hfc.comcastbusiness.net>
References: <50DF09C7.1060009@dcrocker.net> <20200.1356985377@sandelman.ca> <4613980CFC78314ABFD7F85CC30277210EE27C34@IL-EX10.ad.checkpoint.com> <2C17B081-ECE7-4CD0-99AB-72324EA0BE27@mnot.net> <alpine.OSX.2.01.1301041514310.81626@173-11-110-132-sfba.hfc.comcastbusiness.net>
X-Mailer: MH-E 8.3; nmh 1.3-dev; XEmacs 21.4 (patch 22)
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
Date: Sun, 06 Jan 2013 17:12:51 -0500
Message-ID: <11785.1357510371@sandelman.ca>
Sender: mcr@sandelman.ca
Cc: Mark Nottingham <mnot@mnot.net>, IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 06 Jan 2013 22:13:53 -0000

>>>>> "Ole" == Ole Jacobsen <ole@cisco.com> writes:
    Ole> This location was "dictated" (if that's the right word) by a
    Ole> desire to  
    Ole> co-locate (back-to-back) with the IEEE.

yeah, I know, but I gotta say to the IEEE.... SERIOUSLY?

    Ole> As for transportation to restaurants etc, I believe shuttle options ar
    Ole> being explored.

Thank you.
Do you know when this might be announced?

-- 
]               Never tell me the odds!                 | ipv6 mesh networks [ 
]   Michael Richardson, Sandelman Software Works        | network architect  [ 
]     mcr@sandelman.ca  http://www.sandelman.ca/        |   ruby on rails    [ 
	

From ole@cisco.com  Sun Jan  6 14:31:20 2013
Return-Path: <ole@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3A07021F85C6 for <ietf@ietfa.amsl.com>; Sun,  6 Jan 2013 14:31:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.599
X-Spam-Level: 
X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
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 cM+JXVz8rdLQ for <ietf@ietfa.amsl.com>; Sun,  6 Jan 2013 14:31:19 -0800 (PST)
Received: from ams-iport-3.cisco.com (ams-iport-3.cisco.com [144.254.224.146]) by ietfa.amsl.com (Postfix) with ESMTP id 67A5621F85C4 for <ietf@ietf.org>; Sun,  6 Jan 2013 14:31:19 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=403; q=dns/txt; s=iport; t=1357511479; x=1358721079; h=date:from:reply-to:to:cc:subject:in-reply-to:message-id: references:mime-version; bh=eS4vGUm0hPZpwzW0jFPWWpesS85VSuzeWszDEelh3BE=; b=NATs4kop120KAcKbLIXeT0rY/9BkMtTeklDnDbpSyuO8rnjFQ/PIw2J8 V004crQqMEsVXTt7wkbV/WAlFbGgPAU42LR7RC2U4ZYt97pRT5K0HKPef euQMNQ1KZBdxK77ImX5hluONdJLZgovjDegsOytMJozhFYBflL+zyQxbG c=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ag4FAGL66VCQ/khM/2dsb2JhbABFgy66JxZzgh4BAQEDATo/EAsOCi5XBogkBrV7kRUDiGGTFYpegxU
X-IronPort-AV: E=Sophos;i="4.84,421,1355097600"; d="scan'208";a="10899557"
Received: from ams-core-3.cisco.com ([144.254.72.76]) by ams-iport-3.cisco.com with ESMTP; 06 Jan 2013 22:31:18 +0000
Received: from [10.27.1.132] (sjc-ole-8913.cisco.com [10.27.1.132]) by ams-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id r06MVBRd006818 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 6 Jan 2013 22:31:13 GMT
Date: Sun, 6 Jan 2013 14:31:03 -0800 (PST)
From: Ole Jacobsen <ole@cisco.com>
To: Michael Richardson <mcr@sandelman.ca>
Subject: Re: travel guide for the next IETF...
In-Reply-To: <11785.1357510371@sandelman.ca>
Message-ID: <alpine.OSX.2.01.1301061429500.19083@173-11-110-132-sfba.hfc.comcastbusiness.net>
References: <50DF09C7.1060009@dcrocker.net> <20200.1356985377@sandelman.ca> <4613980CFC78314ABFD7F85CC30277210EE27C34@IL-EX10.ad.checkpoint.com> <2C17B081-ECE7-4CD0-99AB-72324EA0BE27@mnot.net> <alpine.OSX.2.01.1301041514310.81626@173-11-110-132-sfba.hfc.comcastbusiness.net> <11785.1357510371@sandelman.ca>
User-Agent: Alpine 2.01 (OSX 1266 2009-07-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Cc: Mark Nottingham <mnot@mnot.net>, IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: Ole Jacobsen <ole@cisco.com>
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 06 Jan 2013 22:31:20 -0000

On Sun, 6 Jan 2013, Michael Richardson wrote:
> 
> yeah, I know, but I gotta say to the IEEE.... SERIOUSLY?

Apparently the IEEE folks love it, have been there before.

> 
>     Ole> As for transportation to restaurants etc, I believe shuttle options ar
>     Ole> being explored.
> 
> Thank you.
> Do you know when this might be announced?

No, but I will try to find out.

Ole

> 

From sayrer@gmail.com  Sun Jan  6 16:01:36 2013
Return-Path: <sayrer@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3E1E421F857B; Sun,  6 Jan 2013 16:01:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 AJ0W-a3YgXMX; Sun,  6 Jan 2013 16:01:35 -0800 (PST)
Received: from mail-we0-f177.google.com (mail-we0-f177.google.com [74.125.82.177]) by ietfa.amsl.com (Postfix) with ESMTP id 223E621F8578; Sun,  6 Jan 2013 16:01:34 -0800 (PST)
Received: by mail-we0-f177.google.com with SMTP id x48so9224028wey.8 for <multiple recipients>; Sun, 06 Jan 2013 16:01:34 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=dw+ysy5x2Qze/pzJPJljE4jmDrGirRkeSdFljnROM/o=; b=gFcK7/BKijCgnKvfld7Uc1Xkqsc8Cx4/Y9VHv59KLPGuSoXEFN/mchcUwXqBO5gc60 4KqixqSC/x6xT9BP2zcgxpBrNLHUEZ7eN+qVMgYbwT90iDptnRdaigBgWqg7SH+QCCMk neeDlHjYCYmJdd2dcul/glzWFWinFdvo9l4Wsoh9Q9fr/zW5hVDSbw+RAVueSMrpxquc A/kl8zopZcQ8l/n1gTIxEVI9NGj8HV5xcTqtLjIrjaKTViKp3Oz2PrMW+yBo4FAhGqD2 svjXNNQlFvL3qGTMZsvjUqRFlAB2bEwmNY3Lwe6DqYS2D/JBz3ntIxiHUlnhA5nUIaWA Cy4w==
MIME-Version: 1.0
Received: by 10.194.23.37 with SMTP id j5mr92782594wjf.28.1357516894252; Sun, 06 Jan 2013 16:01:34 -0800 (PST)
Received: by 10.194.1.101 with HTTP; Sun, 6 Jan 2013 16:01:34 -0800 (PST)
In-Reply-To: <1357515310.6827.23.camel@polyglot>
References: <20121211150057.28223.93310.idtracker@ietfa.amsl.com> <50cb04b9.86df440a.72fe.1e20SMTPIN_ADDED_BROKEN@mx.google.com> <CABP7RbeNsZ_rBWRjou=VG+hBhUKaOz+y1a0sSChwWiHte9znnQ@mail.gmail.com> <50cb5f3c.694c420a.38fb.39afSMTPIN_ADDED_BROKEN@mx.google.com> <CAChr6SxZRc3B_HCbw76kLe2dsRSr43r-gLpfMVnCUfJTrZdTLA@mail.gmail.com> <CABP7RbfA33huBFadMeXTTEt=MkjW8-d4DFH7+GLXGurnm9sSRw@mail.gmail.com> <CAOXDeqpPE4eNy_qJpDPdPHbCQakG9-hDcNZ3Sj9r4kWedByVzQ@mail.gmail.com> <CAChr6SwtS_=iS-k4mJm1vHjEvvGVzay5jDYeGheqsPZqO-89CQ@mail.gmail.com> <EABB8F51-C3B4-49F5-8672-5C2ABAC7043A@mnot.net> <CAChr6Sx7JdKM91EwJaSZ0Ra_F4FSqkuc3vzTY1LM=F_8sWho+Q@mail.gmail.com> <1357515310.6827.23.camel@polyglot>
Date: Sun, 6 Jan 2013 16:01:34 -0800
Message-ID: <CAChr6SyAq=7aQdZn54ihYK+0hDhL--2Oaq0RvehoNFbwKNNShA@mail.gmail.com>
Subject: Re: [apps-discuss] Last Call: <draft-ietf-appsawg-json-pointer-07.txt> (JSON Pointer) to Proposed Standard
From: Robert Sayre <sayrer@gmail.com>
To: "Paul C. Bryan" <pbryan@anode.ca>
Content-Type: text/plain; charset=ISO-8859-1
Cc: Mark Nottingham <mnot@mnot.net>, IETF Discussion <ietf@ietf.org>, IETF Apps Discuss <apps-discuss@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 07 Jan 2013 00:01:36 -0000

On Sun, Jan 6, 2013 at 3:35 PM, Paul C. Bryan <pbryan@anode.ca> wrote:
>

Thank you for the technical response.

>
> 1) The ambiguity around arrays makes the patch format unsuitable for common
> concurrent editing algorithms.
>
>
> Common concurrent editing algorithms should, in my opinion, use techniques
> to ensure the state of the resource (relative to the edits) is known. In
> HTTP, we have ETag and If-Match/If-None-Match preconditions. In JSON Patch,
> we have (a rudimentary) test operation.

That is sequential editing, not concurrent editing. Here are a few
links to make sure we're not talking past each other:

http://en.wikipedia.org/wiki/Operational_transformation#Basics

The above overview section contains a two-step insert/delete process
bearing an uncanny resemblance to a JSON Patch document.

Here's some software that uses patch documents in this fashion:

http://en.wikipedia.org/wiki/Operational_transformation#OT_software

>
> [snip]
>
>
> 3) It's not possible to tell whether a JSON Pointer document is
> syntactically correct in isolation.
>
>
> There is no such thing as a JSON Pointer document.

Yes, I meant JSON Pointer /reference/. This error seems tangential to
the thread in general, though, which is why I didn't bother to correct
myself when others raised this point.

>
> This issue is a problem in practice, and it's a problem in theory as well.
> JSON-Patch messages aren't sufficiently self-descriptive, so they aren't
> appropriate for use in a RESTful system.
>
>
> 99% of RESTful systems I'm familiar with are based on HTTP. Where optimistic
> concurrency is acceptable, HTTP preconditions seems to provide acceptable
> coverage. Where more granularity or more pessimistic concurrency is
> required, implementors are free to use their own mechanisms, including more
> expressive predicates (as has been proposed here, with my endorsement)
> and/or resource locking. These are intentionally out of scope for JSON
> Patch.

Fully disagree. My point is that the array ambiguity makes it hard to
implement more optimistic concurrency.

>
> Later in this thread, you wrote:
>
> Ah. I meant that the WG seems to be favoring "running code" a little too
> heavily in the presence of a bug. It's an old argument, and it's boring: "We
> can't change it now, there are already twelve users!"
>
>
> I don't agree that this is a bug; it lacks a feature that you and some
> others have requested.

The only rationale I've seen prior to my message was something about
"feeling natural" and "static languages" that I admit I don't fully
understand. Are there other technical arguments I've missed? I'm happy
to go read up.

> Our reasoning for resisting such change is
> legitimate.

This last assertion really isn't qualified very well. Do you have a
more extensive rationale, or is a simple contradiction the extent of
your argument?

- Rob

From sayrer@gmail.com  Sun Jan  6 17:15:08 2013
Return-Path: <sayrer@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3520B21F84F8; Sun,  6 Jan 2013 17:15:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
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 pPiw64mRZ-Bq; Sun,  6 Jan 2013 17:15:07 -0800 (PST)
Received: from mail-wg0-x229.google.com (mail-wg0-x229.google.com [IPv6:2a00:1450:400c:c00::229]) by ietfa.amsl.com (Postfix) with ESMTP id 09FBB21F84F6; Sun,  6 Jan 2013 17:15:06 -0800 (PST)
Received: by mail-wg0-f41.google.com with SMTP id ds1so1765670wgb.4 for <multiple recipients>; Sun, 06 Jan 2013 17:15:05 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=cerFm2Nwtrzw/JgZDkqrf/mLp5kDOiTPKeIMc5/Si4E=; b=maSQOtsZTCbPbcNXJtr6yUdwI0Dgu/NEqc6x+CqmspBZqdHggdmHiNCmAogyUU8M5/ GVBqA5MCk2dr2TL/rFU3vbfXXUXYK3NJIg6bwdVIRips5OxkdoYWvCUvJ+kmoy1ME3n6 uvS1zp1vSDqnXXAi7J1UZIJlM+hsT2x8BilrXEe7iyi0RYaYETDUWj13vpuzPUi9b/8P N8Acj7DmjcTetotwhr743TPc+nA2m8YeMGe08wdnAhcPA1m6qBb1D8GPdAwyI4uIfofb JSKNwu4cqhxv43//yP+zFiuDQuSFImu8ydFpGrYXinEAdmIOkGWyT/WHzAGrXgqLzJlW 4o2A==
MIME-Version: 1.0
Received: by 10.180.88.40 with SMTP id bd8mr6568125wib.33.1357521305755; Sun, 06 Jan 2013 17:15:05 -0800 (PST)
Received: by 10.194.1.101 with HTTP; Sun, 6 Jan 2013 17:15:05 -0800 (PST)
In-Reply-To: <CAChr6SyAq=7aQdZn54ihYK+0hDhL--2Oaq0RvehoNFbwKNNShA@mail.gmail.com>
References: <20121211150057.28223.93310.idtracker@ietfa.amsl.com> <50cb04b9.86df440a.72fe.1e20SMTPIN_ADDED_BROKEN@mx.google.com> <CABP7RbeNsZ_rBWRjou=VG+hBhUKaOz+y1a0sSChwWiHte9znnQ@mail.gmail.com> <50cb5f3c.694c420a.38fb.39afSMTPIN_ADDED_BROKEN@mx.google.com> <CAChr6SxZRc3B_HCbw76kLe2dsRSr43r-gLpfMVnCUfJTrZdTLA@mail.gmail.com> <CABP7RbfA33huBFadMeXTTEt=MkjW8-d4DFH7+GLXGurnm9sSRw@mail.gmail.com> <CAOXDeqpPE4eNy_qJpDPdPHbCQakG9-hDcNZ3Sj9r4kWedByVzQ@mail.gmail.com> <CAChr6SwtS_=iS-k4mJm1vHjEvvGVzay5jDYeGheqsPZqO-89CQ@mail.gmail.com> <EABB8F51-C3B4-49F5-8672-5C2ABAC7043A@mnot.net> <CAChr6Sx7JdKM91EwJaSZ0Ra_F4FSqkuc3vzTY1LM=F_8sWho+Q@mail.gmail.com> <1357515310.6827.23.camel@polyglot> <CAChr6SyAq=7aQdZn54ihYK+0hDhL--2Oaq0RvehoNFbwKNNShA@mail.gmail.com>
Date: Sun, 6 Jan 2013 17:15:05 -0800
Message-ID: <CAChr6SxorKO20rGYi-e4YNF=HNGrwz8wPGKCFZQYWQwqsetjjg@mail.gmail.com>
Subject: Re: [apps-discuss] Last Call: <draft-ietf-appsawg-json-pointer-07.txt> (JSON Pointer) to Proposed Standard
From: Robert Sayre <sayrer@gmail.com>
To: "Paul C. Bryan" <pbryan@anode.ca>
Content-Type: text/plain; charset=ISO-8859-1
Cc: Mark Nottingham <mnot@mnot.net>, IETF Discussion <ietf@ietf.org>, IETF Apps Discuss <apps-discuss@ietf.org>, IESG <iesg@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 07 Jan 2013 01:15:08 -0000

On Sun, Jan 6, 2013 at 4:01 PM, Robert Sayre <sayrer@gmail.com> wrote:
> On Sun, Jan 6, 2013 at 3:35 PM, Paul C. Bryan <pbryan@anode.ca> wrote:
>>
>>
>> Common concurrent editing algorithms should, in my opinion, use techniques
>> to ensure the state of the resource (relative to the edits) is known. In
>> HTTP, we have ETag and If-Match/If-None-Match preconditions. In JSON Patch,
>> we have (a rudimentary) test operation.
...
> links to make sure we're not talking past each other:

Actually, let me restate my point in terms of RFC5789 (HTTP PATCH).
That will make it easier to communicate.

RFC 5789 Section 2.2 (Error Handling) defines error conditions which
correspond directly to the point at hand: 'Conflicting state' and
'Conflicting modification'. Section 5 of the JSON Patch document
directly references RFC5789, Section 2.2.

With that in mind, let's note that there are several normative
requirements in the JSON Patch document directed at conflicting state.
One such example is from Section 4.2 'remove'. It reads: "The target
location MUST exist for the operation to be successful.". If a server
received an HTTP JSON Patch request attempting to delete a
non-existent location, this text from RFC5789 would seem to apply:

"Conflicting state:  Can be specified with a 409 (Conflict) status
      code when the request cannot be applied given the state of the
      resource.  For example, if the client attempted to apply a
      structural modification and the structures assumed to exist did
      not exist ..."

The text above wouldn't be necessary in JSON Patch or RFC5789 if
RFC5789 required checking ETags and preconditions for all use cases
(it doesn't). The larger point is that RFC5789, and patch formats in
general, make all sorts of allowances for *non-conflicting* concurrent
edits to a common ancestor. The problem with leaving this JSON Pointer
array ambiguity in the draft is that patch messages which should
trigger '409 Conflict' errors can be mistakenly and 'successfully' (in
the HTTP sense) applied to a different structure than intended.

In summary, the JSON Patch draft allows patch documents to be
formulated that make it impossible to correctly implement RFC5789, a
normative reference.

Here are the questions the IESG focuses on during review:
"Reviews should focus on these questions: 'Is this document a
reasonable basis on which to build the salient part of the Internet
infrastructure? If not, what changes would make it so?'"

For JSON Patch, the answer to the first question is 'no', because of a
deficiency in JSON Pointer. The change needed to make these documents
acceptable as part of the Internet infrastructure is to make Arrays
explicit in JSON Pointer syntax.

- Rob

From johnl@iecc.com  Sun Jan  6 18:26:09 2013
Return-Path: <johnl@iecc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8A08E21F8615 for <ietf@ietfa.amsl.com>; Sun,  6 Jan 2013 18:26:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -109.992
X-Spam-Level: 
X-Spam-Status: No, score=-109.992 tagged_above=-999 required=5 tests=[AWL=-1.207, BAYES_40=-0.185, HABEAS_ACCREDITED_SOI=-4.3, RCVD_IN_BSP_TRUSTED=-4.3, USER_IN_WHITELIST=-100]
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 2iGfAYr0PmC3 for <ietf@ietfa.amsl.com>; Sun,  6 Jan 2013 18:26:08 -0800 (PST)
Received: from leila.iecc.com (leila6.iecc.com [IPv6:2001:470:1f07:1126:0:4c:6569:6c61]) by ietfa.amsl.com (Postfix) with ESMTP id 7F10E21F8633 for <ietf@ietf.org>; Sun,  6 Jan 2013 18:26:08 -0800 (PST)
Received: (qmail 7542 invoked from network); 7 Jan 2013 02:26:06 -0000
Received: from leila.iecc.com (64.57.183.34) by mail1.iecc.com with QMQP; 7 Jan 2013 02:26:06 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:subject:vbr-info; s=50ea323e.xn--30v786c.k1301; i=johnl@user.iecc.com; bh=WfrHKDtlQh1Eby5wgcnEvxqAqEvSlpmsg0EVGwtw8q8=; b=rrtrpLiLLg3AMa5G2udGU/CMtyYGOZ7KWIqjCoIDjNfO4UKUBjFI2WP63i3thPcX9O0R4k41bXRVsfvFGAqEQx4VSHET/r/Of44eE2ED7oUlkYc0XRTCJUPjKfePfhLSAjdsTf8DvE7KPhd9q4dy15OmTvwB8wvFeu7nhqmTjI8=
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:subject:vbr-info; s=50ea323e.xn--30v786c.k1301; olt=johnl@user.iecc.com; bh=WfrHKDtlQh1Eby5wgcnEvxqAqEvSlpmsg0EVGwtw8q8=; b=sdCCgWGf0+5kXpqM9vP15JrUBFpMTBmn2rzCc7cumLaFukNnROFMSuCLzMOlf3M+m/8dt0LN4G5yE8LW6qUkKiMudxKw2MLwROtjRlRNIGebhpYrdfXgTz2ahJd9Y9LuTQq7AaSXRNB6dklEEKPazH87TjMGeGZ/kU3pwCqUGdw=
VBR-Info: md=iecc.com; mc=all; mv=dwl.spamhaus.org
Date: 7 Jan 2013 02:25:42 -0000
Message-ID: <20130107022542.97244.qmail@joyce.lan>
From: "John Levine" <johnl@taugh.com>
To: ietf@ietf.org
Subject: Re: travel guide for the next IETF...
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 07 Jan 2013 02:26:09 -0000

>> yeah, I know, but I gotta say to the IEEE.... SERIOUSLY?
>
>Apparently the IEEE folks love it, have been there before.

Look at the reviews on Tripadvisor or Google, and for the most part
they're quite positive.  We're an odd group, much more price sensitive
than most conventioneers, and way more demanding about food options.

Having said that, I'm renting a car and staying at the Sheraton about
2 miles away for $16/day plus a surprisingly small number of points.
If you ask nicely, you can drive around with me and look for places to
eat.

From jeanjour@comcast.net  Sun Jan  6 20:49:59 2013
Return-Path: <jeanjour@comcast.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D6A7721F85C2 for <ietf@ietfa.amsl.com>; Sun,  6 Jan 2013 20:49:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.437
X-Spam-Level: 
X-Spam-Status: No, score=-100.437 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_NET=0.611,  RDNS_NONE=0.1, USER_IN_WHITELIST=-100]
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 KO0SsIWrBya3 for <ietf@ietfa.amsl.com>; Sun,  6 Jan 2013 20:49:59 -0800 (PST)
Received: from qmta14.westchester.pa.mail.comcast.net (qmta14.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:44:76:96:59:212]) by ietfa.amsl.com (Postfix) with ESMTP id 0B84D21F84F6 for <ietf@ietf.org>; Sun,  6 Jan 2013 20:49:58 -0800 (PST)
Received: from omta05.westchester.pa.mail.comcast.net ([76.96.62.43]) by qmta14.westchester.pa.mail.comcast.net with comcast id ksn51k0030vyq2s5EspynT; Mon, 07 Jan 2013 04:49:58 +0000
Received: from [10.0.1.3] ([98.229.211.49]) by omta05.westchester.pa.mail.comcast.net with comcast id kspx1k00Y14WE023RspxN7; Mon, 07 Jan 2013 04:49:58 +0000
Mime-Version: 1.0
Message-Id: <a062408a2cd10003cf574@[10.0.1.3]>
In-Reply-To: <CADnDZ8_GgVeapUKefFMqOvwOo00X8_rFDWMR0vb-Zvu_p=yT3A@mail.gmail.com>
References: <CADnDZ8_GgVeapUKefFMqOvwOo00X8_rFDWMR0vb-Zvu_p=yT3A@mail.gmail.com>
Date: Sun, 6 Jan 2013 23:49:52 -0500
To: Abdussalam Baryun <abdussalambaryun@gmail.com>, petithug@acm.org
From: John Day <jeanjour@comcast.net>
Subject: Re: A proposal for a scientific approach to this question [was Re: 	I'm struggling with 2219 language again]
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20121106; t=1357534198; bh=muz8r/sW2FW0tx7swI3J0W64XWQH8uLG4qjT39sz5ag=; h=Received:Received:Mime-Version:Message-Id:Date:To:From:Subject: Content-Type; b=oFP3T0gqF0UvmgrpueWado5g78s5pbn83md7FmodGe6UWga647NcDJ9ZlgGCt04he iDwmsOUUElGa2OcKi016NgWOfPT9l/6Xdcv7uy73bYVGv8RxjYcTISIr2ZHf9vg7yd NQ+IYJW85ELCMLjDYOnvok5gCQM4mkQW8nbbDOJETPwaIkh+XPGJuiSAfDOSOkAspY T7kGh7vpyzh1KUUgaTNNesa8mzVi7TcB57CsAVO/QyTRpVrkc/s3jecLDwCqaKgIV8 bvBxUQ3zJe/s1tOtDEUvn3TRfX/aqnKi0VJT8mt+6lAOKmM9G3K64unzbS4EtzDfQn UzxkWGzJCuVTA==
Cc: ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 07 Jan 2013 04:50:00 -0000

Strictly speaking, the language of 2119 should be followed wherever 
necessary in order for the text to be normative and make it mandatory 
that a conforming implementation meets some requirement.  Otherwise, 
someone could build an implementation and claim it was correct and 
possibly cause legal problems. However, in the IETF there is also a 
requirement that there be two independent but communicating 
implementations for an RFC to standards-track. Correct?

For all practical purposes, this requirement makes being able to 
communicate with one of the existing implementations the formal and 
normative definition of the RFC.  Any debate over the content of the 
RFC text is resolved by what the implementations do.  It would seem 
to be at the discretion of the authors of the implementations to 
determine whether or not any problems that are raised are bugs or not.

Then it would seem that regardless of whether 2119 is followed, the 
RFCs are merely informative guides.

So while the comments are valid that RFC 2119 should be followed, 
they are also irrelevant.

Given that any natural language description is going to be ambiguous, 
this is probably for the best.

Take care,
John Day

At 9:41 AM +0100 1/6/13, Abdussalam Baryun wrote:
>Hi Marc Petit-Huguenin ,
>
>>I read the responses so far, and what can be said today is that there is 2
>philosophies, with supporters in both camps.  The goal of the IETF is to make
>the Internet work better, and I do believe that RFC 2119 is one of the
>fundamental tool to reach this goal, but having two ways to use it does not
>help this goal.
>
>I like the approach, and agree with you that we need a solution in
>IETF which still is not solved or ignored by participants fo some
>reasons. However, I agree of a survey or an experiment what ever we
>call it, that makes IETF reflects to the RFC2119 performance on the
>end-user of such product implementation of RFC protocols. I think many
>old participants already have good experience to inform us of some
>reality of IETF standards' end-user production.
>
>AB


From stbryant@cisco.com  Mon Jan  7 02:53:51 2013
Return-Path: <stbryant@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B86C321F846E for <ietf@ietfa.amsl.com>; Mon,  7 Jan 2013 02:53:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -109.953
X-Spam-Level: 
X-Spam-Status: No, score=-109.953 tagged_above=-999 required=5 tests=[AWL=-0.646, BAYES_00=-2.599, MISSING_HEADERS=1.292, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
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 ZK+fZOoN5eVL for <ietf@ietfa.amsl.com>; Mon,  7 Jan 2013 02:53:50 -0800 (PST)
Received: from ams-iport-3.cisco.com (ams-iport-3.cisco.com [144.254.224.146]) by ietfa.amsl.com (Postfix) with ESMTP id 9C0CF21F8436 for <ietf@ietf.org>; Mon,  7 Jan 2013 02:53:50 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=274; q=dns/txt; s=iport; t=1357556030; x=1358765630; h=message-id:date:from:reply-to:mime-version:cc:subject: references:in-reply-to:content-transfer-encoding; bh=6BM7LYSJm9swcptQ78rfgTlXzoxFzFOz1q5sDmfuWC0=; b=Ounx0taCBDlDzpDPbcddz2fdfVeul+5VcuuGci3cSg0Me+N+du9KoHRO Jb6lCVZJsBbiD/IL5dHeBr2gB0c2LKo8ZTkwlG/emJoZRuk8PEmbyu/1m u35OaUM1k7R3B+xIjEpHvMJPatCPKmZhGtRsQWSXSUdxgzgJlL4nZnKPB E=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AnQWAK+n6lCQ/khN/2dsb2JhbABFg0e5BAQEGWcWc4IfAQEEOEABEAshFgQLCQMCAQIBRRMBBwEBiBO2bok1h2ADlguFa4pegnQ
X-IronPort-AV: E=Sophos;i="4.84,423,1355097600"; d="scan'208";a="10910027"
Received: from ams-core-4.cisco.com ([144.254.72.77]) by ams-iport-3.cisco.com with ESMTP; 07 Jan 2013 10:53:49 +0000
Received: from cisco.com (mrwint.cisco.com [64.103.70.36]) by ams-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id r07ArnGJ000912 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Mon, 7 Jan 2013 10:53:49 GMT
Received: from [127.0.0.1] (localhost [127.0.0.1]) by cisco.com (8.14.4+Sun/8.8.8) with ESMTP id r07Armhv016813; Mon, 7 Jan 2013 10:53:48 GMT
Message-ID: <50EAA93C.6060206@cisco.com>
Date: Mon, 07 Jan 2013 10:53:48 +0000
From: Stewart Bryant <stbryant@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
CC: ietf <ietf@ietf.org>
Subject: Re: A proposal for a scientific approach to this question [was Re: I'm struggling with 2219 language again]
References: <CADnDZ8_GgVeapUKefFMqOvwOo00X8_rFDWMR0vb-Zvu_p=yT3A@mail.gmail.com> <a062408a2cd10003cf574@[10.0.1.3]>
In-Reply-To: <a062408a2cd10003cf574@[10.0.1.3]>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: stbryant@cisco.com
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 07 Jan 2013 10:53:51 -0000

Speaking as both a reviewer and an author, I would like
to ground this thread to some form of reality.

Can anyone point to specific cases where absence or over
use of an RFC2119 key word caused an interoperability failure,
or excessive development time?

- Stewart





From jeanjour@comcast.net  Mon Jan  7 04:28:11 2013
Return-Path: <jeanjour@comcast.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BF3B321F8715 for <ietf@ietfa.amsl.com>; Mon,  7 Jan 2013 04:28:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.437
X-Spam-Level: 
X-Spam-Status: No, score=-100.437 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_NET=0.611,  RDNS_NONE=0.1, USER_IN_WHITELIST=-100]
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 CCdV44nIa46t for <ietf@ietfa.amsl.com>; Mon,  7 Jan 2013 04:28:11 -0800 (PST)
Received: from qmta02.westchester.pa.mail.comcast.net (qmta02.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:43:76:96:62:24]) by ietfa.amsl.com (Postfix) with ESMTP id 2A14221F84C0 for <ietf@ietf.org>; Mon,  7 Jan 2013 04:28:11 -0800 (PST)
Received: from omta01.westchester.pa.mail.comcast.net ([76.96.62.11]) by qmta02.westchester.pa.mail.comcast.net with comcast id kz271k0050EZKEL510UAx2; Mon, 07 Jan 2013 12:28:10 +0000
Received: from [10.0.1.3] ([98.229.211.49]) by omta01.westchester.pa.mail.comcast.net with comcast id l0U81k00114WE023M0UAXA; Mon, 07 Jan 2013 12:28:10 +0000
Mime-Version: 1.0
Message-Id: <a062408a5cd106d980f2d@[10.0.1.3]>
In-Reply-To: <50EAA93C.6060206@cisco.com>
References: <CADnDZ8_GgVeapUKefFMqOvwOo00X8_rFDWMR0vb-Zvu_p=yT3A@mail.gmail.com> <a062408a2cd10003cf574@[10.0.1.3]> <50EAA93C.6060206@cisco.com>
Date: Mon, 7 Jan 2013 07:22:17 -0500
To: stbryant@cisco.com
From: John Day <jeanjour@comcast.net>
Subject: Re: A proposal for a scientific approach to this question [was Re: 	I'm struggling with 2219 language again]
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20121106; t=1357561690; bh=xWCc8YJsO4KPMJ0gTAIey3MNM8bCeX95Qxi6qgV2pzw=; h=Received:Received:Mime-Version:Message-Id:Date:To:From:Subject: Content-Type; b=Hbh8q7G1BVM5gJNKc6LOOr6qARqkDtNGZWkkjwZfPvHhenHFRX9PtuOTlvCVU1Ds1 xdESZ4p6zuMqe7pOB3Kt6+Cm+ofDFuBsQRPMyV/0TppiLIPfvThBrogHTVZycR91uX BYufVlyXGKl2UbhVHt5etTMFTd1y6Vge2rF3Ku+fcmCdIzbTIjIarEOW6MyWOZ9B9s KlQmzDxwGrCSMEEINmu0g7/FtXDDE2GE1LvKkMNqpAxdqRdVtUSZQB17u3pWgh4EFk wweAYYSEv/bWG65DebAKFy256RHNMJ8I41Ff4F/lCeSfMpjAUB0s5JQ2K/zij4F+TG vdTRE0Ja8nmBQ==
Cc: ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 07 Jan 2013 12:28:11 -0000

As you are guessing that is unlikely, however, the more pertinent 
question is whether it has prevented some innovative approach to 
implementations.  This would be the more interesting question.

We tend to think of these as state machines and describe them 
accordingly.  There are other approaches which might be prevented if 
using a MUST when it wasn't needed.

At 10:53 AM +0000 1/7/13, Stewart Bryant wrote:
>Speaking as both a reviewer and an author, I would like
>to ground this thread to some form of reality.
>
>Can anyone point to specific cases where absence or over
>use of an RFC2119 key word caused an interoperability failure,
>or excessive development time?
>
>- Stewart


From stbryant@cisco.com  Mon Jan  7 04:43:19 2013
Return-Path: <stbryant@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1C7BB21F853C for <ietf@ietfa.amsl.com>; Mon,  7 Jan 2013 04:43:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.507
X-Spam-Level: 
X-Spam-Status: No, score=-110.507 tagged_above=-999 required=5 tests=[AWL=0.092, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
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 7nOdmb90gEEZ for <ietf@ietfa.amsl.com>; Mon,  7 Jan 2013 04:43:18 -0800 (PST)
Received: from ams-iport-4.cisco.com (ams-iport-4.cisco.com [144.254.224.147]) by ietfa.amsl.com (Postfix) with ESMTP id E9D4121F8506 for <ietf@ietf.org>; Mon,  7 Jan 2013 04:42:49 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1267; q=dns/txt; s=iport; t=1357562570; x=1358772170; h=message-id:date:from:reply-to:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=oucBE7LsAu7o8GsjWhJXDJtHIbN1E0MRMkUdRopyCyE=; b=dVDh6Z4f4WOfOdaQ1J5GxIDB5QqHILoH38NpWMhtKxy/bw6efGAJjKSf Uv6tBt5iwg8lC8e/RndoWDJxAoU7jnR82j+Muimm9/msz/wHO3rqr1s4A 8uvGGD6jB0eZq9hpBRKYxh6pOR1huHeqGheFuHqEaR54U8tvBo63iX1PK Y=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AqsHALPB6lCQ/khR/2dsb2JhbABFg0e6DBZzgh4BAQEEOEABEAsOCgkWBAsJAwIBAgFFBg0BBwEBiBMMtg2JNYdgA5YLhWuKXoJ0
X-IronPort-AV: E=Sophos;i="4.84,424,1355097600"; d="scan'208";a="10924964"
Received: from ams-core-1.cisco.com ([144.254.72.81]) by ams-iport-4.cisco.com with ESMTP; 07 Jan 2013 12:42:46 +0000
Received: from cisco.com (mrwint.cisco.com [64.103.70.36]) by ams-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id r07Cgit7005901 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 7 Jan 2013 12:42:44 GMT
Received: from [127.0.0.1] (localhost [127.0.0.1]) by cisco.com (8.14.4+Sun/8.8.8) with ESMTP id r07CghF8024716; Mon, 7 Jan 2013 12:42:43 GMT
Message-ID: <50EAC2C3.2080807@cisco.com>
Date: Mon, 07 Jan 2013 12:42:43 +0000
From: Stewart Bryant <stbryant@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: John Day <jeanjour@comcast.net>
Subject: Re: A proposal for a scientific approach to this question [was Re: I'm struggling with 2219 language again]
References: <CADnDZ8_GgVeapUKefFMqOvwOo00X8_rFDWMR0vb-Zvu_p=yT3A@mail.gmail.com> <a062408a2cd10003cf574@[10.0.1.3]> <50EAA93C.6060206@cisco.com> <a062408a5cd106d980f2d@[10.0.1.3]>
In-Reply-To: <a062408a5cd106d980f2d@[10.0.1.3]>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: stbryant@cisco.com
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 07 Jan 2013 12:43:19 -0000

Indeed an interesting additional question.

My view is that you MUST NOT use RFC2119 language, unless you MUST use 
it, for exactly that reason. What is important is "on the wire" (a term 
that from experience is very difficult to define) inter-operation, and 
implementers need to be free to achieve that though any means that suits 
them.

- Stewart

On 07/01/2013 12:22, John Day wrote:
> As you are guessing that is unlikely, however, the more pertinent 
> question is whether it has prevented some innovative approach to 
> implementations.  This would be the more interesting question.
>
> We tend to think of these as state machines and describe them 
> accordingly.  There are other approaches which might be prevented if 
> using a MUST when it wasn't needed.
>
> At 10:53 AM +0000 1/7/13, Stewart Bryant wrote:
>> Speaking as both a reviewer and an author, I would like
>> to ground this thread to some form of reality.
>>
>> Can anyone point to specific cases where absence or over
>> use of an RFC2119 key word caused an interoperability failure,
>> or excessive development time?
>>
>> - Stewart
>
> .
>


-- 
For corporate legal information go to:

http://www.cisco.com/web/about/doing_business/legal/cri/index.html


From brian.e.carpenter@gmail.com  Mon Jan  7 05:31:16 2013
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B757F21F85AE for <ietf@ietfa.amsl.com>; Mon,  7 Jan 2013 05:31:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.691
X-Spam-Level: 
X-Spam-Status: No, score=-101.691 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, RCVD_ILLEGAL_IP=1.908, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
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 k14lNpTG3Gjq for <ietf@ietfa.amsl.com>; Mon,  7 Jan 2013 05:31:16 -0800 (PST)
Received: from mail-bk0-f45.google.com (mail-bk0-f45.google.com [209.85.214.45]) by ietfa.amsl.com (Postfix) with ESMTP id A086421F8621 for <ietf@ietf.org>; Mon,  7 Jan 2013 05:31:15 -0800 (PST)
Received: by mail-bk0-f45.google.com with SMTP id jk13so8328582bkc.4 for <ietf@ietf.org>; Mon, 07 Jan 2013 05:31:14 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:organization:user-agent :mime-version:to:cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=kFQcD3UkuGz4iGshXLjEWOddvQI++bVThEvHtnMMPfE=; b=E3RkqRbm7I28/AncjLXhBKIaLAHIbSmAadlsEh29xCi7o8+p4n30z7fCm/r9qlDKDH pSlTqEKAqRYkZlxbQGNCJAsbOH6bc1BWTgGbTFR+Mrv0M9CUKJYUeeIdeBCeDCyuAMFV L3/Dpe0PL9bJKvPNR3hpB0HN/bYmdROCWP607dSuARr2Z8jjYhIfAZG+s2UY5uFI+hs8 jQY8Qj5AVZb2h0iEP2ZwAPtX9OuezSNodV8i1OzZGGCiIaA8w5JDnv4WYT6dX1/lP/2Y f9brbCSzLr99Uva0TbKe4I9IzXfINKNMK+m/WscvSJtK8oHf/xnRJk5+DeKUzmS0sCTR /IWw==
X-Received: by 10.204.154.202 with SMTP id p10mr30003942bkw.29.1357565474437;  Mon, 07 Jan 2013 05:31:14 -0800 (PST)
Received: from [192.168.1.65] (host-2-102-219-246.as13285.net. [2.102.219.246]) by mx.google.com with ESMTPS id o7sm42407608bkv.13.2013.01.07.05.31.12 (version=SSLv3 cipher=OTHER); Mon, 07 Jan 2013 05:31:13 -0800 (PST)
Message-ID: <50EACE23.7040407@gmail.com>
Date: Mon, 07 Jan 2013 13:31:15 +0000
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: stbryant@cisco.com
Subject: Re: A proposal for a scientific approach to this question [was Re: I'm struggling with 2219 language again]
References: <CADnDZ8_GgVeapUKefFMqOvwOo00X8_rFDWMR0vb-Zvu_p=yT3A@mail.gmail.com>	<a062408a2cd10003cf574@[10.0.1.3]> <50EAA93C.6060206@cisco.com>	<a062408a5cd106d980f2d@[10.0.1.3]> <50EAC2C3.2080807@cisco.com>
In-Reply-To: <50EAC2C3.2080807@cisco.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 07 Jan 2013 13:31:16 -0000

On 07/01/2013 12:42, Stewart Bryant wrote:
> Indeed an interesting additional question.
> 
> My view is that you MUST NOT use RFC2119 language, unless you MUST use
> it, for exactly that reason. What is important is "on the wire" (a term
> that from experience is very difficult to define) inter-operation, and
> implementers need to be free to achieve that though any means that suits
> them.

Agreed. Imagine the effect if the TCP standard had said that a particular
congestion control algorithm was mandatory. Oh, wait...

... RFC 1122 section 4.2.2.15 says that a TCP MUST implement reference [TCP:7]
which is Van's SIGCOMM'88 paper. So apparently any TCP that uses a more recent
congestion control algorithm is non-conformant. Oh, wait...

... RFC 2001 is a proposed standard defining congestion control algorithms,
but it doesn't update RFC 1122, and it uses lower-case. Oh, wait...

RFC 2001 is obsoleted by RFC 2581 which obsoleted by RFC 5681. These both
use RFC 2119 keywords, but they still don't update RFC 1122.

This is such a rat's nest that it has a guidebook (RFC 5783, "Congestion
Control in the RFC Series") and of course it's still an open research topic.

Attempting to validate TCP implementations on the basis of conformance
with RFC 2119 keywords would be, well, missing the point.

I know this is an extreme case, but I believe it shows the futility of
trying to be either legalistic or mathematical in this area.

   Brian

From jeanjour@comcast.net  Mon Jan  7 06:48:47 2013
Return-Path: <jeanjour@comcast.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9AB8E21F8775 for <ietf@ietfa.amsl.com>; Mon,  7 Jan 2013 06:48:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.437
X-Spam-Level: 
X-Spam-Status: No, score=-100.437 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_NET=0.611,  RDNS_NONE=0.1, USER_IN_WHITELIST=-100]
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 hJdKDfKiR+vp for <ietf@ietfa.amsl.com>; Mon,  7 Jan 2013 06:48:47 -0800 (PST)
Received: from qmta02.westchester.pa.mail.comcast.net (qmta02.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:43:76:96:62:24]) by ietfa.amsl.com (Postfix) with ESMTP id 9266321F8686 for <ietf@ietf.org>; Mon,  7 Jan 2013 06:48:11 -0800 (PST)
Received: from omta21.westchester.pa.mail.comcast.net ([76.96.62.72]) by qmta02.westchester.pa.mail.comcast.net with comcast id l0JW1k0011ZXKqc512oB2v; Mon, 07 Jan 2013 14:48:11 +0000
Received: from [10.0.1.3] ([98.229.211.49]) by omta21.westchester.pa.mail.comcast.net with comcast id l2oA1k00G14WE023h2oACB; Mon, 07 Jan 2013 14:48:11 +0000
Mime-Version: 1.0
Message-Id: <a062408aecd108d307700@[10.0.1.3]>
In-Reply-To: <50EACE23.7040407@gmail.com>
References: <CADnDZ8_GgVeapUKefFMqOvwOo00X8_rFDWMR0vb-Zvu_p=yT3A@mail.gmail.com> <a062408a2cd10003cf574@[10.0.1.3]> <50EAA93C.6060206@cisco.com> <a062408a5cd106d980f2d@[10.0.1.3]> <50EAC2C3.2080807@cisco.com> <50EACE23.7040407@gmail.com>
Date: Mon, 7 Jan 2013 09:45:43 -0500
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, stbryant@cisco.com
From: John Day <jeanjour@comcast.net>
Subject: Re: A proposal for a scientific approach to this question [was Re:  I'm struggling with 2219 language again]
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20121106; t=1357570091; bh=n/Mxa5AXFY0InrGb++lz8cu6MjGLSBQcQcByOiEsjXg=; h=Received:Received:Mime-Version:Message-Id:Date:To:From:Subject: Content-Type; b=WNvc5JfWOyTJNdOBMJXMXUvI8KM8QJ+VeL6TS1qXyJX2+Rqf90YHtXeHyLRY8e0c8 8R5C+W/BlzN3/vnjneswamyWmi98nT7GXwrh4OAVeZSdGYKkUhH6SwAA5HxZakDzrQ yRhDar0hy/FAZzeoOiimvzYsO1B7VptdXzPgNXgDMwXzwqjrqp4Sp62qxj9pynbuth KNwvThHrM1tEyR/Ixrx+O8Bteyu2VySPlzuuwXqRRjtU06JC5KZHcTbzsmRjR0uOeI JbpkBxM3FWF7H7iIADtCqo0gOU6fLhLNP3hy2DzpNPpPB/ua80WpBnZ+WyM5udBfhr 2r2xRWHSgoaHw==
Cc: ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 07 Jan 2013 14:48:47 -0000

Let me get this straight, Brian.  It would seem you are pointing out 
that the IETF does not have a clear idea of what it is doing?  ;-)  I 
could believe that.

No, your example is not an example of what I suggested at all.

Yours is an example of not specifying the conditions that a 
congestion control algorithm must have rather than the congestion 
control algorithm itself.

What I was suggesting (and it is very easy trap to fall into) was 
defining a spec with one implementation environment in mind and not 
realizing you are constraining things unnecessarily. Consider the 
difference between defining TCP as a state machine with that sort of 
implementation in mind and building an implementation in LISP. (I 
know someone who did it.)  It would be very easy to make assumptions 
about how something was described that made a LISP implementation 
unduly messy, or missed an opportunity for a major simplification.

It is quite easy to do some thing mathematical in this area (not 
necessarily alluding to formal specification), but you do have to 
have a clear concept of the levels of abstraction.  Of course, once 
you do, you still have the question whether there is a higher 
probability of errors in the math or the program.

Yes, programming is just math of a different kind, which of course is 
the point.

Take care,
John

At 1:31 PM +0000 1/7/13, Brian E Carpenter wrote:
>On 07/01/2013 12:42, Stewart Bryant wrote:
>>  Indeed an interesting additional question.
>>
>>  My view is that you MUST NOT use RFC2119 language, unless you MUST use
>>  it, for exactly that reason. What is important is "on the wire" (a term
>>  that from experience is very difficult to define) inter-operation, and
>>  implementers need to be free to achieve that though any means that suits
>>  them.
>
>Agreed. Imagine the effect if the TCP standard had said that a particular
>congestion control algorithm was mandatory. Oh, wait...
>
>... RFC 1122 section 4.2.2.15 says that a TCP MUST implement reference [TCP:7]
>which is Van's SIGCOMM'88 paper. So apparently any TCP that uses a more recent
>congestion control algorithm is non-conformant. Oh, wait...
>
>... RFC 2001 is a proposed standard defining congestion control algorithms,
>but it doesn't update RFC 1122, and it uses lower-case. Oh, wait...
>
>RFC 2001 is obsoleted by RFC 2581 which obsoleted by RFC 5681. These both
>use RFC 2119 keywords, but they still don't update RFC 1122.
>
>This is such a rat's nest that it has a guidebook (RFC 5783, "Congestion
>Control in the RFC Series") and of course it's still an open research topic.
>
>Attempting to validate TCP implementations on the basis of conformance
>with RFC 2119 keywords would be, well, missing the point.
>
>I know this is an extreme case, but I believe it shows the futility of
>trying to be either legalistic or mathematical in this area.
>
>    Brian


From presnick@qti.qualcomm.com  Mon Jan  7 07:34:25 2013
Return-Path: <presnick@qti.qualcomm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C188F21F88F1 for <ietf@ietfa.amsl.com>; Mon,  7 Jan 2013 07:34:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.599
X-Spam-Level: 
X-Spam-Status: No, score=-103.599 tagged_above=-999 required=5 tests=[AWL=1.000, BAYES_00=-2.599, GB_I_LETTER=-2, USER_IN_WHITELIST=-100]
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 VewiCnxQgp3O for <ietf@ietfa.amsl.com>; Mon,  7 Jan 2013 07:34:24 -0800 (PST)
Received: from sabertooth02.qualcomm.com (sabertooth02.qualcomm.com [65.197.215.38]) by ietfa.amsl.com (Postfix) with ESMTP id C9B4821F88ED for <ietf@ietf.org>; Mon,  7 Jan 2013 07:34:24 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qti.qualcomm.com; i=@qti.qualcomm.com; q=dns/txt; s=qcdkim; t=1357571082; x=1389107082; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=76TFip95W6f1NX/51R+54jpOP5pnqEc8F2ij9yHUi9Q=; b=fTCkXAuzm3PK4Glb6kQMFUcRZQD93T3cQxn2pOaMYhg2AyEVjoUupCf8 BJT7dYVnsxNoivUivcVkiIYQo80v/rl74qoLVz4/bpm9QYv+tN81kZ6az xETQ60AP2fNaIsBjl4twbkFDg5qHyxENOwTDkl7w0rng2hYFuKFWWjsBg A=;
X-IronPort-AV: E=Sophos;i="4.84,424,1355126400"; d="scan'208";a="14915162"
Received: from ironmsg01-lv.qualcomm.com ([10.47.202.180]) by sabertooth02.qualcomm.com with ESMTP; 07 Jan 2013 07:04:41 -0800
Received: from nasanexhc07.na.qualcomm.com ([172.30.39.190]) by ironmsg01-lv.qualcomm.com with ESMTP/TLS/RC4-SHA; 07 Jan 2013 07:34:23 -0800
Received: from 75-145-176-246-illinois.hfc.comcastbusiness.net (172.30.39.5) by qcmail1.qualcomm.com (172.30.39.190) with Microsoft SMTP Server (TLS) id 14.2.318.4; Mon, 7 Jan 2013 07:34:23 -0800
Message-ID: <50EAEAFC.1070707@qti.qualcomm.com>
Date: Mon, 7 Jan 2013 09:34:20 -0600
From: Pete Resnick <presnick@qti.qualcomm.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.7; en-US; rv:1.9.1.9) Gecko/20100630 Eudora/3.0.4
MIME-Version: 1.0
To: <ned+ietf@mauve.mrochek.com>
Subject: Re: I'm struggling with 2219 language again
References: <7ED55FF1-3E1A-4DF7-918E-07790517B848@softarmor.com>	<50E68CB5.4010107@gmail.com>	<201301042223.r04MNgRA020196@cichlid.raleigh.ibm.com> <01OOLLQ4P2AE00008S@mauve.mrochek.com>
In-Reply-To: <01OOLLQ4P2AE00008S@mauve.mrochek.com>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-Originating-IP: [172.30.39.5]
Cc: Thomas Narten <narten@us.ibm.com>, ietf@ietf.org, Dean Willis <dean.willis@softarmor.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 07 Jan 2013 15:34:25 -0000

Dean, I am struggling constantly with 2119 as an AD, because if I take 
the letter (and the spirit) of 2119 at face value, a lot of people are 
doing this wrong. And 2119 is a BCP; it's one of our process documents. 
So I'd like this to be cleared up as much as you. I think there is 
active harm in the misuse we are seeing.

To Ned's points:

On 1/4/13 7:05 PM, ned+ietf@mauve.mrochek.com wrote:
>> +1 to Brian and others saying upper case should be used sparingly, and
>> only where it really matters. If even then.
>>      
> That's the entire point: The terms provide additional information as to
> what the authors consider the important points of compliance to be.
>    

We will like end up in violent agreement, but I think the above 
statement is incorrect. Nowhere in 2119 will you find the words 
"conform" or conformance" or "comply" or "compliance", and I think 
there's a reason for that: We long ago found that we did not really care 
about conformance or compliance in the IETF. What we cared about was 
interoperability of independently developed implementations, because 
independently developing implementations that interoperate with other 
folks is what makes the Internet robust. Importantly, we specifically 
did not want to dictate how you write your code or tell you specific 
algorithms to follow; that makes for everyone implementing the same 
brittle code.

The useful function of 2119 is that it allows us to document the 
important *behavioral* requirements that I have to be aware of when I am 
implementing (e.g., even though it's not obvious, my implementation MUST 
send such-and-so or the other side is going to crash and burn; e.g., 
even though it's not obvious, the other side MAY send this-and-that, and 
therefore my implementation needs to be able to handle it). And those 
"even though it's not obvious" statements are important. It wastes my 
time as an implementer to try to figure out what interoperability 
requirement is meant by, "You MUST implement a variable to keep track of 
such-and-so-state" (and yes, we see these in specs lately), and it makes 
for everyone potentially implementing the same broken code.

>> The notion (that some have) that MUST means you have to do something
>> to be compliant and that a "must" (lower case) is optional is just
>> nuts.
>>      

You bet, Thomas!

> In some ways I find the use of SHOULD and SHOULD NOT be to be more useful
> than MUST and MUST NOT. MUST and MUST NOT are usually obvious. SHOULD and
> SHOULD NOT are things on the boundary, and how boundary cases are handled
> is often what separated a good implementation from a mediocre or even poor
> one.
>    

Agreed. Indeed, if you have a MUST or MUST NOT, I'd almost always be 
inclined to have a "because" clause. If you can't given an explanation 
of why I need this warning, there's a good chance the MUST is 
inappropriate. (One that I've seen of late is "If the implementation 
wants to send, it MUST set the <send> field to 'true'. If it wants to 
receive, it MUST set the <send> field to 'false'." I have no idea what 
those MUSTs are telling me. Under what circumstances could I possibly 
want to send but set the <send> field to "false"?)

>> The idea that upper case language can be used to identify all the
>> required parts of a specificition from a
>> compliance/conformance/interoperability perspective is just
>> wrong. This has never been the case (and would be exceeding painful to
>> do), though (again) some people seem to think this would be useful and
>> thus like lots of upper case language.
>>      
> At most it provides the basis for a compliance checklist. But such checklists
> never cover all the points involved in compliance. Heck, most specifications in
> toto don't do that. Some amount of common sense is always required.
>    

And again, it's worse than incomplete. It also makes for brittle code. I 
don't want you checking to see if you coded things the same way that I 
did, which is what a compliance list gets you. I want you checking that 
your *behavior* from the net interoperates with me. Insofar as you want 
to call *that* compliance, well, OK, but I don't think that's what 
people mean.

>> Where you want to use MUST is where an implementation might be tempted
>> to take a short cut -- to the detriment of the Internet -- but could
>> do so without actually breaking interoperability.

Exactly!

>> IMO, too many specs seriously overuse/misuse 2119 language, to the
>> detriment of readability, common sense, and reserving the terms to
>> bring attention to those cases where it really is important to
>> highlight an important point that may not be obvious to a casual
>> reader/implementor.
>>      
> Sadly true.
>    

And to the detriment of good code..

pr

-- 
Pete Resnick<http://www.qualcomm.com/~presnick/>
Qualcomm Technologies, Inc. - +1 (858)651-4478


From jgs@juniper.net  Mon Jan  7 07:50:50 2013
Return-Path: <jgs@juniper.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CC33721F8903 for <ietf@ietfa.amsl.com>; Mon,  7 Jan 2013 07:50:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.467
X-Spam-Level: 
X-Spam-Status: No, score=-3.467 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, UNRESOLVED_TEMPLATE=3.132]
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 YtWaUsEigV7K for <ietf@ietfa.amsl.com>; Mon,  7 Jan 2013 07:50:50 -0800 (PST)
Received: from exprod7og120.obsmtp.com (exprod7og120.obsmtp.com [64.18.2.18]) by ietfa.amsl.com (Postfix) with ESMTP id 4649021F873B for <ietf@ietf.org>; Mon,  7 Jan 2013 07:50:49 -0800 (PST)
Received: from P-EMHUB03-HQ.jnpr.net ([66.129.224.36]) (using TLSv1) by exprod7ob120.postini.com ([64.18.6.12]) with SMTP ID DSNKUOru2VaGK9nYgATktiWOwBFwRthB1fh3@postini.com; Mon, 07 Jan 2013 07:50:50 PST
Received: from P-CLDFE01-HQ.jnpr.net (172.24.192.59) by P-EMHUB03-HQ.jnpr.net (172.24.192.37) with Microsoft SMTP Server (TLS) id 8.3.213.0; Mon, 7 Jan 2013 07:50:26 -0800
Received: from o365mail.juniper.net (207.17.137.149) by o365mail.juniper.net (172.24.192.59) with Microsoft SMTP Server id 14.1.355.2; Mon, 7 Jan 2013 07:50:26 -0800
Received: from co1outboundpool.messaging.microsoft.com (216.32.180.186) by o365mail.juniper.net (207.17.137.149) with Microsoft SMTP Server (TLS) id 14.1.355.2; Mon, 7 Jan 2013 07:52:36 -0800
Received: from mail177-co1-R.bigfish.com (10.243.78.213) by CO1EHSOBE013.bigfish.com (10.243.66.76) with Microsoft SMTP Server id 14.1.225.23; Mon, 7 Jan 2013 15:50:25 +0000
Received: from mail177-co1 (localhost [127.0.0.1])	by mail177-co1-R.bigfish.com (Postfix) with ESMTP id 7023398011A	for <ietf@ietf.org.FOPE.CONNECTOR.OVERRIDE>; Mon,  7 Jan 2013 15:50:25 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.242.197; KIP:(null); UIP:(null); (null); H:BL2PRD0512HT003.namprd05.prod.outlook.com; R:internal; EFV:INT
X-SpamScore: 1
X-BigFish: PS1(zz98dI9371Ida00hzz1de0h1202h1e76h1d1ah1d2ah1082kzz8275chz2dh2a8h668h839h944hd25he5bhf0ah1220h1288h12a5h12a9h12bdh137ah13b6h1441h1504h1537h153bh162dh1631h1758h1155h)
Received: from mail177-co1 (localhost.localdomain [127.0.0.1]) by mail177-co1 (MessageSwitch) id 1357573823996735_32235; Mon,  7 Jan 2013 15:50:23 +0000 (UTC)
Received: from CO1EHSMHS015.bigfish.com (unknown [10.243.78.203])	by mail177-co1.bigfish.com (Postfix) with ESMTP id F146A900106; Mon,  7 Jan 2013 15:50:23 +0000 (UTC)
Received: from BL2PRD0512HT003.namprd05.prod.outlook.com (157.56.242.197) by CO1EHSMHS015.bigfish.com (10.243.66.25) with Microsoft SMTP Server (TLS) id 14.1.225.23; Mon, 7 Jan 2013 15:50:20 +0000
Received: from BL2PRD0512MB614.namprd05.prod.outlook.com ([169.254.9.165]) by BL2PRD0512HT003.namprd05.prod.outlook.com ([10.255.233.36]) with mapi id 14.16.0245.002; Mon, 7 Jan 2013 15:50:17 +0000
From: John Scudder <jgs@juniper.net>
To: John Day <jeanjour@comcast.net>
Subject: Re: A proposal for a scientific approach to this question [was	Re: I'm struggling with 2219 language again]
Thread-Topic: A proposal for a scientific approach to this question [was	Re: I'm struggling with 2219 language again]
Thread-Index: AQHN7JJ9+4KZ60tG4kWRpNOAqIvUBJg+BDum
Date: Mon, 7 Jan 2013 15:50:16 +0000
Message-ID: <A23D1754-2416-41D9-ADD3-7A89CFA34BDF@juniper.net>
References: <CADnDZ8_GgVeapUKefFMqOvwOo00X8_rFDWMR0vb-Zvu_p=yT3A@mail.gmail.com>, <a062408a2cd10003cf574@[10.0.1.3]>
In-Reply-To: <a062408a2cd10003cf574@[10.0.1.3]>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [75.151.14.9]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-FOPE-CONNECTOR: Id%0$Dn%*$RO%0$TLS%0$FQDN%$TlsDn%
X-FOPE-CONNECTOR: Id%12219$Dn%IETF.ORG$RO%2$TLS%5$FQDN%onpremiseedge-1018244.customer.frontbridge.com$TlsDn%o365mail.juniper.net
X-FOPE-CONNECTOR: Id%12219$Dn%COMCAST.NET$RO%2$TLS%5$FQDN%onpremiseedge-1018244.customer.frontbridge.com$TlsDn%o365mail.juniper.net
Cc: ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 07 Jan 2013 15:50:50 -0000

On Jan 6, 2013, at 11:50 PM, "John Day" <jeanjour@comcast.net> wrote:

> However, in the IETF there is also a requirement that there be two indepe=
ndent but communicating implementations for an RFC to standards-track. Corr=
ect?

Alas, no.=20

--John=


From ned+ietf@mauve.mrochek.com  Mon Jan  7 08:00:44 2013
Return-Path: <ned+ietf@mauve.mrochek.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 33AA721F86DC for <ietf@ietfa.amsl.com>; Mon,  7 Jan 2013 08:00:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 Q6YtuIVhYpS4 for <ietf@ietfa.amsl.com>; Mon,  7 Jan 2013 08:00:43 -0800 (PST)
Received: from mauve.mrochek.com (mauve.mrochek.com [66.59.230.40]) by ietfa.amsl.com (Postfix) with ESMTP id 7940321F86C4 for <ietf@ietf.org>; Mon,  7 Jan 2013 08:00:43 -0800 (PST)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01OOP9710KHS004MU6@mauve.mrochek.com> for ietf@ietf.org; Mon, 7 Jan 2013 07:55:40 -0800 (PST)
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01OOOK7O8W0W00008T@mauve.mrochek.com> (original mail from NED@mauve.mrochek.com) for ietf@ietf.org; Mon, 7 Jan 2013 07:55:33 -0800 (PST)
From: ned+ietf@mauve.mrochek.com
Message-id: <01OOP96WJL0G00008T@mauve.mrochek.com>
Date: Mon, 07 Jan 2013 07:41:55 -0800 (PST)
Subject: Re: A proposal for a scientific approach to this question [was Re:	I'm struggling with 2219 language again]
In-reply-to: "Your message dated Mon, 07 Jan 2013 13:31:15 +0000" <50EACE23.7040407@gmail.com>
MIME-version: 1.0
Content-type: TEXT/PLAIN
References: <CADnDZ8_GgVeapUKefFMqOvwOo00X8_rFDWMR0vb-Zvu_p=yT3A@mail.gmail.com> <a062408a2cd10003cf574@[10.0.1.3]> <50EAA93C.6060206@cisco.com> <a062408a5cd106d980f2d@[10.0.1.3]> <50EAC2C3.2080807@cisco.com> <50EACE23.7040407@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Cc: ietf <ietf@ietf.org>, stbryant@cisco.com
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 07 Jan 2013 16:00:44 -0000

> On 07/01/2013 12:42, Stewart Bryant wrote:
> > Indeed an interesting additional question.
> >
> > My view is that you MUST NOT use RFC2119 language, unless you MUST use
> > it, for exactly that reason. What is important is "on the wire" (a term
> > that from experience is very difficult to define) inter-operation, and
> > implementers need to be free to achieve that though any means that suits
> > them.

> Agreed. Imagine the effect if the TCP standard had said that a particular
> congestion control algorithm was mandatory. Oh, wait...

> ... RFC 1122 section 4.2.2.15 says that a TCP MUST implement reference [TCP:7]
> which is Van's SIGCOMM'88 paper. So apparently any TCP that uses a more recent
> congestion control algorithm is non-conformant. Oh, wait...

> ... RFC 2001 is a proposed standard defining congestion control algorithms,
> but it doesn't update RFC 1122, and it uses lower-case. Oh, wait...

> RFC 2001 is obsoleted by RFC 2581 which obsoleted by RFC 5681. These both
> use RFC 2119 keywords, but they still don't update RFC 1122.

> This is such a rat's nest that it has a guidebook (RFC 5783, "Congestion
> Control in the RFC Series") and of course it's still an open research topic.

> Attempting to validate TCP implementations on the basis of conformance
> with RFC 2119 keywords would be, well, missing the point.

> I know this is an extreme case, but I believe it shows the futility of
> trying to be either legalistic or mathematical in this area.

Exactly. Looking for cases where the use/non-use of capitalized terms caused an
interoperability failure is a bit silly, because the use/non-use of such terms
doesn't carry that sort of weight.

What does happen is that implementation and therefore interoperability quality
can suffer when standards emphasize the wrong points of compliance. Things
work, but not as well as they should or could.

A fairly common case of this in application protocols is an emphasis on
low-level limits and restrictions while ignoring higher-level requirements. For
example, our email standards talk a fair bit about so-called "minimim maximums"
that in practice are rarely an issue, all the while failing to specify a
mandatory minimum set of semantics all agents must support. This has led to
lack of interoperable functionality in the long term.

Capitalized terms are both a blessing and a curse in this regard. They make it
easy to point out the really important stuff. But in doing so, they also
make it easy to put the emphasis in the wrong places.

tl;dr: Capitulized terms are a tool, and like any tool they can be misused.

				Ned

From jeanjour@comcast.net  Mon Jan  7 08:18:17 2013
Return-Path: <jeanjour@comcast.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 937C721F890E for <ietf@ietfa.amsl.com>; Mon,  7 Jan 2013 08:18:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.437
X-Spam-Level: 
X-Spam-Status: No, score=-100.437 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_NET=0.611,  RDNS_NONE=0.1, USER_IN_WHITELIST=-100]
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 64iOYzDPo0Tg for <ietf@ietfa.amsl.com>; Mon,  7 Jan 2013 08:18:16 -0800 (PST)
Received: from qmta03.westchester.pa.mail.comcast.net (qmta03.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:43:76:96:62:32]) by ietfa.amsl.com (Postfix) with ESMTP id 8ED7021F8903 for <ietf@ietf.org>; Mon,  7 Jan 2013 08:18:16 -0800 (PST)
Received: from omta19.westchester.pa.mail.comcast.net ([76.96.62.98]) by qmta03.westchester.pa.mail.comcast.net with comcast id l2YL1k00127AodY534JG1D; Mon, 07 Jan 2013 16:18:16 +0000
Received: from [10.0.1.3] ([98.229.211.49]) by omta19.westchester.pa.mail.comcast.net with comcast id l4JF1k00H14WE023f4JFlF; Mon, 07 Jan 2013 16:18:16 +0000
Mime-Version: 1.0
Message-Id: <a062408b4cd10a475eb1d@[10.0.1.3]>
In-Reply-To: <A23D1754-2416-41D9-ADD3-7A89CFA34BDF@juniper.net>
References: <CADnDZ8_GgVeapUKefFMqOvwOo00X8_rFDWMR0vb-Zvu_p=yT3A@mail.gmail.com>, <a062 408a2cd10003cf574@[10.0.1.3]> <A23D1754-2416-41D9-ADD3-7A89CFA34BDF@juniper.net>
Date: Mon, 7 Jan 2013 11:12:56 -0500
To: John Scudder <jgs@juniper.net>, John Day <jeanjour@comcast.net>
From: John Day <jeanjour@comcast.net>
Subject: Re: A proposal for a scientific approach to this question [was Re:  	I'm struggling with 2219 language again]
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20121106; t=1357575496; bh=bOXJGD1iXdF30+jIT6GklYR/gYzjES1G+bhBx66IcdA=; h=Received:Received:Mime-Version:Message-Id:Date:To:From:Subject: Content-Type; b=GKfyhk5QhT6NksOz9ID9GAtUjuvq65zttIw3ZVCl6Z2fK6UA2Kp91sG7GorBi3zCO g9xi311AS50zN+/9TzZGdP+SGY8bwQz75CBb+r3On8lHy0VHKjmHzBq4C9vHhvgcG/ 74PQbQCGOhoUIs/EkeoptGtYiv2YjYg/TZ+WEQe2PLpcovZO0EUjHFfeCvvvBm8pCS d73QBgBA23iROuy/WFZMqdzo9JC0sguSQX58QOyx4m9vZA4I9F/DP3TuzFPbptYd9u ZQPOCYQbUG73BU66pKB3l9WK0tcNJ37xS0yVL/XA7tUknDQOeqoJesX37hhmzqxt0u gd+D+tk32XG/A==
Cc: ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 07 Jan 2013 16:18:17 -0000

Alas, indeed.  ;-)


At 3:50 PM +0000 1/7/13, John Scudder wrote:
>On Jan 6, 2013, at 11:50 PM, "John Day" <jeanjour@comcast.net> wrote:
>
>>  However, in the IETF there is also a requirement that there be two 
>>independent but communicating implementations for an RFC to 
>>standards-track. Correct?
>
>Alas, no.
>
>--John


From worley@shell01.TheWorld.com  Mon Jan  7 08:19:40 2013
Return-Path: <worley@shell01.TheWorld.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 03ACF21F89EE for <ietf@ietfa.amsl.com>; Mon,  7 Jan 2013 08:19:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.98
X-Spam-Level: 
X-Spam-Status: No, score=-2.98 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, RCVD_IN_SORBS_WEB=0.619]
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 JKgwqpZ4X8aF for <ietf@ietfa.amsl.com>; Mon,  7 Jan 2013 08:19:39 -0800 (PST)
Received: from TheWorld.com (pcls5.std.com [192.74.137.145]) by ietfa.amsl.com (Postfix) with ESMTP id E564321F8994 for <ietf@ietf.org>; Mon,  7 Jan 2013 08:19:38 -0800 (PST)
Received: from shell.TheWorld.com (root@shell01.theworld.com [192.74.137.71]) by TheWorld.com (8.14.5/8.14.5) with ESMTP id r07GJPoB032460; Mon, 7 Jan 2013 11:19:27 -0500
Received: from shell01.TheWorld.com (localhost.theworld.com [127.0.0.1]) by shell.TheWorld.com (8.13.6/8.12.8) with ESMTP id r07GJPLV4687360; Mon, 7 Jan 2013 11:19:25 -0500 (EST)
Received: (from worley@localhost) by shell01.TheWorld.com (8.13.6/8.13.6/Submit) id r07GJPHP4704236; Mon, 7 Jan 2013 11:19:25 -0500 (EST)
Date: Mon, 7 Jan 2013 11:19:25 -0500 (EST)
Message-Id: <201301071619.r07GJPHP4704236@shell01.TheWorld.com>
From: worley@ariadne.com (Dale R. Worley)
Sender: worley@ariadne.com (Dale R. Worley)
To: eng.mahmoudemam@yahoo.com, ietf@ietf.org
In-reply-to: <CADnDZ8-2ez_Hjb6rUMtJrB2ckfDXk6jek2x5PrXUvLyS5O_QYQ@mail.gmail.com> (abdussalambaryun@gmail.com)
Subject: Re: Hello ::Please I need to know LEACH protocol standard???
References: <CADnDZ8-2ez_Hjb6rUMtJrB2ckfDXk6jek2x5PrXUvLyS5O_QYQ@mail.gmail.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 07 Jan 2013 16:19:40 -0000

> I am a researcher of Master's degree , working on LEACH routing
> protocol for wireless sensor networks and i need to know for which
> standard does LEACH , its family ,or even Layer 3 belong to.

A Google search suggests that LEACH has not been standardized.  LEACH
appears to have been invented by academics; several papers have been
published about it.

In regard to "layer 3", see http://en.wikipedia.org/wiki/OSI_model

Dale

From mmorley@mpcm.com  Sun Jan  6 19:23:50 2013
Return-Path: <mmorley@mpcm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 735AA21F8555 for <ietf@ietfa.amsl.com>; Sun,  6 Jan 2013 19:23:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.976
X-Spam-Level: 
X-Spam-Status: No, score=-2.976 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
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 o5t0OqVliaML for <ietf@ietfa.amsl.com>; Sun,  6 Jan 2013 19:23:49 -0800 (PST)
Received: from mail-la0-f43.google.com (mail-la0-f43.google.com [209.85.215.43]) by ietfa.amsl.com (Postfix) with ESMTP id B7F8A21F8542 for <ietf@ietf.org>; Sun,  6 Jan 2013 19:23:48 -0800 (PST)
Received: by mail-la0-f43.google.com with SMTP id eg20so14315415lab.16 for <ietf@ietf.org>; Sun, 06 Jan 2013 19:23:47 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :x-gm-message-state; bh=ro39O8NhduStT3XQnHzOKdba0RXxFCku6N1ZtKZwe+0=; b=T+lGO1V3ghs/jOKLpcj9T7zG6i+wXkEVVd9qgldI9Gujnk5bZZBQvLflo5qxqKr7Vh p9U2EwoxPZ4MO5AXpkIh/Gn6DT5bOqG2ZoOdEda2ViL0ElTRb2pXahrb6bqKZs7O1D+O hoUjQbtcgx9n/fZJXQao97j/geG0qL12DNW78jliBaNhCgqdEZA5Y0AQeajk3h5el9v4 d36+jfyumPccZgA25oh+iEnwd6isnGsAHz4tPXXir4CphVvq8Wlmrxkp5wFHnEHwdl1P zeZ//T3sk1MSpUuw1Sc98NkH6JvhaEQw6j0phZl3/SSzyfOG6/2U9gfZsdlgKQwoeyur HPaA==
MIME-Version: 1.0
Received: by 10.112.87.40 with SMTP id u8mr24179427lbz.50.1357529027336; Sun, 06 Jan 2013 19:23:47 -0800 (PST)
Sender: mmorley@mpcm.com
Received: by 10.114.38.137 with HTTP; Sun, 6 Jan 2013 19:23:47 -0800 (PST)
In-Reply-To: <CAChr6SxorKO20rGYi-e4YNF=HNGrwz8wPGKCFZQYWQwqsetjjg@mail.gmail.com>
References: <20121211150057.28223.93310.idtracker@ietfa.amsl.com> <50cb04b9.86df440a.72fe.1e20SMTPIN_ADDED_BROKEN@mx.google.com> <CABP7RbeNsZ_rBWRjou=VG+hBhUKaOz+y1a0sSChwWiHte9znnQ@mail.gmail.com> <50cb5f3c.694c420a.38fb.39afSMTPIN_ADDED_BROKEN@mx.google.com> <CAChr6SxZRc3B_HCbw76kLe2dsRSr43r-gLpfMVnCUfJTrZdTLA@mail.gmail.com> <CABP7RbfA33huBFadMeXTTEt=MkjW8-d4DFH7+GLXGurnm9sSRw@mail.gmail.com> <CAOXDeqpPE4eNy_qJpDPdPHbCQakG9-hDcNZ3Sj9r4kWedByVzQ@mail.gmail.com> <CAChr6SwtS_=iS-k4mJm1vHjEvvGVzay5jDYeGheqsPZqO-89CQ@mail.gmail.com> <EABB8F51-C3B4-49F5-8672-5C2ABAC7043A@mnot.net> <CAChr6Sx7JdKM91EwJaSZ0Ra_F4FSqkuc3vzTY1LM=F_8sWho+Q@mail.gmail.com> <1357515310.6827.23.camel@polyglot> <CAChr6SyAq=7aQdZn54ihYK+0hDhL--2Oaq0RvehoNFbwKNNShA@mail.gmail.com> <CAChr6SxorKO20rGYi-e4YNF=HNGrwz8wPGKCFZQYWQwqsetjjg@mail.gmail.com>
Date: Sun, 6 Jan 2013 22:23:47 -0500
X-Google-Sender-Auth: Ny6xVmqSjYgYU1tb3ochhYuU63Q
Message-ID: <CAOXDeqqE2mCLapwvjwQkme5VTpRCfmF0mFQcx02WW0-zi4i5=g@mail.gmail.com>
Subject: Re: [apps-discuss] Last Call: <draft-ietf-appsawg-json-pointer-07.txt> (JSON Pointer) to Proposed Standard
From: Matthew Morley <matt@mpcm.com>
To: Robert Sayre <sayrer@gmail.com>
Content-Type: multipart/alternative; boundary=bcaec554df40725ba304d2aa5b85
X-Gm-Message-State: ALoCoQkseFN0BN9XMR5BpHemeDeMh+JmTe/uzFafyzJU4WYqijcqqNmAYh821wImFeRPyHqzQvfI
X-Mailman-Approved-At: Mon, 07 Jan 2013 08:26:22 -0800
Cc: IETF Apps Discuss <apps-discuss@ietf.org>, Mark Nottingham <mnot@mnot.net>, IETF Discussion <ietf@ietf.org>, "Paul C. Bryan" <pbryan@anode.ca>, IESG <iesg@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 07 Jan 2013 03:23:50 -0000

--bcaec554df40725ba304d2aa5b85
Content-Type: text/plain; charset=ISO-8859-1

On Sun, Jan 6, 2013 at 8:15 PM, Robert Sayre <sayrer@gmail.com> wrote:

> On Sun, Jan 6, 2013 at 4:01 PM, Robert Sayre <sayrer@gmail.com> wrote:
> > On Sun, Jan 6, 2013 at 3:35 PM, Paul C. Bryan <pbryan@anode.ca> wrote:
> >>
> >>
> >> Common concurrent editing algorithms should, in my opinion, use
> techniques
> >> to ensure the state of the resource (relative to the edits) is known. In
> >> HTTP, we have ETag and If-Match/If-None-Match preconditions. In JSON
> Patch,
> >> we have (a rudimentary) test operation.
> ...
> > links to make sure we're not talking past each other:
>
> Actually, let me restate my point in terms of RFC5789 (HTTP PATCH).
> That will make it easier to communicate.
>
> RFC 5789 Section 2.2 (Error Handling) defines error conditions which
> correspond directly to the point at hand: 'Conflicting state' and
> 'Conflicting modification'. Section 5 of the JSON Patch document
> directly references RFC5789, Section 2.2.
>
> With that in mind, let's note that there are several normative
> requirements in the JSON Patch document directed at conflicting state.
> One such example is from Section 4.2 'remove'. It reads: "The target
> location MUST exist for the operation to be successful.". If a server
> received an HTTP JSON Patch request attempting to delete a
> non-existent location, this text from RFC5789 would seem to apply:
>
> "Conflicting state:  Can be specified with a 409 (Conflict) status
>       code when the request cannot be applied given the state of the
>       resource.  For example, if the client attempted to apply a
>       structural modification and the structures assumed to exist did
>       not exist ..."
>
> The text above wouldn't be necessary in JSON Patch or RFC5789 if
> RFC5789 required checking ETags and preconditions for all use cases
> (it doesn't). The larger point is that RFC5789, and patch formats in
> general, make all sorts of allowances for *non-conflicting* concurrent
> edits to a common ancestor. The problem with leaving this JSON Pointer
> array ambiguity in the draft is that patch messages which should
> trigger '409 Conflict' errors can be mistakenly and 'successfully' (in
> the HTTP sense) applied to a different structure than intended.
>
> In summary, the JSON Patch draft allows patch documents to be
> formulated that make it impossible to correctly implement RFC5789, a
> normative reference.
>
> Here are the questions the IESG focuses on during review:
> "Reviews should focus on these questions: 'Is this document a
> reasonable basis on which to build the salient part of the Internet
> infrastructure? If not, what changes would make it so?'"
>
> For JSON Patch, the answer to the first question is 'no', because of a
> deficiency in JSON Pointer. The change needed to make these documents
> acceptable as part of the Internet infrastructure is to make Arrays
> explicit in JSON Pointer syntax.
>
> - Rob
>

For me the deficiency is not in the pointer, but patch format being
generated.

One approach is to push that *one* test, structure conformity, into the
pointer syntax. Another is via the type operation.

If a vague patch is generated, vague results are to be expected.

Testing for *just* the structure does not really create a verbose patch
either. Which is why I am not overly in favor of a syntax specific to
arrays, with this argument.

For example, if you are replacing a key in a object, the json-pointer to
get there, *and* the value would be required to ensure it is not
vague. Setting /a/b/c to 6 when it was 4, and applying that patch without
such tests to a document where /a/b/c is 13, is also vague.

Without tests, the patch format is optimistic at best, there is no escaping
this fact. Changing the spec for the json-pointer syntax to address
vagueness in json-patch specification seems wrong to me.

If json-pointer is not well suited, because of the desire for a descriptive
path which includes structure and value, perhaps a different specification
is need. One that provides both path, structure, and value confirmation in
the pointer string. Though at that point is more of a query path, so
something like JsonPath (http://goessner.net/articles/JsonPath/)?

I prefer the test/type operations and the json-pointer specification, with
optimistic patches.

-- 
Matthew P. C. Morley

--bcaec554df40725ba304d2aa5b85
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On Sun, Jan 6, 2013 at 8:15 PM, Robert Sayre <span dir=3D"ltr">&lt;<a href=
=3D"mailto:sayrer@gmail.com" target=3D"_blank">sayrer@gmail.com</a>&gt;</sp=
an> wrote:<br><div class=3D"gmail_quote"><blockquote class=3D"gmail_quote" =
style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class=3D"im">On Sun, Jan 6, 2013 at 4:01 PM, Robert Sayre &lt;<a href=
=3D"mailto:sayrer@gmail.com">sayrer@gmail.com</a>&gt; wrote:<br>
&gt; On Sun, Jan 6, 2013 at 3:35 PM, Paul C. Bryan &lt;<a href=3D"mailto:pb=
ryan@anode.ca">pbryan@anode.ca</a>&gt; wrote:<br>
&gt;&gt;<br>
&gt;&gt;<br>
</div><div class=3D"im">&gt;&gt; Common concurrent editing algorithms shoul=
d, in my opinion, use techniques<br>
&gt;&gt; to ensure the state of the resource (relative to the edits) is kno=
wn. In<br>
&gt;&gt; HTTP, we have ETag and If-Match/If-None-Match preconditions. In JS=
ON Patch,<br>
&gt;&gt; we have (a rudimentary) test operation.<br>
</div>...<br>
<div class=3D"im">&gt; links to make sure we&#39;re not talking past each o=
ther:<br>
<br>
</div>Actually, let me restate my point in terms of RFC5789 (HTTP PATCH).<b=
r>
That will make it easier to communicate.<br>
<br>
RFC 5789 Section 2.2 (Error Handling) defines error conditions which<br>
correspond directly to the point at hand: &#39;Conflicting state&#39; and<b=
r>
&#39;Conflicting modification&#39;. Section 5 of the JSON Patch document<br=
>
directly references RFC5789, Section 2.2.<br>
<br>
With that in mind, let&#39;s note that there are several normative<br>
requirements in the JSON Patch document directed at conflicting state.<br>
One such example is from Section 4.2 &#39;remove&#39;. It reads: &quot;The =
target<br>
location MUST exist for the operation to be successful.&quot;. If a server<=
br>
received an HTTP JSON Patch request attempting to delete a<br>
non-existent location, this text from RFC5789 would seem to apply:<br>
<br>
&quot;Conflicting state: =A0Can be specified with a 409 (Conflict) status<b=
r>
=A0 =A0 =A0 code when the request cannot be applied given the state of the<=
br>
=A0 =A0 =A0 resource. =A0For example, if the client attempted to apply a<br=
>
=A0 =A0 =A0 structural modification and the structures assumed to exist did=
<br>
=A0 =A0 =A0 not exist ...&quot;<br>
<br>
The text above wouldn&#39;t be necessary in JSON Patch or RFC5789 if<br>
RFC5789 required checking ETags and preconditions for all use cases<br>
(it doesn&#39;t). The larger point is that RFC5789, and patch formats in<br=
>
general, make all sorts of allowances for *non-conflicting* concurrent<br>
edits to a common ancestor. The problem with leaving this JSON Pointer<br>
array ambiguity in the draft is that patch messages which should<br>
trigger &#39;409 Conflict&#39; errors can be mistakenly and &#39;successful=
ly&#39; (in<br>
the HTTP sense) applied to a different structure than intended.<br>
<br>
In summary, the JSON Patch draft allows patch documents to be<br>
formulated that make it impossible to correctly implement RFC5789, a<br>
normative reference.<br>
<br>
Here are the questions the IESG focuses on during review:<br>
&quot;Reviews should focus on these questions: &#39;Is this document a<br>
reasonable basis on which to build the salient part of the Internet<br>
infrastructure? If not, what changes would make it so?&#39;&quot;<br>
<br>
For JSON Patch, the answer to the first question is &#39;no&#39;, because o=
f a<br>
deficiency in JSON Pointer. The change needed to make these documents<br>
acceptable as part of the Internet infrastructure is to make Arrays<br>
explicit in JSON Pointer syntax.<br>
<div class=3D"HOEnZb"><div class=3D"h5"><br>
- Rob<br></div></div></blockquote></div><br>For me the deficiency is not in=
 the pointer, but patch format being generated.<br><br>One approach is to p=
ush that *one* test, structure=A0conformity, into the pointer syntax.=A0Ano=
ther is via the type operation.<br>
<br>If a vague patch is generated, vague results are to be expected.<br><br=
>Testing for *just* the structure does not really create a verbose patch ei=
ther. Which is why I am not overly in favor of a syntax specific to arrays,=
 with this argument.<br>
<br>For example, if you are replacing a key in a object, the json-pointer t=
o get there, *and* the value would be required to ensure it is not vague.=
=A0Setting /a/b/c to 6 when it was 4, and applying that patch without such =
tests to a document where /a/b/c is 13, is also vague. =A0<br>
<br>Without tests, the patch format is optimistic at best, there is no esca=
ping this fact. Changing the spec for the json-pointer syntax to address va=
gueness in json-patch specification seems wrong to me.<br><br>If json-point=
er is not well suited, because of the desire for a descriptive path which i=
ncludes structure and value, perhaps a different=A0specification is need. O=
ne that provides both path, structure, and value confirmation in the pointe=
r string. Though at that point is more of a query path, so something like J=
sonPath (<a href=3D"http://goessner.net/articles/JsonPath/">http://goessner=
.net/articles/JsonPath/</a>)?<br>
<div><br>I prefer the test/type operations and the json-pointer specificati=
on, with optimistic patches.<br><br></div>-- <br>Matthew P. C. Morley

--bcaec554df40725ba304d2aa5b85--

From pbryan@anode.ca  Sun Jan  6 15:35:13 2013
Return-Path: <pbryan@anode.ca>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C089B21F8586; Sun,  6 Jan 2013 15:35:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001]
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 ZBk35INM1-ZQ; Sun,  6 Jan 2013 15:35:13 -0800 (PST)
Received: from maple.anode.ca (maple.anode.ca [72.14.183.184]) by ietfa.amsl.com (Postfix) with ESMTP id 006FA21F8584; Sun,  6 Jan 2013 15:35:12 -0800 (PST)
Received: from [192.168.1.1] (S0106a021b762dbb3.vf.shawcable.net [174.1.50.247]) by maple.anode.ca (Postfix) with ESMTPSA id AFBE56AB7; Sun,  6 Jan 2013 23:35:11 +0000 (UTC)
Message-ID: <1357515310.6827.23.camel@polyglot>
Subject: Re: [apps-discuss] Last Call: <draft-ietf-appsawg-json-pointer-07.txt> (JSON Pointer) to Proposed Standard
From: "Paul C. Bryan" <pbryan@anode.ca>
To: Robert Sayre <sayrer@gmail.com>
Date: Sun, 06 Jan 2013 15:35:10 -0800
In-Reply-To: <CAChr6Sx7JdKM91EwJaSZ0Ra_F4FSqkuc3vzTY1LM=F_8sWho+Q@mail.gmail.com>
References: <20121211150057.28223.93310.idtracker@ietfa.amsl.com> <50cb04b9.86df440a.72fe.1e20SMTPIN_ADDED_BROKEN@mx.google.com> <CABP7RbeNsZ_rBWRjou=VG+hBhUKaOz+y1a0sSChwWiHte9znnQ@mail.gmail.com> <50cb5f3c.694c420a.38fb.39afSMTPIN_ADDED_BROKEN@mx.google.com> <CAChr6SxZRc3B_HCbw76kLe2dsRSr43r-gLpfMVnCUfJTrZdTLA@mail.gmail.com> <CABP7RbfA33huBFadMeXTTEt=MkjW8-d4DFH7+GLXGurnm9sSRw@mail.gmail.com> <CAOXDeqpPE4eNy_qJpDPdPHbCQakG9-hDcNZ3Sj9r4kWedByVzQ@mail.gmail.com> <CAChr6SwtS_=iS-k4mJm1vHjEvvGVzay5jDYeGheqsPZqO-89CQ@mail.gmail.com> <EABB8F51-C3B4-49F5-8672-5C2ABAC7043A@mnot.net> <CAChr6Sx7JdKM91EwJaSZ0Ra_F4FSqkuc3vzTY1LM=F_8sWho+Q@mail.gmail.com>
Content-Type: multipart/alternative; boundary="=-B1xg1qOCqeQSYLxluh/N"
X-Mailer: Evolution 3.4.4-1 
Mime-Version: 1.0
X-Mailman-Approved-At: Mon, 07 Jan 2013 08:26:31 -0800
Cc: Mark Nottingham <mnot@mnot.net>, IETF Discussion <ietf@ietf.org>, IETF Apps Discuss <apps-discuss@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 06 Jan 2013 23:35:13 -0000

--=-B1xg1qOCqeQSYLxluh/N
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit

> On Sat, 2013-01-05 at 16:19 -0800, Robert Sayre wrote:


[snip]


> 1) The ambiguity around arrays makes the patch format unsuitable for
> common concurrent editing algorithms.


Common concurrent editing algorithms should, in my opinion, use
techniques to ensure the state of the resource (relative to the edits)
is known. In HTTP, we have ETag and If-Match/If-None-Match
preconditions. In JSON Patch, we have (a rudimentary) test operation.

[snip]


> 3) It's not possible to tell whether a JSON Pointer document is
> syntactically correct in isolation.


There is no such thing as a JSON Pointer document.


> This issue is a problem in practice, and it's a problem in theory as
> well. JSON-Patch messages aren't sufficiently self-descriptive, so
> they aren't appropriate for use in a RESTful system.


99% of RESTful systems I'm familiar with are based on HTTP. Where
optimistic concurrency is acceptable, HTTP preconditions seems to
provide acceptable coverage. Where more granularity or more pessimistic
concurrency is required, implementors are free to use their own
mechanisms, including more expressive predicates (as has been proposed
here, with my endorsement) and/or resource locking. These are
intentionally out of scope for JSON Patch.

Later in this thread, you wrote:


> Ah. I meant that the WG seems to be favoring "running code" a little
> too heavily in the presence of a bug. It's an old argument, and it's
> boring: "We can't change it now, there are already twelve users!"


I don't agree that this is a bug; it lacks a feature that you and some
others have requested. Our reasoning for resisting such change is
legitimate.

The reason I value implementations is because they endorse the
specification through tangible action. Some of their authors have
participated in this forum to help improve the specification and create
consensus around it. Unfortunately, you've raised objections quite late
in the process, and I'm personally not persuaded that the issues you've
raised warrants (likely significant) changes.

Paul

--=-B1xg1qOCqeQSYLxluh/N
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: 7bit

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
  <META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
  <META NAME="GENERATOR" CONTENT="GtkHTML/4.4.4">
</HEAD>
<BODY>
<BLOCKQUOTE TYPE=CITE>
    On Sat, 2013-01-05 at 16:19 -0800, Robert Sayre wrote:<BR>
</BLOCKQUOTE>
<BR>
[snip]<BR>
<BR>
<BLOCKQUOTE TYPE=CITE>
    1) The ambiguity around arrays makes the patch format unsuitable for common concurrent editing algorithms.<BR>
</BLOCKQUOTE>
<BR>
Common concurrent editing algorithms should, in my opinion, use techniques to ensure the state of the resource (relative to the edits) is known. In HTTP, we have ETag and If-Match/If-None-Match preconditions. In JSON Patch, we have (a rudimentary) test operation.<BR>
<BR>
[snip]<BR>
<BR>
<BLOCKQUOTE TYPE=CITE>
    3) It's not possible to tell whether a JSON Pointer document is syntactically correct in isolation.<BR>
</BLOCKQUOTE>
<BR>
There is no such thing as a JSON Pointer document.<BR>
<BR>
<BLOCKQUOTE TYPE=CITE>
    This issue is a problem in practice, and it's a problem in theory as well. JSON-Patch messages aren't sufficiently self-descriptive, so they aren't appropriate for use in a RESTful system.<BR>
</BLOCKQUOTE>
<BR>
99% of RESTful systems I'm familiar with are based on HTTP. Where optimistic concurrency is acceptable, HTTP preconditions seems to provide acceptable coverage. Where more granularity or more pessimistic concurrency is required, implementors are free to use their own mechanisms, including more expressive predicates (as has been proposed here, with my endorsement) and/or resource locking. These are intentionally out of scope for JSON Patch.<BR>
<BR>
Later in this thread, you wrote:<BR>
<BR>
<BLOCKQUOTE TYPE=CITE>
    <FONT COLOR="#2e3436">Ah. I meant that the WG seems to be favoring &quot;running code&quot; a little too heavily in the presence of a bug. It's an old argument, and it's boring: &quot;We can't change it now, there are already twelve users!&quot;</FONT><BR>
</BLOCKQUOTE>
<BR>
I don't agree that this is a bug; it lacks a feature that you and some others have requested. Our reasoning for resisting such change is legitimate.<BR>
<BR>
The reason I value implementations is because they endorse the specification through tangible action. Some of their authors have participated in this forum to help improve the specification and create consensus around it. Unfortunately, you've raised objections quite late in the process, and I'm personally not persuaded that the issues you've raised warrants (likely significant) changes.<BR>
<BR>
Paul
</BODY>
</HTML>

--=-B1xg1qOCqeQSYLxluh/N--


From ned+ietf@mauve.mrochek.com  Mon Jan  7 08:31:34 2013
Return-Path: <ned+ietf@mauve.mrochek.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C659821F890E for <ietf@ietfa.amsl.com>; Mon,  7 Jan 2013 08:31:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[AWL=1.000,  BAYES_00=-2.599, GB_I_LETTER=-2]
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 X-Ef8kp7w5Hy for <ietf@ietfa.amsl.com>; Mon,  7 Jan 2013 08:31:34 -0800 (PST)
Received: from mauve.mrochek.com (mauve.mrochek.com [66.59.230.40]) by ietfa.amsl.com (Postfix) with ESMTP id 5B66021F8901 for <ietf@ietf.org>; Mon,  7 Jan 2013 08:31:33 -0800 (PST)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01OOPAA7CG74004V2R@mauve.mrochek.com> for ietf@ietf.org; Mon, 7 Jan 2013 08:26:29 -0800 (PST)
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01OOOK7O8W0W00008T@mauve.mrochek.com> (original mail from NED@mauve.mrochek.com) for ietf@ietf.org; Mon, 7 Jan 2013 08:26:24 -0800 (PST)
From: ned+ietf@mauve.mrochek.com
Message-id: <01OOPAA4ZBDC00008T@mauve.mrochek.com>
Date: Mon, 07 Jan 2013 08:04:03 -0800 (PST)
Subject: Re: I'm struggling with 2219 language again
In-reply-to: "Your message dated Mon, 07 Jan 2013 09:34:20 -0600" <50EAEAFC.1070707@qti.qualcomm.com>
MIME-version: 1.0
Content-type: TEXT/PLAIN; format=flowed
References: <7ED55FF1-3E1A-4DF7-918E-07790517B848@softarmor.com> <50E68CB5.4010107@gmail.com> <201301042223.r04MNgRA020196@cichlid.raleigh.ibm.com> <01OOLLQ4P2AE00008S@mauve.mrochek.com> <50EAEAFC.1070707@qti.qualcomm.com>
To: Pete Resnick <presnick@qti.qualcomm.com>
Cc: ned+ietf@mauve.mrochek.com, Thomas Narten <narten@us.ibm.com>, ietf@ietf.org, Dean Willis <dean.willis@softarmor.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 07 Jan 2013 16:31:34 -0000

> Dean, I am struggling constantly with 2119 as an AD, because if I take
> the letter (and the spirit) of 2119 at face value, a lot of people are
> doing this wrong. And 2119 is a BCP; it's one of our process documents.
> So I'd like this to be cleared up as much as you. I think there is
> active harm in the misuse we are seeing.

> To Ned's points:

> On 1/4/13 7:05 PM, ned+ietf@mauve.mrochek.com wrote:
> >> +1 to Brian and others saying upper case should be used sparingly, and
> >> only where it really matters. If even then.
> >>
> > That's the entire point: The terms provide additional information as to
> > what the authors consider the important points of compliance to be.
> >

> We will like end up in violent agreement, but I think the above
> statement is incorrect. Nowhere in 2119 will you find the words
> "conform" or conformance" or "comply" or "compliance", and I think
> there's a reason for that: We long ago found that we did not really care
> about conformance or compliance in the IETF. What we cared about was
> interoperability of independently developed implementations, because
> independently developing implementations that interoperate with other
> folks is what makes the Internet robust. Importantly, we specifically
> did not want to dictate how you write your code or tell you specific
> algorithms to follow; that makes for everyone implementing the same
> brittle code.

Meh. I know the IETF has a thing about these terms, and insofar as they  can
lead to the use of and/or overreliance on compliance testing rather than
interoperability testing, I agree with that sentiment.

OTOH, when it comes to actually, you know, writing code, this entire attitude
is IMNSHO more than a little precious. Maybe I've missed them, but in my
experience our avoidance of these terms has not resulted in the magical
creation of a widely available perfect reference implementation that allows me
to check interoperability. In fact in a lot of cases when I write code I have
absolutely nothing to test against - and this is often true even when I'm
implementing a standard that's been around for many years.

In such cases the use of compliance language - and yes, it is compliance
language, the avoidance of that term in RFC 2119 notwithstanding - is
essential. And for that matter it's still compliance language even if RFC 2119
terms are not used.

I'll also note that RFC 1123 most certainly does use the term "compliant" in
regards to capitalized terms it defines, and if nitpicking on this point
becames an issue I have zero problem replacing references to RFC 2119 with
references to RFC 1123 in the future.

All that said, I'll again point out that these terms are a double-edged sword,
and can be used to put the emphasis in the wrong place or even to specify
downright silly requirements. But that's a argument for better review of our
specifications, because saying "MUST do this stupid and couterproductive thing"
isn't fixed in any real sense by removing the capitalization.

> The useful function of 2119 is that it allows us to document the
> important *behavioral* requirements that I have to be aware of when I am
> implementing (e.g., even though it's not obvious, my implementation MUST
> send such-and-so or the other side is going to crash and burn; e.g.,
> even though it's not obvious, the other side MAY send this-and-that, and
> therefore my implementation needs to be able to handle it). And those
> "even though it's not obvious" statements are important. It wastes my
> time as an implementer to try to figure out what interoperability
> requirement is meant by, "You MUST implement a variable to keep track of
> such-and-so-state" (and yes, we see these in specs lately), and it makes
> for everyone potentially implementing the same broken code.

Good point. Pointing out the nonobvious bits where things have to be done in a
certain way is probably the most important use-case for these terms.

				Ned

From dean.willis@softarmor.com  Mon Jan  7 12:19:12 2013
Return-Path: <dean.willis@softarmor.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DAB3221F88D6 for <ietf@ietfa.amsl.com>; Mon,  7 Jan 2013 12:19:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.599
X-Spam-Level: 
X-Spam-Status: No, score=-103.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
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 QfDQQ-BGuNEL for <ietf@ietfa.amsl.com>; Mon,  7 Jan 2013 12:19:11 -0800 (PST)
Received: from mail-gh0-f171.google.com (mail-gh0-f171.google.com [209.85.160.171]) by ietfa.amsl.com (Postfix) with ESMTP id B9C1221F88CC for <ietf@ietf.org>; Mon,  7 Jan 2013 12:19:11 -0800 (PST)
Received: by mail-gh0-f171.google.com with SMTP id r17so2525690ghr.2 for <ietf@ietf.org>; Mon, 07 Jan 2013 12:19:11 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=softarmor.com; s=google; h=x-received:content-type:mime-version:subject:from:in-reply-to:date :content-transfer-encoding:message-id:references:to:x-mailer; bh=KrISDGUgbC98768DKl5EogY41Ql1vAVb1kpvCY2Mvjw=; b=cFD0hOqenChXSoYujlWtwW6AbDsYeUIUQll1rQv/Z8BtmA/YxL5yiRJXChwUUa0OKX rUnKl8MBDRuvYwqVT7NK11nD3/b84N9iYnRfalBDMAjqE0pEKZQTVxMoITfXqEIPb2yx mLvV3/IOfKJUk4Hqr8sVuVqzSOmLMkOFAud2A=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:content-type:mime-version:subject:from:in-reply-to:date :content-transfer-encoding:message-id:references:to:x-mailer :x-gm-message-state; bh=KrISDGUgbC98768DKl5EogY41Ql1vAVb1kpvCY2Mvjw=; b=dNaCxlGgrXf/AkOYkuObSgIRH3SyaLuyHVZCq0nJh2VvY/eEPb7z6Ww55vSMcXGwkT osjtOa2pVH6dXVzrcotpgDVsy6M/2gXlyd66asZLEHy+Ogi6L1S3Z6Wdvrs5pRyMHqLo Rfuo4Jt9Dx9rJ5EBH1l95UP5m+Ib9alD1flmOUJvXz4NeX3QD38OYW/GHowJq1wm1CU5 hp+SI/ICEKMbzImqXb0tQGBaAvqmToFt/ob34y/fuOCXFyeKxq5GFUQFCwh1wF3Zm2td 2Crr8I7MEJv5IxqQnmlDGC0QplusLILr7eWJye+eyVKCrmBb4q78kO2srrPWBx04xYHn TJ/g==
X-Received: by 10.236.141.81 with SMTP id f57mr69656035yhj.13.1357589951237; Mon, 07 Jan 2013 12:19:11 -0800 (PST)
Received: from [10.202.225.173] ([76.199.251.252]) by mx.google.com with ESMTPS id k63sm68265055yhj.20.2013.01.07.12.19.10 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 07 Jan 2013 12:19:10 -0800 (PST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Subject: Re: I'm struggling with 2219 language again
From: Dean Willis <dean.willis@softarmor.com>
In-Reply-To: <50E717D8.50003@isi.edu>
Date: Mon, 7 Jan 2013 14:19:09 -0600
Content-Transfer-Encoding: quoted-printable
Message-Id: <96EA00BE-F53D-41DA-BA73-65C7287D19C1@softarmor.com>
References: <7ED55FF1-3E1A-4DF7-918E-07790517B848@softarmor.com> <50E68CB5.4010107@gmail.com> <50E717D8.50003@isi.edu>
To: "ietf@ietf.org" <ietf@ietf.org>
X-Mailer: Apple Mail (2.1499)
X-Gm-Message-State: ALoCoQn9Z4apD5KetTqpiJ1k3kjs/DoQJ7u3UzaBUbDepGX6/hkGoiFyjgeBbhJ/6xo8oA5swWNb
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 07 Jan 2013 20:19:13 -0000

Well, I've learned some things here, and shall attempt to summarize:

1) First. the "1" key is really close to the "2" key, and my =
spell-checker doesn't care. Apparently,  I'm not alone in this problem.

2) We're all over the map in our use of 2119 language, and it is =
creating many headaches beyond my own.

3) The majority of respondents feel that 2119 language should be used as =
stated in 2119 -- sparingly, and free that MUST is not a substitute for =
"does". But some people feel we need a more formal specification =
language that goes beyond "key point compliance" or "requirements =
definition", and some are using 2119 words in that role and like it.

I'm torn as to what to do with the draft in question. I picked up an =
editorial role after the authors fatigued in response to some 100+ AD =
comments (with several DISCUSSes) and a gen-art review that proposed =
adding several hundred 2119 invocations (and that was backed up with a =
DISCUSS demeaning that the gen-art comments be dealt with). My =
co-editor, who is doing most of the key-stroking, favors lots of 2119 =
language. And I think it turns the draft into unreadable felrgercarb.

But there's nothing hard we can point to and say "This is the =
guideline", because usage has softened the guidelines in 2119 itself. =
It's rather like those rules in one's Home Owner's Association handbooks =
that can no longer be enforced because widespread violations have =
already been approved.

There appears to be interest in clarification, but nobody really wants =
to revise the immortal words of RFC 2119, although there is a proposal =
to add a few more words, like IF and THEN to the vocabulary (I'm hoping =
for GOTO, myself; perhaps we can make 2119 a Turing-complete language.)

--
Dean
=20





From framefritti@gmail.com  Mon Jan  7 12:40:16 2013
Return-Path: <framefritti@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4C9B221F88EA for <ietf@ietfa.amsl.com>; Mon,  7 Jan 2013 12:40:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 fkigjMwc6eL2 for <ietf@ietfa.amsl.com>; Mon,  7 Jan 2013 12:40:10 -0800 (PST)
Received: from mail-la0-f49.google.com (mail-la0-f49.google.com [209.85.215.49]) by ietfa.amsl.com (Postfix) with ESMTP id 0566B21F88E8 for <ietf@ietf.org>; Mon,  7 Jan 2013 12:40:09 -0800 (PST)
Received: by mail-la0-f49.google.com with SMTP id fk20so16744569lab.8 for <ietf@ietf.org>; Mon, 07 Jan 2013 12:40:09 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=at7RaqOsgpqfrMKAqAZwJ1lvLfyrAg0WZs4Sq0x5Tj0=; b=H5V7dJ9yA6Kj7fHJ6M5cYxbTUeUJfGVhjJHkpNLv/u0U5iAD4lnu9HubfQ+0G331Rd 7FCqMS4k07aLsl9mo8so2uDGyV35HOPDRIcz7ornSeUcgHHKJrFY8JWVn7swIujzP4vr dVi+8Se4ZlOWY0O4ELfmuzEixf+dOgwERK5tODwqgiZfj1QNRk8GWp3no4oyQ+/eGzQ4 WIGHcF94Em0tRDWYKFINoKAcGa+VQPfSma3C2iQVmBccIyf1WnXFuEF9SiqZ8xRdiJ9D XnntkgXrjr3X/iB8W9hvMfLMz/loBlypPhuEHv2Z5zsjgRvAmp9bGZPFA+nU2YKStcxi zSnQ==
MIME-Version: 1.0
Received: by 10.112.85.35 with SMTP id e3mr23915361lbz.106.1357591208935; Mon, 07 Jan 2013 12:40:08 -0800 (PST)
Received: by 10.112.108.133 with HTTP; Mon, 7 Jan 2013 12:40:08 -0800 (PST)
In-Reply-To: <96EA00BE-F53D-41DA-BA73-65C7287D19C1@softarmor.com>
References: <7ED55FF1-3E1A-4DF7-918E-07790517B848@softarmor.com> <50E68CB5.4010107@gmail.com> <50E717D8.50003@isi.edu> <96EA00BE-F53D-41DA-BA73-65C7287D19C1@softarmor.com>
Date: Mon, 7 Jan 2013 21:40:08 +0100
Message-ID: <CABSMSPUw0_JP7KfuRGi8=qHXL4yOxZR8qvttF9FixedEZ24X5w@mail.gmail.com>
Subject: Re: I'm struggling with 2219 language again
From: Riccardo Bernardini <framefritti@gmail.com>
To: Dean Willis <dean.willis@softarmor.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 07 Jan 2013 20:40:16 -0000

>
> There appears to be interest in clarification, but nobody really wants to=
 revise the immortal words of RFC 2119, although there is a proposal to add=
 a few more words, like IF and THEN to the vocabulary (I'm hoping for GOTO,=
 myself; perhaps we can make 2119 a Turing-complete language.)
>

Hmm... GOTO is bad style... Why not the COME FROM from
Intercal?http://en.wikipedia.org/wiki/INTERCAL   :-) (sorry, could not
resist...)

From swb@internet2.edu  Mon Jan  7 12:49:38 2013
Return-Path: <swb@internet2.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D449421F8967 for <ietf@ietfa.amsl.com>; Mon,  7 Jan 2013 12:49:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.099
X-Spam-Level: 
X-Spam-Status: No, score=-5.099 tagged_above=-999 required=5 tests=[AWL=1.500,  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 JmF9JP2NSZG7 for <ietf@ietfa.amsl.com>; Mon,  7 Jan 2013 12:49:38 -0800 (PST)
Received: from tx2outboundpool.messaging.microsoft.com (tx2ehsobe005.messaging.microsoft.com [65.55.88.15]) by ietfa.amsl.com (Postfix) with ESMTP id 3034421F88CA for <ietf@ietf.org>; Mon,  7 Jan 2013 12:49:37 -0800 (PST)
Received: from mail71-tx2-R.bigfish.com (10.9.14.240) by TX2EHSOBE009.bigfish.com (10.9.40.29) with Microsoft SMTP Server id 14.1.225.23; Mon, 7 Jan 2013 20:49:37 +0000
Received: from mail71-tx2 (localhost [127.0.0.1])	by mail71-tx2-R.bigfish.com (Postfix) with ESMTP id 0AECB3E010C; Mon,  7 Jan 2013 20:49:37 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.232.165; KIP:(null); UIP:(null); IPV:NLI; H:BLUPRD0810HT003.namprd08.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: -6
X-BigFish: S-6(zzbb2dI98dI179dN1432Izz1d77h1de0h1202h1e76h1d1ah1d2ah1082kz8dhz8275dh17326ahz2dh2a8h668h839h947hd25he5bhf0ah1288h12a5h12a9h12bdh137ah13b6h1441h1504h1537h153bh162dh1631h1758h1765h1155h)
Received: from mail71-tx2 (localhost.localdomain [127.0.0.1]) by mail71-tx2 (MessageSwitch) id 1357591775234354_1891; Mon,  7 Jan 2013 20:49:35 +0000 (UTC)
Received: from TX2EHSMHS015.bigfish.com (unknown [10.9.14.252])	by mail71-tx2.bigfish.com (Postfix) with ESMTP id 2A8EA600E8; Mon,  7 Jan 2013 20:49:35 +0000 (UTC)
Received: from BLUPRD0810HT003.namprd08.prod.outlook.com (157.56.232.165) by TX2EHSMHS015.bigfish.com (10.9.99.115) with Microsoft SMTP Server (TLS) id 14.1.225.23; Mon, 7 Jan 2013 20:49:31 +0000
Received: from swbi2mbp.local (67.241.75.185) by pod51019.outlook.com (10.255.125.38) with Microsoft SMTP Server (TLS) id 14.16.245.2; Mon, 7 Jan 2013 20:49:29 +0000
Message-ID: <50EB34D7.7000702@internet2.edu>
Date: Mon, 7 Jan 2013 15:49:27 -0500
From: Scott Brim <swb@internet2.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: Riccardo Bernardini <framefritti@gmail.com>
Subject: Re: I'm struggling with 2219 language again
References: <7ED55FF1-3E1A-4DF7-918E-07790517B848@softarmor.com> <50E68CB5.4010107@gmail.com> <50E717D8.50003@isi.edu> <96EA00BE-F53D-41DA-BA73-65C7287D19C1@softarmor.com> <CABSMSPUw0_JP7KfuRGi8=qHXL4yOxZR8qvttF9FixedEZ24X5w@mail.gmail.com>
In-Reply-To: <CABSMSPUw0_JP7KfuRGi8=qHXL4yOxZR8qvttF9FixedEZ24X5w@mail.gmail.com>
X-Enigmail-Version: 1.4.6
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
X-Originating-IP: [67.241.75.185]
X-OriginatorOrg: internet2.edu
Cc: "ietf@ietf.org" <ietf@ietf.org>, Dean Willis <dean.willis@softarmor.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 07 Jan 2013 20:49:38 -0000

On 01/07/13 15:40, Riccardo Bernardini allegedly wrote:
>>
>> There appears to be interest in clarification, but nobody really wants to revise the immortal words of RFC 2119, although there is a proposal to add a few more words, like IF and THEN to the vocabulary (I'm hoping for GOTO, myself; perhaps we can make 2119 a Turing-complete language.)
>>
> 
> Hmm... GOTO is bad style... Why not the COME FROM from
> Intercal?http://en.wikipedia.org/wiki/INTERCAL   :-) (sorry, could not
> resist...)
> 

unwind-protect shall rule them all

but I digress


From petithug@acm.org  Mon Jan  7 13:06:34 2013
Return-Path: <petithug@acm.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9ECF421F8A0C for <ietf@ietfa.amsl.com>; Mon,  7 Jan 2013 13:06:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.954
X-Spam-Level: 
X-Spam-Status: No, score=-101.954 tagged_above=-999 required=5 tests=[AWL=0.646, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
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 Z5f7r85jCwEE for <ietf@ietfa.amsl.com>; Mon,  7 Jan 2013 13:06:33 -0800 (PST)
Received: from implementers.org (implementers.org [IPv6:2604:3400:dc1:41:216:3eff:fe5b:8240]) by ietfa.amsl.com (Postfix) with ESMTP id 930E721F8900 for <ietf@ietf.org>; Mon,  7 Jan 2013 13:06:33 -0800 (PST)
Received: from [IPv6:2601:9:4b80:32:c43a:546e:d347:2aad] (unknown [IPv6:2601:9:4b80:32:c43a:546e:d347:2aad]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (Client CN "Marc Petit-Huguenin", Issuer "implementers.org" (verified OK)) by implementers.org (Postfix) with ESMTPS id 0332320373; Mon,  7 Jan 2013 21:06:30 +0000 (UTC)
Message-ID: <50EB38E2.7090909@acm.org>
Date: Mon, 07 Jan 2013 13:06:42 -0800
From: Marc Petit-Huguenin <petithug@acm.org>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.11) Gecko/20121122 Icedove/10.0.11
MIME-Version: 1.0
To: Dean Willis <dean.willis@softarmor.com>
Subject: Re: I'm struggling with 2219 language again
References: <7ED55FF1-3E1A-4DF7-918E-07790517B848@softarmor.com> <50E68CB5.4010107@gmail.com> <50E717D8.50003@isi.edu> <96EA00BE-F53D-41DA-BA73-65C7287D19C1@softarmor.com>
In-Reply-To: <96EA00BE-F53D-41DA-BA73-65C7287D19C1@softarmor.com>
X-Enigmail-Version: 1.4.1
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 07 Jan 2013 21:06:34 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On 01/07/2013 12:19 PM, Dean Willis wrote:
> 
> Well, I've learned some things here, and shall attempt to summarize:
> 
> 1) First. the "1" key is really close to the "2" key, and my spell-checker 
> doesn't care. Apparently,  I'm not alone in this problem.
> 
> 2) We're all over the map in our use of 2119 language, and it is creating 
> many headaches beyond my own.
> 
> 3) The majority of respondents feel that 2119 language should be used as 
> stated in 2119 -- sparingly, and free that MUST is not a substitute for 
> "does". But some people feel we need a more formal specification language 
> that goes beyond "key point compliance" or "requirements definition", and 
> some are using 2119 words in that role and like it.
> 
> I'm torn as to what to do with the draft in question. I picked up an 
> editorial role after the authors fatigued in response to some 100+ AD 
> comments (with several DISCUSSes) and a gen-art review that proposed
> adding several hundred 2119 invocations (and that was backed up with a
> DISCUSS demeaning that the gen-art comments be dealt with). My co-editor,
> who is doing most of the key-stroking, favors lots of 2119 language. And I
> think it turns the draft into unreadable felrgercarb.

My proposal for the aforementioned draft is to put on hold for now the edits
related to this discussion, then let the WG, IETF (during last call) and IESG
decide what to do.  The edits are done and ready to be merged, so the painful
part is already done: https://github.com/petithug/p2psip-base-master/branches.

- -- 
Marc Petit-Huguenin
Email: marc@petit-huguenin.org
Blog: http://blog.marc.petit-huguenin.org
Profile: http://www.linkedin.com/in/petithug
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iQIcBAEBCAAGBQJQ6zjKAAoJECnERZXWan7EIQ0P/RhLlXZVgXdpaxFbdO3PE1Fz
CQTaOt5oK7FT8/GGm+8AAMDOUSmlAiG5NeJ3+M0pRn3sRgNnJN/erRhv51tjax7i
PVAQrKnFFSICnIpDjLKlW86e8iTuP+9tfxDScP7Tnqwgt5f85p0FWDJls4NNVZQA
rBacSPMp8rIjoxPpWRclqSEkUGOE2TUuNHIs5ucLXKsyBu4d3JmIPFlOfD3x/Lid
FpNApKRB88tIt9IK7V8DJKOAv6wPYMtXAJrtV5clDAUGx2ntcZO9OgY50dkNs7p5
RpPLpEEq0PQb6JTRv/91hOJZ8xff4xxvqUsSNgkGniwsUKLRW3tca6yUGNowPzD1
W49/JOyojEbKx/x+AL2My6rMgor6VpatsbPx4ToVGNZ62/eo1YavSShg6DN44kvR
PNCvTAC6MhGEgATD5p9OPze5ucJDhWKh5X10gngmF6NS2i2jdQzpqkjO3zsjLoWS
zO9K1WYQaLZz81JWFvWAMUzNSz1PEXJU6dTMHZ5BqtllXShzkrinJGeDErC4gkSA
qLaG8IhDvLu3Skm1f/ygts6+2W/9W7onJaKr3ned0BLk4Hgm24hynXWP5rAoFacg
AFO7Gim9I0nTyk9gz7GdVeZcgw1kOpSnMhjC1GNFvZKa+Zmgtux5oWF0emXZemQy
9ZBoossXwqrEk6BmL6An
=4vXi
-----END PGP SIGNATURE-----

From huubatwork@gmail.com  Mon Jan  7 13:35:28 2013
Return-Path: <huubatwork@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 607BA21F88F5; Mon,  7 Jan 2013 13:35:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 lhm4V6JzJx-z; Mon,  7 Jan 2013 13:35:27 -0800 (PST)
Received: from mail-we0-f172.google.com (mail-we0-f172.google.com [74.125.82.172]) by ietfa.amsl.com (Postfix) with ESMTP id D03B521F872E; Mon,  7 Jan 2013 13:35:26 -0800 (PST)
Received: by mail-we0-f172.google.com with SMTP id r3so10734202wey.3 for <multiple recipients>; Mon, 07 Jan 2013 13:35:25 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:disposition-notification-to:date:from :reply-to:user-agent:mime-version:to:cc:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=pNezEYCkc6lw8sgzwQ/6zusZaaHO4Dnm0p4uIs9Kg5w=; b=o/J1Q1qodV8FRkpNMzdbbhQLHNFEjN6Z7R1x4B8+6QX3SJP7UnuYCzjltOtzkRPDSg xemFyWSjglab+LKboN8X7LPjUs/+044MznXRZJkuKJyFTD7idezrX+a0s8BYkD/f2TUY 4NLEbvWWS10musqkekOd3y4MzRIcmHsZb9n3Ls3iDZtnZq/rD/evmScfWvUkB6LG02Kj UtIssGZWsnTEkHZkWmmiYw9yq/xFUJ4AQb4iwDo+GYLvxfWgONSvOZUD3cHfPeBSCSHn g1lizPnh9pspgWtqwEd+ynWOEhMuCiX3kODngG/4n8wZjOjQlC713u2P/SOC5l+IZC42 qzhw==
X-Received: by 10.180.93.133 with SMTP id cu5mr11354095wib.32.1357594525855; Mon, 07 Jan 2013 13:35:25 -0800 (PST)
Received: from McAsterix.local (dhcp-077-250-051-060.chello.nl. [77.250.51.60]) by mx.google.com with ESMTPS id p2sm15582525wic.7.2013.01.07.13.35.24 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 07 Jan 2013 13:35:25 -0800 (PST)
Message-ID: <50EB3F9C.7010605@gmail.com>
Date: Mon, 07 Jan 2013 22:35:24 +0100
From: Huub van Helvoort <huubatwork@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: Greg Mirsky <gregimirsky@gmail.com>
Subject: Re: [PWE3] Gen-ART review of draft-ietf-pwe3-mpls-eth-oam-iwk-06
References: <CD08F2D5.6DC40%nabil.n.bitar@verizon.com> <CD0C3AE6.6E673%nabil.n.bitar@verizon.com> <CA+RyBmWWUQ+y7Mc1nG3+KndXCytfUkQqnNTg4ezpK2JcGyiCuQ@mail.gmail.com>
In-Reply-To: <CA+RyBmWWUQ+y7Mc1nG3+KndXCytfUkQqnNTg4ezpK2JcGyiCuQ@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "pwe3@ietf.org" <pwe3@ietf.org>, "gen-art@ietf.org" <gen-art@ietf.org>, "Bitar, Nabil N" <nabil.n.bitar@verizon.com>, "dinmohan@hotmail.com" <dinmohan@hotmail.com>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: huubatwork@gmail.com
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 07 Jan 2013 21:35:28 -0000

Hello Nabil,

Greg is almost right.

RDI == Remote Defect Indication

This is the abbreviation used in IEEE 802.1ag, Y.1731, G.707, G.8121
and rfc6428.

Regards, Huub.
====

> can we avoid different interpretation of the same abbreviation (RDI):
>
> RDI   Remote Defect Indication for Continuity Check Message
>
> RDI   Reverse Defect Indication
>
> AFAIK, the latter form is the interpretation used by both IEEE 802.1ag
> and Y.1731. How useful is the first form?
>
> Regards,
>
> Greg
>
>
>
> On Fri, Jan 4, 2013 at 8:17 AM, Bitar, Nabil N
> <nabil.n.bitar@verizon.com <mailto:nabil.n.bitar@verizon.com>> wrote:
>
>     Hi Dave,
>     Related to abbreviations comment below and to be clearer, I renamed
>     the original terminology section to "Abbreviations and Terminology".
>     I also created a subsection called "Abbreviations" ,and
>     "Terminology" became the second subsection.  Here iis how the edits look
>
>
>       3. Abbreviations and Terminology____
>
>
>         3.1. Abbreviations____
>
>     AISAlarm Indication Signal____
>
>     ACAttachment Circuit____
>
>     BFDBidirectional Forwarding Detection____
>
>     CCContinuity Check____
>
>     CCMContinuity Check Message____
>
>     CECustomer Equipment____
>
>     CVConnectivity Verification____
>
>     E-LMI Ethernet Local Management Interface____
>
>     EVCEthernet Virtual Circuit____
>
>     LDPLabel Distribution Protocol____
>
>     LoSLoss of Signal____
>
>     MAMaintenance Association____
>
>     MDMaintenance Domain____
>
>     MEMaintenance Entity____
>
>     MEGMaintenance Entity Group____
>
>     MEPMaintenance End Point____
>
>     MIPMaintenance End Point____
>
>     MPLSMultiprotocol Label Switching____
>
>     MS-PW Multi-Segment Pseudowire____
>
>     NSNative Service____
>
>     OAMOperations, Administration, and Maintenance____
>
>     PEProvider Edge____
>
>     PSNPacket Switched Network____
>
>     PWPseudowire____
>
>     RDIRemote Defect Indication for Continuity Check Message____
>
>         RDI   Reverse Defect Indication
>
>     S-PESwitching Provider Edge____
>
>     TLVType Length Value____
>
>     T-PETerminating Provider Edge____
>
>     __ __
>
>
>         3.2. Terminology____
>
>     This document uses the following terms with corresponding
>     definitions: ____
>
>     - MD Level:Maintenance Domain (MD) Level which identifies a value in
>     the range of 0-7 associated with Ethernet OAM frame. MD Level
>     identifies the span of the Ethernet OAM frame.____
>
>     - MEP:Maintenance End Point is responsible for origination and
>     termination of OAM frames for a given MEG.____
>
>     - MIP: Maintenance Intermediate Point is located between peer MEPs
>     and can process OAM frames but does not initiate or terminate them.____
>
>     Further, this document also uses the terminology and conventions
>     used in [RFC6310].____
>
>
>
>     Thanks,
>
>     Nabil

From narten@us.ibm.com  Mon Jan  7 13:47:18 2013
Return-Path: <narten@us.ibm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1155C21F84D8 for <ietf@ietfa.amsl.com>; Mon,  7 Jan 2013 13:47:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.599
X-Spam-Level: 
X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
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 wGZFOknkRsxA for <ietf@ietfa.amsl.com>; Mon,  7 Jan 2013 13:47:17 -0800 (PST)
Received: from e9.ny.us.ibm.com (e9.ny.us.ibm.com [32.97.182.139]) by ietfa.amsl.com (Postfix) with ESMTP id D937521F8496 for <ietf@ietf.org>; Mon,  7 Jan 2013 13:47:15 -0800 (PST)
Received: from /spool/local by e9.ny.us.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for <ietf@ietf.org> from <narten@us.ibm.com>; Mon, 7 Jan 2013 16:47:14 -0500
Received: from d01dlp03.pok.ibm.com (9.56.250.168) by e9.ny.us.ibm.com (192.168.1.109) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted;  Mon, 7 Jan 2013 16:47:12 -0500
Received: from d01relay04.pok.ibm.com (d01relay04.pok.ibm.com [9.56.227.236]) by d01dlp03.pok.ibm.com (Postfix) with ESMTP id 349E5C90041 for <ietf@ietf.org>; Mon,  7 Jan 2013 16:47:12 -0500 (EST)
Received: from d03av03.boulder.ibm.com (d03av03.boulder.ibm.com [9.17.195.169]) by d01relay04.pok.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id r07LlAtN158010 for <ietf@ietf.org>; Mon, 7 Jan 2013 16:47:10 -0500
Received: from d03av03.boulder.ibm.com (loopback [127.0.0.1]) by d03av03.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP id r07LkhlZ000820 for <ietf@ietf.org>; Mon, 7 Jan 2013 14:46:47 -0700
Received: from cichlid.raleigh.ibm.com (sig-9-65-234-46.mts.ibm.com [9.65.234.46]) by d03av03.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVin) with ESMTP id r07LkaB1032439 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 7 Jan 2013 14:46:40 -0700
Received: from cichlid.raleigh.ibm.com (localhost.localdomain [127.0.0.1]) by cichlid.raleigh.ibm.com (8.14.5/8.12.5) with ESMTP id r07LkXff020987; Mon, 7 Jan 2013 16:46:33 -0500
Message-Id: <201301072146.r07LkXff020987@cichlid.raleigh.ibm.com>
To: stbryant@cisco.com
Subject: Re: A proposal for a scientific approach to this question [was Re: I'm struggling with 2219 language again]
In-reply-to: <50EAC2C3.2080807@cisco.com>
References: <CADnDZ8_GgVeapUKefFMqOvwOo00X8_rFDWMR0vb-Zvu_p=yT3A@mail.gmail.com> <a062408a2cd10003cf574@[10.0.1.3]> <50EAA93C.6060206@cisco.com> <a062408a5cd106d980f2d@[10.0.1.3]> <50EAC2C3.2080807@cisco.com>
Comments: In-reply-to Stewart Bryant <stbryant@cisco.com> message dated "Mon, 07 Jan 2013 12:42:43 +0000."
Date: Mon, 07 Jan 2013 16:46:33 -0500
From: Thomas Narten <narten@us.ibm.com>
X-Content-Scanned: Fidelis XPS MAILER
x-cbid: 13010721-7182-0000-0000-0000043E616B
Cc: ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 07 Jan 2013 21:47:19 -0000

Stewart Bryant <stbryant@cisco.com> writes:

> Indeed an interesting additional question.

> My view is that you MUST NOT use RFC2119 language, unless you MUST use 
> it, for exactly that reason. What is important is "on the wire" (a term 
> that from experience is very difficult to define) inter-operation, and 
> implementers need to be free to achieve that though any means that suits 
> them.

The latter goes without saying. It's one of the "obvious" assumptions
that underlies all IETF protocols. It may not be written down, but its
always been an underlying principle.

E.g., from RFC 1971:

   A host maintains a number of data structures and flags related to
   autoconfiguration. In the following, we present conceptual variables
   and show how they are used to perform autoconfiguration. The specific
   variables are used for demonstration purposes only, and an
   implementation is not required to have them, so long as its external
   behavior is consistent with that described in this document.

Other document (that I've long forgotten) say similar things.   

That sort of language was put into specific documents specifically
because some individuals sometimes would raise the concern that a spec
was trying to "restrict" an implementation.
   
IETF specs have always been about describing external behavior
(i.e. what you can see "on the wire"), and how someone implements
internally to produce the required external behavior is none of the
IETF's business (and never has been).

(Someone earlier on this thread seemed to maybe think the above is not
a given, but it really always has been.)

Thomas


From heard@pobox.com  Mon Jan  7 17:01:34 2013
Return-Path: <heard@pobox.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AC52F21F86F5 for <ietf@ietfa.amsl.com>; Mon,  7 Jan 2013 17:01:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 8kPFUx6Nu8Vc for <ietf@ietfa.amsl.com>; Mon,  7 Jan 2013 17:01:33 -0800 (PST)
Received: from shell4.bayarea.net (shell4.bayarea.net [209.128.82.1]) by ietfa.amsl.com (Postfix) with ESMTP id C293521F86CC for <ietf@ietf.org>; Mon,  7 Jan 2013 17:01:33 -0800 (PST)
Received: (qmail 21061 invoked from network); 7 Jan 2013 17:01:33 -0800
Received: from shell4.bayarea.net (209.128.82.1) by shell4.bayarea.net with (DHE-RSA-AES256-SHA encrypted) SMTP; 7 Jan 2013 17:01:33 -0800
Date: Mon, 7 Jan 2013 17:01:33 -0800 (PST)
From: "C. M. Heard" <heard@pobox.com>
X-X-Sender: heard@shell4.bayarea.net
To: IETF Discussion <ietf@ietf.org>
Subject: Re: I'm struggling with 2219 language again
In-Reply-To: <01OOPAA4ZBDC00008T@mauve.mrochek.com>
Message-ID: <Pine.LNX.4.64.1301071655200.18718@shell4.bayarea.net>
References: <7ED55FF1-3E1A-4DF7-918E-07790517B848@softarmor.com> <50E68CB5.4010107@gmail.com> <201301042223.r04MNgRA020196@cichlid.raleigh.ibm.com> <01OOLLQ4P2AE00008S@mauve.mrochek.com> <50EAEAFC.1070707@qti.qualcomm.com> <01OOPAA4ZBDC00008T@mauve.mrochek.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 08 Jan 2013 01:01:34 -0000

On Mon, 7 Jan 2013, ned+ietf@mauve.mrochek.com wrote:
> I'll also note that RFC 1123 most certainly does use the term "compliant" in
> regards to capitalized terms it defines, and if nitpicking on this point
> becames an issue I have zero problem replacing references to RFC 2119 with
> references to RFC 1123 in the future.

+1.  There is similar language in RFC 1122 and RFC 1812.  From the standpoint 
of making the requirements clear for an implementor, I think that these three 
specifications were among the best the IETF ever produced.

//cmh

From uyeshiro@ifa.hawaii.edu  Mon Jan  7 17:41:24 2013
Return-Path: <uyeshiro@ifa.hawaii.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6313C11E80D9 for <ietf@ietfa.amsl.com>; Mon,  7 Jan 2013 17:41:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[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 G+4DnM03ErF6 for <ietf@ietfa.amsl.com>; Mon,  7 Jan 2013 17:41:23 -0800 (PST)
Received: from hale.ifa.hawaii.edu (hale.ifa.hawaii.edu [128.171.2.6]) by ietfa.amsl.com (Postfix) with ESMTP id 218BB11E80D7 for <ietf@ietf.org>; Mon,  7 Jan 2013 17:41:23 -0800 (PST)
Received: from XeonAL (xeonal [128.171.163.193]) by hale.ifa.hawaii.edu (8.13.8/8.13.8) with ESMTP id r081ev8Q021502; Mon, 7 Jan 2013 15:41:01 -1000 (HST)
From: "Robin Uyeshiro" <uyeshiro@IfA.Hawaii.Edu>
To: <ned+ietf@mauve.mrochek.com>, "'Pete Resnick'" <presnick@qti.qualcomm.com>
Subject: Compliance to a protocol description? (wasRE: I'm struggling with 2219 language again)
Date: Mon, 7 Jan 2013 15:41:28 -1000
Message-ID: <80A77E6812FA497191CF5AC3E50867C9@XeonAL>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.6863
In-Reply-To: <01OOPAA4ZBDC00008T@mauve.mrochek.com>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.6157
Thread-Index: Ac3s9HkCNFZiL7bNTPiCTENC6XC0vAALsUBg
Importance: Normal
Cc: 'Thomas Narten' <narten@us.ibm.com>, ietf@ietf.org, 'Dean Willis' <dean.willis@softarmor.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 08 Jan 2013 01:41:24 -0000

Maybe part of the job of a working group should be to both/either =
produce or
approve a reference implementation and/or a test for "interoperability"? =
 I
always thought a spec should include an acceptance test.  Contracts =
often
do.

If a company submits code that becomes reference code for =
interoperability
tests, that code is automatically interoperable and "certified".  That =
might
mean more companies would spend money to produce working code.  It might
mean that more working code gets submitted earlier, as the earliest =
approved
code would tend to become the reference.  By code, I don't mean source,
necessarily.

Then there would be a more objective test for compliance and less =
dependence
on capitalization and the description.

++++++++++++++++++++++++++++++++

  Meh. I know the IETF has a thing about these terms, and insofar as =
they
can
  lead to the use of and/or overreliance on compliance testing rather =
than
  interoperability testing, I agree with that sentiment.

  OTOH, when it comes to actually, you know, writing code, this entire
attitude
  is IMNSHO more than a little precious. Maybe I've missed them, but in =
my
  experience our avoidance of these terms has not resulted in the =
magical
  creation of a widely available perfect reference implementation that
allows me
  to check interoperability. In fact in a lot of cases when I write code =
I
have
  absolutely nothing to test against - and this is often true even when =
I'm
  implementing a standard that's been around for many years.

				Ned


From jeanjour@comcast.net  Mon Jan  7 18:09:32 2013
Return-Path: <jeanjour@comcast.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F38D921F865D for <ietf@ietfa.amsl.com>; Mon,  7 Jan 2013 18:09:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.797
X-Spam-Level: 
X-Spam-Status: No, score=-100.797 tagged_above=-999 required=5 tests=[AWL=-0.360, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_NET=0.611, RDNS_NONE=0.1, USER_IN_WHITELIST=-100]
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 5LOimKLNs+7P for <ietf@ietfa.amsl.com>; Mon,  7 Jan 2013 18:09:31 -0800 (PST)
Received: from qmta04.westchester.pa.mail.comcast.net (qmta04.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:43:76:96:62:40]) by ietfa.amsl.com (Postfix) with ESMTP id 3445621F8645 for <ietf@ietf.org>; Mon,  7 Jan 2013 18:09:31 -0800 (PST)
Received: from omta21.westchester.pa.mail.comcast.net ([76.96.62.72]) by qmta04.westchester.pa.mail.comcast.net with comcast id lCPo1k0031ZXKqc54E9Wif; Tue, 08 Jan 2013 02:09:30 +0000
Received: from [10.0.1.3] ([98.229.211.49]) by omta21.westchester.pa.mail.comcast.net with comcast id lE9V1k00r14WE023hE9WTr; Tue, 08 Jan 2013 02:09:30 +0000
Mime-Version: 1.0
Message-Id: <a06240801cd112ca0edab@[10.0.1.3]>
In-Reply-To: <201301072146.r07LkXff020987@cichlid.raleigh.ibm.com>
References: <CADnDZ8_GgVeapUKefFMqOvwOo00X8_rFDWMR0vb-Zvu_p=yT3A@mail.gmail.com> <a062408a2cd10003cf574@[10.0.1.3]> <50EAA93C.6060206@cisco.com> <a062408a5cd106d980f2d@[10.0.1.3]> <50EAC2C3.2080807@cisco.com> <201301072146.r07LkXff020987@cichlid.raleigh.ibm.com>
Date: Mon, 7 Jan 2013 21:01:05 -0500
To: Thomas Narten <narten@us.ibm.com>, stbryant@cisco.com
From: John Day <jeanjour@comcast.net>
Subject: Re: A proposal for a scientific approach to this question [was Re: I'm struggling with 2219 language again]
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20121106; t=1357610970; bh=2cVOotjh95av3cAvYFD6w1Up9RqYEtZzr4jqr5TA+VM=; h=Received:Received:Mime-Version:Message-Id:Date:To:From:Subject: Content-Type; b=Qwj+ziuitN8BYDKd1SgGCrBzIYpgfaUhLhgybpFzfT813k28g+OJuAKdQo+19qgOC v2zYMxWXwXifsI4JJxMWTUHCBGtKXK7PEMGVov12Y60GV5+vkSW0myE+l+i/qi32pa WIScouCIsbCdIy6emK8Fd+eAZwFEI65cfm8s5tPNcIHo5vnMgQMFL89ji68Cb5X39L 9EmIoxd09TXXv6TVb3Wp4i/OmbPl9ebUPgsUqKyvR4rdbL5k7b70r8OzZ2U6sXce/0 b0tsGClIdutro3vZn97JIeTNsR0N5ch9kwGWxCrXlMxS5zVTc1ttn+RfXgqJcAz/Nc cbyu94HyqUFog==
Cc: ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 08 Jan 2013 02:09:32 -0000

All standards groups that I am aware of have had the same view.  This 
is not uncommon.

Although, I would point out that the TCP specification nor do most 
protocols specifications of this type follow this rule.  State 
transitions are not visible on the wire.  The rules for sliding 
window are not described entirely in terms of the behavior seen on 
the line, etc.

I have seen specifications that attempted this and the 
implementations built from them were very different and did not come 
close to interoperating or in some cases of even doing the same thing.

In fact, I remember that we thought the new Telnet spec (1973) was a 
paragon of clarity until a new site joined the Net that had not been 
part of the commuity and came up with an implementation that bore no 
relation to what anyone else had done.

This problem is a lot more subtle than you imagine.

Take care,
John Day

At 4:46 PM -0500 1/7/13, Thomas Narten wrote:
>Stewart Bryant <stbryant@cisco.com> writes:
>
>>  Indeed an interesting additional question.
>
>>  My view is that you MUST NOT use RFC2119 language, unless you MUST use
>>  it, for exactly that reason. What is important is "on the wire" (a term
>>  that from experience is very difficult to define) inter-operation, and
>>  implementers need to be free to achieve that though any means that suits
>>  them.
>
>The latter goes without saying. It's one of the "obvious" assumptions
>that underlies all IETF protocols. It may not be written down, but its
>always been an underlying principle.
>
>E.g., from RFC 1971:
>
>    A host maintains a number of data structures and flags related to
>    autoconfiguration. In the following, we present conceptual variables
>    and show how they are used to perform autoconfiguration. The specific
>    variables are used for demonstration purposes only, and an
>    implementation is not required to have them, so long as its external
>    behavior is consistent with that described in this document.
>
>Other document (that I've long forgotten) say similar things.  
>
>That sort of language was put into specific documents specifically
>because some individuals sometimes would raise the concern that a spec
>was trying to "restrict" an implementation.
>   
>IETF specs have always been about describing external behavior
>(i.e. what you can see "on the wire"), and how someone implements
>internally to produce the required external behavior is none of the
>IETF's business (and never has been).
>
>(Someone earlier on this thread seemed to maybe think the above is not
>a given, but it really always has been.)
>
>Thomas


From johnl@iecc.com  Mon Jan  7 18:29:47 2013
Return-Path: <johnl@iecc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5E81221F87ED for <ietf@ietfa.amsl.com>; Mon,  7 Jan 2013 18:29:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.596
X-Spam-Level: 
X-Spam-Status: No, score=-110.596 tagged_above=-999 required=5 tests=[AWL=0.603, BAYES_00=-2.599, HABEAS_ACCREDITED_SOI=-4.3, RCVD_IN_BSP_TRUSTED=-4.3, USER_IN_WHITELIST=-100]
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 eBrMFjQeDlGg for <ietf@ietfa.amsl.com>; Mon,  7 Jan 2013 18:29:46 -0800 (PST)
Received: from leila.iecc.com (leila6.iecc.com [IPv6:2001:470:1f07:1126:0:4c:6569:6c61]) by ietfa.amsl.com (Postfix) with ESMTP id 41F2521F87EA for <ietf@ietf.org>; Mon,  7 Jan 2013 18:29:46 -0800 (PST)
Received: (qmail 12445 invoked from network); 8 Jan 2013 02:29:44 -0000
Received: from leila.iecc.com (64.57.183.34) by mail1.iecc.com with QMQP; 8 Jan 2013 02:29:44 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:vbr-info; s=50eb8498.xn--yuvv84g.k1301; i=johnl@user.iecc.com; bh=2o9vf9RMeqxRYMuASLTboA846HVHAIVPraC/gWMaI/U=; b=O49iel88tB1TcKfaVw5AzdtK3JQjRFwWr4MX8MZpCT6wSoyzogugaT6XWReiLEXFws3TaatcFXqtT38dqT2YRVKwAwD/KR9N4ahelefD1HuYz1tfDpo7f1vGF1mj0oAJnDbrGvPTj0EUDtEfiaL6CO36jD0lR9StW/TugyFqpfE=
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:vbr-info; s=50eb8498.xn--yuvv84g.k1301; olt=johnl@user.iecc.com; bh=2o9vf9RMeqxRYMuASLTboA846HVHAIVPraC/gWMaI/U=; b=aiQ8fGKY6Bco8L0vNgEZlm7Cpfnmz+gDzYhaKB1NTEFVyfpEKhMl8WJTEvOwXhU45xgqaoIc92mM374rcsDkmm3Ck6fBcHd5TuyN74r9gSgokvjCICb1bKKu/yCRvLzVLJG6TvvJZwzh8PIc1gDMvPs6tFqNJk9lI8Sb3onLNdc=
VBR-Info: md=iecc.com; mc=all; mv=dwl.spamhaus.org
Date: 8 Jan 2013 02:29:22 -0000
Message-ID: <20130108022922.49564.qmail@joyce.lan>
From: "John Levine" <johnl@taugh.com>
To: ietf@ietf.org
Subject: Re: I'm struggling with 2219 language again
In-Reply-To: <96EA00BE-F53D-41DA-BA73-65C7287D19C1@softarmor.com>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 7bit
Cc: dean.willis@softarmor.com
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 08 Jan 2013 02:29:47 -0000

> But some people feel we need a more formal specification language
> that goes beyond "key point compliance" or "requirements definition",
> and some are using 2119 words in that role and like it.

Having read specs like the Algol 68 report and ANSI X3.53-1976, the
PL/I standard that's largely written in VDL, I have an extremely low
opinion of specs that attempt to be very formal.  

The problem is not unlike the one with the fad for proofs of program
correctness back in the 1970s and 1980s.  Your formal thing ends up
being in effect a large chunk of software, which will have just as
many bugs as any other large chunk of software.  The PL/I standard is
famous for that; to implement it you both need to be able to decode
the VDL and to know PL/I well enough to recognize the mistakes.

What we really need to strive for is clear writing, which is not the
same thing as formal writing.  When you're writing clearly, the places
where you'd need 2119 stuff would be where you want to emphasize that
something that might seem optional or not a big deal is in fact
important and mandatory or important and forbidden.

R's,
John

From johnl@iecc.com  Mon Jan  7 18:56:55 2013
Return-Path: <johnl@iecc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 498BD21F84DA for <ietf@ietfa.amsl.com>; Mon,  7 Jan 2013 18:56:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.797
X-Spam-Level: 
X-Spam-Status: No, score=-110.797 tagged_above=-999 required=5 tests=[AWL=0.402, BAYES_00=-2.599, HABEAS_ACCREDITED_SOI=-4.3, RCVD_IN_BSP_TRUSTED=-4.3, USER_IN_WHITELIST=-100]
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 Qjjs+t5JWxpG for <ietf@ietfa.amsl.com>; Mon,  7 Jan 2013 18:56:54 -0800 (PST)
Received: from leila.iecc.com (leila6.iecc.com [IPv6:2001:470:1f07:1126:0:4c:6569:6c61]) by ietfa.amsl.com (Postfix) with ESMTP id 719DB21F84D1 for <ietf@ietf.org>; Mon,  7 Jan 2013 18:56:54 -0800 (PST)
Received: (qmail 18066 invoked from network); 8 Jan 2013 02:56:53 -0000
Received: from leila.iecc.com (64.57.183.34) by mail1.iecc.com with QMQP; 8 Jan 2013 02:56:53 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:vbr-info; s=50eb8af5.xn--i8sz2z.k1301; i=johnl@user.iecc.com; bh=An7fNFKRREVroRvKAGklfMJS7OU3TFoe/s99SX+rnrU=; b=HgQeKp8zg3VT1eeFz2+hkD07rMF0+1HTWD+UidW+0EwEJ284N6EcCZ5AFPmK5vT67gTocP+FlBhD5ypWVsk5jCh5AZ9HFISwqke95N8SLcnfaiighLB3Oib6Ww6H5hwbmxAY/YdJBGIPm8FprnaKN7RkQUneiWa35msLj67jzgs=
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:vbr-info; s=50eb8af5.xn--i8sz2z.k1301; olt=johnl@user.iecc.com; bh=An7fNFKRREVroRvKAGklfMJS7OU3TFoe/s99SX+rnrU=; b=pxwU86DlnRmCdmy5tIRAGQ3NmzuwbhacGP+4hxsn61HWYLqATe+8zpP3zBihjoXWJCNF7wssvcZgwEIia53YiPn9nDvGGI3lnew7AUFEBizHcM+YRdlxv0oa3VhTLoSEjsy9VXcBoi7hmxeJEtuab+pzc/Iw2sWq8V/3R1Bi4xs=
VBR-Info: md=iecc.com; mc=all; mv=dwl.spamhaus.org
Date: 8 Jan 2013 02:56:31 -0000
Message-ID: <20130108025631.50489.qmail@joyce.lan>
From: "John Levine" <johnl@taugh.com>
To: ietf@ietf.org
Subject: Re: travel guide for the next IETF...
In-Reply-To: <20130107022542.97244.qmail@joyce.lan>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 08 Jan 2013 02:56:55 -0000

Oh, if you were considering a visit to one of the nearby theme parks,
check out their latest hi-tech innovation:

http://www.nytimes.com/2013/01/07/business/media/at-disney-parks-a-bracelet-meant-to-build-loyalty-and-sales.html


From jeanjour@comcast.net  Mon Jan  7 19:02:49 2013
Return-Path: <jeanjour@comcast.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C7D4821F869C for <ietf@ietfa.amsl.com>; Mon,  7 Jan 2013 19:02:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.746
X-Spam-Level: 
X-Spam-Status: No, score=-100.746 tagged_above=-999 required=5 tests=[AWL=-0.309, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_NET=0.611, RDNS_NONE=0.1, USER_IN_WHITELIST=-100]
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 VM9qDZTyakvV for <ietf@ietfa.amsl.com>; Mon,  7 Jan 2013 19:02:49 -0800 (PST)
Received: from qmta03.westchester.pa.mail.comcast.net (qmta03.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:43:76:96:62:32]) by ietfa.amsl.com (Postfix) with ESMTP id 1FD3021F86A6 for <ietf@ietf.org>; Mon,  7 Jan 2013 19:02:49 -0800 (PST)
Received: from omta04.westchester.pa.mail.comcast.net ([76.96.62.35]) by qmta03.westchester.pa.mail.comcast.net with comcast id l1sA1k00G0ldTLk53F2ohB; Tue, 08 Jan 2013 03:02:48 +0000
Received: from [10.0.1.3] ([98.229.211.49]) by omta04.westchester.pa.mail.comcast.net with comcast id lF2n1k00u14WE023QF2oPi; Tue, 08 Jan 2013 03:02:48 +0000
Mime-Version: 1.0
Message-Id: <a06240800cd1136142b80@[10.0.1.3]>
In-Reply-To: <20130108022922.49564.qmail@joyce.lan>
References: <20130108022922.49564.qmail@joyce.lan>
Date: Mon, 7 Jan 2013 21:52:51 -0500
To: "John Levine" <johnl@taugh.com>, ietf@ietf.org
From: John Day <jeanjour@comcast.net>
Subject: Re: I'm struggling with 2219 language again
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20121106; t=1357614168; bh=kEuRBxQxvGj0QuFnq8Hxnw6L5dSYR92NjOz3G6kA2GQ=; h=Received:Received:Mime-Version:Message-Id:Date:To:From:Subject: Content-Type; b=TUXbFd+UgHq4E2Ry1Wz4DY4zXF/5xRi61iRf+U+MBqBq9ES09lYUN32DwVuQrKJOo rfjLNUF2401Grd0gmFtZwdAQa2qj3e5uLKY8TYVlPeH5Icr3g5Xl2sHA3XxCbICR2Q XfrpofOQxZeMBJIGE5W6GQlZdevj5djZO+94l+iD+TCyy/aHdh1MClvfMEYM0ys/lX A3TLiNwYW6lcDx2b7XP73ZNBT3o43pcinsYg5TI2RmM+NVLRUyAC794sqJGsYlswh4 GkJcwTcdXJ58Md3H16wc+nnDldET6vR1u0mStI9vZG7gWbi8dPWdqP1gpRekTDksIG PDLoCbN8gazPQ==
Cc: dean.willis@softarmor.com
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 08 Jan 2013 03:02:49 -0000

I have spent more than a little time on this problem and have 
probably looked at more approaches to specification than most, 
probably well over a 100.  I would have to agree.  Most of the very 
formal methods such as VDL or those based on writing predicates in 
the equivalent of first-order logic end up with very complex 
predicates.  Which of course means there is a higher probability of 
errors in the predicates than in the code.  (Something I pointed out 
in a review for a course of the first PhD thesis (King's Program 
Verifier) that attempted it.  Much to the chagrin of the professor.)

Of course protocols are a much simpler problem that a specification 
of a general program (finite state machine vs Turing machine), but 
even so from what I have seen the same problems exist.  As you say, 
the best answer is good clean code for the parts that are part of the 
protocol and only write requirements the parts that aren't.  The hard 
part is drawing that boundary.  There is much that is specific to the 
implementation that we often don't recognize.  The more approaches 
one can get, the better.  Triangulation works well!  ;-)

At 2:29 AM +0000 1/8/13, John Levine wrote:
>  > But some people feel we need a more formal specification language
>>  that goes beyond "key point compliance" or "requirements definition",
>>  and some are using 2119 words in that role and like it.
>
>Having read specs like the Algol 68 report and ANSI X3.53-1976, the
>PL/I standard that's largely written in VDL, I have an extremely low
>opinion of specs that attempt to be very formal. 
>
>The problem is not unlike the one with the fad for proofs of program
>correctness back in the 1970s and 1980s.  Your formal thing ends up
>being in effect a large chunk of software, which will have just as
>many bugs as any other large chunk of software.  The PL/I standard is
>famous for that; to implement it you both need to be able to decode
>the VDL and to know PL/I well enough to recognize the mistakes.
>
>What we really need to strive for is clear writing, which is not the
>same thing as formal writing.  When you're writing clearly, the places
>where you'd need 2119 stuff would be where you want to emphasize that
>something that might seem optional or not a big deal is in fact
>important and mandatory or important and forbidden.
>
>R's,
>John


From john-ietf@jck.com  Mon Jan  7 19:41:46 2013
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 737D111E8099 for <ietf@ietfa.amsl.com>; Mon,  7 Jan 2013 19:41:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.669
X-Spam-Level: 
X-Spam-Status: No, score=-101.669 tagged_above=-999 required=5 tests=[AWL=-0.930, BAYES_20=-0.74, USER_IN_WHITELIST=-100]
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 5y7pK3a+Q7A0 for <ietf@ietfa.amsl.com>; Mon,  7 Jan 2013 19:41:46 -0800 (PST)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id CF6E321F8450 for <ietf@ietf.org>; Mon,  7 Jan 2013 19:41:45 -0800 (PST)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1TsQ4O-0001Zb-Q8; Mon, 07 Jan 2013 22:41:44 -0500
Date: Mon, 07 Jan 2013 22:41:39 -0500
From: John C Klensin <john-ietf@jck.com>
To: John Levine <johnl@taugh.com>, ietf@ietf.org
Subject: Re: travel guide for the next IETF...
Message-ID: <24A2D707C70DF4A1338D34CF@JcK-HP8200.jck.com>
In-Reply-To: <20130108025631.50489.qmail@joyce.lan>
References: <20130108025631.50489.qmail@joyce.lan>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 08 Jan 2013 03:41:46 -0000

--On Tuesday, January 08, 2013 02:56 +0000 John Levine
<johnl@taugh.com> wrote:

> Oh, if you were considering a visit to one of the nearby theme
> parks, check out their latest hi-tech innovation:
> 
> http://www.nytimes.com/2013/01/07/business/media/at-disney-par
> ks-a-bracelet-meant-to-build-loyalty-and-sales.html

Maybe FedEx and Memphis would lend us some geese, so we could
pretend they are ducks and practice getting them lined up.
Otherwise, we may just need to provide the leadership with mouse
ears.  Again.

   john





From superuser@gmail.com  Mon Jan  7 20:40:22 2013
Return-Path: <superuser@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6EB4C11E8097; Mon,  7 Jan 2013 20:40:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.598
X-Spam-Level: 
X-Spam-Status: No, score=-3.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
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 utRG83JWgdBS; Mon,  7 Jan 2013 20:40:21 -0800 (PST)
Received: from mail-la0-f41.google.com (mail-la0-f41.google.com [209.85.215.41]) by ietfa.amsl.com (Postfix) with ESMTP id C276021F846E; Mon,  7 Jan 2013 20:40:20 -0800 (PST)
Received: by mail-la0-f41.google.com with SMTP id em20so8112lab.28 for <multiple recipients>; Mon, 07 Jan 2013 20:40:19 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=WWhwUo8iuICmHP0k/Wkr1TSkhuqa4juxuM6ZL+Wc5iY=; b=Q6pZjTpZAvnld7wxtJ+TqIdPVhDzFpnaLNvvfMsHxrnqMYlmSGFex/AzumtJ29+QAV dYTRV/oFAn9t1xQdLCqTvEAc5UXSzP9zWB1z9CD0atvJ/RyLyTgrXpICJLcWu8sRejX/ PMwne6tq1cdmM8Kc9x/4YQ8cYBViorkfBZDRlbf6KHWRJU5dztoHoDIX8YMc8J1jHz5M 2QeWIa4WcoAEZiowsUblOkWQUXFfdX0FbgaITz/+PqnPCPkGcdx12R9W67lg97lQIewl cvJK7OO2WyuBcTT39iWbTA1Q5qwE6zeBMj8VwjrD0XD36/9iIs27W7lTy12zYES7N5pX Jeww==
MIME-Version: 1.0
Received: by 10.112.87.104 with SMTP id w8mr26229283lbz.49.1357620019682; Mon, 07 Jan 2013 20:40:19 -0800 (PST)
Received: by 10.112.61.67 with HTTP; Mon, 7 Jan 2013 20:40:19 -0800 (PST)
In-Reply-To: <1357608790.27936.223.camel@pbryan-wsl.internal.salesforce.com>
References: <20121211150057.28223.93310.idtracker@ietfa.amsl.com> <50cb04b9.86df440a.72fe.1e20SMTPIN_ADDED_BROKEN@mx.google.com> <CABP7RbeNsZ_rBWRjou=VG+hBhUKaOz+y1a0sSChwWiHte9znnQ@mail.gmail.com> <50cb5f3c.694c420a.38fb.39afSMTPIN_ADDED_BROKEN@mx.google.com> <CAChr6SxZRc3B_HCbw76kLe2dsRSr43r-gLpfMVnCUfJTrZdTLA@mail.gmail.com> <CABP7RbfA33huBFadMeXTTEt=MkjW8-d4DFH7+GLXGurnm9sSRw@mail.gmail.com> <CAOXDeqpPE4eNy_qJpDPdPHbCQakG9-hDcNZ3Sj9r4kWedByVzQ@mail.gmail.com> <CAChr6SwtS_=iS-k4mJm1vHjEvvGVzay5jDYeGheqsPZqO-89CQ@mail.gmail.com> <EABB8F51-C3B4-49F5-8672-5C2ABAC7043A@mnot.net> <CAChr6Sx7JdKM91EwJaSZ0Ra_F4FSqkuc3vzTY1LM=F_8sWho+Q@mail.gmail.com> <1357515310.6827.23.camel@polyglot> <CAChr6SyAq=7aQdZn54ihYK+0hDhL--2Oaq0RvehoNFbwKNNShA@mail.gmail.com> <1357608790.27936.223.camel@pbryan-wsl.internal.salesforce.com>
Date: Mon, 7 Jan 2013 20:40:19 -0800
Message-ID: <CAL0qLwY5VjYrGsh-=r3B6aS3ggAjMfPYg0_pc_StEcOoL=+Ttw@mail.gmail.com>
Subject: Re: [apps-discuss] Last Call: <draft-ietf-appsawg-json-pointer-07.txt> (JSON Pointer) to Proposed Standard
From: "Murray S. Kucherawy" <superuser@gmail.com>
To: "Paul C. Bryan" <pbryan@anode.ca>
Content-Type: multipart/alternative; boundary=bcaec554e0f6035f4004d2bf8b75
Cc: Mark Nottingham <mnot@mnot.net>, IETF Discussion <ietf@ietf.org>, IETF Apps Discuss <apps-discuss@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 08 Jan 2013 04:40:22 -0000

--bcaec554e0f6035f4004d2bf8b75
Content-Type: text/plain; charset=ISO-8859-1

I apologize for being absent for this thread until now.  Vacation and
medical matters interfered with me keeping current.

First, with my participant hat on:

I've been occasionally comparing this work to conventional UNIX "patch" to
try to maintain a point of reference as these works developed.  As such,
I'm swayed by the argument (which, as I recall, was part of working group
deliberations prior to WGLC) that we have the "test" operations, so people
generating patch documents should use them to ensure proper context before
applying any of the operations that alter the target.  UNIX "patch"
accomplishes this by default by surrounding the lines to be changed in the
target with context lines that aren't changed, and so must exist precisely
as-is before the change can be made or the change is rejected.  Consider a
target file comprising 26 lines, each containing the next character of the
upper-case English alphabet and a newline, but the M and the N lines are
swapped.  A typical patch to fix this would look like so:

--- x   Mon Jan  7 20:27:36 2013
+++ y   Mon Jan  7 20:27:40 2013
@@ -10,8 +10,8 @@
 J
 K
 L
-N
 M
+N
 O
 P
 Q

The default for UNIX "diff" is to produce three lines of context above and
below the change to be made to ensure the change is being made in the right
place.  One could also request no lines of context, yielding:

--- x   Mon Jan  7 20:27:36 2013
+++ y   Mon Jan  7 20:27:40 2013
@@ -13 +12,0 @@
-N
@@ -14,0 +14 @@
+N

But this doesn't bother to check any context, except of course to ensure
that the target file is at least 14 lines long.  Although the top one is
clearly safer, both are actually legal patches.

In my view, these two JSON documents present a language for referencing and
object and changing it, and also for querying for context, just like the
conventional UNIX diff/patch format does.  But in neither the UNIX case nor
the proposed JSON case is the context part mandatory to use (though one
could certainly argue it's foolish to skip doing so).  That seems fine to
me.

Then, with my co-chair hat on:

Although I hear and understand Robert's position that this is an important
thing that needs to be addressed, it is not my view after reviewing this
thread that there's rough consensus to reopen the question.  Please note
that this is not an "it's too late in the process to change this" position,
but rather one that notes that the burden of supporting a change to
something that already has rough consensus is on the person proposing the
change, and I don't believe Robert has succeeded here.

That said, I would ask the document editors to consider adding a paragraph
or an appendix indicating this issue was considered during development of
the work and the current format was deliberately selected, preferably with
some supporting text.  This will ensure future readers will not interpret
the chosen design as a bug, but rather an intentional design choice.

-MSK, APPSAWG co-chair

On Mon, Jan 7, 2013 at 5:33 PM, Paul C. Bryan <pbryan@anode.ca> wrote:

> **
> On Sun, 2013-01-06 at 16:01 -0800, Robert Sayre wrote:
>
>  This last assertion really isn't qualified very well.
>
>
> It would have been better for me to state this is my opinion, based on
> discussions that were animated from similar objections raised in the past.
>
> Paul
>
> _______________________________________________
> apps-discuss mailing list
> apps-discuss@ietf.org
> https://www.ietf.org/mailman/listinfo/apps-discuss
>
>

--bcaec554e0f6035f4004d2bf8b75
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div><div><div><div><div><div><div><div>I apologize for be=
ing absent for this thread until now.=A0 Vacation and medical matters inter=
fered with me keeping current.<br><br></div>First, with my participant hat =
on:<br>
<br>I&#39;ve been occasionally comparing this work to conventional UNIX &qu=
ot;patch&quot; to try to maintain a point of reference as these works devel=
oped.=A0 As such, I&#39;m swayed by the argument (which, as I recall, was p=
art of working group deliberations prior to WGLC) that we have the &quot;te=
st&quot; operations, so people generating patch documents should use them t=
o ensure proper context before applying any of the operations that alter th=
e target.=A0 UNIX &quot;patch&quot; accomplishes this by default by surroun=
ding the lines to be changed in the target with context lines that aren&#39=
;t changed, and so must exist precisely as-is before the change can be made=
 or the change is rejected.=A0 Consider a target file comprising 26 lines, =
each containing the next character of the upper-case English alphabet and a=
 newline, but the M and the N lines are swapped.=A0 A typical patch to fix =
this would look like so:<br>
</div><br>--- x=A0=A0 Mon Jan=A0 7 20:27:36 2013<br>+++ y=A0=A0 Mon Jan=A0 =
7 20:27:40 2013<br>@@ -10,8 +10,8 @@<br>=A0J<br>=A0K<br>=A0L<br>-N<br>=A0M<=
br>+N<br>=A0O<br>=A0P<br>=A0Q<br><br></div>The default for UNIX &quot;diff&=
quot; is to produce three lines of context above and below the change to be=
 made to ensure the change is being made in the right place.=A0 One could a=
lso request no lines of context, yielding:<br>
<br>--- x=A0=A0 Mon Jan=A0 7 20:27:36 2013<br>+++ y=A0=A0 Mon Jan=A0 7 20:2=
7:40 2013<br>@@ -13 +12,0 @@<br>-N<br>@@ -14,0 +14 @@<br>+N<br><br></div>Bu=
t this doesn&#39;t bother to check any context, except of course to ensure =
that the target file is at least 14 lines long.=A0 Although the top one is =
clearly safer, both are actually legal patches.<br>
<br></div>In my view, these two JSON documents present a language for refer=
encing and object and changing it, and also for querying for context, just =
like the conventional UNIX diff/patch format does.=A0 But in neither the UN=
IX case nor the proposed JSON case is the context part mandatory to use (th=
ough one could certainly argue it&#39;s foolish to skip doing so).=A0 That =
seems fine to me.<br>
<br></div>Then, with my co-chair hat on:<br><br></div>Although I hear and u=
nderstand Robert&#39;s position that this is an important thing that needs =
to be addressed, it is not my view after reviewing this thread that there&#=
39;s rough consensus to reopen the question.=A0 Please note that this is no=
t an &quot;it&#39;s too late in the process to change this&quot; position, =
but rather one that notes that the burden of supporting a change to somethi=
ng that already has rough consensus is on the person proposing the change, =
and I don&#39;t believe Robert has succeeded here.<br>
<br></div>That said, I would ask the document editors to consider adding a =
paragraph or an appendix indicating this issue was considered during develo=
pment of the work and the current format was deliberately selected, prefera=
bly with some supporting text.=A0 This will ensure future readers will not =
interpret the chosen design as a bug, but rather an intentional design choi=
ce.<br>
<br>-MSK, APPSAWG co-chair<br><div><div><div><div><div><div><div><div><div =
class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Mon, Jan 7, 2013 at=
 5:33 PM, Paul C. Bryan <span dir=3D"ltr">&lt;<a href=3D"mailto:pbryan@anod=
e.ca" target=3D"_blank">pbryan@anode.ca</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><u></u>


 =20
 =20

<div><div class=3D"im">
On Sun, 2013-01-06 at 16:01 -0800, Robert Sayre wrote:<br>
<br>
<blockquote type=3D"CITE">
<pre>This last assertion really isn&#39;t qualified very well.
</pre>
</blockquote>
<br></div>
It would have been better for me to state this is my opinion, based on disc=
ussions that were animated from similar objections raised in the past. <br>=
<span class=3D"HOEnZb"><font color=3D"#888888">
<br>
Paul
</font></span></div>

<br>_______________________________________________<br>
apps-discuss mailing list<br>
<a href=3D"mailto:apps-discuss@ietf.org">apps-discuss@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/apps-discuss" target=3D"_b=
lank">https://www.ietf.org/mailman/listinfo/apps-discuss</a><br>
<br></blockquote></div><br></div></div></div></div></div></div></div></div>=
</div></div>

--bcaec554e0f6035f4004d2bf8b75--

From jasnell@gmail.com  Mon Jan  7 20:47:39 2013
Return-Path: <jasnell@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6435511E8097; Mon,  7 Jan 2013 20:47:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.098
X-Spam-Level: 
X-Spam-Status: No, score=-4.098 tagged_above=-999 required=5 tests=[AWL=-0.500, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
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 2iR0x5evJ-wp; Mon,  7 Jan 2013 20:47:38 -0800 (PST)
Received: from mail-ia0-f175.google.com (mail-ia0-f175.google.com [209.85.210.175]) by ietfa.amsl.com (Postfix) with ESMTP id 3D7E921F84E8; Mon,  7 Jan 2013 20:47:38 -0800 (PST)
Received: by mail-ia0-f175.google.com with SMTP id z3so17286336iad.34 for <multiple recipients>; Mon, 07 Jan 2013 20:47:37 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:mime-version:in-reply-to:references:from:date:message-id :subject:to:cc:content-type; bh=0xVLh/hK31Z61PfEmjR1JybJiQ0ghfzc1B1IwJLAG40=; b=x8DwHnM4Zv9eP2DOw1dUXl0O314Dr5rHH+kkppusBlhqT46QSQR9ll8cppy9dxy1tT sNy3nDvw7uIDHJeA9pxkiwBdPS0xwnf9E4cEvHX40O0mMZFssjJh1KwFAddpbgpbNIC9 8HJCXkDj3eJgl2foVxiKvJ05ly5lJdTnUvUHxxcvRKap7ePH7fYSEVKBUjt6SyAL1XJa zWJ3CRJyGM2cZ3BMeSIO2Fl6dm9ZQG3XviQvxuUYKFoyip209dV+C0slKM65YKvNDYRT cT5mafocYie96D3bE4Dxt087P9/DWZ3w4fvqw2ngGUYHONOp2x1Vv5hHy0T52z8RFff4 kDjw==
X-Received: by 10.50.219.233 with SMTP id pr9mr7607426igc.19.1357620457722; Mon, 07 Jan 2013 20:47:37 -0800 (PST)
MIME-Version: 1.0
Received: by 10.64.7.19 with HTTP; Mon, 7 Jan 2013 20:47:17 -0800 (PST)
In-Reply-To: <CAL0qLwY5VjYrGsh-=r3B6aS3ggAjMfPYg0_pc_StEcOoL=+Ttw@mail.gmail.com>
References: <20121211150057.28223.93310.idtracker@ietfa.amsl.com> <50cb04b9.86df440a.72fe.1e20SMTPIN_ADDED_BROKEN@mx.google.com> <CABP7RbeNsZ_rBWRjou=VG+hBhUKaOz+y1a0sSChwWiHte9znnQ@mail.gmail.com> <50cb5f3c.694c420a.38fb.39afSMTPIN_ADDED_BROKEN@mx.google.com> <CAChr6SxZRc3B_HCbw76kLe2dsRSr43r-gLpfMVnCUfJTrZdTLA@mail.gmail.com> <CABP7RbfA33huBFadMeXTTEt=MkjW8-d4DFH7+GLXGurnm9sSRw@mail.gmail.com> <CAOXDeqpPE4eNy_qJpDPdPHbCQakG9-hDcNZ3Sj9r4kWedByVzQ@mail.gmail.com> <CAChr6SwtS_=iS-k4mJm1vHjEvvGVzay5jDYeGheqsPZqO-89CQ@mail.gmail.com> <EABB8F51-C3B4-49F5-8672-5C2ABAC7043A@mnot.net> <CAChr6Sx7JdKM91EwJaSZ0Ra_F4FSqkuc3vzTY1LM=F_8sWho+Q@mail.gmail.com> <1357515310.6827.23.camel@polyglot> <CAChr6SyAq=7aQdZn54ihYK+0hDhL--2Oaq0RvehoNFbwKNNShA@mail.gmail.com> <1357608790.27936.223.camel@pbryan-wsl.internal.salesforce.com> <CAL0qLwY5VjYrGsh-=r3B6aS3ggAjMfPYg0_pc_StEcOoL=+Ttw@mail.gmail.com>
From: James M Snell <jasnell@gmail.com>
Date: Mon, 7 Jan 2013 20:47:17 -0800
Message-ID: <CABP7RbcEZ6sBHV6ot_JPbTPsx4psmBMrie-DiV5Ro=gPzhyMUg@mail.gmail.com>
Subject: Re: [apps-discuss] Last Call: <draft-ietf-appsawg-json-pointer-07.txt> (JSON Pointer) to Proposed Standard
To: "Murray S. Kucherawy" <superuser@gmail.com>
Content-Type: multipart/alternative; boundary=14dae934120f1f514304d2bfa505
Cc: IETF Apps Discuss <apps-discuss@ietf.org>, Mark Nottingham <mnot@mnot.net>, IETF Discussion <ietf@ietf.org>, "Paul C. Bryan" <pbryan@anode.ca>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 08 Jan 2013 04:47:39 -0000

--14dae934120f1f514304d2bfa505
Content-Type: text/plain; charset=UTF-8

If I may, I would follow this up with a suggestion that a separate I-D that
provides a more complete treatment of fully-concurrent patch operations
would be helpful. JSON-Patch is largely designed around atomic and
sequential modification operations and is not, necessarily a great match
for the kind of OT-style mechanisms Robert was referencing. I don't
personally have any use cases that would require the level of concurrency
Robert is suggesting but it would be an interesting pursuit nonetheless.


On Mon, Jan 7, 2013 at 8:40 PM, Murray S. Kucherawy <superuser@gmail.com>wrote:

> I apologize for being absent for this thread until now.  Vacation and
> medical matters interfered with me keeping current.
>
> First, with my participant hat on:
>
> I've been occasionally comparing this work to conventional UNIX "patch" to
> try to maintain a point of reference as these works developed.  As such,
> I'm swayed by the argument (which, as I recall, was part of working group
> deliberations prior to WGLC) that we have the "test" operations, so people
> generating patch documents should use them to ensure proper context before
> applying any of the operations that alter the target.  UNIX "patch"
> accomplishes this by default by surrounding the lines to be changed in the
> target with context lines that aren't changed, and so must exist precisely
> as-is before the change can be made or the change is rejected.  Consider a
> target file comprising 26 lines, each containing the next character of the
> upper-case English alphabet and a newline, but the M and the N lines are
> swapped.  A typical patch to fix this would look like so:
>
> --- x   Mon Jan  7 20:27:36 2013
> +++ y   Mon Jan  7 20:27:40 2013
> @@ -10,8 +10,8 @@
>  J
>  K
>  L
> -N
>  M
> +N
>  O
>  P
>  Q
>
> The default for UNIX "diff" is to produce three lines of context above and
> below the change to be made to ensure the change is being made in the right
> place.  One could also request no lines of context, yielding:
>
> --- x   Mon Jan  7 20:27:36 2013
> +++ y   Mon Jan  7 20:27:40 2013
> @@ -13 +12,0 @@
> -N
> @@ -14,0 +14 @@
> +N
>
> But this doesn't bother to check any context, except of course to ensure
> that the target file is at least 14 lines long.  Although the top one is
> clearly safer, both are actually legal patches.
>
> In my view, these two JSON documents present a language for referencing
> and object and changing it, and also for querying for context, just like
> the conventional UNIX diff/patch format does.  But in neither the UNIX case
> nor the proposed JSON case is the context part mandatory to use (though one
> could certainly argue it's foolish to skip doing so).  That seems fine to
> me.
>
> Then, with my co-chair hat on:
>
> Although I hear and understand Robert's position that this is an important
> thing that needs to be addressed, it is not my view after reviewing this
> thread that there's rough consensus to reopen the question.  Please note
> that this is not an "it's too late in the process to change this" position,
> but rather one that notes that the burden of supporting a change to
> something that already has rough consensus is on the person proposing the
> change, and I don't believe Robert has succeeded here.
>
> That said, I would ask the document editors to consider adding a paragraph
> or an appendix indicating this issue was considered during development of
> the work and the current format was deliberately selected, preferably with
> some supporting text.  This will ensure future readers will not interpret
> the chosen design as a bug, but rather an intentional design choice.
>
> -MSK, APPSAWG co-chair
>
> On Mon, Jan 7, 2013 at 5:33 PM, Paul C. Bryan <pbryan@anode.ca> wrote:
>
>> **
>> On Sun, 2013-01-06 at 16:01 -0800, Robert Sayre wrote:
>>
>>  This last assertion really isn't qualified very well.
>>
>>
>> It would have been better for me to state this is my opinion, based on
>> discussions that were animated from similar objections raised in the past.
>>
>> Paul
>>
>> _______________________________________________
>> apps-discuss mailing list
>> apps-discuss@ietf.org
>> https://www.ietf.org/mailman/listinfo/apps-discuss
>>
>>
>
> _______________________________________________
> apps-discuss mailing list
> apps-discuss@ietf.org
> https://www.ietf.org/mailman/listinfo/apps-discuss
>
>

--14dae934120f1f514304d2bfa505
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><font face=3D"courier new, monospace">If I may, I would fo=
llow this up with a suggestion that a separate I-D that provides a more com=
plete treatment of fully-concurrent patch operations would be helpful. JSON=
-Patch is largely designed around atomic and sequential modification operat=
ions and is not, necessarily a great match for the kind of OT-style mechani=
sms Robert was referencing. I don&#39;t personally have any use cases that =
would require the level of concurrency Robert is suggesting but it would be=
 an interesting pursuit nonetheless.</font></div>

<div class=3D"gmail_extra"><br><br><div class=3D"gmail_quote">On Mon, Jan 7=
, 2013 at 8:40 PM, Murray S. Kucherawy <span dir=3D"ltr">&lt;<a href=3D"mai=
lto:superuser@gmail.com" target=3D"_blank">superuser@gmail.com</a>&gt;</spa=
n> wrote:<br>

<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div dir=3D"ltr"><div><div><div><div><div><d=
iv><div><div>I apologize for being absent for this thread until now.=C2=A0 =
Vacation and medical matters interfered with me keeping current.<br>

<br></div>First, with my participant hat on:<br>
<br>I&#39;ve been occasionally comparing this work to conventional UNIX &qu=
ot;patch&quot; to try to maintain a point of reference as these works devel=
oped.=C2=A0 As such, I&#39;m swayed by the argument (which, as I recall, wa=
s part of working group deliberations prior to WGLC) that we have the &quot=
;test&quot; operations, so people generating patch documents should use the=
m to ensure proper context before applying any of the operations that alter=
 the target.=C2=A0 UNIX &quot;patch&quot; accomplishes this by default by s=
urrounding the lines to be changed in the target with context lines that ar=
en&#39;t changed, and so must exist precisely as-is before the change can b=
e made or the change is rejected.=C2=A0 Consider a target file comprising 2=
6 lines, each containing the next character of the upper-case English alpha=
bet and a newline, but the M and the N lines are swapped.=C2=A0 A typical p=
atch to fix this would look like so:<br>


</div><br>--- x=C2=A0=C2=A0 Mon Jan=C2=A0 7 20:27:36 2013<br>+++ y=C2=A0=C2=
=A0 Mon Jan=C2=A0 7 20:27:40 2013<br>@@ -10,8 +10,8 @@<br>=C2=A0J<br>=C2=A0=
K<br>=C2=A0L<br>-N<br>=C2=A0M<br>+N<br>=C2=A0O<br>=C2=A0P<br>=C2=A0Q<br><br=
></div>The default for UNIX &quot;diff&quot; is to produce three lines of c=
ontext above and below the change to be made to ensure the change is being =
made in the right place.=C2=A0 One could also request no lines of context, =
yielding:<br>


<br>--- x=C2=A0=C2=A0 Mon Jan=C2=A0 7 20:27:36 2013<br>+++ y=C2=A0=C2=A0 Mo=
n Jan=C2=A0 7 20:27:40 2013<br>@@ -13 +12,0 @@<br>-N<br>@@ -14,0 +14 @@<br>=
+N<br><br></div>But this doesn&#39;t bother to check any context, except of=
 course to ensure that the target file is at least 14 lines long.=C2=A0 Alt=
hough the top one is clearly safer, both are actually legal patches.<br>


<br></div>In my view, these two JSON documents present a language for refer=
encing and object and changing it, and also for querying for context, just =
like the conventional UNIX diff/patch format does.=C2=A0 But in neither the=
 UNIX case nor the proposed JSON case is the context part mandatory to use =
(though one could certainly argue it&#39;s foolish to skip doing so).=C2=A0=
 That seems fine to me.<br>


<br></div>Then, with my co-chair hat on:<br><br></div>Although I hear and u=
nderstand Robert&#39;s position that this is an important thing that needs =
to be addressed, it is not my view after reviewing this thread that there&#=
39;s rough consensus to reopen the question.=C2=A0 Please note that this is=
 not an &quot;it&#39;s too late in the process to change this&quot; positio=
n, but rather one that notes that the burden of supporting a change to some=
thing that already has rough consensus is on the person proposing the chang=
e, and I don&#39;t believe Robert has succeeded here.<br>


<br></div>That said, I would ask the document editors to consider adding a =
paragraph or an appendix indicating this issue was considered during develo=
pment of the work and the current format was deliberately selected, prefera=
bly with some supporting text.=C2=A0 This will ensure future readers will n=
ot interpret the chosen design as a bug, but rather an intentional design c=
hoice.<br>


<br>-MSK, APPSAWG co-chair<br><div><div><div><div><div><div><div><div><div =
class=3D"gmail_extra"><br><div class=3D"gmail_quote"><div><div class=3D"h5"=
>On Mon, Jan 7, 2013 at 5:33 PM, Paul C. Bryan <span dir=3D"ltr">&lt;<a hre=
f=3D"mailto:pbryan@anode.ca" target=3D"_blank">pbryan@anode.ca</a>&gt;</spa=
n> wrote:<br>


</div></div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;bo=
rder-left:1px #ccc solid;padding-left:1ex"><div><div class=3D"h5"><u></u>


 =20
 =20

<div><div>
On Sun, 2013-01-06 at 16:01 -0800, Robert Sayre wrote:<br>
<br>
<blockquote type=3D"CITE">
<pre>This last assertion really isn&#39;t qualified very well.
</pre>
</blockquote>
<br></div>
It would have been better for me to state this is my opinion, based on disc=
ussions that were animated from similar objections raised in the past. <br>=
<span><font color=3D"#888888">
<br>
Paul
</font></span></div>

<br></div></div><div class=3D"im">_________________________________________=
______<br>
apps-discuss mailing list<br>
<a href=3D"mailto:apps-discuss@ietf.org" target=3D"_blank">apps-discuss@iet=
f.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/apps-discuss" target=3D"_b=
lank">https://www.ietf.org/mailman/listinfo/apps-discuss</a><br>
<br></div></blockquote></div><br></div></div></div></div></div></div></div>=
</div></div></div>
<br>_______________________________________________<br>
apps-discuss mailing list<br>
<a href=3D"mailto:apps-discuss@ietf.org">apps-discuss@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/apps-discuss" target=3D"_b=
lank">https://www.ietf.org/mailman/listinfo/apps-discuss</a><br>
<br></blockquote></div><br></div>

--14dae934120f1f514304d2bfa505--

From sayrer@gmail.com  Mon Jan  7 22:33:04 2013
Return-Path: <sayrer@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 478AE21F87AB; Mon,  7 Jan 2013 22:33:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 ZWnmRhm-gH7c; Mon,  7 Jan 2013 22:33:03 -0800 (PST)
Received: from mail-wg0-f44.google.com (mail-wg0-f44.google.com [74.125.82.44]) by ietfa.amsl.com (Postfix) with ESMTP id 5A64021F8495; Mon,  7 Jan 2013 22:33:03 -0800 (PST)
Received: by mail-wg0-f44.google.com with SMTP id dr12so37720wgb.35 for <multiple recipients>; Mon, 07 Jan 2013 22:33:02 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=+J3QendoWh4gfNc8MPvXB04WrjNfms4WaT2TVLaPF+M=; b=KZyS8vZDxDKcr7PdbwlmoOGUvxJEJ4GrCcXjKHVY7fqqJ0K0Gjz3onOrexxU7mf2Bw a2A3qCt2LaLJ43c1NfqyaAZ4aEv2gs8HXobQKCv1QxW45gm9RPg6GSYG4IORyJfP92Mh ZgfC82aNr4pV3ydCq8CrfFNJC6177937RBwOI+odqkC3Cy3xGtuwikuwJAmw2qhNF1Gk V/WhciVK1hm8wG8dCfUhZaRRZ6zxwjqzwN4nSx0ru4BdomGorDcWkzkZ8uGWvJckWQpA UQbitllhtkJ3aeQNag4UcfzD8azI1C9SWS8m9ip1RN1qzigzuSX/ByZ3MRgek7zzkBnF lKzQ==
MIME-Version: 1.0
Received: by 10.180.88.40 with SMTP id bd8mr12679682wib.33.1357626782367; Mon, 07 Jan 2013 22:33:02 -0800 (PST)
Received: by 10.194.1.101 with HTTP; Mon, 7 Jan 2013 22:33:02 -0800 (PST)
In-Reply-To: <CAL0qLwY5VjYrGsh-=r3B6aS3ggAjMfPYg0_pc_StEcOoL=+Ttw@mail.gmail.com>
References: <20121211150057.28223.93310.idtracker@ietfa.amsl.com> <50cb04b9.86df440a.72fe.1e20SMTPIN_ADDED_BROKEN@mx.google.com> <CABP7RbeNsZ_rBWRjou=VG+hBhUKaOz+y1a0sSChwWiHte9znnQ@mail.gmail.com> <50cb5f3c.694c420a.38fb.39afSMTPIN_ADDED_BROKEN@mx.google.com> <CAChr6SxZRc3B_HCbw76kLe2dsRSr43r-gLpfMVnCUfJTrZdTLA@mail.gmail.com> <CABP7RbfA33huBFadMeXTTEt=MkjW8-d4DFH7+GLXGurnm9sSRw@mail.gmail.com> <CAOXDeqpPE4eNy_qJpDPdPHbCQakG9-hDcNZ3Sj9r4kWedByVzQ@mail.gmail.com> <CAChr6SwtS_=iS-k4mJm1vHjEvvGVzay5jDYeGheqsPZqO-89CQ@mail.gmail.com> <EABB8F51-C3B4-49F5-8672-5C2ABAC7043A@mnot.net> <CAChr6Sx7JdKM91EwJaSZ0Ra_F4FSqkuc3vzTY1LM=F_8sWho+Q@mail.gmail.com> <1357515310.6827.23.camel@polyglot> <CAChr6SyAq=7aQdZn54ihYK+0hDhL--2Oaq0RvehoNFbwKNNShA@mail.gmail.com> <1357608790.27936.223.camel@pbryan-wsl.internal.salesforce.com> <CAL0qLwY5VjYrGsh-=r3B6aS3ggAjMfPYg0_pc_StEcOoL=+Ttw@mail.gmail.com>
Date: Mon, 7 Jan 2013 22:33:02 -0800
Message-ID: <CAChr6Sy1uwUOBgzRarGoax6opp=PE_Bv1wK3b6+nDeMSpU6n-A@mail.gmail.com>
Subject: Re: [apps-discuss] Last Call: <draft-ietf-appsawg-json-pointer-07.txt> (JSON Pointer) to Proposed Standard
From: Robert Sayre <sayrer@gmail.com>
To: "Murray S. Kucherawy" <superuser@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: IETF Apps Discuss <apps-discuss@ietf.org>, Mark Nottingham <mnot@mnot.net>, IETF Discussion <ietf@ietf.org>, "Paul C. Bryan" <pbryan@anode.ca>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 08 Jan 2013 06:33:04 -0000

On Mon, Jan 7, 2013 at 8:40 PM, Murray S. Kucherawy <superuser@gmail.com> wrote:
>
> we have the "test" operations, so people
> generating patch documents should use them to ensure proper context before
> applying any of the operations that alter the target.

I don't see how can the "test" operation be used to determine the
intended target structure of an operation with a JSON Pointer of "/1".
Maybe there should be an example in the draft.

- Rob

From sayrer@gmail.com  Mon Jan  7 23:57:57 2013
Return-Path: <sayrer@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F3CAD21F87D5; Mon,  7 Jan 2013 23:57:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 j41HsCgllxhM; Mon,  7 Jan 2013 23:57:56 -0800 (PST)
Received: from mail-we0-f178.google.com (mail-we0-f178.google.com [74.125.82.178]) by ietfa.amsl.com (Postfix) with ESMTP id 208A921F87D1; Mon,  7 Jan 2013 23:57:55 -0800 (PST)
Received: by mail-we0-f178.google.com with SMTP id x43so82389wey.37 for <multiple recipients>; Mon, 07 Jan 2013 23:57:55 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=f4Zm3pUIP9ZOlZA5ntLnSiy8H727h7I7Az+pKb5N7v8=; b=ohI1YR3QlHZ84yadzyq45o1K6uX2Zi3BFvUN90nT5yS6R2i7/R6VRhKs9bE/uIQuyW 81t/zXlVqvu+kM2QNSfCQo7iEJ9PQs43iTQ68WFT9fmRv/D+v8h6xfPhOiRiFaJuNxlr dCSQoSexSwFTX00MYCtoU/qav7zJ+zvl1Q+oH1x1qr2ul+NdaobJmcWP3oyIOYRg1QKr /UDpCgsKZ+/1DpDY4cX+YcKn6SPweDybE7mH+Bo9LHHFyXM/AVu4wA/51zxqzYaPHX5U G9Z1PwKURaEEMaTIhCL0aBxHoVk9bGylCK/wc83j6Vw4u4GnZcZ4C94gec9xZ3/5Uq20 k/Jg==
MIME-Version: 1.0
Received: by 10.194.23.37 with SMTP id j5mr99616912wjf.28.1357631875372; Mon, 07 Jan 2013 23:57:55 -0800 (PST)
Received: by 10.194.1.101 with HTTP; Mon, 7 Jan 2013 23:57:55 -0800 (PST)
In-Reply-To: <CAL0qLwY5VjYrGsh-=r3B6aS3ggAjMfPYg0_pc_StEcOoL=+Ttw@mail.gmail.com>
References: <20121211150057.28223.93310.idtracker@ietfa.amsl.com> <50cb04b9.86df440a.72fe.1e20SMTPIN_ADDED_BROKEN@mx.google.com> <CABP7RbeNsZ_rBWRjou=VG+hBhUKaOz+y1a0sSChwWiHte9znnQ@mail.gmail.com> <50cb5f3c.694c420a.38fb.39afSMTPIN_ADDED_BROKEN@mx.google.com> <CAChr6SxZRc3B_HCbw76kLe2dsRSr43r-gLpfMVnCUfJTrZdTLA@mail.gmail.com> <CABP7RbfA33huBFadMeXTTEt=MkjW8-d4DFH7+GLXGurnm9sSRw@mail.gmail.com> <CAOXDeqpPE4eNy_qJpDPdPHbCQakG9-hDcNZ3Sj9r4kWedByVzQ@mail.gmail.com> <CAChr6SwtS_=iS-k4mJm1vHjEvvGVzay5jDYeGheqsPZqO-89CQ@mail.gmail.com> <EABB8F51-C3B4-49F5-8672-5C2ABAC7043A@mnot.net> <CAChr6Sx7JdKM91EwJaSZ0Ra_F4FSqkuc3vzTY1LM=F_8sWho+Q@mail.gmail.com> <1357515310.6827.23.camel@polyglot> <CAChr6SyAq=7aQdZn54ihYK+0hDhL--2Oaq0RvehoNFbwKNNShA@mail.gmail.com> <1357608790.27936.223.camel@pbryan-wsl.internal.salesforce.com> <CAL0qLwY5VjYrGsh-=r3B6aS3ggAjMfPYg0_pc_StEcOoL=+Ttw@mail.gmail.com>
Date: Mon, 7 Jan 2013 23:57:55 -0800
Message-ID: <CAChr6Syt-FYUMBOPR8wD5wKeZk2r=AK=4_CTOxgWndGUFTB1=A@mail.gmail.com>
Subject: Re: [apps-discuss] Last Call: <draft-ietf-appsawg-json-pointer-07.txt> (JSON Pointer) to Proposed Standard
From: Robert Sayre <sayrer@gmail.com>
To: "Murray S. Kucherawy" <superuser@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: IETF Apps Discuss <apps-discuss@ietf.org>, Mark Nottingham <mnot@mnot.net>, IETF Discussion <ietf@ietf.org>, "Paul C. Bryan" <pbryan@anode.ca>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 08 Jan 2013 07:57:57 -0000

On Mon, Jan 7, 2013 at 8:40 PM, Murray S. Kucherawy <superuser@gmail.com> wrote:
>
> Then, with my co-chair hat on:
>
> it is not my view after reviewing this
> thread that there's rough consensus to reopen the question.

I agree with this assessment.

- Rob

From cabo@tzi.org  Tue Jan  8 00:19:16 2013
Return-Path: <cabo@tzi.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 93FC621F8700; Tue,  8 Jan 2013 00:19:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.249
X-Spam-Level: 
X-Spam-Status: No, score=-106.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 VkwOx1T5JOfZ; Tue,  8 Jan 2013 00:19:15 -0800 (PST)
Received: from informatik.uni-bremen.de (mailhost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::12]) by ietfa.amsl.com (Postfix) with ESMTP id 99AE421F8514; Tue,  8 Jan 2013 00:19:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from smtp-fb3.informatik.uni-bremen.de (smtp-fb3.informatik.uni-bremen.de [134.102.224.120]) by informatik.uni-bremen.de (8.14.3/8.14.3) with ESMTP id r088J60f022874; Tue, 8 Jan 2013 09:19:06 +0100 (CET)
Received: from [192.168.217.105] (p54892470.dip.t-dialin.net [84.137.36.112]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp-fb3.informatik.uni-bremen.de (Postfix) with ESMTPSA id 6D28DBDE; Tue,  8 Jan 2013 09:19:06 +0100 (CET)
Subject: Re: [apps-discuss] Last Call: <draft-ietf-appsawg-json-pointer-07.txt> (JSON Pointer) to Proposed Standard
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Content-Type: text/plain; charset=windows-1252
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <CAChr6SxZRc3B_HCbw76kLe2dsRSr43r-gLpfMVnCUfJTrZdTLA@mail.gmail.com>
Date: Tue, 8 Jan 2013 09:19:05 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <018651D6-83D4-42D6-86EB-0FAA5DE10DDA@tzi.org>
References: <20121211150057.28223.93310.idtracker@ietfa.amsl.com> <50cb04b9.86df440a.72fe.1e20SMTPIN_ADDED_BROKEN@mx.google.com> <CABP7RbeNsZ_rBWRjou=VG+hBhUKaOz+y1a0sSChwWiHte9znnQ@mail.gmail.com> <50cb5f3c.694c420a.38fb.39afSMTPIN_ADDED_BROKEN@mx.google.com> <CAChr6SxZRc3B_HCbw76kLe2dsRSr43r-gLpfMVnCUfJTrZdTLA@mail.gmail.com>
To: Robert Sayre <sayrer@gmail.com>
X-Mailer: Apple Mail (2.1499)
Cc: Markus Lanthaler <markus.lanthaler@gmx.net>, IETF Apps Discuss <apps-discuss@ietf.org>, IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 08 Jan 2013 08:19:16 -0000

For those who wonder what all the fuzz in this thread is about, let me =
try to explain this with some different terminology, exposing what kind =
of intuition these widely diverging value judgements might derive from.

In programming, there are two camps: static typers and dynamic typers.  =
Static typers want to annotate their programs with information about the =
objects being manipulated so the compiler can help them catch careless =
mistakes even before the program runs.  Dynamic typers don't care about =
that as much, because they know they have to write tests anyway (not all =
programming errors are exposable as type errors) and these will uncover =
the same careless mistakes.  [The runtime system will actually check =
types once the specific context of execution is available, that's why =
it's called "dynamic typing".]

The programming debate is beside the point here for a number of =
reasons*), but it does shape the thinking of programmers, and it seems =
in particular it shaped the thinking of some of the commenters here.

/a/1/b/2 is something that a dynamic typer would come up with.  The =
specific semantics are well-defined, but only in the specific execution =
context (what JSON document this is being applied to).
/a:1/b:2 (to use James' strawman syntax that distinguishes JSON object =
keys from array indices) exposes more typing info, so it is more =
statically typed, and it will catch mismatches between the types that =
the JSON pointer assumed to be present and those that actually are.

For a static-typing fundamentalist, it is viscerally unacceptable to =
forego the opportunity of catching this kind of "type error".

For a non-fundamentalist, this is more of an issue of probabilities, and =
the interlocking of mechanisms. =20
Which percentage of usage errors will be caught by this?
Many, many mismatches between JSON pointers and JSON instances to will =
just not happen to trigger this particular type error.
So it can be argued that the ability to catch it doesn't really help =
much: If you care about mismatch errors, you already need to have =
something else in place to catch them -- relying only on the likelihood =
of a mismatch to trigger an array/object mismatch would be imprudent. So =
in reality, the ability to catch the type error buys you nothing.
(Or, actually, very little, as improved diagnostics is always worth =
something in a debugging situation.)

TL;DR: there is no "ambiguity" at all.  Please stop referring to an =
"ambiguity".  There is none.
Just a missed opportunity to catch an error, caused by not sending along =
(redundant) type information.

(You will gather that my 2 cents for this change are "not worth it", but =
I was more interested in explaining the mere existence of this =
discussion, first.  Applying the wrong intuitions to an engineering =
decision is one of the major causes of suboptimal design...)

Gr=FC=DFe, Carsten

*) Well, for a start, we are not here to catch errors in programming.  =
Programming languages are difficult because they are the human interface =
to the computer's programmability.  JSON pointers are a pure =
machine-to-machine mechanism, so most of the issues in programming just =
don't arise.  Porting your intuitions from programming to this is not =
going to work very well.


From lear@cisco.com  Tue Jan  8 01:53:25 2013
Return-Path: <lear@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4880721F88A1 for <ietf@ietfa.amsl.com>; Tue,  8 Jan 2013 01:53:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.599
X-Spam-Level: 
X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
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 eVn3rckMcJ2R for <ietf@ietfa.amsl.com>; Tue,  8 Jan 2013 01:53:24 -0800 (PST)
Received: from ams-iport-2.cisco.com (ams-iport-2.cisco.com [144.254.224.141]) by ietfa.amsl.com (Postfix) with ESMTP id D066B21F8444 for <ietf@ietf.org>; Tue,  8 Jan 2013 01:53:20 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1681; q=dns/txt; s=iport; t=1357638801; x=1358848401; h=message-id:date:from:mime-version:to:subject: content-transfer-encoding; bh=IHSe7M50wITpkTzCDvflKkfscR6vkkd3sx9tYAOKo6Y=; b=Q8RsveKC0Gzq2L7YtZKHtb4Qy9z3HVIxmn/kQLDCsmrxsdf26zrTWHdN rSld537CntvbNvSLxkLqeSnPlLPdJQ8FUZKrBlPF6t8iV9q865Pi5J6d7 WtmJNR3wtH5a3VLEF3SY4ntqm9CRVV/ZscI9JSScf5ggdcQunH8/Z7Tfl A=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AjQIAJnr61CQ/khN/2dsb2JhbABEg0eCcrccFnOCMxVCEzYCBRYLAgsDAgECAUsNCAEBiBOZCY5RgkCNOYEiizCDMIETA5YLkEmCdQ
X-IronPort-AV: E=Sophos;i="4.84,430,1355097600"; d="scan'208";a="79598949"
Received: from ams-core-4.cisco.com ([144.254.72.77]) by ams-iport-2.cisco.com with ESMTP; 08 Jan 2013 09:53:19 +0000
Received: from elear-mac.local (dhcp-10-55-92-103.cisco.com [10.55.92.103]) by ams-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id r089rJhx014364 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Tue, 8 Jan 2013 09:53:19 GMT
Message-ID: <50EBEC8E.3060204@cisco.com>
Date: Tue, 08 Jan 2013 10:53:18 +0100
From: Eliot Lear <lear@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: IETF Discussion <ietf@ietf.org>
Subject: Mark Crispin: 1956 - 2012
X-Enigmail-Version: 1.4.6
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 08 Jan 2013 09:53:25 -0000

It's probably escaped our notice because of the holidays, Mark Crispin
passed away on the 28th of December.  I didn't know Mark too well, but
he was a very important visionary. 

I first enjoyed his work as a user of the MM program on TOPS-20, upon
which he based the design of IMAP.  MM featured strong searching and
marking capabilities, as well as all the customization a person could
want.  It was through MM that people individualized there messages with
funny headers or a cute name.  And it was all so easy to use.  Mark was
constantly reminding us about that, and how UNIX's interface could
always stand improvement.  Mark was an unabashed TOPS-20 fan.

Before the world had fully converged on vt100 semantics, Mark worked to
standardize SUPDUP and the SUPDUP option.  He was also early to
recognize the limitations of a single host table.

Mark's sense of humor brought us RFC-748, the Telnet randomly-lose
option, which was the first April 1 RFC.  He also wrote another such RFC
for UTF-9 and UTF-10.

Most of us benefit from Mark's work today through our use of IMAP, which
followed Einstein's advice by having a protocol that was as simple as
possible to tackle the necessary problems, but no simpler.  We know this
because our first attempt was POP, which was too simple.  Mark knew he
had hit the balance right because he made benefited from his experience
with lots of running code and direct work with many end users.

I will miss his quirkiness, his cowboy boots, and his recommendations
for the best Japanese food in a town where the IETF would visit, and I
will miss the contributions he should have had more time to make.

Eliot

From daedulus@btconnect.com  Tue Jan  8 02:06:09 2013
Return-Path: <daedulus@btconnect.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 03A9421F8841; Tue,  8 Jan 2013 02:06:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[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 uLj5msViPh3K; Tue,  8 Jan 2013 02:06:08 -0800 (PST)
Received: from co9outboundpool.messaging.microsoft.com (co9ehsobe001.messaging.microsoft.com [207.46.163.24]) by ietfa.amsl.com (Postfix) with ESMTP id 449B521F86C0; Tue,  8 Jan 2013 02:06:07 -0800 (PST)
Received: from mail192-co9-R.bigfish.com (10.236.132.232) by CO9EHSOBE003.bigfish.com (10.236.130.66) with Microsoft SMTP Server id 14.1.225.23; Tue, 8 Jan 2013 10:06:07 +0000
Received: from mail192-co9 (localhost [127.0.0.1])	by mail192-co9-R.bigfish.com (Postfix) with ESMTP id 658B24C01FA; Tue,  8 Jan 2013 10:06:07 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.250.181; KIP:(null); UIP:(null); IPV:NLI; H:AMSPRD0711HT004.eurprd07.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: -21
X-BigFish: PS-21(zz98dI9371I542I1432I4015Izz1de0h1202h1e76h1d1ah1d2ahzz8275bh8275dh1033ILz2dh2a8h5a9h668h839h947hd24hf0ah1177h1179h1288h12a5h12a9h12bdh137ah139eh13b6h1441h1504h1537h162dh1631h1758h17f1h184fh304l1155h)
Received: from mail192-co9 (localhost.localdomain [127.0.0.1]) by mail192-co9 (MessageSwitch) id 1357639565369630_27729; Tue,  8 Jan 2013 10:06:05 +0000 (UTC)
Received: from CO9EHSMHS020.bigfish.com (unknown [10.236.132.253])	by mail192-co9.bigfish.com (Postfix) with ESMTP id 5790132004C; Tue,  8 Jan 2013 10:06:05 +0000 (UTC)
Received: from AMSPRD0711HT004.eurprd07.prod.outlook.com (157.56.250.181) by CO9EHSMHS020.bigfish.com (10.236.130.30) with Microsoft SMTP Server (TLS) id 14.1.225.23; Tue, 8 Jan 2013 10:05:59 +0000
Received: from DBXPRD0611HT001.eurprd06.prod.outlook.com (157.56.254.85) by pod51017.outlook.com (10.242.14.165) with Microsoft SMTP Server (TLS) id 14.16.245.2; Tue, 8 Jan 2013 10:05:43 +0000
Message-ID: <011d01cded87$67cbf4c0$4001a8c0@gateway.2wire.net>
From: t.p. <daedulus@btconnect.com>
To: <huubatwork@gmail.com>, Greg Mirsky <gregimirsky@gmail.com>
References: <CD08F2D5.6DC40%nabil.n.bitar@verizon.com><CD0C3AE6.6E673%nabil.n.bitar@verizon.com><CA+RyBmWWUQ+y7Mc1nG3+KndXCytfUkQqnNTg4ezpK2JcGyiCuQ@mail.gmail.com> <50EB3F9C.7010605@gmail.com>
Subject: Re: [PWE3] Gen-ART review of draft-ietf-pwe3-mpls-eth-oam-iwk-06
Date: Tue, 8 Jan 2013 10:03:19 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Originating-IP: [157.56.254.85]
X-OriginatorOrg: btconnect.com
Cc: gen-art@ietf.org, "Bitar, Nabil N" <nabil.n.bitar@verizon.com>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 08 Jan 2013 10:06:09 -0000

I notice too that MEP and MIP are incorrectly expanded:-(

Tom Petch


----- Original Message -----
From: "Huub van Helvoort" <huubatwork@gmail.com>
To: "Greg Mirsky" <gregimirsky@gmail.com>
Cc: <pwe3@ietf.org>; <gen-art@ietf.org>; "Bitar, Nabil N"
<nabil.n.bitar@verizon.com>; <dinmohan@hotmail.com>; <ietf@ietf.org>
Sent: Monday, January 07, 2013 9:35 PM
Subject: Re: [PWE3] Gen-ART review of
draft-ietf-pwe3-mpls-eth-oam-iwk-06


> Hello Nabil,
>
> Greg is almost right.
>
> RDI == Remote Defect Indication
>
> This is the abbreviation used in IEEE 802.1ag, Y.1731, G.707, G.8121
> and rfc6428.
>
> Regards, Huub.
> ====
>
> > can we avoid different interpretation of the same abbreviation
(RDI):
> >
> > RDI   Remote Defect Indication for Continuity Check Message
> >
> > RDI   Reverse Defect Indication
> >
> > AFAIK, the latter form is the interpretation used by both IEEE
802.1ag
> > and Y.1731. How useful is the first form?
> >
> > Regards,
> >
> > Greg
> >
> >
> >
> > On Fri, Jan 4, 2013 at 8:17 AM, Bitar, Nabil N
> > <nabil.n.bitar@verizon.com <mailto:nabil.n.bitar@verizon.com>>
wrote:
> >
> >     Hi Dave,
> >     Related to abbreviations comment below and to be clearer, I
renamed
> >     the original terminology section to "Abbreviations and
Terminology".
> >     I also created a subsection called "Abbreviations" ,and
> >     "Terminology" became the second subsection.  Here iis how the
edits look
> >
> >
> >       3. Abbreviations and Terminology____
> >
> >
> >         3.1. Abbreviations____
> >
> >     AISAlarm Indication Signal____
> >
> >     ACAttachment Circuit____
> >
> >     BFDBidirectional Forwarding Detection____
> >
> >     CCContinuity Check____
> >
> >     CCMContinuity Check Message____
> >
> >     CECustomer Equipment____
> >
> >     CVConnectivity Verification____
> >
> >     E-LMI Ethernet Local Management Interface____
> >
> >     EVCEthernet Virtual Circuit____
> >
> >     LDPLabel Distribution Protocol____
> >
> >     LoSLoss of Signal____
> >
> >     MAMaintenance Association____
> >
> >     MDMaintenance Domain____
> >
> >     MEMaintenance Entity____
> >
> >     MEGMaintenance Entity Group____
> >
> >     MEPMaintenance End Point____
> >
> >     MIPMaintenance End Point____
> >
> >     MPLSMultiprotocol Label Switching____
> >
> >     MS-PW Multi-Segment Pseudowire____
> >
> >     NSNative Service____
> >
> >     OAMOperations, Administration, and Maintenance____
> >
> >     PEProvider Edge____
> >
> >     PSNPacket Switched Network____
> >
> >     PWPseudowire____
> >
> >     RDIRemote Defect Indication for Continuity Check Message____
> >
> >         RDI   Reverse Defect Indication
> >
> >     S-PESwitching Provider Edge____
> >
> >     TLVType Length Value____
> >
> >     T-PETerminating Provider Edge____
> >
> >     __ __
> >
> >
> >         3.2. Terminology____
> >
> >     This document uses the following terms with corresponding
> >     definitions: ____
> >
> >     - MD Level:Maintenance Domain (MD) Level which identifies a
value in
> >     the range of 0-7 associated with Ethernet OAM frame. MD Level
> >     identifies the span of the Ethernet OAM frame.____
> >
> >     - MEP:Maintenance End Point is responsible for origination and
> >     termination of OAM frames for a given MEG.____
> >
> >     - MIP: Maintenance Intermediate Point is located between peer
MEPs
> >     and can process OAM frames but does not initiate or terminate
them.____
> >
> >     Further, this document also uses the terminology and conventions
> >     used in [RFC6310].____
> >
> >
> >
> >     Thanks,
> >
> >     Nabil
>



From markus.lanthaler@gmx.net  Tue Jan  8 02:13:34 2013
Return-Path: <markus.lanthaler@gmx.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 82CF621F8903 for <ietf@ietfa.amsl.com>; Tue,  8 Jan 2013 02:13:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.758
X-Spam-Level: 
X-Spam-Status: No, score=0.758 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MSGID_MULTIPLE_AT=1.449, RCVD_ILLEGAL_IP=1.908]
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 OXWGnU-Qx-HX for <ietf@ietfa.amsl.com>; Tue,  8 Jan 2013 02:13:33 -0800 (PST)
Received: from mout.gmx.net (mout.gmx.net [212.227.17.20]) by ietfa.amsl.com (Postfix) with ESMTP id 51CD621F88F1 for <ietf@ietf.org>; Tue,  8 Jan 2013 02:13:33 -0800 (PST)
Received: from mailout-de.gmx.net ([10.1.76.17]) by mrigmx.server.lan (mrigmx001) with ESMTP (Nemesis) id 0MbeI7-1Tbg7d1q69-00J15Y for <ietf@ietf.org>; Tue, 08 Jan 2013 11:13:32 +0100
Received: (qmail invoked by alias); 08 Jan 2013 10:13:31 -0000
Received: from net-2-34-222-137.cust.dsl.vodafone.it (EHLO Vostro3500) [2.34.222.137] by mail.gmx.net (mp017) with SMTP; 08 Jan 2013 11:13:31 +0100
X-Authenticated: #419883
X-Provags-ID: V01U2FsdGVkX1+n/Mwv5tWndEk8xXeor5RzUnSwhyncWJv48YoyjQ Ay6B8Ke9T5UdPQ
From: "Markus Lanthaler" <markus.lanthaler@gmx.net>
To: "'Conal Tuohy'" <conal.tuohy@versi.edu.au>, "'Matthew Morley'" <matt@mpcm.com>
References: <20121211150057.28223.93310.idtracker@ietfa.amsl.com>	<50cb04b9.86df440a.72fe.1e20SMTPIN_ADDED_BROKEN@mx.google.com>	<CABP7RbeNsZ_rBWRjou=VG+hBhUKaOz+y1a0sSChwWiHte9znnQ@mail.gmail.com>	<50cb5f3c.694c420a.38fb.39afSMTPIN_ADDED_BROKEN@mx.google.com>	<CAChr6SxZRc3B_HCbw76kLe2dsRSr43r-gLpfMVnCUfJTrZdTLA@mail.gmail.com>	<CABP7RbfA33huBFadMeXTTEt=MkjW8-d4DFH7+GLXGurnm9sSRw@mail.gmail.com>	<CAOXDeqpPE4eNy_qJpDPdPHbCQakG9-hDcNZ3Sj9r4kWedByVzQ@mail.gmail.com>	<CAChr6SwtS_=iS-k4mJm1vHjEvvGVzay5jDYeGheqsPZqO-89CQ@mail.gmail.com>	<EABB8F51-C3B4-49F5-8672-5C2ABAC7043A@mnot.net>	<CAChr6Sx7JdKM91EwJaSZ0Ra_F4FSqkuc3vzTY1LM=F_8sWho+Q@mail.gmail.com>	<1357515310.6827.23.camel@polyglot>	<CAChr6SyAq=7aQdZn54ihYK+0hDhL--2Oaq0RvehoNFbwKNNShA@mail.gmail.com>	<CAChr6SxorKO20rGYi-e4YNF=HNGrwz8wPGKCFZQYWQwqsetjjg@mail.gmail.com>	<CAOXDeqqE2mCLapwvjwQkme5VTpRCfmF0mFQcx02WW0-zi4i5=g@mail.gmail.com> <50EB4E8B.30700@versi.edu.au>
In-Reply-To: <50EB4E8B.30700@versi.edu.au>
Subject: RE: [apps-discuss] Last Call: <draft-ietf-appsawg-json-pointer-07.txt> (JSON Pointer) to Proposed Standard
Date: Tue, 8 Jan 2013 11:13:27 +0100
Message-ID: <012401cded88$cf33b520$6d9b1f60$@lanthaler@gmx.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Ac3tJ+OAEKBBA7A8SiKxpzd4U1tVmQAX70lw
Content-Language: de
X-Y-GMX-Trusted: 0
Cc: 'Mark Nottingham' <mnot@mnot.net>, 'IESG' <iesg@ietf.org>, 'IETF Apps Discuss' <apps-discuss@ietf.org>, 'IETF Discussion' <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 08 Jan 2013 10:13:34 -0000

On Monday, January 07, 2013 11:39 PM, Conal Tuohy wrote:

> On 07/01/13 13:23, Matthew Morley wrote:
>
> > For me the deficiency is not in the pointer, but patch
> > format being generated.
> >
> > One approach is to push that *one* test, structure=A0conformity,
> >  into the pointer syntax.=A0Another is via the type operation.
> >
> > If a vague patch is generated, vague results are to be expected.
>
> It seems to me, on the contrary, that the deficiency is in the
> pointer syntax, and I think it would be a mistake to try to work
> around that deficiency in JSON Patch. Because aren't there other
> things which one might do with JSON Pointer than use it with JSON
> Patch? There's been mention of having it registered as a URI
> fragment identifier syntax for JSON for example. JSON Pointers
> could then end up all over the place, outside of patches. IMHO
> JSON Pointer needs to be taken seriously as a technology in its
> own right.

I would like to second that. Since JSON Pointer and JSON Patch will be =
two
independent standards I expect (hope) that JSON Pointer will be used for
many other things than patching and that's exactly the reason why I =
raised
this in the first place.

I still believe that the current ambiguity might hinder many valuable =
use
cases in the future. I do understand that we are already quite late in =
the
process but since the fix is rather trivial I don't see a compelling =
reason
to not resolve this now.


Cheers,
Markus



--
Markus Lanthaler
@markuslanthaler


From huubatwork@gmail.com  Tue Jan  8 02:17:44 2013
Return-Path: <huubatwork@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2758721F845F; Tue,  8 Jan 2013 02:17:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 UySH6cxLq9nd; Tue,  8 Jan 2013 02:17:43 -0800 (PST)
Received: from mail-we0-f172.google.com (mail-we0-f172.google.com [74.125.82.172]) by ietfa.amsl.com (Postfix) with ESMTP id 0455B21F845E; Tue,  8 Jan 2013 02:17:42 -0800 (PST)
Received: by mail-we0-f172.google.com with SMTP id r3so189176wey.17 for <multiple recipients>; Tue, 08 Jan 2013 02:17:42 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:disposition-notification-to:date:from :reply-to:user-agent:mime-version:to:cc:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=zIBzdHGYVKAfaBNIymrwdvkwRojAwOl8dDiHkv1KRew=; b=vV4KW9wxueFOmRhYKpi4Poc390A9SLZdwAIqijH6pGzD4ZmMxuNk32O1J/qIH82p3Z ImqD/q8vR596+zxCmgpCoi9i6TsCMdb8b/k1s3a03urPda1hMbGmJi1Ub1K4g/Mn9A/q X0rp3Nd/Gh6hAWVX0EUStVbHUtDvkgRlTij4usFWjC6k+es0QxbEcDm0EV+cY1Or+Zqv Dq2MmrZwYidYTjlERVEuIHLLrMb1CbztMxmEFBurFP+WmaD2shtapgYVFBW35+XBbB62 OlrUQGo+8fkc1vG428S+S0imB9wqP9BPwLe+fMtXFFUhywH/ELkEtHxng42lOpe5a7Ff wdDQ==
X-Received: by 10.180.107.129 with SMTP id hc1mr13943778wib.34.1357640262238;  Tue, 08 Jan 2013 02:17:42 -0800 (PST)
Received: from McAsterix.local (dhcp-077-250-051-060.chello.nl. [77.250.51.60]) by mx.google.com with ESMTPS id df2sm15917119wib.0.2013.01.08.02.17.40 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 08 Jan 2013 02:17:41 -0800 (PST)
Message-ID: <50EBF245.1020602@gmail.com>
Date: Tue, 08 Jan 2013 11:17:41 +0100
From: Huub van Helvoort <huubatwork@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: Greg Mirsky <gregimirsky@gmail.com>
Subject: Re: [PWE3] Gen-ART review of draft-ietf-pwe3-mpls-eth-oam-iwk-06
References: <CD08F2D5.6DC40%nabil.n.bitar@verizon.com> <CD0C3AE6.6E673%nabil.n.bitar@verizon.com> <CA+RyBmWWUQ+y7Mc1nG3+KndXCytfUkQqnNTg4ezpK2JcGyiCuQ@mail.gmail.com>
In-Reply-To: <CA+RyBmWWUQ+y7Mc1nG3+KndXCytfUkQqnNTg4ezpK2JcGyiCuQ@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "Bitar, Nabil N" <nabil.n.bitar@verizon.com>, "ietf@ietf.org" <ietf@ietf.org>, "gen-art@ietf.org" <gen-art@ietf.org>, "dinmohan@hotmail.com" <dinmohan@hotmail.com>, "sajassi@cisco.com" <sajassi@cisco.com>, "pwe3@ietf.org" <pwe3@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: huubatwork@gmail.com
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 08 Jan 2013 10:17:44 -0000

Dear Greg,

You responded:

 > IEEE 802.1ag interprets MEP and MIP as:
 >
 >   * Maintenance association End Point
 >   * Maintenance domain Intermediate Point

Indeed, and MA == MEG, MD == ME.

 > Y.1731 interprets them as:
 >
 >   * Maintenance entity group (MEG) End Point
 >   * MEG Intermediate Point

Correct.

 > The reference to MD Level implies reference to IEEE 802.1ag, at least as
 > use of terminology, since Y.1731 doesn't have Maintenance Domain
 > construct and refers to the same value as MEG Level. I'd suggest to
 > follow one model, IEEE 802.1ag or Y.1731, terminology throughout the
 > document so that there's no need for re-mapping. I think that it is
 > easier to follow Y.1731.

I agree that this is the best.
These are the abbreviations used for MPLS-TP too.

Best regards, Huub.


 > On Fri, Jan 4, 2013 at 8:30 AM, Huub van Helvoort <huubatwork@gmail.com
 > <mailto:huubatwork@gmail.com>> wrote:
 >
 >     All,
 >
 >     Some nits that need to be fixed:
 >
 >
 >
 >         ME  Maintenance Entity
 >
 >         MEG  Maintenance Entity Group
 >
 >         MEP Maintenance End Point
 >
 >
 >     MEP  "ME End Point" or "Maintenance Entity End Point"
 >
 >
 >         MIP  Maintenance End Point
 >
 >
 >     MIP  "ME Intermediate Point" or "Maintenance Entity Intermediate 
Point"
 >
 >
 >
 >              3.2. Terminology
 >
 >
 >         - MEP:  Maintenance End Point is responsible for origination and
 >         termination of OAM frames for a given MEG.
 >
 >
 >     - MEP:  Maintenance Entity End Point is responsible for origination
 >
 >
 >         - MIP: Maintenance Intermediate Point is located between peer
 >         MEPs and
 >         can process OAM frames but does not initiate or terminate them.
 >
 >
 >     - MIP: Maintenance Entity Intermediate Point is located between
 >
 >
 >     Regards, Huub.


From loa@pi.nu  Tue Jan  8 03:01:55 2013
Return-Path: <loa@pi.nu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7278121F8E3C; Tue,  8 Jan 2013 03:01:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.048
X-Spam-Level: 
X-Spam-Status: No, score=-101.048 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_RELAY_NODNS=1.451, RDNS_NONE=0.1, USER_IN_WHITELIST=-100]
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 vVp-ecWg1HSk; Tue,  8 Jan 2013 03:01:54 -0800 (PST)
Received: from mail.pi.nu (unknown [195.206.248.139]) by ietfa.amsl.com (Postfix) with ESMTP id 6918121F8E1C; Tue,  8 Jan 2013 03:01:54 -0800 (PST)
Received: from [192.168.1.103] (81-236-221-144-no93.tbcn.telia.com [81.236.221.144]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.pi.nu (Postfix) with ESMTPSA id 768027FE07; Tue,  8 Jan 2013 12:01:51 +0100 (CET)
Message-ID: <50EBFCA0.3060307@pi.nu>
Date: Tue, 08 Jan 2013 12:01:52 +0100
From: Loa Andersson <loa@pi.nu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:16.0) Gecko/20121010 Thunderbird/16.0.1
MIME-Version: 1.0
To: Greg Mirsky <gregimirsky@gmail.com>
Subject: Re: [PWE3] Gen-ART review of draft-ietf-pwe3-mpls-eth-oam-iwk-06
References: <CD08F2D5.6DC40%nabil.n.bitar@verizon.com> <CD0C3AE6.6E673%nabil.n.bitar@verizon.com> <CA+RyBmWWUQ+y7Mc1nG3+KndXCytfUkQqnNTg4ezpK2JcGyiCuQ@mail.gmail.com>
In-Reply-To: <CA+RyBmWWUQ+y7Mc1nG3+KndXCytfUkQqnNTg4ezpK2JcGyiCuQ@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "Bitar, Nabil N" <nabil.n.bitar@verizon.com>, "ietf@ietf.org" <ietf@ietf.org>, "gen-art@ietf.org" <gen-art@ietf.org>, "dinmohan@hotmail.com" <dinmohan@hotmail.com>, "sajassi@cisco.com" <sajassi@cisco.com>, "pwe3@ietf.org" <pwe3@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 08 Jan 2013 11:01:55 -0000

Greg,

RFC 6428 expands RDI as:

    RDI: Remote Defect Indication

/Loa

On 2013-01-07 21:51, Greg Mirsky wrote:
> Dear Nabil,
> can we avoid different interpretation of the same abbreviation (RDI):
>
>     RDI   Remote Defect Indication for Continuity Check Message
>
>     RDI   Reverse Defect Indication
>
> AFAIK, the latter form is the interpretation used by both IEEE 802.1ag
> and Y.1731. How useful is the first form?
>
> Regards,
>
> Greg
>
>
>
> On Fri, Jan 4, 2013 at 8:17 AM, Bitar, Nabil N
> <nabil.n.bitar@verizon.com <mailto:nabil.n.bitar@verizon.com>> wrote:
>
>     Hi Dave,
>     Related to abbreviations comment below and to be clearer, I renamed
>     the original terminology section to "Abbreviations and Terminology".
>     I also created a subsection called "Abbreviations" ,and
>     "Terminology" became the second subsection.  Here iis how the edits look
>
>
>       3. Abbreviations and Terminology____
>
>
>         3.1. Abbreviations____
>
>     AISAlarm Indication Signal____
>
>     ACAttachment Circuit____
>
>     BFDBidirectional Forwarding Detection____
>
>     CCContinuity Check____
>
>     CCMContinuity Check Message____
>
>     CECustomer Equipment____
>
>     CVConnectivity Verification____
>
>     E-LMI Ethernet Local Management Interface____
>
>     EVCEthernet Virtual Circuit____
>
>     LDPLabel Distribution Protocol____
>
>     LoSLoss of Signal____
>
>     MAMaintenance Association____
>
>     MDMaintenance Domain____
>
>     MEMaintenance Entity____
>
>     MEGMaintenance Entity Group____
>
>     MEPMaintenance End Point____
>
>     MIPMaintenance End Point____
>
>     MPLSMultiprotocol Label Switching____
>
>     MS-PW Multi-Segment Pseudowire____
>
>     NSNative Service____
>
>     OAMOperations, Administration, and Maintenance____
>
>     PEProvider Edge____
>
>     PSNPacket Switched Network____
>
>     PWPseudowire____
>
>     RDIRemote Defect Indication for Continuity Check Message____
>
>         RDI   Reverse Defect Indication
>
>     S-PESwitching Provider Edge____
>
>     TLVType Length Value____
>
>     T-PETerminating Provider Edge____
>
>     __ __
>
>
>         3.2. Terminology____
>
>     This document uses the following terms with corresponding
>     definitions: ____
>
>     - MD Level:Maintenance Domain (MD) Level which identifies a value in
>     the range of 0-7 associated with Ethernet OAM frame. MD Level
>     identifies the span of the Ethernet OAM frame.____
>
>     - MEP:Maintenance End Point is responsible for origination and
>     termination of OAM frames for a given MEG.____
>
>     - MIP: Maintenance Intermediate Point is located between peer MEPs
>     and can process OAM frames but does not initiate or terminate them.____
>
>     Further, this document also uses the terminology and conventions
>     used in [RFC6310].____
>
>
>
>     Thanks,
>
>     Nabil
>
>
>     From: <Bitar>, Nabil N <nabil.n.bitar@one.verizon.com
>     <mailto:nabil.n.bitar@one.verizon.com>>
>     Date: Wednesday, January 2, 2013 11:28 AM
>     To: "Black, David" <david.black@emc.com
>     <mailto:david.black@emc.com>>, "dinmohan@hotmail.com
>     <mailto:dinmohan@hotmail.com>" <dinmohan@hotmail.com
>     <mailto:dinmohan@hotmail.com>>, "Bitar, Nabil N"
>     <nabil.n.bitar@one.verizon.com
>     <mailto:nabil.n.bitar@one.verizon.com>>, Sagessi <sajassi@cisco.com
>     <mailto:sajassi@cisco.com>>, "gen-art@ietf.org
>     <mailto:gen-art@ietf.org>" <gen-art@ietf.org <mailto:gen-art@ietf.org>>
>     Cc: "pwe3@ietf.org <mailto:pwe3@ietf.org>" <pwe3@ietf.org
>     <mailto:pwe3@ietf.org>>, "ietf@ietf.org <mailto:ietf@ietf.org>"
>     <ietf@ietf.org <mailto:ietf@ietf.org>>
>     Subject: Re: Gen-ART review of draft-ietf-pwe3-mpls-eth-oam-iwk-06
>
>     Hi Dave,
>     Sorry for a late reply addressing your comments. Please, see inline.
>
>     Thanks,
>     Nabil
>
>     From: "Black, David" <david.black@emc.com <mailto:david.black@emc.com>>
>     Date: Monday, August 20, 2012 8:57 PM
>     To: "dinmohan@hotmail.com <mailto:dinmohan@hotmail.com>"
>     <dinmohan@hotmail.com <mailto:dinmohan@hotmail.com>>, "Bitar, Nabil
>     N" <nabil.n.bitar@one.verizon.com
>     <mailto:nabil.n.bitar@one.verizon.com>>, Sagessi <sajassi@cisco.com
>     <mailto:sajassi@cisco.com>>, "gen-art@ietf.org
>     <mailto:gen-art@ietf.org>" <gen-art@ietf.org <mailto:gen-art@ietf.org>>
>     Cc: "Black, David" <david.black@emc.com
>     <mailto:david.black@emc.com>>, "pwe3@ietf.org
>     <mailto:pwe3@ietf.org>" <pwe3@ietf.org <mailto:pwe3@ietf.org>>,
>     "ietf@ietf.org <mailto:ietf@ietf.org>" <ietf@ietf.org
>     <mailto:ietf@ietf.org>>
>     Subject: Gen-ART review of draft-ietf-pwe3-mpls-eth-oam-iwk-06
>
>     I am the assigned Gen-ART reviewer for this draft. For background on
>     Gen-ART, please
>     see the FAQ at
>     <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>
>     Please resolve these comments along with any other Last Call
>     comments you may receive.
>
>     Document: draft-ietf-pwe3-mpls-eth-oam-iwk-06
>     Reviewer: David L. Black
>     Review Date: August 20, 2012
>     IETF LC End Date: August 20, 2012
>
>     Summary:
>     This draft is basically ready for publication, but has nits that
>     should be fixed before publication.
>
>     <NB> Thanks.
>
>     This draft covers defect behavior for Ethernet pseudowires,
>
>     including defect state mapping and PE defect reporting behavior.
>
>     The draft is generally in good shape.  I found a few minor nits.
>
>     1) The draft uses a lot of acronyms - while each acronym appears to
>
>     be expanded on first use, an additional section near the start of the
>
>     draft listing all of them would be helpful.
>
>
>     <NB> Done.
>
>     2) There's a typo in the first paragraph of section 2:
>
>           covers the following Ethernet OAM (Opertaions, Administration and
>
>     Opertaions -> Operations.
>
>
>     <NB> Thanks. Done.
>
>     3) The following normative reference is incomplete - please add
>     additional
>
>     information that will enable a reader to locate the referenced document:
>
>           [MEF16] "Ethernet Local Management Interface", MEF16, January
>     2006.
>
>
>     [MEF16] "Ethernet Local Management Interface", Metro Ethernet Forum
>     Technical Specification MEF16, January 2006.
>
>     <NB> changed it to :
>
>     4) idnits2.12.13 did not like the pagination:
>
>        == The page length should not exceed 58 lines per page, but there
>     was 22
>           longer pages, the longest (page 1) being 61 lines
>
>     <NB> That will be fixed.
>     Thanks,
>     --David
>     ----------------------------------------------------
>     David L. Black, Distinguished Engineer
>     EMC Corporation, 176 South St., Hopkinton, MA  01748
>     +1 (508) 293-7953 <tel:%2B1%20%28508%29%20293-7953>             FAX:
>     +1 (508) 293-7786 <tel:%2B1%20%28508%29%20293-7786>
>     david.black@emc.com <mailto:david.black@emc.com>        Mobile: +1
>     (978) 394-7754 <tel:%2B1%20%28978%29%20394-7754>
>     ----------------------------------------------------
>
>     _______________________________________________
>     pwe3 mailing list
>     pwe3@ietf.org <mailto:pwe3@ietf.org>
>     https://www.ietf.org/mailman/listinfo/pwe3
>
>
>
>
> _______________________________________________
> pwe3 mailing list
> pwe3@ietf.org
> https://www.ietf.org/mailman/listinfo/pwe3
>

-- 


Loa Andersson                         email: loa.andersson@ericsson.com
Sr Strategy and Standards Manager            loa@pi.nu
Ericsson Inc                          phone: +46 10 717 52 13
                                              +46 767 72 92 13

From glenzorn@gmail.com  Tue Jan  8 03:07:16 2013
Return-Path: <glenzorn@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0EEF421F8440 for <ietf@ietfa.amsl.com>; Tue,  8 Jan 2013 03:07:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 STF5abu71GFs for <ietf@ietfa.amsl.com>; Tue,  8 Jan 2013 03:07:15 -0800 (PST)
Received: from mail-pa0-f45.google.com (mail-pa0-f45.google.com [209.85.220.45]) by ietfa.amsl.com (Postfix) with ESMTP id 83A2521F8462 for <ietf@ietf.org>; Tue,  8 Jan 2013 03:06:50 -0800 (PST)
Received: by mail-pa0-f45.google.com with SMTP id bg2so269339pad.32 for <ietf@ietf.org>; Tue, 08 Jan 2013 03:06:50 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=k9vCCatoO3v+ko1t7ujC34gJBfa3Q/F03gFbPz2H9Pw=; b=JAq82XweP0Y3jUIDkASOwZXq85Dy57bhBnwHe/OKUyhJ3WpGgsD1+T/2zcoFortoaf cQN6oGsQiaICLPEzdckK0IsXz10oFUjo9qoDqeSXQloWV12wI6ESyYn1aveQBgTiRaow QJAF/GDsimKcraZjJifGECI4vTYtfy1UwWxCRCWJW6IPxHydQWe01Hpbn+NCjpnxcaU4 Yw94yK+5IR+BUQ7XE+XT/koJY6LMVVZTGsM1BIoWJy19E4SA3MP2Nt7u+PGubsttE2cK XT6hJdKqm6yG74izTHjSxn88DDutrdI3LGSCR88QoAIeulzwAlKY/CA9hniyndVnmxsH mTtg==
X-Received: by 10.68.223.131 with SMTP id qu3mr196896352pbc.89.1357643210208;  Tue, 08 Jan 2013 03:06:50 -0800 (PST)
Received: from [192.168.0.102] (ppp-124-120-66-230.revip2.asianet.co.th. [124.120.66.230]) by mx.google.com with ESMTPS id ti9sm2749700pbc.16.2013.01.08.03.06.47 (version=SSLv3 cipher=OTHER); Tue, 08 Jan 2013 03:06:49 -0800 (PST)
Message-ID: <50EBFDC5.1030000@gmail.com>
Date: Tue, 08 Jan 2013 18:06:45 +0700
From: Glen Zorn <glenzorn@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: Ole Jacobsen <ole@cisco.com>
Subject: Re: travel guide for the next IETF...
References: <50DF09C7.1060009@dcrocker.net> <20200.1356985377@sandelman.ca> <4613980CFC78314ABFD7F85CC30277210EE27C34@IL-EX10.ad.checkpoint.com> <2C17B081-ECE7-4CD0-99AB-72324EA0BE27@mnot.net> <alpine.OSX.2.01.1301041514310.81626@173-11-110-132-sfba.hfc.comcastbusiness.net> <11785.1357510371@sandelman.ca> <alpine.OSX.2.01.1301061429500.19083@173-11-110-132-sfba.hfc.comcastbusiness.net>
In-Reply-To: <alpine.OSX.2.01.1301061429500.19083@173-11-110-132-sfba.hfc.comcastbusiness.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Mark Nottingham <mnot@mnot.net>, Michael Richardson <mcr@sandelman.ca>, IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 08 Jan 2013 11:07:16 -0000

On 01/07/2013 05:31 AM, Ole Jacobsen wrote:
>
 > On Sun, 6 Jan 2013, Michael Richardson wrote:
 >>
 >> yeah, I know, but I gotta say to the IEEE.... SERIOUSLY?
 >
 > Apparently the IEEE folks love it, have been there before.

It was very nice (I am one of those IEEE folks) if you had a nice 
expense account; however, it is expensive and far from anything else, as 
I recall.

...


From sm@resistor.net  Tue Jan  8 03:31:20 2013
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4B91721F8C5B for <ietf@ietfa.amsl.com>; Tue,  8 Jan 2013 03:31:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.569
X-Spam-Level: 
X-Spam-Status: No, score=-102.569 tagged_above=-999 required=5 tests=[AWL=0.030, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 PL1CFgJov7Nq for <ietf@ietfa.amsl.com>; Tue,  8 Jan 2013 03:31:19 -0800 (PST)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id A9EBF21F8C59 for <ietf@ietf.org>; Tue,  8 Jan 2013 03:31:19 -0800 (PST)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r08BVCBb027145; Tue, 8 Jan 2013 03:31:15 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1357644677; bh=PlhP9zVxoLXquZ6NK++7bDgd2/KC11glDQL4uCigOUY=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=k5YjX7c42ZXXsDdvCo7NQ336w3JrqVG+e3y3gqOZY/l2I89mAOC+WSOI4ghGCdvUx IlALmJTC6BV6uAoX3ucTDNQdwzigAF1801phRLD7WXEBmwjz3YW+vrnnRTtiC84wlI O+TAM62uDCsSUzzUj3gcN5NsANDuZw+Tl6BNzJUM=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1357644677; i=@resistor.net; bh=PlhP9zVxoLXquZ6NK++7bDgd2/KC11glDQL4uCigOUY=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=LTbwIjK6Gr2yYELGjU/rmqMmYjVYAkBe8P1ex+N8REj/HfIndNvATJHdVNCGyNfcu TugFUPV3O4G6dXfVY6/7aBRiJekcqFAukgWvF/3Qg0q8mdTbP22ul2DnbaaB73DReM P5hNxR22pt5csFkc6Hw+XNVcoCB+CPmnUjVbF2qI=
Message-Id: <6.2.5.6.2.20130108025003.0be79d18@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Tue, 08 Jan 2013 03:21:30 -0800
To: IETF Discussion <ietf@ietf.org>
From: SM <sm@resistor.net>
Subject: Re: Mark Crispin: 1956 - 2012
In-Reply-To: <50EBEC8E.3060204@cisco.com>
References: <50EBEC8E.3060204@cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 08 Jan 2013 11:31:20 -0000

At 01:53 08-01-2013, Eliot Lear wrote:
>It's probably escaped our notice because of the holidays, Mark Crispin
>passed away on the 28th of December.  I didn't know Mark too well, but
>he was a very important visionary.

Mark Crispin wrote 25 RFCs between April 1977 and June 2008.  He is 
the author of the Internet Message Access Protocol (IMAP4rev1) and he 
wrote c-client library which is the reference for IMAP.  I learned a 
lot through his comments.  Quoting one of his messages:

   "Instead of asking for new features from UW, think about implementing those
    features yourself.  Study the code.  Try to understand it.  Ask questions
    about the internals to the remaining UW people while you still 
have a chance
    of getting an answer."

Regards,
-sm 


From abdussalambaryun@gmail.com  Tue Jan  8 03:53:56 2013
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 38C7B21F8CE8 for <ietf@ietfa.amsl.com>; Tue,  8 Jan 2013 03:53:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.577
X-Spam-Level: 
X-Spam-Status: No, score=-3.577 tagged_above=-999 required=5 tests=[AWL=0.022,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 WyZK4DXa341Q for <ietf@ietfa.amsl.com>; Tue,  8 Jan 2013 03:53:55 -0800 (PST)
Received: from mail-vb0-f49.google.com (mail-vb0-f49.google.com [209.85.212.49]) by ietfa.amsl.com (Postfix) with ESMTP id 7E13621F8686 for <ietf@ietf.org>; Tue,  8 Jan 2013 03:53:55 -0800 (PST)
Received: by mail-vb0-f49.google.com with SMTP id r6so267289vbi.36 for <ietf@ietf.org>; Tue, 08 Jan 2013 03:53:54 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=F6kLWuXxGFrfFkGnXIzr3C2+6K+cdgEtAH24wwpgc+I=; b=ZWWAtK8Mo6LndvSF2VHlmaCf/v9Brch7zLtyd/Ol1FZ2efbbdvs0SmZ5TvJ8NzBXL1 /D1r4ngpZlogg5GXe6J6zRqT+B6gwTMoo1+QrRv7A71Ipvb8/0MHSssemtyXg8TcLhu6 Cxq936Qjzxw3E5zH0vrc+NxUVEI6AgI66W8sUNXvmTtrp8AATp3WD4b9W6Y/OQrb9g7H bHk7oLU8DSbZ/kFkGGF6fACCie+DSRpfQXCMxgI7Do2+1iFXMJSagYKtQnmaB9mcGFuY DUcwdPjwLokzlGpX6moLU/mzDVohMr/frryIDg7DFdrBYgCN/o7k6xXv7gTvPhQ74ctm TGzA==
MIME-Version: 1.0
Received: by 10.58.198.135 with SMTP id jc7mr87042417vec.51.1357646034873; Tue, 08 Jan 2013 03:53:54 -0800 (PST)
Received: by 10.220.145.5 with HTTP; Tue, 8 Jan 2013 03:53:54 -0800 (PST)
In-Reply-To: <a062408a2cd10003cf574@10.0.1.3>
References: <CADnDZ8_GgVeapUKefFMqOvwOo00X8_rFDWMR0vb-Zvu_p=yT3A@mail.gmail.com> <a062408a2cd10003cf574@10.0.1.3>
Date: Tue, 8 Jan 2013 12:53:54 +0100
Message-ID: <CADnDZ88BVr6wj_RTGh8bMEkUt-sobWuDH-v0wyHVabSETVHrkA@mail.gmail.com>
Subject: Re: A proposal for a scientific approach to this question [was Re: I'm struggling with 2219 language again]
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: John Day <jeanjour@comcast.net>
Content-Type: text/plain; charset=ISO-8859-1
Cc: ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 08 Jan 2013 11:53:56 -0000

Hi John,

thank you for your reply (i.e. learned alot), so I understand that a
RFC standard track may have more than one implementation but same
behavior enough not to make an error. Regarding following 2119, I
understand most text follow it only when there are normative actions.
Regarding implementer claiming following a RFC, but the question of
error in process is does the RFC lack communication requirement with
the community?

AB

On 1/7/13, John Day <jeanjour@comcast.net> wrote:
> Strictly speaking, the language of 2119 should be followed wherever
> necessary in order for the text to be normative and make it mandatory
> that a conforming implementation meets some requirement.  Otherwise,
> someone could build an implementation and claim it was correct and
> possibly cause legal problems. However, in the IETF there is also a
> requirement that there be two independent but communicating
> implementations for an RFC to standards-track. Correct?
>
> For all practical purposes, this requirement makes being able to
> communicate with one of the existing implementations the formal and
> normative definition of the RFC.  Any debate over the content of the
> RFC text is resolved by what the implementations do.  It would seem
> to be at the discretion of the authors of the implementations to
> determine whether or not any problems that are raised are bugs or not.
>
> Then it would seem that regardless of whether 2119 is followed, the
> RFCs are merely informative guides.
>
> So while the comments are valid that RFC 2119 should be followed,
> they are also irrelevant.
>
> Given that any natural language description is going to be ambiguous,
> this is probably for the best.
>
> Take care,
> John Day
>
> At 9:41 AM +0100 1/6/13, Abdussalam Baryun wrote:
>>Hi Marc Petit-Huguenin ,
>>
>>>I read the responses so far, and what can be said today is that there is
>>> 2
>>philosophies, with supporters in both camps.  The goal of the IETF is to
>> make
>>the Internet work better, and I do believe that RFC 2119 is one of the
>>fundamental tool to reach this goal, but having two ways to use it does
>> not
>>help this goal.
>>
>>I like the approach, and agree with you that we need a solution in
>>IETF which still is not solved or ignored by participants fo some
>>reasons. However, I agree of a survey or an experiment what ever we
>>call it, that makes IETF reflects to the RFC2119 performance on the
>>end-user of such product implementation of RFC protocols. I think many
>>old participants already have good experience to inform us of some
>>reality of IETF standards' end-user production.
>>
>>AB
>
>

From rwfranks@gmail.com  Tue Jan  8 05:41:54 2013
Return-Path: <rwfranks@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EF2B821F851E for <ietf@ietfa.amsl.com>; Tue,  8 Jan 2013 05:41:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.977
X-Spam-Level: 
X-Spam-Status: No, score=-102.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
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 AVt1MPMFd6qw for <ietf@ietfa.amsl.com>; Tue,  8 Jan 2013 05:41:53 -0800 (PST)
Received: from mail-wg0-f45.google.com (mail-wg0-f45.google.com [74.125.82.45]) by ietfa.amsl.com (Postfix) with ESMTP id 4552F21F8505 for <ietf@ietf.org>; Tue,  8 Jan 2013 05:41:53 -0800 (PST)
Received: by mail-wg0-f45.google.com with SMTP id dq12so341170wgb.12 for <ietf@ietf.org>; Tue, 08 Jan 2013 05:41:52 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:cc:content-type; bh=EwN28uJeDQdjxVyhvnkzgTccq/y1Pb4HImytR7/3PPk=; b=uQJwyMj9DXoVVLA90xQ9aJfaLc0FU0UYF/fEGNi2QdamvBbUqZQo/6SDra31DSfqQ6 q5yWhEwR+XfxD2jhjB/esIhVrhS5Vb6TzVO1omw10Fi82ZkZXXERJ2iHpPcyeyyrDL/8 9BPWcWNHwVJOXN7VbiSlLnNKx88PTEA/7p2A8mkso8rfOJ4N0HVpyNpcUQ/1GnvVaw8O hbbELFJpJHa5oZAVBMDVkpMvR1fV93f1FResuuDtq7LEZ1E3aeabX+qG9V52Vp5rcsdA maHW+vbX4RZR3sj5zZjIDiLGfk+pQM62B0/N0E2HOV6t/OCiiN2WrF9uMvF36f08AO6g 1UIw==
X-Received: by 10.180.109.10 with SMTP id ho10mr15229548wib.9.1357652512453; Tue, 08 Jan 2013 05:41:52 -0800 (PST)
MIME-Version: 1.0
Sender: rwfranks@gmail.com
Received: by 10.194.18.65 with HTTP; Tue, 8 Jan 2013 05:41:32 -0800 (PST)
In-Reply-To: <50E87B7B.5070605@acm.org>
References: <7ED55FF1-3E1A-4DF7-918E-07790517B848@softarmor.com> <50E87B7B.5070605@acm.org>
From: Dick Franks <rwfranks@acm.org>
Date: Tue, 8 Jan 2013 13:41:32 +0000
X-Google-Sender-Auth: 5TD6m9rLpobFrkqUZX2Agr3n64s
Message-ID: <CAKW6Ri6mb2468ScH8zcfQFzerA-wsVqOTY56vgXgQ1OrX8mEdw@mail.gmail.com>
Subject: Re: A proposal for a scientific approach to this question [was Re: I'm struggling with 2219 language again]
To: Marc Petit-Huguenin <petithug@acm.org>
Content-Type: text/plain; charset=UTF-8
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 08 Jan 2013 13:41:54 -0000

On 5 January 2013 19:14, Marc Petit-Huguenin <petithug@acm.org> wrote:
[snip]
>
> Another way to look at it would be to run the following experiment:
>
> 1. Someone design a new protocol, something simple but not obvious, and write
> in a formal language and keep it secret.
>
Which raises the obvious question:  Why do we not write protocol specs
in a formal specification language instead of struggling with the
ambiguities of natural language?

Theorem provers and automated verification tools could then be brought
to bear on both specifiations and implementations.



Dick
--

From bclaise@cisco.com  Tue Jan  8 06:05:25 2013
Return-Path: <bclaise@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F14E921F89CB; Tue,  8 Jan 2013 06:05:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.369
X-Spam-Level: 
X-Spam-Status: No, score=-10.369 tagged_above=-999 required=5 tests=[AWL=0.230, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 FGXPuM9tBTEw; Tue,  8 Jan 2013 06:05:25 -0800 (PST)
Received: from av-tac-bru.cisco.com (weird-brew.cisco.com [144.254.15.118]) by ietfa.amsl.com (Postfix) with ESMTP id 38F2F21F89C0; Tue,  8 Jan 2013 06:05:25 -0800 (PST)
X-TACSUNS: Virus Scanned
Received: from strange-brew.cisco.com (localhost.cisco.com [127.0.0.1]) by av-tac-bru.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id r08E5ORe008437; Tue, 8 Jan 2013 15:05:24 +0100 (CET)
Received: from [10.60.67.89] (ams-bclaise-8918.cisco.com [10.60.67.89]) by strange-brew.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id r08E5Nr2005436; Tue, 8 Jan 2013 15:05:23 +0100 (CET)
Message-ID: <50EC27A3.3070705@cisco.com>
Date: Tue, 08 Jan 2013 15:05:23 +0100
From: Benoit Claise <bclaise@cisco.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: [radext] Last Call: <draft-ietf-radext-radius-extensions-07.txt> (Remote	Authentication Dial In User Service (RADIUS) Protocol	Extensions) to Proposed Standard
References: <20130104143514.20728.47886.idtracker@ietfa.amsl.com>
In-Reply-To: <20130104143514.20728.47886.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: radext@ietf.org, The IESG <iesg-secretary@ietf.org>, IETF-Announce <ietf-announce@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 08 Jan 2013 14:05:26 -0000

Dear all,

Please note that version 8 has just been posted.

Regards, Benoit
> The IESG has received a request from the RADIUS EXTensions WG (radext) to
> consider the following document:
> - 'Remote Authentication Dial In User Service (RADIUS) Protocol
>     Extensions'
>    <draft-ietf-radext-radius-extensions-07.txt> as Proposed Standard
>
> The IESG plans to make a decision in the next few weeks, and solicits
> final comments on this action. Please send substantive comments to the
> ietf@ietf.org mailing lists by 2013-01-18. Exceptionally, comments may be
> sent to iesg@ietf.org instead. In either case, please retain the
> beginning of the Subject line to allow automated sorting.
>
> Abstract
>
>
>     The Remote Authentication Dial In User Service (RADIUS) protocol is
>     nearing exhaustion of its current 8-bit Attribute Type space.  In
>     addition, experience shows a growing need for complex grouping, along
>     with attributes which can carry more than 253 octets of data.  This
>     document defines changes to RADIUS which address all of the above
>     problems.
>
>
>
>
> The file can be obtained via
> http://datatracker.ietf.org/doc/draft-ietf-radext-radius-extensions/
>
> IESG discussion can be tracked via
> http://datatracker.ietf.org/doc/draft-ietf-radext-radius-extensions/ballot/
>
>
> No IPR declarations have been submitted directly on this I-D.
>
>
> _______________________________________________
> radext mailing list
> radext@ietf.org
> https://www.ietf.org/mailman/listinfo/radext
>
>


From jeanjour@comcast.net  Tue Jan  8 06:45:34 2013
Return-Path: <jeanjour@comcast.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4E3F121F892E for <ietf@ietfa.amsl.com>; Tue,  8 Jan 2013 06:45:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.707
X-Spam-Level: 
X-Spam-Status: No, score=-100.707 tagged_above=-999 required=5 tests=[AWL=-0.270, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_NET=0.611, RDNS_NONE=0.1, USER_IN_WHITELIST=-100]
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 sHfJSHkIPPVd for <ietf@ietfa.amsl.com>; Tue,  8 Jan 2013 06:45:33 -0800 (PST)
Received: from qmta04.westchester.pa.mail.comcast.net (qmta04.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:43:76:96:62:40]) by ietfa.amsl.com (Postfix) with ESMTP id 2C88421F873B for <ietf@ietf.org>; Tue,  8 Jan 2013 06:45:33 -0800 (PST)
Received: from omta22.westchester.pa.mail.comcast.net ([76.96.62.73]) by qmta04.westchester.pa.mail.comcast.net with comcast id lRmx1k0031ap0As54SlYHL; Tue, 08 Jan 2013 14:45:32 +0000
Received: from [10.0.1.3] ([98.229.211.49]) by omta22.westchester.pa.mail.comcast.net with comcast id lSlX1k00e14WE023iSlYA5; Tue, 08 Jan 2013 14:45:32 +0000
Mime-Version: 1.0
Message-Id: <a0624080acd11df9df1f7@[10.0.1.3]>
In-Reply-To: <CAKW6Ri6mb2468ScH8zcfQFzerA-wsVqOTY56vgXgQ1OrX8mEdw@mail.gmail.com>
References: <7ED55FF1-3E1A-4DF7-918E-07790517B848@softarmor.com> <50E87B7B.5070605@acm.org> <CAKW6Ri6mb2468ScH8zcfQFzerA-wsVqOTY56vgXgQ1OrX8mEdw@mail.gmail.com>
Date: Tue, 8 Jan 2013 09:45:23 -0500
To: Dick Franks <rwfranks@acm.org>, Marc Petit-Huguenin <petithug@acm.org>
From: John Day <jeanjour@comcast.net>
Subject: Re: A proposal for a scientific approach to this question [was Re: 	I'm struggling with 2219 language again]
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20121106; t=1357656332; bh=YfRoK3k8cextDtUd93DaPo2vvCzrjmwSHHlY1edoq5Q=; h=Received:Received:Mime-Version:Message-Id:Date:To:From:Subject: Content-Type; b=PmUfRl7lfW6bnMpPfxB1qcmsVMk+UnFE0JCZ3Y25b8B+DHuT1l/7qVTJPcIfrMoxP wVDtZDav4ymuyN8uxqTZe4sHwPfML1uytdsiF4KlmRGb6Mc3vGLE1pOrCdk8a7pZ3g zY0ZcQQ0XaSnc8a48hSvck5DoY+UieevunXV0i6F5tH/C1JVjG+u1Q83g7ka+NfDBT CqmscWDwUrVbN0R8lXBaczHNnCBwLna+dqmqlv6fbPXdlmb5fSX++4VGEnWlhmTt32 8OkWp5CN6qoTKSvzJTHP3Y4ZYfaDoQtR2nVUz8/N8QDePqTDAdJViMjL6fUotrgwyl B8o0MdOtHdkBA==
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 08 Jan 2013 14:45:34 -0000

The reasons have been discussed or at least alluded to previously in 
this thread.  The short answer is we have been there and done that: 
30 years ago.

All those tools were developed and used successfully in the 80s.   I 
know of cases where doing the formal specification alongside the 
design phase caught lots of problems.   However, there are two 
central problems:  First, in general, programmers are lazy and just 
want to code. ;-)  Using a formal method is a lot more work.  Second, 
the complexity of the formal statements that must be written down is 
greater than the code.  So there is a higher probability of mistakes 
in the formal description than in the code.  Admittedly, if those 
statements are made, one has a far greater understanding of what you 
are doing.

Once you have both, there is still the problem that if a bug or 
ambiguity shows up, neither the code nor the formal spec nor a prose 
spec can be taken be the right one.  What is right is still in the 
heads of the authors.  All of these are merely approximations.  One 
has to go back and look at all of them and determine what the right 
answer is.  Of course, the more things one has to look at the better. 
(for a bit more, see Chapter 1 of PNA).

John

>Which raises the obvious question:  Why do we not write protocol specs
>in a formal specification language instead of struggling with the
>ambiguities of natural language?
>
>Theorem provers and automated verification tools could then be brought
>to bear on both specifiations and implementations.
>
>
>
>Dick
>--


From d3e3e3@gmail.com  Tue Jan  8 07:13:13 2013
Return-Path: <d3e3e3@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 89F5A21F8A52 for <ietf@ietfa.amsl.com>; Tue,  8 Jan 2013 07:13:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.599
X-Spam-Level: 
X-Spam-Status: No, score=-103.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
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 NQFZ2Tc1Wr-Z for <ietf@ietfa.amsl.com>; Tue,  8 Jan 2013 07:13:12 -0800 (PST)
Received: from mail-ob0-f179.google.com (mail-ob0-f179.google.com [209.85.214.179]) by ietfa.amsl.com (Postfix) with ESMTP id 93E9621F87AB for <ietf@ietf.org>; Tue,  8 Jan 2013 07:13:12 -0800 (PST)
Received: by mail-ob0-f179.google.com with SMTP id x4so462064obh.10 for <ietf@ietf.org>; Tue, 08 Jan 2013 07:13:12 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; bh=8CbbqklL4GvyGg+Pk8X87miQ6uY4zSDmmfop78r0T3M=; b=a/1ViD7fzD7OaNW/tYupioa+kFYSxwlU0uoVy+D5GUoM61OFo820pzwT/9THjDaUjl Yc+khMf8ZrNDoofBj1mk6gwNBNrnRCOUSyvZ5eYxzSsr5w1hDLXlZUjj0MtG48x6/5FR EzgnQImeKNO1fUsH9l1ey3t67CXF/kaS7qDfLc5JqLaBZmK00W/bpkMdYuzOaxU8PJMs gmGRjlUMbL5RPtluHbtV36FFGpxuPalic+NddRrs8JCdw3p9P5CjR0ZwB/mbEziR4KZx Ixdx+UdgJD5Hd8kNvnk/a1yCQSXh3pCxuezWvvkals/W4R6PuwDYgbs6BxZUQKW53hFf YXNg==
Received: by 10.60.32.69 with SMTP id g5mr36767574oei.21.1357657992143; Tue, 08 Jan 2013 07:13:12 -0800 (PST)
MIME-Version: 1.0
Received: by 10.76.144.105 with HTTP; Tue, 8 Jan 2013 07:12:52 -0800 (PST)
In-Reply-To: <a0624080acd11df9df1f7@10.0.1.3>
References: <7ED55FF1-3E1A-4DF7-918E-07790517B848@softarmor.com> <50E87B7B.5070605@acm.org> <CAKW6Ri6mb2468ScH8zcfQFzerA-wsVqOTY56vgXgQ1OrX8mEdw@mail.gmail.com> <a0624080acd11df9df1f7@10.0.1.3>
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Tue, 8 Jan 2013 10:12:52 -0500
Message-ID: <CAF4+nEE9uq_811ZMX4ShCqoprL_FZFhY4XW9W2U0TZmpf86uTQ@mail.gmail.com>
Subject: Re: A proposal for a scientific approach to this question [was Re: I'm struggling with 2219 language again]
To: IETF Discussion <ietf@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 08 Jan 2013 15:13:13 -0000

Another problem is maintenance. Protocols change. Having to maintain a
formal specification is commonly at least an order of magnitude more
effort than maintaining a prose description. So it doesn't happen and
they very rapidly get out of synch in any living protocol. As an
example, the IEEE 802.11 (Wi-Fi) standard used to have a normative
formal description of the MAC operation (see Annex C of 802.11-1999).
By 802.11-2007 this was out of synch but was still included as
informational material on the theory it might be of some use and the
section began with the words "This clause is no longer maintained...".
Although still present as informational in 802.11-2012, the first
words of that section are now "This annex is obsolete."

And, as has been mentioned before, I'd like to emphasize that the IETF
experience and principal is that, if you want interoperation,
compliance testing is useless. The way to interoperation is
interoperation testing between implementations and, to a first
approximation, the more and the earlier you do interoperation testing,
the better.

Thanks,
Donald
=============================
 Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
 155 Beaver Street, Milford, MA 01757 USA
 d3e3e3@gmail.com


On Tue, Jan 8, 2013 at 9:45 AM, John Day <jeanjour@comcast.net> wrote:
> The reasons have been discussed or at least alluded to previously in this
> thread.  The short answer is we have been there and done that: 30 years ago.
>
> All those tools were developed and used successfully in the 80s.   I know of
> cases where doing the formal specification alongside the design phase caught
> lots of problems.   However, there are two central problems:  First, in
> general, programmers are lazy and just want to code. ;-)  Using a formal
> method is a lot more work.  Second, the complexity of the formal statements
> that must be written down is greater than the code.  So there is a higher
> probability of mistakes in the formal description than in the code.
> Admittedly, if those statements are made, one has a far greater
> understanding of what you are doing.
>
> Once you have both, there is still the problem that if a bug or ambiguity
> shows up, neither the code nor the formal spec nor a prose spec can be taken
> be the right one.  What is right is still in the heads of the authors.  All
> of these are merely approximations.  One has to go back and look at all of
> them and determine what the right answer is.  Of course, the more things one
> has to look at the better. (for a bit more, see Chapter 1 of PNA).
>
> John
>
>
>> Which raises the obvious question:  Why do we not write protocol specs
>> in a formal specification language instead of struggling with the
>> ambiguities of natural language?
>>
>> Theorem provers and automated verification tools could then be brought
>> to bear on both specifiations and implementations.
>>
>>
>>
>> Dick
>> --
>
>

From jeanjour@comcast.net  Tue Jan  8 07:54:46 2013
Return-Path: <jeanjour@comcast.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8088D21F88B1 for <ietf@ietfa.amsl.com>; Tue,  8 Jan 2013 07:54:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.677
X-Spam-Level: 
X-Spam-Status: No, score=-100.677 tagged_above=-999 required=5 tests=[AWL=-0.240, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_NET=0.611, RDNS_NONE=0.1, USER_IN_WHITELIST=-100]
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 ltiDt9McE0Ca for <ietf@ietfa.amsl.com>; Tue,  8 Jan 2013 07:54:46 -0800 (PST)
Received: from qmta07.westchester.pa.mail.comcast.net (qmta07.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:43:76:96:62:64]) by ietfa.amsl.com (Postfix) with ESMTP id 8DC1121F8833 for <ietf@ietf.org>; Tue,  8 Jan 2013 07:54:45 -0800 (PST)
Received: from omta16.westchester.pa.mail.comcast.net ([76.96.62.88]) by qmta07.westchester.pa.mail.comcast.net with comcast id lTfP1k0051uE5Es57Tul83; Tue, 08 Jan 2013 15:54:45 +0000
Received: from [10.0.1.3] ([98.229.211.49]) by omta16.westchester.pa.mail.comcast.net with comcast id lTuj1k00R14WE023cTukT5; Tue, 08 Jan 2013 15:54:45 +0000
Mime-Version: 1.0
Message-Id: <a06240811cd11f0cb5e46@[10.0.1.3]>
In-Reply-To: <CAF4+nEE9uq_811ZMX4ShCqoprL_FZFhY4XW9W2U0TZmpf86uTQ@mail.gmail.com>
References: <7ED55FF1-3E1A-4DF7-918E-07790517B848@softarmor.com> <50E87B7B.5070605@acm.org> <CAKW6Ri6mb2468ScH8zcfQFzerA-wsVqOTY56vgXgQ1OrX8mEdw@mail.gmail.com> <a0624080acd11df9df1f7@10.0.1.3> <CAF4+nEE9uq_811ZMX4ShCqoprL_FZFhY4XW9W2U0TZmpf86uTQ@mail.gmail.com>
Date: Tue, 8 Jan 2013 10:51:46 -0500
To: Donald Eastlake <d3e3e3@gmail.com>, IETF Discussion <ietf@ietf.org>
From: John Day <jeanjour@comcast.net>
Subject: Re: A proposal for a scientific approach to this question [was Re: 	I'm struggling with 2219 language again]
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20121106; t=1357660485; bh=usupgj7IzAadExeka0cCFuktA8NtPAPm5hamoXRHb3w=; h=Received:Received:Mime-Version:Message-Id:Date:To:From:Subject: Content-Type; b=FnIRLBRH51ZswPbvSE8ikUVEHxKwwFS4JxvMBiIUwqA/ZXTwKcX2CoTeUZaqnIsjE AIaHA5LqV+3g5f93YvHNv5Ob3OCwprzaxsixhjUMpVynGdjuHUTkDwStpBvy+cErij lsyyjlDkiN/c7kaVUH+a4pZffdBFzwElI0gLQjdKkWOQ0iCSXN210F+tQc60GQG+m+ LAGjmKn2waZ9viEFL03dYPTLIiU8qLRXitrUamJ+OqHYUFHYfvulvKfSAFoE5p2Fq7 ClfSpMGXLkGvMFRRnvdJKRgD0WacYXrd4Mgz8yGRnaKl6pWn/1DYVcgVin0k4Qegif LMdFOyIEqCB6A==
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 08 Jan 2013 15:54:46 -0000

Hear. Hear.  Ditto!  Absolutely.  etc.

At 10:12 AM -0500 1/8/13, Donald Eastlake wrote:
>Another problem is maintenance. Protocols change. Having to maintain a
>formal specification is commonly at least an order of magnitude more
>effort than maintaining a prose description. So it doesn't happen and
>they very rapidly get out of synch in any living protocol. As an
>example, the IEEE 802.11 (Wi-Fi) standard used to have a normative
>formal description of the MAC operation (see Annex C of 802.11-1999).
>By 802.11-2007 this was out of synch but was still included as
>informational material on the theory it might be of some use and the
>section began with the words "This clause is no longer maintained...".
>Although still present as informational in 802.11-2012, the first
>words of that section are now "This annex is obsolete."
>
>And, as has been mentioned before, I'd like to emphasize that the IETF
>experience and principal is that, if you want interoperation,
>compliance testing is useless. The way to interoperation is
>interoperation testing between implementations and, to a first
>approximation, the more and the earlier you do interoperation testing,
>the better.
>
>Thanks,
>Donald
>=============================
>  Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
>  155 Beaver Street, Milford, MA 01757 USA
>  d3e3e3@gmail.com
>
>
>On Tue, Jan 8, 2013 at 9:45 AM, John Day <jeanjour@comcast.net> wrote:
>>  The reasons have been discussed or at least alluded to previously in this
>>  thread.  The short answer is we have been there and done that: 30 years ago.
>>
>>  All those tools were developed and used successfully in the 80s.   I know of
>>  cases where doing the formal specification alongside the design phase caught
>>  lots of problems.   However, there are two central problems:  First, in
>>  general, programmers are lazy and just want to code. ;-)  Using a formal
>>  method is a lot more work.  Second, the complexity of the formal statements
>>  that must be written down is greater than the code.  So there is a higher
>>  probability of mistakes in the formal description than in the code.
>>  Admittedly, if those statements are made, one has a far greater
>>  understanding of what you are doing.
>>
>>  Once you have both, there is still the problem that if a bug or ambiguity
>>  shows up, neither the code nor the formal spec nor a prose spec can be taken
>>  be the right one.  What is right is still in the heads of the authors.  All
>>  of these are merely approximations.  One has to go back and look at all of
>>  them and determine what the right answer is.  Of course, the more things one
>>  has to look at the better. (for a bit more, see Chapter 1 of PNA).
>>
>>  John
>>
>>
>>>  Which raises the obvious question:  Why do we not write protocol specs
>>>  in a formal specification language instead of struggling with the
>>>  ambiguities of natural language?
>>>
>>>  Theorem provers and automated verification tools could then be brought
>>>  to bear on both specifiations and implementations.
>>>
>>>
>>>
>>>  Dick
>>>  --
>>
>>


From sayrer@gmail.com  Tue Jan  8 08:19:23 2013
Return-Path: <sayrer@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4923D21F85C2; Tue,  8 Jan 2013 08:19:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 7q7lQcCMzRFg; Tue,  8 Jan 2013 08:19:21 -0800 (PST)
Received: from mail-wg0-f54.google.com (mail-wg0-f54.google.com [74.125.82.54]) by ietfa.amsl.com (Postfix) with ESMTP id F245421F85C3; Tue,  8 Jan 2013 08:19:20 -0800 (PST)
Received: by mail-wg0-f54.google.com with SMTP id fg15so463845wgb.33 for <multiple recipients>; Tue, 08 Jan 2013 08:19:14 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=16UXqXdN60Yfl5fuz9rxKqd7LzfCwN8C/zf4TwZl46E=; b=QQt6kfCtZ3c9TpxDRn6YUaN9XeFzzj0qSGj+QFfo/8zAU1GroU1mnK6IvuUiPNCO/n jBgN5ptXfpRLY/RHYT+kIAVL3oOIhfpG4TEHc18ggl5+r3b2RyyYyacgiz+6pvRO5l0G SIq47ESuS0KeHJcnmIs43uFgbawhvTuyvDO5plxgUiyg5ChvyS0tXmimDcpYMWk0V2pU k/UTJ1htq1m7yNa1xp92t9Z7vrXMGmpMs+02kLU5KOHxYMsAO5yqj+qt03Il2X+3TnZ+ lbqC5WduY3Uw4pjs8gEpTqwGt2Hqig+slhD9y+xYKRu+TVOXqH9liZVuU/NYDEUT9ZM5 08hQ==
MIME-Version: 1.0
Received: by 10.180.103.136 with SMTP id fw8mr15592842wib.27.1357661947770; Tue, 08 Jan 2013 08:19:07 -0800 (PST)
Received: by 10.194.1.101 with HTTP; Tue, 8 Jan 2013 08:19:07 -0800 (PST)
In-Reply-To: <CAD5Szk-U1LeBSfUgah8XXE2LZ=utR=0W-V7VsT6j-i2VixZerg@mail.gmail.com>
References: <20121211150057.28223.93310.idtracker@ietfa.amsl.com> <50cb04b9.86df440a.72fe.1e20SMTPIN_ADDED_BROKEN@mx.google.com> <CABP7RbeNsZ_rBWRjou=VG+hBhUKaOz+y1a0sSChwWiHte9znnQ@mail.gmail.com> <50cb5f3c.694c420a.38fb.39afSMTPIN_ADDED_BROKEN@mx.google.com> <CAChr6SxZRc3B_HCbw76kLe2dsRSr43r-gLpfMVnCUfJTrZdTLA@mail.gmail.com> <CABP7RbfA33huBFadMeXTTEt=MkjW8-d4DFH7+GLXGurnm9sSRw@mail.gmail.com> <CAOXDeqpPE4eNy_qJpDPdPHbCQakG9-hDcNZ3Sj9r4kWedByVzQ@mail.gmail.com> <CAChr6SwtS_=iS-k4mJm1vHjEvvGVzay5jDYeGheqsPZqO-89CQ@mail.gmail.com> <EABB8F51-C3B4-49F5-8672-5C2ABAC7043A@mnot.net> <CAChr6Sx7JdKM91EwJaSZ0Ra_F4FSqkuc3vzTY1LM=F_8sWho+Q@mail.gmail.com> <1357515310.6827.23.camel@polyglot> <CAChr6SyAq=7aQdZn54ihYK+0hDhL--2Oaq0RvehoNFbwKNNShA@mail.gmail.com> <CAChr6SxorKO20rGYi-e4YNF=HNGrwz8wPGKCFZQYWQwqsetjjg@mail.gmail.com> <CAOXDeqqE2mCLapwvjwQkme5VTpRCfmF0mFQcx02WW0-zi4i5=g@mail.gmail.com> <50EB4E8B.30700@versi.edu.au> <CAOXDeqoOj1K_zBWVZbE2j4Vnp1pYZ1yUEp9nyTKZmp-QrAziqg@mail.gmail.com> <CAD5Szk-U1LeBSfUgah8XXE2LZ=utR=0W-V7VsT6j-i2VixZerg@mail.gmail.com>
Date: Tue, 8 Jan 2013 08:19:07 -0800
Message-ID: <CAChr6SzvXWkkCZU3GPGFJtoqZ=0AOktFhrML6ZMtf7nU9iwxjw@mail.gmail.com>
Subject: Re: [apps-discuss] Last Call: <draft-ietf-appsawg-json-pointer-07.txt> (JSON Pointer) to Proposed Standard
From: Robert Sayre <sayrer@gmail.com>
To: Jared Rosoff <jsr@10gen.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: Mark Nottingham <mnot@mnot.net>, IETF Discussion <ietf@ietf.org>, Matthew Morley <matt@mpcm.com>, IETF Apps Discuss <apps-discuss@ietf.org>, IESG <iesg@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 08 Jan 2013 16:19:23 -0000

Hi Jared,

Earlier in the thread, I actually directly asked whether software that
operates on arbitrary JSON was in scope for this WG (my example was
CouchDB), after having suggested either changing the path syntax or
renaming the array operations.[0]

The editors didn't respond, except with process points or simple
contradictions without rationale. My conclusion is that software such
as MongoDB must be out of scope here. To their credit, the editors did
point out that anyone is free to try again, and I plan to do just
that. There's no reason to hold up this WG, since they seem to be
burnt out.

- Rob

[0] http://www.ietf.org/mail-archive/web/apps-discuss/current/msg08552.html


On Tue, Jan 8, 2013 at 12:26 AM, Jared Rosoff <jsr@10gen.com> wrote:
> hi team, i'm new to the discussion here, but wanted to jump in. i work on
> mongodb, a json database, and i wanted to share how we deal with these
> issues.
>
> mongodb uses almost the same notation for pointers ("a.b.c" instead of
> "/a/b/c"). We also index arrays in the same way as json pointer ( "a.0"
> refers to the 0th element of the array called "a"). and this works fine in
> practice. (ref: http://docs.mongodb.org/manual/core/document/#dot-notation)
>
> our update syntax is different tho. the verbs in mongodb updates for json
> documents are more specific:
>
> set / unset / rename (operations on fields)
> inc (increment integer values)
> push / pop / pull (operations on arrays)
> addToSet / removeFromSet (operations on arrays)
>
> (ref http://docs.mongodb.org/manual/reference/operators/#update)
>
> since update operations are more specific and type dependent, it's easy to
> throw an error if an unexpected type is encountered (e.g. try to push onto a
> field that has a non-array value) and to act smartly on empty fields ( if
> path to push is empty, we assume it should be an array, create it, and then
> push the value onto it).
>
> i concur the the pointer syntax is fine and ambiguity comes from the
> definition of operators in json patch.
>
> -j
>
>
> On Mon, Jan 7, 2013 at 10:26 PM, Matthew Morley <matt@mpcm.com> wrote:
>>
>> On Mon, Jan 7, 2013 at 5:39 PM, Conal Tuohy <conal.tuohy@versi.edu.au>
>> wrote:
>>>
>>> On 07/01/13 13:23, Matthew Morley wrote:
>>>
>>>
>>> For me the deficiency is not in the pointer, but patch format being
>>> generated.
>>>
>>> One approach is to push that *one* test, structure conformity, into the
>>> pointer syntax. Another is via the type operation.
>>>
>>> If a vague patch is generated, vague results are to be expected.
>>>
>>> It seems to me, on the contrary, that the deficiency is in the pointer
>>> syntax, and I think it would be a mistake to try to work around that
>>> deficiency in JSON Patch. Because aren't there other things which one might
>>> do with JSON Pointer than use it with JSON Patch? There's been mention of
>>> having it registered as a URI fragment identifier syntax for JSON for
>>> example. JSON Pointers could then end up all over the place, outside of
>>> patches. IMHO JSON Pointer needs to be taken seriously as a technology in
>>> its own right.
>>
>>
>> Couldn't agree more about it being taken seriously in its own right. :)
>>
>> JSON Pointer for me exists outside of JSON Patch, always has and will do
>> the way we think about structures. As it represents both a resolution path
>> and an identity string (both ends of the path concept). I see value from the
>> identity view, in describing a location that is aware of being inside an
>> array.
>>
>> But JSON Pointer should not be changed just because of issues with JSON
>> Patch, especially when JSON Patch is attempting to address those issues with
>> other mechanisms within the specification. That is all I was trying to
>> express. The syntax change should be for other reasons, if it is going to be
>> made.
>>
>> My personal experience (for what its worth): In the past I've tried a
>> number of syntaxes like JSON Pointer. Mostly a.b.c.0 and even a.b.c:0 at
>> times to address the same issues suggested here. Though my experiences
>> pushed me towards a single syntax using a.b.c.0, and thus my support for
>> /a/b/c/0 over /a/b/c:0.
>>
>> The system at first used the . or : syntax, combined with dynamic tokens,
>> being pointers themselves, to resolve other pointers. So it was not
>> reasonable to know ahead of time if an end point was an array or an object.
>> "a.b.c.{d.e.f}" could end up in an array or in an object, depending on the
>> value at d.e.f at the time of resolution. Especially with many layers of
>> tokens to resolve, and changing data structures.
>>
>> I found in practice, it didn't really matter, so the choice of . or : was
>> phased out. At the end of the day the two syntaxes point to mutually
>> exclusive points within the data, so that `meta data` about the structure
>> was removed from the syntax we used. It didn't add value, even if it added
>> clarity at times. We also had functions at the end of paths, but that goes
>> beyond the JSON focus of the JSON Pointer goals, so those points are not
>> relevant here.
>>
>> This discussion thread seems to be getting overly complicated, but JSON
>> Pointer changes should come from the JSON Pointer view point and that
>> specifications goals, not from short comings in JSON Patch.
>>
>> --
>> Matthew P. C. Morley
>> _______________________________________________
>> apps-discuss mailing list
>> apps-discuss@ietf.org
>> https://www.ietf.org/mailman/listinfo/apps-discuss
>>
>
>
> _______________________________________________
> apps-discuss mailing list
> apps-discuss@ietf.org
> https://www.ietf.org/mailman/listinfo/apps-discuss
>

From jasnell@gmail.com  Tue Jan  8 09:07:13 2013
Return-Path: <jasnell@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 78DAA21F84E0; Tue,  8 Jan 2013 09:07:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.036
X-Spam-Level: 
X-Spam-Status: No, score=-4.036 tagged_above=-999 required=5 tests=[AWL=-0.438, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
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 Vywmc-YQNH+b; Tue,  8 Jan 2013 09:07:12 -0800 (PST)
Received: from mail-ia0-f179.google.com (mail-ia0-f179.google.com [209.85.210.179]) by ietfa.amsl.com (Postfix) with ESMTP id DB80821F84C0; Tue,  8 Jan 2013 09:07:11 -0800 (PST)
Received: by mail-ia0-f179.google.com with SMTP id o25so561155iad.10 for <multiple recipients>; Tue, 08 Jan 2013 09:07:11 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=a8mUXHBc/lhQAOsrQLKZhHZSou57RXlD5TzUU91Kv9M=; b=BYM2as89e5+kSXXnASNb/uq4X3C+CRDwFYwZUxCqp2Eg5S5Ff25aR3RBXIQy/0aGfA OnIY13hbaCFeo/Qw5574i+76p9EsOy+qwrVODOYrpeAFTEx/BGNedMDLYMF33bUSDIAn MqInw15BhMoXKOQAjKImejhfa+DkJbPjUuYhI0eRAvFRJOZjRZiKYXmBPqcme1FKK75p xEnhAqHWbKBctl2/tfSf3JIyHE+nLlxwBPEjIZVgWPuiJnxjQBNgRPMg849AdtcrhASP BUfGjtC9GNaH1ffAB5NX091eaumfiHlc/hAalstWa40dzsn9kgP2L0qPjLb0fRSNyIhs TqsQ==
Received: by 10.50.150.174 with SMTP id uj14mr9636735igb.19.1357664831403; Tue, 08 Jan 2013 09:07:11 -0800 (PST)
MIME-Version: 1.0
Received: by 10.64.7.19 with HTTP; Tue, 8 Jan 2013 09:06:50 -0800 (PST)
In-Reply-To: <CAD5Szk-U1LeBSfUgah8XXE2LZ=utR=0W-V7VsT6j-i2VixZerg@mail.gmail.com>
References: <20121211150057.28223.93310.idtracker@ietfa.amsl.com> <50cb04b9.86df440a.72fe.1e20SMTPIN_ADDED_BROKEN@mx.google.com> <CABP7RbeNsZ_rBWRjou=VG+hBhUKaOz+y1a0sSChwWiHte9znnQ@mail.gmail.com> <50cb5f3c.694c420a.38fb.39afSMTPIN_ADDED_BROKEN@mx.google.com> <CAChr6SxZRc3B_HCbw76kLe2dsRSr43r-gLpfMVnCUfJTrZdTLA@mail.gmail.com> <CABP7RbfA33huBFadMeXTTEt=MkjW8-d4DFH7+GLXGurnm9sSRw@mail.gmail.com> <CAOXDeqpPE4eNy_qJpDPdPHbCQakG9-hDcNZ3Sj9r4kWedByVzQ@mail.gmail.com> <CAChr6SwtS_=iS-k4mJm1vHjEvvGVzay5jDYeGheqsPZqO-89CQ@mail.gmail.com> <EABB8F51-C3B4-49F5-8672-5C2ABAC7043A@mnot.net> <CAChr6Sx7JdKM91EwJaSZ0Ra_F4FSqkuc3vzTY1LM=F_8sWho+Q@mail.gmail.com> <1357515310.6827.23.camel@polyglot> <CAChr6SyAq=7aQdZn54ihYK+0hDhL--2Oaq0RvehoNFbwKNNShA@mail.gmail.com> <CAChr6SxorKO20rGYi-e4YNF=HNGrwz8wPGKCFZQYWQwqsetjjg@mail.gmail.com> <CAOXDeqqE2mCLapwvjwQkme5VTpRCfmF0mFQcx02WW0-zi4i5=g@mail.gmail.com> <50EB4E8B.30700@versi.edu.au> <CAOXDeqoOj1K_zBWVZbE2j4Vnp1pYZ1yUEp9nyTKZmp-QrAziqg@mail.gmail.com> <CAD5Szk-U1LeBSfUgah8XXE2LZ=utR=0W-V7VsT6j-i2VixZerg@mail.gmail.com>
From: James M Snell <jasnell@gmail.com>
Date: Tue, 8 Jan 2013 09:06:50 -0800
Message-ID: <CABP7Rbea9HoauQs_VhzdgUzgbFoLG=ppP98V2wzo86=145tWTA@mail.gmail.com>
Subject: Re: [apps-discuss] Last Call: <draft-ietf-appsawg-json-pointer-07.txt> (JSON Pointer) to Proposed Standard
To: Jared Rosoff <jsr@10gen.com>
Content-Type: multipart/alternative; boundary=f46d043d644bfff78a04d2c9f9f6
Cc: Mark Nottingham <mnot@mnot.net>, IETF Discussion <ietf@ietf.org>, Matthew Morley <matt@mpcm.com>, IETF Apps Discuss <apps-discuss@ietf.org>, IESG <iesg@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 08 Jan 2013 17:07:13 -0000

--f46d043d644bfff78a04d2c9f9f6
Content-Type: text/plain; charset=UTF-8

Fortunately the JSON-Patch syntax is designed such that it is possible to
extend the range of defined operations without breaking basic structure...
much as I have done with the json-predicates draft. You would need to
define a new media type to associate with the extensions but that's not
difficult.

Consider something along the lines of.. application/json-patch-ext...

[
  {"op": "unset", "path": "/a/b"},
  {"op": "inc", "path": "/a/c"},
  {"op": "push", "path": "/a/d", "value": 1}
]

- James



On Tue, Jan 8, 2013 at 12:26 AM, Jared Rosoff <jsr@10gen.com> wrote:

> hi team, i'm new to the discussion here, but wanted to jump in. i work on
> mongodb, a json database, and i wanted to share how we deal with these
> issues.
>
> mongodb uses almost the same notation for pointers ("a.b.c" instead of
> "/a/b/c"). We also index arrays in the same way as json pointer ( "a.0"
> refers to the 0th element of the array called "a"). and this works fine in
> practice. (ref: http://docs.mongodb.org/manual/core/document/#dot-notation
> )
>
> our update syntax is different tho. the verbs in mongodb updates for json
> documents are more specific:
>
> set / unset / rename (operations on fields)
> inc (increment integer values)
> push / pop / pull (operations on arrays)
> addToSet / removeFromSet (operations on arrays)
>
> (ref http://docs.mongodb.org/manual/reference/operators/#update)
>
> since update operations are more specific and type dependent, it's easy to
> throw an error if an unexpected type is encountered (e.g. try to push onto
> a field that has a non-array value) and to act smartly on empty fields ( if
> path to push is empty, we assume it should be an array, create it, and then
> push the value onto it).
>
> i concur the the pointer syntax is fine and ambiguity comes from the
> definition of operators in json patch.
>
> -j
>
>
> On Mon, Jan 7, 2013 at 10:26 PM, Matthew Morley <matt@mpcm.com> wrote:
>
>> On Mon, Jan 7, 2013 at 5:39 PM, Conal Tuohy <conal.tuohy@versi.edu.au>wrote:
>>
>>>  On 07/01/13 13:23, Matthew Morley wrote:
>>>
>>>
>>> For me the deficiency is not in the pointer, but patch format being
>>> generated.
>>>
>>> One approach is to push that *one* test, structure conformity, into the
>>> pointer syntax. Another is via the type operation.
>>>
>>> If a vague patch is generated, vague results are to be expected.
>>>
>>> It seems to me, on the contrary, that the deficiency is in the pointer
>>> syntax, and I think it would be a mistake to try to work around that
>>> deficiency in JSON Patch. Because aren't there other things which one might
>>> do with JSON Pointer than use it with JSON Patch? There's been mention of
>>> having it registered as a URI fragment identifier syntax for JSON for
>>> example. JSON Pointers could then end up all over the place, outside of
>>> patches. IMHO JSON Pointer needs to be taken seriously as a technology in
>>> its own right.
>>>
>>
>> Couldn't agree more about it being taken seriously in its own right. :)
>>
>> JSON Pointer for me exists outside of JSON Patch, always has and will do
>> the way we think about structures. As it represents both a resolution path
>> and an identity string (both ends of the path concept). I see value from
>> the identity view, in describing a location that is aware of being inside
>> an array.
>>
>> But JSON Pointer should not be changed just because of issues with JSON
>> Patch, especially when JSON Patch is attempting to address those issues
>> with other mechanisms within the specification. That is all I was trying to
>> express. The syntax change should be for other reasons, if it is going to
>> be made.
>>
>> My personal experience (for what its worth): In the past I've tried a
>> number of syntaxes like JSON Pointer. Mostly a.b.c.0 and even a.b.c:0 at
>> times to address the same issues suggested here. Though my experiences
>> pushed me towards a single syntax using a.b.c.0, and thus my support for
>> /a/b/c/0 over /a/b/c:0.
>>
>> The system at first used the . or : syntax, combined with dynamic tokens,
>> being pointers themselves, to resolve other pointers. So it was not
>> reasonable to know ahead of time if an end point was an array or an object.
>>  "a.b.c.{d.e.f}" could end up in an array or in an object, depending on the
>> value at d.e.f at the time of resolution. Especially with many layers of
>> tokens to resolve, and changing data structures.
>>
>> I found in practice, it didn't really matter, so the choice of . or : was
>> phased out. At the end of the day the two syntaxes point to mutually
>> exclusive points within the data, so that `meta data` about the structure
>> was removed from the syntax we used. It didn't add value, even if it added
>> clarity at times. We also had functions at the end of paths, but that goes
>> beyond the JSON focus of the JSON Pointer goals, so those points are not
>> relevant here.
>>
>> This discussion thread seems to be getting overly complicated, but JSON
>> Pointer changes should come from the JSON Pointer view point and that
>> specifications goals, not from short comings in JSON Patch.
>>
>> --
>> Matthew P. C. Morley
>> _______________________________________________
>> apps-discuss mailing list
>> apps-discuss@ietf.org
>> https://www.ietf.org/mailman/listinfo/apps-discuss
>>
>>
>
> _______________________________________________
> apps-discuss mailing list
> apps-discuss@ietf.org
> https://www.ietf.org/mailman/listinfo/apps-discuss
>
>

--f46d043d644bfff78a04d2c9f9f6
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><font face=3D"courier new, monospace">Fortunately the JSON=
-Patch syntax is designed such that it is possible to extend the range of d=
efined operations without breaking basic structure... much as I have done w=
ith the json-predicates draft. You would need to define a new media type to=
 associate with the extensions but that&#39;s not difficult.</font><div>

<font face=3D"courier new, monospace"><br></font></div><div style><font fac=
e=3D"courier new, monospace">Consider something along the lines of.. applic=
ation/json-patch-ext...</font></div><div style><font face=3D"courier new, m=
onospace"><br>

</font></div><div style><font face=3D"courier new, monospace">[</font></div=
><div style><font face=3D"courier new, monospace">=C2=A0 {</font><span styl=
e=3D"font-family:&#39;courier new&#39;,monospace">&quot;op&quot;: &quot;uns=
et&quot;, &quot;path&quot;: &quot;/a/b&quot;</span><span style=3D"font-fami=
ly:&#39;courier new&#39;,monospace">},</span></div>

<div style><span style=3D"font-family:&#39;courier new&#39;,monospace">=C2=
=A0 {&quot;op&quot;: &quot;inc&quot;, &quot;path&quot;: &quot;/a/c&quot;},<=
/span></div><div style><span style=3D"font-family:&#39;courier new&#39;,mon=
ospace">=C2=A0 {&quot;op&quot;: &quot;push&quot;, &quot;path&quot;: &quot;/=
a/d&quot;, &quot;value&quot;: 1}</span></div>

<div style><font face=3D"courier new, monospace">]</font></div><div style><=
font face=3D"courier new, monospace"><br></font></div><div style><font face=
=3D"courier new, monospace">- James</font></div><div style><font face=3D"co=
urier new, monospace"><br>

</font></div></div><div class=3D"gmail_extra"><br><br><div class=3D"gmail_q=
uote">On Tue, Jan 8, 2013 at 12:26 AM, Jared Rosoff <span dir=3D"ltr">&lt;<=
a href=3D"mailto:jsr@10gen.com" target=3D"_blank">jsr@10gen.com</a>&gt;</sp=
an> wrote:<br>

<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div>hi team, i&#39;m new to the discussion =
here, but wanted to jump in. i work on mongodb, a json database, and i want=
ed to share how we deal with these issues.=C2=A0</div>

<div><br></div>mongodb uses almost the same notation for pointers (&quot;a.=
b.c&quot; instead of &quot;/a/b/c&quot;). We also index arrays in the same =
way as json pointer ( &quot;a.0&quot; refers to the 0th element of the arra=
y called &quot;a&quot;). and this works fine in practice. (ref:=C2=A0<a hre=
f=3D"http://docs.mongodb.org/manual/core/document/#dot-notation" target=3D"=
_blank">http://docs.mongodb.org/manual/core/document/#dot-notation</a>)=C2=
=A0<div>


<br></div><div>our update syntax is different tho. the verbs in mongodb upd=
ates for json documents are more specific:=C2=A0</div><div><br></div><div>s=
et / unset / rename (operations on fields)=C2=A0</div><div>inc (increment i=
nteger values)=C2=A0</div>


<div>push / pop / pull (operations on arrays)=C2=A0</div><div>addToSet / re=
moveFromSet (operations on arrays)=C2=A0</div><div><br></div><div>(ref <a h=
ref=3D"http://docs.mongodb.org/manual/reference/operators/#update" target=
=3D"_blank">http://docs.mongodb.org/manual/reference/operators/#update</a>)=
=C2=A0</div>


<div><br></div><div>since update operations are more specific and type depe=
ndent, it&#39;s easy to throw an error if an unexpected type is encountered=
 (e.g. try to push onto a field that has a non-array value) and to act smar=
tly on empty fields ( if path to push is empty, we assume it should be an a=
rray, create it, and then push the value onto it).=C2=A0</div>


<div><br></div><div>i concur the the pointer syntax is fine and ambiguity c=
omes from the definition of operators in json patch.=C2=A0</div><span class=
=3D"HOEnZb"><font color=3D"#888888"><div><br></div><div>-j</div><div><br></=
div>

</font></span><div><br><div class=3D"gmail_quote"><div><div class=3D"h5">On=
 Mon, Jan 7, 2013 at 10:26 PM, Matthew Morley <span dir=3D"ltr">&lt;<a href=
=3D"mailto:matt@mpcm.com" target=3D"_blank">matt@mpcm.com</a>&gt;</span> wr=
ote:<br>


</div></div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;bo=
rder-left:1px #ccc solid;padding-left:1ex"><div><div class=3D"h5"><div>On M=
on, Jan 7, 2013 at 5:39 PM, Conal Tuohy <span dir=3D"ltr">&lt;<a href=3D"ma=
ilto:conal.tuohy@versi.edu.au" target=3D"_blank">conal.tuohy@versi.edu.au</=
a>&gt;</span> wrote:<br>


</div><div class=3D"gmail_quote"><div><blockquote class=3D"gmail_quote" sty=
le=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">

 =20
   =20
 =20
  <div bgcolor=3D"#FFFFFF" text=3D"#000000"><div>
    <div>On 07/01/13 13:23, Matthew Morley
      wrote:<br>
    </div>
    <blockquote type=3D"cite">
     =20
      <br>
      For me the deficiency is not in the pointer, but patch format
      being generated.<br>
      <br>
      One approach is to push that *one* test, structure=C2=A0conformity,
      into the pointer syntax.=C2=A0Another is via the type operation.<br>
      <br>
      If a vague patch is generated, vague results are to be expected.<br>
    </blockquote></div>
    It seems to me, on the contrary, that the deficiency is in the
    pointer syntax, and I think it would be a mistake to try to work
    around that deficiency in JSON Patch. Because aren&#39;t there other
    things which one might do with JSON Pointer than use it with JSON
    Patch? There&#39;s been mention of having it registered as a URI
    fragment identifier syntax for JSON for example. JSON Pointers could
    then end up all over the place, outside of patches. IMHO JSON
    Pointer needs to be taken seriously as a technology in its own
    right.=C2=A0</div></blockquote></div><div><br>Couldn&#39;t agree more a=
bout it being taken seriously in its own right. :)<br><br>JSON Pointer for =
me exists outside of JSON Patch, always has and will do the way we think ab=
out structures. As it represents both a resolution path and an identity str=
ing (both ends of the path concept). I see value from the identity view, in=
 describing a location that is aware of being inside an array.</div>



<div><br>But JSON Pointer should not be changed just because of issues with=
 JSON Patch, especially when JSON Patch is attempting to address those issu=
es with other mechanisms within the specification. That is all I was trying=
 to express. The syntax change should be for other reasons, if it is going =
to be made.<br>



<br></div><div>My personal experience (for what its worth): In the past I&#=
39;ve tried a number of syntaxes like JSON Pointer. Mostly a.b.c.0 and even=
 a.b.c:0 at times to address the same issues suggested here. Though my expe=
riences pushed me towards a single syntax using a.b.c.0, and thus my suppor=
t for /a/b/c/0 over /a/b/c:0.<br>



<br>The system at first used the . or : syntax, combined with dynamic token=
s, being pointers themselves, to resolve other pointers. So it was not reas=
onable to know ahead of time if an end point was an array or an object. =C2=
=A0&quot;a.b.c.{d.e.f}&quot; could end up in an array or in an object, depe=
nding on the value at d.e.f at the time of resolution. Especially with many=
 layers of tokens to resolve, and changing data structures.<br>



<br>I found in practice, it didn&#39;t really matter, so the choice of . or=
 : was phased out. At the end of the day the two syntaxes point to mutually=
 exclusive points within the data, so that `meta data` about the structure =
was removed from the syntax we used. It didn&#39;t add value, even if it ad=
ded clarity at times. We also had functions at the end of paths, but that g=
oes beyond the JSON focus of the JSON Pointer goals, so those points are no=
t relevant here.<br>



</div></div><div><br>This discussion thread seems to be getting overly comp=
licated, but JSON Pointer changes should come from the JSON Pointer view po=
int and that specifications goals, not from short comings in JSON Patch.<sp=
an><font color=3D"#888888"><br>



<br></font></span></div><span><font color=3D"#888888">-- <br>Matthew P. C. =
Morley
</font></span><br></div></div><div class=3D"im">___________________________=
____________________<br>
apps-discuss mailing list<br>
<a href=3D"mailto:apps-discuss@ietf.org" target=3D"_blank">apps-discuss@iet=
f.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/apps-discuss" target=3D"_b=
lank">https://www.ietf.org/mailman/listinfo/apps-discuss</a><br>
<br></div></blockquote></div><br></div>
<br>_______________________________________________<br>
apps-discuss mailing list<br>
<a href=3D"mailto:apps-discuss@ietf.org">apps-discuss@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/apps-discuss" target=3D"_b=
lank">https://www.ietf.org/mailman/listinfo/apps-discuss</a><br>
<br></blockquote></div><br></div>

--f46d043d644bfff78a04d2c9f9f6--

From conal.tuohy@gmail.com  Mon Jan  7 14:39:18 2013
Return-Path: <conal.tuohy@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3A1B321F87D5; Mon,  7 Jan 2013 14:39:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.643
X-Spam-Level: 
X-Spam-Status: No, score=-2.643 tagged_above=-999 required=5 tests=[AWL=0.100,  BAYES_00=-2.599, FU_ENDS_2_WRDS=0.255, HTML_MESSAGE=0.001, J_CHICKENPOX_55=0.6, RCVD_IN_DNSWL_LOW=-1]
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 1gmmHx30ef3r; Mon,  7 Jan 2013 14:39:17 -0800 (PST)
Received: from mail-da0-f44.google.com (mail-da0-f44.google.com [209.85.210.44]) by ietfa.amsl.com (Postfix) with ESMTP id CDA3121F8835; Mon,  7 Jan 2013 14:39:16 -0800 (PST)
Received: by mail-da0-f44.google.com with SMTP id z20so8893152dae.3 for <multiple recipients>; Mon, 07 Jan 2013 14:39:16 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:sender:message-id:date:from:user-agent:mime-version:to :cc:subject:references:in-reply-to:content-type; bh=dTIXJFCLeu5k41HtqbS06tSljk19RUaV2XENEFAHFgc=; b=UGC7JnXQjXBHybUmI4RGLVhqts94KXyXeVt9IfEgjEHMxvoGgUauoccu+MyRE5Ct1E nGUPvmTOcid71YRIRwjcl2N7I0o0geAlinY9jE586Dd18ujN00HEvaCm8qx9zsfbXEjQ 7J1Onb7LbA/EhwdFy17d92vNktw9K/JiTxEf4egna6A45IZKeNeNWLeBlFKogGC9Imt2 kwlabR1GSKiNAzzZHTEwlY7V44MqY7mw1ga80DVdmIalu+OWrCOI7M7BxcVQoJ/fgs0S nECF0hORik1kbpcm5Kpvd1uIVb0b62uvTgROI1lMuyessl/1SwaDMIq1HTGQl61a8DKY RAiQ==
X-Received: by 10.68.213.202 with SMTP id nu10mr193946308pbc.91.1357598356307;  Mon, 07 Jan 2013 14:39:16 -0800 (PST)
Received: from [10.1.1.8] (d58-106-8-154.rdl801.qld.optusnet.com.au. [58.106.8.154]) by mx.google.com with ESMTPS id ai8sm38344177pbd.14.2013.01.07.14.39.11 (version=SSLv3 cipher=OTHER); Mon, 07 Jan 2013 14:39:14 -0800 (PST)
Sender: Conal Tuohy <conal.tuohy@gmail.com>
Message-ID: <50EB4E8B.30700@versi.edu.au>
Date: Tue, 08 Jan 2013 08:39:07 +1000
From: Conal Tuohy <conal.tuohy@versi.edu.au>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:16.0) Gecko/20121011 Thunderbird/16.0.1
MIME-Version: 1.0
To: Matthew Morley <matt@mpcm.com>
Subject: Re: [apps-discuss] Last Call: <draft-ietf-appsawg-json-pointer-07.txt> (JSON Pointer) to Proposed Standard
References: <20121211150057.28223.93310.idtracker@ietfa.amsl.com> <50cb04b9.86df440a.72fe.1e20SMTPIN_ADDED_BROKEN@mx.google.com> <CABP7RbeNsZ_rBWRjou=VG+hBhUKaOz+y1a0sSChwWiHte9znnQ@mail.gmail.com> <50cb5f3c.694c420a.38fb.39afSMTPIN_ADDED_BROKEN@mx.google.com> <CAChr6SxZRc3B_HCbw76kLe2dsRSr43r-gLpfMVnCUfJTrZdTLA@mail.gmail.com> <CABP7RbfA33huBFadMeXTTEt=MkjW8-d4DFH7+GLXGurnm9sSRw@mail.gmail.com> <CAOXDeqpPE4eNy_qJpDPdPHbCQakG9-hDcNZ3Sj9r4kWedByVzQ@mail.gmail.com> <CAChr6SwtS_=iS-k4mJm1vHjEvvGVzay5jDYeGheqsPZqO-89CQ@mail.gmail.com> <EABB8F51-C3B4-49F5-8672-5C2ABAC7043A@mnot.net> <CAChr6Sx7JdKM91EwJaSZ0Ra_F4FSqkuc3vzTY1LM=F_8sWho+Q@mail.gmail.com> <1357515310.6827.23.camel@polyglot> <CAChr6SyAq=7aQdZn54ihYK+0hDhL--2Oaq0RvehoNFbwKNNShA@mail.gmail.com> <CAChr6SxorKO20rGYi-e4YNF=HNGrwz8wPGKCFZQYWQwqsetjjg@mail.gmail.com> <CAOXDeqqE2mCLapwvjwQkme5VTpRCfmF0mFQcx02WW0-zi4i5=g@mail.gmail.com>
In-Reply-To: <CAOXDeqqE2mCLapwvjwQkme5VTpRCfmF0mFQcx02WW0-zi4i5=g@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------010408020306010502060903"
X-Mailman-Approved-At: Tue, 08 Jan 2013 09:24:11 -0800
Cc: IESG <iesg@ietf.org>, Mark Nottingham <mnot@mnot.net>, IETF Discussion <ietf@ietf.org>, IETF Apps Discuss <apps-discuss@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 07 Jan 2013 22:39:18 -0000

This is a multi-part message in MIME format.
--------------010408020306010502060903
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

On 07/01/13 13:23, Matthew Morley wrote:
>
> For me the deficiency is not in the pointer, but patch format being 
> generated.
>
> One approach is to push that *one* test, structure conformity, into 
> the pointer syntax. Another is via the type operation.
>
> If a vague patch is generated, vague results are to be expected.
It seems to me, on the contrary, that the deficiency is in the pointer 
syntax, and I think it would be a mistake to try to work around that 
deficiency in JSON Patch. Because aren't there other things which one 
might do with JSON Pointer than use it with JSON Patch? There's been 
mention of having it registered as a URI fragment identifier syntax for 
JSON for example. JSON Pointers could then end up all over the place, 
outside of patches. IMHO JSON Pointer needs to be taken seriously as a 
technology in its own right.

-- 
Conal Tuohy
HuNI <http://huni.net.au/> Technical Coordinator 
<http://apidictor.huni.net.au/trac/wiki/ConalSpace>
Victorian eResearch Strategic Initiative 
<http://versi.edu.au/about-us/versi-team#Con>
Skype: conal.tuohy
Twitter: @conal_tuohy <https://twitter.com/conal_tuohy>


--------------010408020306010502060903
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <div class="moz-cite-prefix">On 07/01/13 13:23, Matthew Morley
      wrote:<br>
    </div>
    <blockquote
cite="mid:CAOXDeqqE2mCLapwvjwQkme5VTpRCfmF0mFQcx02WW0-zi4i5=g@mail.gmail.com"
      type="cite">
      <meta http-equiv="Content-Type" content="text/html;
        charset=ISO-8859-1">
      <br>
      For me the deficiency is not in the pointer, but patch format
      being generated.<br>
      <br>
      One approach is to push that *one* test, structure&nbsp;conformity,
      into the pointer syntax.&nbsp;Another is via the type operation.<br>
      <br>
      If a vague patch is generated, vague results are to be expected.<br>
    </blockquote>
    It seems to me, on the contrary, that the deficiency is in the
    pointer syntax, and I think it would be a mistake to try to work
    around that deficiency in JSON Patch. Because aren't there other
    things which one might do with JSON Pointer than use it with JSON
    Patch? There's been mention of having it registered as a URI
    fragment identifier syntax for JSON for example. JSON Pointers could
    then end up all over the place, outside of patches. IMHO JSON
    Pointer needs to be taken seriously as a technology in its own
    right. <br>
    <br>
    <div class="moz-signature">-- <br>
      <address>
        Conal Tuohy<br>
        <a href="http://huni.net.au/">HuNI</a> <a
          href="http://apidictor.huni.net.au/trac/wiki/ConalSpace">Technical
          Coordinator</a><br>
        <a href="http://versi.edu.au/about-us/versi-team#Con">Victorian
          eResearch Strategic Initiative</a><br>
        Skype: conal.tuohy<br>
        Twitter: <a href="https://twitter.com/conal_tuohy">@conal_tuohy</a>
      </address>
    </div>
  </body>
</html>

--------------010408020306010502060903--

From gregimirsky@gmail.com  Mon Jan  7 12:48:01 2013
Return-Path: <gregimirsky@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0C50321F8971; Mon,  7 Jan 2013 12:48:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.932
X-Spam-Level: 
X-Spam-Status: No, score=-1.932 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, SARE_HTML_USL_OBFU=1.666]
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 lhMmHNGH4Oc9; Mon,  7 Jan 2013 12:48:00 -0800 (PST)
Received: from mail-ee0-f49.google.com (mail-ee0-f49.google.com [74.125.83.49]) by ietfa.amsl.com (Postfix) with ESMTP id BE3B321F8812; Mon,  7 Jan 2013 12:47:59 -0800 (PST)
Received: by mail-ee0-f49.google.com with SMTP id c4so9213377eek.36 for <multiple recipients>; Mon, 07 Jan 2013 12:47:58 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=vvRbjtVEMX1MHqj7TI89HtTB7YsFUGKvSDfxryDMlGY=; b=vcwQ6tr6ZsUh+ojdd31sT0c1ZGYSt58E4fO/XhzFoMbJJVevql9iFf2KhH7OT4ztnu uT/bfG5MSE6xIKIfp/ruTOL4MtjPCY4qSpOrBAVNKldldD424t5MykgsCnHQVztuxFd3 Pjdi2zl7lpotsZ00U3FFVIG55pcHUgvAN8qu514vG5sK8tY9MdgJJus1WeLKT3T3HBm3 qRcziq44jzNC/rWYbpOOMCD9brHclpOTJYfaGv4jum10XwUIhSDPdAzIjy4Pbf5XYHN0 s09fcXvYetEGstdCLyCu6CxiCml+mAAxk9LwN+gyeZusihvKYl/VI701knWVJoc3oEmR rZIA==
MIME-Version: 1.0
Received: by 10.14.207.6 with SMTP id m6mr167536057eeo.10.1357591678287; Mon, 07 Jan 2013 12:47:58 -0800 (PST)
Received: by 10.14.116.77 with HTTP; Mon, 7 Jan 2013 12:47:58 -0800 (PST)
In-Reply-To: <50E70396.6040806@gmail.com>
References: <CD0C3AE6.6E673%nabil.n.bitar@verizon.com> <50E70396.6040806@gmail.com>
Date: Mon, 7 Jan 2013 12:47:58 -0800
Message-ID: <CA+RyBmUP-AFv7g=R4e8D0zdbWy5qASx-AH65PZ-kOy3XYTFcqg@mail.gmail.com>
Subject: Re: [PWE3] Gen-ART review of draft-ietf-pwe3-mpls-eth-oam-iwk-06
From: Greg Mirsky <gregimirsky@gmail.com>
To: huubatwork@gmail.com
Content-Type: multipart/alternative; boundary=047d7b34372cbc004604d2b8f1db
X-Mailman-Approved-At: Tue, 08 Jan 2013 09:25:39 -0800
Cc: "Bitar, Nabil N" <nabil.n.bitar@verizon.com>, "ietf@ietf.org" <ietf@ietf.org>, "gen-art@ietf.org" <gen-art@ietf.org>, "dinmohan@hotmail.com" <dinmohan@hotmail.com>, "sajassi@cisco.com" <sajassi@cisco.com>, "pwe3@ietf.org" <pwe3@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 07 Jan 2013 20:48:01 -0000

--047d7b34372cbc004604d2b8f1db
Content-Type: text/plain; charset=ISO-8859-1

Dear Huub, Nabil, et al.,
IEEE 802.1ag interprets MEP and MIP as:

   - Maintenance association End Point
   - Maintenance domain Intermediate Point

Y.1731 interprets them as:


   - Maintenance entity group (MEG) End Point
   - MEG Intermediate Point

The reference to MD Level implies reference to IEEE 802.1ag, at least as
use of terminology, since Y.1731 doesn't have Maintenance Domain construct
and refers to the same value as MEG Level. I'd suggest to follow one model,
IEEE 802.1ag or Y.1731, terminology throughout the document so that there's
no need for re-mapping. I think that it is easier to follow Y.1731.


Regards,
Greg

On Fri, Jan 4, 2013 at 8:30 AM, Huub van Helvoort <huubatwork@gmail.com>wrote:

> All,
>
> Some nits that need to be fixed:
>
>
>
>  ME  Maintenance Entity
>>
>> MEG  Maintenance Entity Group
>>
>> MEP Maintenance End Point
>>
>
> MEP  "ME End Point" or "Maintenance Entity End Point"
>
>>
>> MIP  Maintenance End Point
>>
>
> MIP  "ME Intermediate Point" or "Maintenance Entity Intermediate Point"
>
>
>
>      3.2. Terminology
>>
>
>  - MEP:  Maintenance End Point is responsible for origination and
>> termination of OAM frames for a given MEG.
>>
>
> - MEP:  Maintenance Entity End Point is responsible for origination
>
>
>  - MIP: Maintenance Intermediate Point is located between peer MEPs and
>> can process OAM frames but does not initiate or terminate them.
>>
>
> - MIP: Maintenance Entity Intermediate Point is located between
>
>
> Regards, Huub.
> ______________________________**_________________
> pwe3 mailing list
> pwe3@ietf.org
> https://www.ietf.org/mailman/**listinfo/pwe3<https://www.ietf.org/mailman/listinfo/pwe3>
>

--047d7b34372cbc004604d2b8f1db
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Dear Huub, Nabil, et al.,<br>IEEE 802.1ag interprets MEP and MIP as:<br><ul=
><li>Maintenance association End Point</li><li>Maintenance domain Intermedi=
ate Point</li></ul>Y.1731 interprets them as:<br><br><ul><li>Maintenance en=
tity group (MEG) End Point</li>
<li>MEG Intermediate Point</li></ul><p>The reference to MD Level implies
 reference to IEEE 802.1ag, at least as use of terminology, since Y.1731
 doesn&#39;t have Maintenance Domain construct and refers to the same value=
=20
as MEG Level. I&#39;d suggest to follow one model, IEEE 802.1ag or Y.1731,=
=20
terminology throughout the document so that there&#39;s no need for=20
re-mapping. I think that it is easier to follow Y.1731.<br>
</p><p><br></p><p>Regards,</p>Greg<br><br><div class=3D"gmail_quote">On Fri=
, Jan 4, 2013 at 8:30 AM, Huub van Helvoort <span dir=3D"ltr">&lt;<a href=
=3D"mailto:huubatwork@gmail.com" target=3D"_blank">huubatwork@gmail.com</a>=
&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">All,<br>
<br>
Some nits that need to be fixed:<div class=3D"im"><br>
<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
ME =A0Maintenance Entity<br>
<br>
MEG =A0Maintenance Entity Group<br>
<br>
MEP Maintenance End Point<br>
</blockquote>
<br></div>
MEP =A0&quot;ME End Point&quot; or &quot;Maintenance Entity End Point&quot;=
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
<br>
MIP =A0Maintenance End Point<br>
</blockquote>
<br>
MIP =A0&quot;ME Intermediate Point&quot; or &quot;Maintenance Entity Interm=
ediate Point&quot;<br>
<br>
<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
=A0 =A0 3.2. Terminology<br>
</blockquote><div class=3D"im">
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
- MEP: =A0Maintenance End Point is responsible for origination and<br>
termination of OAM frames for a given MEG.<br>
</blockquote>
<br></div>
- MEP: =A0Maintenance Entity End Point is responsible for origination<div c=
lass=3D"im"><br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
- MIP: Maintenance Intermediate Point is located between peer MEPs and<br>
can process OAM frames but does not initiate or terminate them.<br>
</blockquote>
<br></div>
- MIP: Maintenance Entity Intermediate Point is located between<br>
<br>
<br>
Regards, Huub.<br>
______________________________<u></u>_________________<br>
pwe3 mailing list<br>
<a href=3D"mailto:pwe3@ietf.org" target=3D"_blank">pwe3@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/pwe3" target=3D"_blank">ht=
tps://www.ietf.org/mailman/<u></u>listinfo/pwe3</a><br>
</blockquote></div><br>

--047d7b34372cbc004604d2b8f1db--

From gregimirsky@gmail.com  Mon Jan  7 12:51:18 2013
Return-Path: <gregimirsky@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A345211E8099; Mon,  7 Jan 2013 12:51:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.765
X-Spam-Level: 
X-Spam-Status: No, score=-2.765 tagged_above=-999 required=5 tests=[AWL=0.833,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
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 Wp3zvuFavN3B; Mon,  7 Jan 2013 12:51:17 -0800 (PST)
Received: from mail-ee0-f41.google.com (mail-ee0-f41.google.com [74.125.83.41]) by ietfa.amsl.com (Postfix) with ESMTP id 9B6A911E8097; Mon,  7 Jan 2013 12:51:16 -0800 (PST)
Received: by mail-ee0-f41.google.com with SMTP id d41so9646748eek.28 for <multiple recipients>; Mon, 07 Jan 2013 12:51:15 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=t1Kx37aHBTx56sKNHCLDf7qx/qOe5xcr1QB0qQO4gHg=; b=DpyetlkPNU05Ps0vYSFQUzrxQQ1G/0CzZ3Fb5Ssrs+EfQ8okSJfTMcI11Y2GbZ1Srj UHzoGLebW3rp5Ctg7R4v97PDzrqdSSqxk3P5spwNjUIwDHZm2Rk6Bz650fs+8rMrpkKP oZONn9Wq6eJKXkT3fGcxnhpNolR1cCAlIyLr0/DoZrAU/ZDvc3G3BYUdQcXxpzw2jDH+ y8ehFF/fPuQ1G/iieEUtCGWFPv5ipBN8Tx9+4Oo1SOD1sJ8pYyITDtyYLcC50PVNdGc8 DnGjphYmg9K+vTv4ywJjLlzQ7NbBGZ3YGkUIiI82L+pHPKuHl7heLRhjYRUyilO3kaKo 5sMw==
MIME-Version: 1.0
Received: by 10.14.1.195 with SMTP id 43mr168346193eed.31.1357591875766; Mon, 07 Jan 2013 12:51:15 -0800 (PST)
Received: by 10.14.116.77 with HTTP; Mon, 7 Jan 2013 12:51:15 -0800 (PST)
In-Reply-To: <CD0C3AE6.6E673%nabil.n.bitar@verizon.com>
References: <CD08F2D5.6DC40%nabil.n.bitar@verizon.com> <CD0C3AE6.6E673%nabil.n.bitar@verizon.com>
Date: Mon, 7 Jan 2013 12:51:15 -0800
Message-ID: <CA+RyBmWWUQ+y7Mc1nG3+KndXCytfUkQqnNTg4ezpK2JcGyiCuQ@mail.gmail.com>
Subject: Re: [PWE3] Gen-ART review of draft-ietf-pwe3-mpls-eth-oam-iwk-06
From: Greg Mirsky <gregimirsky@gmail.com>
To: "Bitar, Nabil N" <nabil.n.bitar@verizon.com>
Content-Type: multipart/alternative; boundary=047d7b66f515814b0b04d2b8fde0
X-Mailman-Approved-At: Tue, 08 Jan 2013 09:25:41 -0800
Cc: "sajassi@cisco.com" <sajassi@cisco.com>, "ietf@ietf.org" <ietf@ietf.org>, "Black, David" <david.black@emc.com>, "dinmohan@hotmail.com" <dinmohan@hotmail.com>, "pwe3@ietf.org" <pwe3@ietf.org>, "gen-art@ietf.org" <gen-art@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 07 Jan 2013 20:51:18 -0000

--047d7b66f515814b0b04d2b8fde0
Content-Type: text/plain; charset=ISO-8859-1

Dear Nabil,
can we avoid different interpretation of the same abbreviation (RDI):

   RDI   Remote Defect Indication for Continuity Check Message

   RDI   Reverse Defect Indication

AFAIK, the latter form is the interpretation used by both IEEE 802.1ag and
Y.1731. How useful is the first form?

Regards,

Greg


On Fri, Jan 4, 2013 at 8:17 AM, Bitar, Nabil N <nabil.n.bitar@verizon.com>wrote:

> Hi Dave,
> Related to abbreviations comment below and to be clearer, I renamed the
> original terminology section to "Abbreviations and Terminology". I also
> created a subsection called "Abbreviations" ,and "Terminology" became the
> second subsection.  Here iis how the edits look
>
> 3. Abbreviations and Terminology****3.1. Abbreviations****
>
>         AIS   Alarm Indication Signal****
>
>    AC    Attachment Circuit****
>
>    BFD   Bidirectional Forwarding Detection****
>
>    CC    Continuity Check****
>
>    CCM   Continuity Check Message****
>
>    CE    Customer Equipment****
>
>    CV    Connectivity Verification****
>
>    E-LMI Ethernet Local Management Interface****
>
>    EVC   Ethernet Virtual Circuit****
>
>    LDP   Label Distribution Protocol****
>
>    LoS   Loss of Signal****
>
>    MA    Maintenance Association****
>
>    MD    Maintenance Domain****
>
>    ME    Maintenance Entity****
>
>    MEG   Maintenance Entity Group****
>
>    MEP   Maintenance End Point****
>
>    MIP   Maintenance End Point****
>
>    MPLS  Multiprotocol Label Switching****
>
>    MS-PW Multi-Segment Pseudowire****
>
>    NS    Native Service****
>
>    OAM   Operations, Administration, and Maintenance****
>
>    PE    Provider Edge****
>
>    PSN   Packet Switched Network****
>
>    PW    Pseudowire****
>
>    RDI   Remote Defect Indication for Continuity Check Message****
>
>    RDI   Reverse Defect Indication
>
>    S-PE  Switching Provider Edge****
>
>    TLV   Type Length Value****
>
>    T-PE  Terminating Provider Edge****
>
> ** **
> 3.2. Terminology****
>
> This document uses the following terms with corresponding definitions: ***
> *
>
> - MD Level:  Maintenance Domain (MD) Level which identifies a value in
> the range of 0-7 associated with Ethernet OAM frame. MD Level identifies
> the span of the Ethernet OAM frame.****
>
>  - MEP:    Maintenance End Point is responsible for origination and
> termination of OAM frames for a given MEG.****
>
>  - MIP:      Maintenance Intermediate Point is located between peer MEPs
> and can process OAM frames but does not initiate or terminate them.****
>
> Further, this document also uses the terminology and conventions used in
> [RFC6310].****
>
>
>
> Thanks,
>
> Nabil
>
> From: <Bitar>, Nabil N <nabil.n.bitar@one.verizon.com>
> Date: Wednesday, January 2, 2013 11:28 AM
> To: "Black, David" <david.black@emc.com>, "dinmohan@hotmail.com" <
> dinmohan@hotmail.com>, "Bitar, Nabil N" <nabil.n.bitar@one.verizon.com>,
> Sagessi <sajassi@cisco.com>, "gen-art@ietf.org" <gen-art@ietf.org>
> Cc: "pwe3@ietf.org" <pwe3@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
> Subject: Re: Gen-ART review of draft-ietf-pwe3-mpls-eth-oam-iwk-06
>
> Hi Dave,
> Sorry for a late reply addressing your comments. Please, see inline.
>
> Thanks,
> Nabil
>
> From: "Black, David" <david.black@emc.com>
> Date: Monday, August 20, 2012 8:57 PM
> To: "dinmohan@hotmail.com" <dinmohan@hotmail.com>, "Bitar, Nabil N" <
> nabil.n.bitar@one.verizon.com>, Sagessi <sajassi@cisco.com>, "
> gen-art@ietf.org" <gen-art@ietf.org>
> Cc: "Black, David" <david.black@emc.com>, "pwe3@ietf.org" <pwe3@ietf.org>,
> "ietf@ietf.org" <ietf@ietf.org>
> Subject: Gen-ART review of draft-ietf-pwe3-mpls-eth-oam-iwk-06
>
> I am the assigned Gen-ART reviewer for this draft. For background on
> Gen-ART, please
> see the FAQ at <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>
> Please resolve these comments along with any other Last Call comments you
> may receive.
>
> Document: draft-ietf-pwe3-mpls-eth-oam-iwk-06
> Reviewer: David L. Black
> Review Date: August 20, 2012
> IETF LC End Date: August 20, 2012
>
> Summary:
> This draft is basically ready for publication, but has nits that
> should be fixed before publication.
>
> <NB> Thanks.
>
>
>
> This draft covers defect behavior for Ethernet pseudowires,
>
> including defect state mapping and PE defect reporting behavior.
>
> The draft is generally in good shape.  I found a few minor nits.
>
>
>
> 1) The draft uses a lot of acronyms - while each acronym appears to
>
> be expanded on first use, an additional section near the start of the
>
> draft listing all of them would be helpful.
>
> <NB> Done.
>
>
>
> 2) There's a typo in the first paragraph of section 2:
>
>
>
>      covers the following Ethernet OAM (Opertaions, Administration and
>
>
>
> Opertaions -> Operations.
>
> <NB> Thanks. Done.
>
>
>
> 3) The following normative reference is incomplete - please add additional
>
> information that will enable a reader to locate the referenced document:
>
>
>
>      [MEF16] "Ethernet Local Management Interface", MEF16, January 2006.
>
> [MEF16] "Ethernet Local Management Interface", Metro Ethernet Forum
> Technical Specification MEF16, January 2006.
>
> <NB> changed it to :
>
>
>
> 4) idnits 2.12.13 did not like the pagination:
>
>
>
>   == The page length should not exceed 58 lines per page, but there was 22
>      longer pages, the longest (page 1) being 61 lines
> <NB> That will be fixed.
>
> Thanks,
> --David
> ----------------------------------------------------
> David L. Black, Distinguished Engineer
> EMC Corporation, 176 South St., Hopkinton, MA  01748
> +1 (508) 293-7953             FAX: +1 (508) 293-7786
> david.black@emc.com        Mobile: +1 (978) 394-7754
> ----------------------------------------------------
>
> _______________________________________________
> pwe3 mailing list
> pwe3@ietf.org
> https://www.ietf.org/mailman/listinfo/pwe3
>
>

--047d7b66f515814b0b04d2b8fde0
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Dear Nabil,<br>can we avoid different interpretation of the same abbreviati=
on (RDI):<br><p style=3D"font-family:Calibri,sans-serif"><span style=3D"fon=
t-family:&#39;Courier New&#39;"><span>=A0=A0 </span>RDI<span>=A0=A0
</span>Remote Defect Indication for Continuity Check Message</span></p><p><=
font face=3D"Courier New">=A0 =A0RDI =A0 Reverse Defect Indication <br></fo=
nt></p><p><font face=3D"Courier New">AFAIK, the latter form is the interpre=
tation used by both IEEE 802.1ag and Y.1731. How useful is the first form?<=
/font></p>
<p><font face=3D"Courier New">Regards,</font></p><p><font face=3D"Courier N=
ew">Greg<br></font></p><br><br><div class=3D"gmail_quote">On Fri, Jan 4, 20=
13 at 8:17 AM, Bitar, Nabil N <span dir=3D"ltr">&lt;<a href=3D"mailto:nabil=
.n.bitar@verizon.com" target=3D"_blank">nabil.n.bitar@verizon.com</a>&gt;</=
span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div style=3D"font-size:14px;font-family:Cal=
ibri,sans-serif;word-wrap:break-word"><div style=3D"font-family:Calibri,san=
s-serif">
Hi Dave,</div><div style=3D"font-family:Calibri,sans-serif">Related to abbr=
eviations comment below and to be clearer, I renamed the original terminolo=
gy section to &quot;Abbreviations and Terminology&quot;. I also created a s=
ubsection called &quot;Abbreviations&quot; ,and &quot;Terminology&quot; bec=
ame the second subsection. =A0Here iis how the edits look</div>
<div style=3D"font-family:Calibri,sans-serif"><br></div><div><h1 style=3D"f=
ont-family:Calibri,sans-serif;margin-right:18.95pt"><a name=3D"13c065c123e6=
3175__Toc218760256"></a><a name=3D"13c065c123e63175__Toc218759895"><span><s=
pan style=3D"font-size:10.5pt"><span>3. </span></span><span style=3D"font-s=
ize:10.5pt">Abbreviations and Terminology</span></span></a><span style=3D"f=
ont-size:10.5pt"><u></u><u></u></span></h1>
<h2 style=3D"font-family:Calibri,sans-serif"><a name=3D"13c065c123e63175__T=
oc218760257"></a><a name=3D"13c065c123e63175__Toc218759896"><span><span sty=
le=3D"font-size:10.5pt"><span>3.1. </span></span><span style=3D"font-size:1=
0.5pt">Abbreviations</span></span></a><span style=3D"font-size:10.5pt"><u><=
/u><u></u></span></h2>
<p style=3D"font-family:Calibri,sans-serif"><span>=A0 =A0 =A0 =A0=A0</span>=
<span style=3D"font-family:&#39;Courier New&#39;">AIS<span>=A0=A0
</span>Alarm Indication Signal<u></u><u></u></span></p><p style=3D"font-fam=
ily:Calibri,sans-serif"><span style=3D"font-family:&#39;Courier New&#39;"><=
span>=A0=A0 </span>AC<span>=A0=A0=A0
</span>Attachment Circuit<u></u><u></u></span></p><p style=3D"font-family:C=
alibri,sans-serif"><span style=3D"font-family:&#39;Courier New&#39;"><span>=
=A0=A0 </span>BFD<span>=A0=A0
</span>Bidirectional Forwarding Detection<u></u><u></u></span></p><p style=
=3D"font-family:Calibri,sans-serif"><span style=3D"font-family:&#39;Courier=
 New&#39;"><span>=A0=A0 </span>CC<span>=A0=A0=A0
</span>Continuity Check<u></u><u></u></span></p><p style=3D"font-family:Cal=
ibri,sans-serif"><span style=3D"font-family:&#39;Courier New&#39;"><span>=
=A0=A0 </span>CCM<span>=A0=A0
</span>Continuity Check Message<u></u><u></u></span></p><p style=3D"font-fa=
mily:Calibri,sans-serif"><span style=3D"font-family:&#39;Courier New&#39;">=
<span>=A0=A0 </span>CE<span>=A0=A0=A0
</span>Customer Equipment<u></u><u></u></span></p><p style=3D"font-family:C=
alibri,sans-serif"><span style=3D"font-family:&#39;Courier New&#39;"><span>=
=A0=A0 </span>CV<span>=A0=A0=A0
</span>Connectivity Verification<u></u><u></u></span></p><p style=3D"font-f=
amily:Calibri,sans-serif"><span style=3D"font-family:&#39;Courier New&#39;"=
><span>=A0=A0 </span>E-LMI Ethernet Local Management Interface<u></u><u></u=
></span></p>
<p style=3D"font-family:Calibri,sans-serif"><span style=3D"font-family:&#39=
;Courier New&#39;"><span>=A0=A0 </span>EVC<span>=A0=A0
</span>Ethernet Virtual Circuit<u></u><u></u></span></p><p style=3D"font-fa=
mily:Calibri,sans-serif"><span style=3D"font-family:&#39;Courier New&#39;">=
<span>=A0=A0 </span>LDP<span>=A0=A0
</span>Label Distribution Protocol<u></u><u></u></span></p><p style=3D"font=
-family:Calibri,sans-serif"><span style=3D"font-family:&#39;Courier New&#39=
;"><span>=A0=A0 </span>LoS<span>=A0=A0
</span>Loss of Signal<u></u><u></u></span></p><p style=3D"font-family:Calib=
ri,sans-serif"><span style=3D"font-family:&#39;Courier New&#39;"><span>=A0=
=A0 </span>MA<span> </span><span>=A0=A0 </span>Maintenance Association<u></=
u><u></u></span></p>
<p style=3D"font-family:Calibri,sans-serif"><span style=3D"font-family:&#39=
;Courier New&#39;"><span>=A0=A0 </span>MD<span>=A0=A0=A0
</span>Maintenance Domain<u></u><u></u></span></p><p style=3D"font-family:C=
alibri,sans-serif"><span style=3D"font-family:&#39;Courier New&#39;"><span>=
=A0=A0 </span>ME<span>=A0=A0=A0
</span>Maintenance Entity<u></u><u></u></span></p><p style=3D"font-family:C=
alibri,sans-serif"><span style=3D"font-family:&#39;Courier New&#39;"><span>=
=A0=A0 </span>MEG<span>=A0=A0
</span>Maintenance Entity Group<u></u><u></u></span></p><p style=3D"font-fa=
mily:Calibri,sans-serif"><span style=3D"font-family:&#39;Courier New&#39;">=
<span>=A0=A0 </span>MEP<span>=A0=A0
</span>Maintenance End Point<u></u><u></u></span></p><p style=3D"font-famil=
y:Calibri,sans-serif"><span style=3D"font-family:&#39;Courier New&#39;"><sp=
an>=A0=A0 </span>MIP<span>=A0=A0
</span>Maintenance End Point<u></u><u></u></span></p><p style=3D"font-famil=
y:Calibri,sans-serif"><span style=3D"font-family:&#39;Courier New&#39;"><sp=
an>=A0=A0 </span>MPLS<span>=A0
</span>Multiprotocol Label Switching<u></u><u></u></span></p><p style=3D"fo=
nt-family:Calibri,sans-serif"><span style=3D"font-family:&#39;Courier New&#=
39;"><span>=A0=A0 </span>MS-PW Multi-Segment Pseudowire<u></u><u></u></span=
></p>
<p style=3D"font-family:Calibri,sans-serif"><span style=3D"font-family:&#39=
;Courier New&#39;"><span>=A0=A0 </span>NS<span>=A0=A0=A0
</span>Native Service<u></u><u></u></span></p><p style=3D"font-family:Calib=
ri,sans-serif"><span style=3D"font-family:&#39;Courier New&#39;"><span>=A0=
=A0 </span>OAM<span>=A0=A0
</span>Operations, Administration, and Maintenance<u></u><u></u></span></p>=
<p style=3D"font-family:Calibri,sans-serif"><span style=3D"font-family:&#39=
;Courier New&#39;"><span>=A0=A0 </span>PE<span>=A0=A0=A0
</span>Provider Edge<u></u><u></u></span></p><p style=3D"font-family:Calibr=
i,sans-serif"><span style=3D"font-family:&#39;Courier New&#39;"><span>=A0=
=A0 </span>PSN<span>=A0=A0
</span>Packet Switched Network<u></u><u></u></span></p><p style=3D"font-fam=
ily:Calibri,sans-serif"><span style=3D"font-family:&#39;Courier New&#39;"><=
span>=A0=A0 </span>PW<span>=A0=A0=A0
</span>Pseudowire<u></u><u></u></span></p><p style=3D"font-family:Calibri,s=
ans-serif"><span style=3D"font-family:&#39;Courier New&#39;"><span>=A0=A0 <=
/span>RDI<span>=A0=A0
</span>Remote Defect Indication for Continuity Check Message<u></u><u></u><=
/span></p><p><font face=3D"Courier New">=A0 =A0RDI =A0 Reverse Defect Indic=
ation=A0</font></p><p style=3D"font-family:Calibri,sans-serif"><span style=
=3D"font-family:&#39;Courier New&#39;"><span>=A0=A0 </span>S-PE<span>=A0
</span>Switching Provider Edge<u></u><u></u></span></p><p style=3D"font-fam=
ily:Calibri,sans-serif"><span style=3D"font-family:&#39;Courier New&#39;"><=
span>=A0=A0 </span>TLV<span>=A0=A0
</span>Type Length Value<u></u><u></u></span></p><p style=3D"font-family:Ca=
libri,sans-serif"><span style=3D"font-family:&#39;Courier New&#39;"><span>=
=A0=A0 </span>T-PE<span>=A0
</span>Terminating Provider Edge<u></u><u></u></span></p><p class=3D"MsoNor=
mal" style=3D"font-family:Calibri,sans-serif"><span style=3D"font-size:10.5=
pt"><u></u>=A0<u></u></span></p><h2 style=3D"font-family:Calibri,sans-serif=
"><a name=3D"13c065c123e63175__Toc218760258"></a><a name=3D"13c065c123e6317=
5__Toc218759897"><span><span style=3D"font-size:10.5pt"><span>3.2. </span><=
/span><span style=3D"font-size:10.5pt">Terminology</span></span></a><span s=
tyle=3D"font-size:10.5pt"><u></u><u></u></span></h2>
<p class=3D"MsoNormal" style=3D"font-family:Calibri,sans-serif;margin-left:=
0in"><span style=3D"font-size:10.5pt">This
document uses the following terms with corresponding definitions: <u></u><u=
></u></span></p><p class=3D"MsoNormal" style=3D"font-family:Calibri,sans-se=
rif"><span style=3D"font-size:10.5pt">- MD Level:<span>=A0 </span>Maintenan=
ce Domain (MD) Level which
identifies a value in the range of 0-7 associated with Ethernet OAM frame. =
MD
Level identifies the span of the Ethernet OAM frame.<u></u><u></u></span></=
p><p class=3D"MsoNormal" style=3D"font-family:Calibri,sans-serif;text-align=
:justify"><span style=3D"font-size:10.5pt"><span>=A0</span>- MEP:<span>=A0 =
</span><span>=A0=A0</span>Maintenance End Point is responsible for
origination and termination of OAM frames for a given MEG.<u></u><u></u></s=
pan></p><p class=3D"MsoNormal" style=3D"font-family:Calibri,sans-serif"><sp=
an style=3D"font-size:10.5pt"><span>=A0</span>- MIP: <span>=A0=A0=A0=A0=A0<=
/span>Maintenance Intermediate Point is located
between peer MEPs and can process OAM frames but does not initiate or termi=
nate
them.<u></u><u></u></span></p><p class=3D"MsoNormal" style=3D"font-family:C=
alibri,sans-serif;margin-left:0in"><span style=3D"font-size:10.5pt">Further=
,
this document also uses the terminology and conventions used in [RFC6310].<=
/span><u></u><u></u></p><p class=3D"MsoNormal" style=3D"font-family:Calibri=
,sans-serif;margin-left:0in"><span style=3D"font-size:10.5pt"><br></span></=
p>
<p class=3D"MsoNormal" style=3D"font-family:Calibri,sans-serif;margin-left:=
0in"><span style=3D"font-size:10.5pt"><br></span></p><p class=3D"MsoNormal"=
 style=3D"font-family:Calibri,sans-serif;margin-left:0in"><span style=3D"fo=
nt-size:10.5pt">Thanks,</span></p>
<p class=3D"MsoNormal" style=3D"font-family:Calibri,sans-serif;margin-left:=
0in"><span style=3D"font-size:10.5pt">Nabil</span></p></div><div style=3D"f=
ont-family:Calibri,sans-serif"><br></div><span style=3D"font-family:Calibri=
,sans-serif"><div style=3D"border-right:medium none;padding-right:0in;paddi=
ng-left:0in;padding-top:3pt;text-align:left;font-size:11pt;border-bottom:me=
dium none;font-family:Calibri;border-top:#b5c4df 1pt solid;padding-bottom:0=
in;border-left:medium none">
<span style=3D"font-weight:bold">From: </span> &lt;Bitar&gt;, Nabil N &lt;<=
a href=3D"mailto:nabil.n.bitar@one.verizon.com" target=3D"_blank">nabil.n.b=
itar@one.verizon.com</a>&gt;<br><span style=3D"font-weight:bold">Date: </sp=
an> Wednesday, January 2, 2013 11:28 AM<br>
<span style=3D"font-weight:bold">To: </span> &quot;Black, David&quot; &lt;<=
a href=3D"mailto:david.black@emc.com" target=3D"_blank">david.black@emc.com=
</a>&gt;, &quot;<a href=3D"mailto:dinmohan@hotmail.com" target=3D"_blank">d=
inmohan@hotmail.com</a>&quot; &lt;<a href=3D"mailto:dinmohan@hotmail.com" t=
arget=3D"_blank">dinmohan@hotmail.com</a>&gt;, &quot;Bitar, Nabil N&quot; &=
lt;<a href=3D"mailto:nabil.n.bitar@one.verizon.com" target=3D"_blank">nabil=
.n.bitar@one.verizon.com</a>&gt;, Sagessi &lt;<a href=3D"mailto:sajassi@cis=
co.com" target=3D"_blank">sajassi@cisco.com</a>&gt;, &quot;<a href=3D"mailt=
o:gen-art@ietf.org" target=3D"_blank">gen-art@ietf.org</a>&quot; &lt;<a hre=
f=3D"mailto:gen-art@ietf.org" target=3D"_blank">gen-art@ietf.org</a>&gt;<br=
>
<span style=3D"font-weight:bold">Cc: </span> &quot;<a href=3D"mailto:pwe3@i=
etf.org" target=3D"_blank">pwe3@ietf.org</a>&quot; &lt;<a href=3D"mailto:pw=
e3@ietf.org" target=3D"_blank">pwe3@ietf.org</a>&gt;, &quot;<a href=3D"mail=
to:ietf@ietf.org" target=3D"_blank">ietf@ietf.org</a>&quot; &lt;<a href=3D"=
mailto:ietf@ietf.org" target=3D"_blank">ietf@ietf.org</a>&gt;<br>
<span style=3D"font-weight:bold">Subject: </span> Re: Gen-ART review of dra=
ft-ietf-pwe3-mpls-eth-oam-iwk-06<br></div><div><br></div><div><div style=3D=
"font-size:14px;font-family:Calibri,sans-serif;word-wrap:break-word"><div><=
font face=3D"Calibri,sans-serif">Hi Dave,</font></div>
<div><font face=3D"Calibri,sans-serif">Sorry for a late reply addressing yo=
ur comments. Please, see inline.</font></div><div><font face=3D"Calibri,san=
s-serif"><br></font></div><div><font face=3D"Calibri,sans-serif">Thanks,</f=
ont></div>
<div><font face=3D"Calibri,sans-serif">Nabil</font></div><div style=3D"font=
-size:14px;font-family:Calibri,sans-serif"><br></div><span style=3D"font-si=
ze:14px;font-family:Calibri,sans-serif"><div style=3D"border-right:medium n=
one;padding-right:0in;padding-left:0in;padding-top:3pt;text-align:left;font=
-size:11pt;border-bottom:medium none;font-family:Calibri;border-top:#b5c4df=
 1pt solid;padding-bottom:0in;border-left:medium none">
<span style=3D"font-weight:bold">From: </span>&quot;Black, David&quot; &lt;=
<a href=3D"mailto:david.black@emc.com" target=3D"_blank">david.black@emc.co=
m</a>&gt;<br><span style=3D"font-weight:bold">Date: </span>Monday, August 2=
0, 2012 8:57 PM<br>
<span style=3D"font-weight:bold">To: </span>&quot;<a href=3D"mailto:dinmoha=
n@hotmail.com" target=3D"_blank">dinmohan@hotmail.com</a>&quot; &lt;<a href=
=3D"mailto:dinmohan@hotmail.com" target=3D"_blank">dinmohan@hotmail.com</a>=
&gt;, &quot;Bitar, Nabil N&quot; &lt;<a href=3D"mailto:nabil.n.bitar@one.ve=
rizon.com" target=3D"_blank">nabil.n.bitar@one.verizon.com</a>&gt;,
 Sagessi &lt;<a href=3D"mailto:sajassi@cisco.com" target=3D"_blank">sajassi=
@cisco.com</a>&gt;, &quot;<a href=3D"mailto:gen-art@ietf.org" target=3D"_bl=
ank">gen-art@ietf.org</a>&quot; &lt;<a href=3D"mailto:gen-art@ietf.org" tar=
get=3D"_blank">gen-art@ietf.org</a>&gt;<br>
<span style=3D"font-weight:bold">Cc: </span>&quot;Black, David&quot; &lt;<a=
 href=3D"mailto:david.black@emc.com" target=3D"_blank">david.black@emc.com<=
/a>&gt;, &quot;<a href=3D"mailto:pwe3@ietf.org" target=3D"_blank">pwe3@ietf=
.org</a>&quot; &lt;<a href=3D"mailto:pwe3@ietf.org" target=3D"_blank">pwe3@=
ietf.org</a>&gt;, &quot;<a href=3D"mailto:ietf@ietf.org" target=3D"_blank">=
ietf@ietf.org</a>&quot;
 &lt;<a href=3D"mailto:ietf@ietf.org" target=3D"_blank">ietf@ietf.org</a>&g=
t;<br><span style=3D"font-weight:bold">Subject: </span>Gen-ART review of dr=
aft-ietf-pwe3-mpls-eth-oam-iwk-06<br></div><div><br></div><div dir=3D"ltr">=
<div>
<div dir=3D"ltr"><font color=3D"#000000" face=3D"Courier New">I am the assi=
gned Gen-ART reviewer for this draft. For background on Gen-ART, please<br>
see the FAQ at &lt;<a href=3D"http://wiki.tools.ietf.org/area/gen/trac/wiki=
/GenArtfaq" target=3D"_blank">http://wiki.tools.ietf.org/area/gen/trac/wiki=
/GenArtfaq</a>&gt;.<br><br>
Please resolve these comments along with any other Last Call comments you m=
ay receive.<br><br>
Document: <span lang=3D"EN">draft-ietf-pwe3-mpls-eth-oam-iwk-06</span></fon=
t></div><div dir=3D"ltr"><font color=3D"#000000" face=3D"Courier New"><span=
 lang=3D"EN"></span>Reviewer: David L. Black<br>
Review Date: August 20, 2012<br>
IETF LC End Date: August 20, 2012<br><br>
Summary:<br>
This draft is basically ready for publication, but has nits that<br>
should be fixed before publication.</font></div></div></div></span><div><br=
></div><div>&lt;NB&gt; Thanks.</div><span style=3D"font-size:14px;font-fami=
ly:Calibri,sans-serif"><div dir=3D"ltr"><div><p><font color=3D"#000000" fac=
e=3D"Courier New"><font face=3D"courier new"></font></font>=A0</p>
<p><font color=3D"#000000" face=3D"Courier New"><font face=3D"courier new">=
This draft covers defect behavior for Ethernet pseudowires<a></a>,</font></=
font></p><p><font color=3D"#000000" face=3D"Courier New"><font face=3D"cour=
ier new">including defect state mapping and PE defect reporting behavior.</=
font></font></p>
<p><font color=3D"#000000" face=3D"Courier New"><font face=3D"courier new">=
The draft is generally in good shape.=A0 I found a few minor nits.</font></=
font></p><p><font face=3D"courier new"></font>=A0</p><p><font face=3D"couri=
er new">1) The draft uses a lot of acronyms - while each acronym appears to=
</font></p>
<p><font face=3D"Courier New">b<font face=3D"courier new">e expanded on fir=
st use, an additional section near the start of the</font></font></p><p><fo=
nt face=3D"Courier New"><font face=3D"courier new"><font><font face=3D"cour=
ier new">draft listing</font> all of them
</font></font></font><font face=3D"courier new">would be helpful.</font></p=
></div></div></span><div><br></div><div>&lt;NB&gt; Done.</div><span style=
=3D"font-size:14px;font-family:Calibri,sans-serif"><div dir=3D"ltr"><div><p=
><font face=3D"courier new"></font>=A0</p>
<p><font face=3D"courier new">2) There&#39;s=A0a typo in the first paragrap=
h of section 2:</font></p><p><font face=3D"courier new"></font>=A0</p><font=
 color=3D"#000000"><div dir=3D"ltr"><font><span lang=3D"EN"><p><font face=
=3D"Courier New">=A0=A0=A0 =A0covers the following Ethernet OAM (Opertaions=
<a></a>, Administration and
</font></p><p><font face=3D"courier new"></font>=A0</p><p><font face=3D"cou=
rier new"><a></a><font face=3D"courier new">Opertaions</font>=A0-&gt; Opera=
tions.</font></p></span></font></div></font></div></div></span><div><br></d=
iv><div>
&lt;NB&gt; Thanks. Done.</div><span style=3D"font-size:14px;font-family:Cal=
ibri,sans-serif"><div dir=3D"ltr"><div><font color=3D"#000000"><div dir=3D"=
ltr"><font><span lang=3D"EN"><p><font face=3D"courier new"></font>=A0</p><p=
><font face=3D"courier new">3) The following normative reference is incompl=
ete - please add additional</font></p>
<p><font face=3D"courier new">information that will enable a reader to loca=
te the referenced document:</font></p><p><font face=3D"courier new"></font>=
=A0</p><font face=3D"courier new"><span lang=3D"EN"><p>=A0=A0=A0 =A0[MEF16]=
 &quot;Ethernet Local Management Interface&quot;, MEF16, January 2006.</p>
</span></font></span></font></div></font></div></div></span><div><br></div>=
<span style=3D"font-family:Calibri,sans-serif"><div dir=3D"ltr"><div><font =
color=3D"#000000"><div dir=3D"ltr"><span style=3D"line-height:16px;font-fam=
ily:&#39;Courier New&#39;">[MEF16] &quot;Ethernet Local Management Interfac=
e&quot;, Metro Ethernet Forum Technical Specification MEF16, January 2006.<=
/span><font><span lang=3D"EN"><font face=3D"courier new"><span lang=3D"EN">=
<p style=3D"font-size:14px">
<font face=3D"courier new"></font>&lt;NB&gt; changed it to :=A0</p><p>=A0</=
p><p style=3D"font-size:14px"><font face=3D"courier new"><font face=3D"cour=
ier new">4)=A0idnits<a></a> 2.12.13 did not like the pagination:</font></fo=
nt></p><p style=3D"font-size:14px">
=A0</p></span></font></span></font><p style=3D"font-size:14px"><font><font =
face=3D"courier new"><font face=3D"courier new">=A0 =3D=3D The page length =
should not exceed 58 lines per page, but there was 22<br>
=A0=A0=A0=A0 longer pages, the longest (page 1) being 61 lines</font></font=
></font></p></div></font></div></div></span><div>&lt;NB&gt; That will be fi=
xed.</div><span style=3D"font-family:Calibri,sans-serif"><div dir=3D"ltr"><=
div><div dir=3D"ltr" style=3D"font-size:14px">
<font face=3D"Courier New"><font color=3D"#000000">=A0</font></font></div><=
div style=3D"font-size:14px"><font face=3D"Courier New">Thanks,</font></div=
><div style=3D"font-size:14px"><font face=3D"courier new">--David</font></d=
iv><div style=3D"font-size:14px">
<font face=3D"Courier New"><font>------------------------------------------=
----------<br>
David L. Black, Distinguished Engineer<br>
EMC Corporation, 176 South St., Hopkinton, MA=A0 01748<br>
<a href=3D"tel:%2B1%20%28508%29%20293-7953" value=3D"+15082937953" target=
=3D"_blank">+1 (508) 293-7953</a>=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 FAX: =
<a href=3D"tel:%2B1%20%28508%29%20293-7786" value=3D"+15082937786" target=
=3D"_blank">+1 (508) 293-7786</a><br>
</font><font><a href=3D"mailto:david.black@emc.com" target=3D"_blank"><font=
>david.black@emc.com</font></a><a></a></font><font>=A0=A0=A0=A0=A0=A0=A0 Mo=
bile: <a href=3D"tel:%2B1%20%28978%29%20394-7754" value=3D"+19783947754" ta=
rget=3D"_blank">+1 (978) 394-7754</a><br>

----------------------------------------------------<br></font></font></div=
></div></div></span></div></div></span></div>
<br>_______________________________________________<br>
pwe3 mailing list<br>
<a href=3D"mailto:pwe3@ietf.org">pwe3@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/pwe3" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/pwe3</a><br>
<br></blockquote></div><br>

--047d7b66f515814b0b04d2b8fde0--

From neil.2.harrison@bt.com  Mon Jan  7 14:25:45 2013
Return-Path: <neil.2.harrison@bt.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D3E1721F8910 for <ietf@ietfa.amsl.com>; Mon,  7 Jan 2013 14:25:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.598
X-Spam-Level: 
X-Spam-Status: No, score=-3.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
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 VwtwyitBsoIE for <ietf@ietfa.amsl.com>; Mon,  7 Jan 2013 14:25:41 -0800 (PST)
Received: from smtpe1.intersmtp.com (smtp61.intersmtp.com [62.239.224.234]) by ietfa.amsl.com (Postfix) with ESMTP id C6CA321F8953 for <ietf@ietf.org>; Mon,  7 Jan 2013 14:25:40 -0800 (PST)
Received: from EVMHT62-UKRD.domain1.systemhost.net (10.36.3.128) by RDW083A005ED61.smtp-e1.hygiene.service (10.187.98.10) with Microsoft SMTP Server (TLS) id 8.3.279.1; Mon, 7 Jan 2013 22:25:38 +0000
Received: from EMV62-UKRD.domain1.systemhost.net ([169.254.1.167]) by EVMHT62-UKRD.domain1.systemhost.net ([10.36.3.128]) with mapi; Mon, 7 Jan 2013 22:25:38 +0000
From: <neil.2.harrison@bt.com>
To: <gregimirsky@gmail.com>, <nabil.n.bitar@verizon.com>
Date: Mon, 7 Jan 2013 22:25:34 +0000
Subject: RE: [PWE3] Gen-ART review of draft-ietf-pwe3-mpls-eth-oam-iwk-06
Thread-Topic: [PWE3] Gen-ART review of draft-ietf-pwe3-mpls-eth-oam-iwk-06
Thread-Index: Ac3tGMEmRPScrTfuTiuRn0aln+F/ZgACrwnA
Message-ID: <6D3D47CB84BDE349BC23BF1C94E316E44283E790C0@EMV62-UKRD.domain1.systemhost.net>
References: <CD08F2D5.6DC40%nabil.n.bitar@verizon.com> <CD0C3AE6.6E673%nabil.n.bitar@verizon.com> <CA+RyBmWWUQ+y7Mc1nG3+KndXCytfUkQqnNTg4ezpK2JcGyiCuQ@mail.gmail.com>
In-Reply-To: <CA+RyBmWWUQ+y7Mc1nG3+KndXCytfUkQqnNTg4ezpK2JcGyiCuQ@mail.gmail.com>
Accept-Language: en-US, en-GB
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, en-GB
Content-Type: multipart/alternative; boundary="_000_6D3D47CB84BDE349BC23BF1C94E316E44283E790C0EMV62UKRDdoma_"
MIME-Version: 1.0
X-Mailman-Approved-At: Tue, 08 Jan 2013 09:25:41 -0800
Cc: sajassi@cisco.com, dinmohan@hotmail.com, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 07 Jan 2013 22:25:46 -0000

--_000_6D3D47CB84BDE349BC23BF1C94E316E44283E790C0EMV62UKRDdoma_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi Greg....

CC per se has little inherent value....but that is historical.  CV does hav=
e proper value.  CV and RDI however should NOT be mutually dependent messag=
es as the latter cannot be meaningfully associated with (a CV flow on) p2mp=
 connections.

And BTW AIS (or FDI) has no value whatsoever in any pkt networks....obvious=
 for cl-ps but this is just as true for co-ps.  It has limited value in the=
 co-cs mode with PVCs, where its origins stem from the fact that (i) the fi=
xed time resource (time-slot) allocated by a server to a client link-connec=
tion has to be filled with something and (ii) that 'something' became binar=
y all 1s simply because that was what the early TTL silicon technology in t=
he PDH produced on failure, ie + 5V.  But when one considers co-cs SVCs the=
n AIS even here starts to look very silly....the underlying key point being=
 that *unless* there is a permanently fixed binding between a server and it=
s clients (even after server failure, ie client does not attempt to re-rout=
e in *its* layer network) then where does the server know who to send the A=
IS (FDI) to?  AIS (FDI) should be strongly deprecated in all future work on=
 OAM.  It took me a little time to fully realise this point.

regards, Neil

From: pwe3-bounces@ietf.org [mailto:pwe3-bounces@ietf.org] On Behalf Of Gre=
g Mirsky
Sent: 07 January 2013 20:51
To: Bitar, Nabil N
Cc: sajassi@cisco.com; ietf@ietf.org; dinmohan@hotmail.com; pwe3@ietf.org; =
gen-art@ietf.org
Subject: Re: [PWE3] Gen-ART review of draft-ietf-pwe3-mpls-eth-oam-iwk-06

Dear Nabil,
can we avoid different interpretation of the same abbreviation (RDI):

   RDI   Remote Defect Indication for Continuity Check Message

   RDI   Reverse Defect Indication

AFAIK, the latter form is the interpretation used by both IEEE 802.1ag and =
Y.1731. How useful is the first form?

Regards,

Greg

On Fri, Jan 4, 2013 at 8:17 AM, Bitar, Nabil N <nabil.n.bitar@verizon.com<m=
ailto:nabil.n.bitar@verizon.com>> wrote:
Hi Dave,
Related to abbreviations comment below and to be clearer, I renamed the ori=
ginal terminology section to "Abbreviations and Terminology". I also create=
d a subsection called "Abbreviations" ,and "Terminology" became the second =
subsection.  Here iis how the edits look

3. Abbreviations and Terminology
3.1. Abbreviations

        AIS   Alarm Indication Signal

   AC    Attachment Circuit

   BFD   Bidirectional Forwarding Detection

   CC    Continuity Check

   CCM   Continuity Check Message

   CE    Customer Equipment

   CV    Connectivity Verification

   E-LMI Ethernet Local Management Interface

   EVC   Ethernet Virtual Circuit

   LDP   Label Distribution Protocol

   LoS   Loss of Signal

   MA    Maintenance Association

   MD    Maintenance Domain

   ME    Maintenance Entity

   MEG   Maintenance Entity Group

   MEP   Maintenance End Point

   MIP   Maintenance End Point

   MPLS  Multiprotocol Label Switching

   MS-PW Multi-Segment Pseudowire

   NS    Native Service

   OAM   Operations, Administration, and Maintenance

   PE    Provider Edge

   PSN   Packet Switched Network

   PW    Pseudowire

   RDI   Remote Defect Indication for Continuity Check Message

   RDI   Reverse Defect Indication

   S-PE  Switching Provider Edge

   TLV   Type Length Value

   T-PE  Terminating Provider Edge

3.2. Terminology
This document uses the following terms with corresponding definitions:
- MD Level:  Maintenance Domain (MD) Level which identifies a value in the =
range of 0-7 associated with Ethernet OAM frame. MD Level identifies the sp=
an of the Ethernet OAM frame.
 - MEP:    Maintenance End Point is responsible for origination and termina=
tion of OAM frames for a given MEG.
 - MIP:      Maintenance Intermediate Point is located between peer MEPs an=
d can process OAM frames but does not initiate or terminate them.
Further, this document also uses the terminology and conventions used in [R=
FC6310].


Thanks,
Nabil

From: <Bitar>, Nabil N <nabil.n.bitar@one.verizon.com<mailto:nabil.n.bitar@=
one.verizon.com>>
Date: Wednesday, January 2, 2013 11:28 AM
To: "Black, David" <david.black@emc.com<mailto:david.black@emc.com>>, "dinm=
ohan@hotmail.com<mailto:dinmohan@hotmail.com>" <dinmohan@hotmail.com<mailto=
:dinmohan@hotmail.com>>, "Bitar, Nabil N" <nabil.n.bitar@one.verizon.com<ma=
ilto:nabil.n.bitar@one.verizon.com>>, Sagessi <sajassi@cisco.com<mailto:saj=
assi@cisco.com>>, "gen-art@ietf.org<mailto:gen-art@ietf.org>" <gen-art@ietf=
.org<mailto:gen-art@ietf.org>>
Cc: "pwe3@ietf.org<mailto:pwe3@ietf.org>" <pwe3@ietf.org<mailto:pwe3@ietf.o=
rg>>, "ietf@ietf.org<mailto:ietf@ietf.org>" <ietf@ietf.org<mailto:ietf@ietf=
.org>>
Subject: Re: Gen-ART review of draft-ietf-pwe3-mpls-eth-oam-iwk-06

Hi Dave,
Sorry for a late reply addressing your comments. Please, see inline.

Thanks,
Nabil

From: "Black, David" <david.black@emc.com<mailto:david.black@emc.com>>
Date: Monday, August 20, 2012 8:57 PM
To: "dinmohan@hotmail.com<mailto:dinmohan@hotmail.com>" <dinmohan@hotmail.c=
om<mailto:dinmohan@hotmail.com>>, "Bitar, Nabil N" <nabil.n.bitar@one.veriz=
on.com<mailto:nabil.n.bitar@one.verizon.com>>, Sagessi <sajassi@cisco.com<m=
ailto:sajassi@cisco.com>>, "gen-art@ietf.org<mailto:gen-art@ietf.org>" <gen=
-art@ietf.org<mailto:gen-art@ietf.org>>
Cc: "Black, David" <david.black@emc.com<mailto:david.black@emc.com>>, "pwe3=
@ietf.org<mailto:pwe3@ietf.org>" <pwe3@ietf.org<mailto:pwe3@ietf.org>>, "ie=
tf@ietf.org<mailto:ietf@ietf.org>" <ietf@ietf.org<mailto:ietf@ietf.org>>
Subject: Gen-ART review of draft-ietf-pwe3-mpls-eth-oam-iwk-06

I am the assigned Gen-ART reviewer for this draft. For background on Gen-AR=
T, please
see the FAQ at <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

Please resolve these comments along with any other Last Call comments you m=
ay receive.

Document: draft-ietf-pwe3-mpls-eth-oam-iwk-06
Reviewer: David L. Black
Review Date: August 20, 2012
IETF LC End Date: August 20, 2012

Summary:
This draft is basically ready for publication, but has nits that
should be fixed before publication.

<NB> Thanks.



This draft covers defect behavior for Ethernet pseudowires,

including defect state mapping and PE defect reporting behavior.

The draft is generally in good shape.  I found a few minor nits.



1) The draft uses a lot of acronyms - while each acronym appears to

be expanded on first use, an additional section near the start of the

draft listing all of them would be helpful.

<NB> Done.



2) There's a typo in the first paragraph of section 2:



     covers the following Ethernet OAM (Opertaions, Administration and



Opertaions -> Operations.

<NB> Thanks. Done.



3) The following normative reference is incomplete - please add additional

information that will enable a reader to locate the referenced document:



     [MEF16] "Ethernet Local Management Interface", MEF16, January 2006.

[MEF16] "Ethernet Local Management Interface", Metro Ethernet Forum Technic=
al Specification MEF16, January 2006.

<NB> changed it to :



4) idnits 2.12.13 did not like the pagination:



  =3D=3D The page length should not exceed 58 lines per page, but there was=
 22
     longer pages, the longest (page 1) being 61 lines
<NB> That will be fixed.

Thanks,
--David
----------------------------------------------------
David L. Black, Distinguished Engineer
EMC Corporation, 176 South St., Hopkinton, MA  01748
+1 (508) 293-7953<tel:%2B1%20%28508%29%20293-7953>             FAX: +1 (508=
) 293-7786<tel:%2B1%20%28508%29%20293-7786>
david.black@emc.com<mailto:david.black@emc.com>        Mobile: +1 (978) 394=
-7754<tel:%2B1%20%28978%29%20394-7754>
----------------------------------------------------

_______________________________________________
pwe3 mailing list
pwe3@ietf.org<mailto:pwe3@ietf.org>
https://www.ietf.org/mailman/listinfo/pwe3


--_000_6D3D47CB84BDE349BC23BF1C94E316E44283E790C0EMV62UKRDdoma_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 12 (filtered medium)">
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:Verdana;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
h1
	{mso-style-priority:9;
	mso-style-link:"Heading 1 Char";
	mso-margin-top-alt:auto;
	margin-right:0cm;
	mso-margin-bottom-alt:auto;
	margin-left:0cm;
	font-size:24.0pt;
	font-family:"Times New Roman","serif";
	font-weight:bold;}
h2
	{mso-style-priority:9;
	mso-style-link:"Heading 2 Char";
	mso-margin-top-alt:auto;
	margin-right:0cm;
	mso-margin-bottom-alt:auto;
	margin-left:0cm;
	font-size:18.0pt;
	font-family:"Times New Roman","serif";
	font-weight:bold;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p
	{mso-style-priority:99;
	mso-margin-top-alt:auto;
	margin-right:0cm;
	mso-margin-bottom-alt:auto;
	margin-left:0cm;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
span.Heading1Char
	{mso-style-name:"Heading 1 Char";
	mso-style-priority:9;
	mso-style-link:"Heading 1";
	font-family:"Cambria","serif";
	color:#365F91;
	font-weight:bold;}
span.Heading2Char
	{mso-style-name:"Heading 2 Char";
	mso-style-priority:9;
	mso-style-link:"Heading 2";
	font-family:"Cambria","serif";
	color:#4F81BD;
	font-weight:bold;}
span.EmailStyle20
	{mso-style-type:personal-reply;
	font-family:"Verdana","sans-serif";
	color:#632423;
	font-weight:normal;
	font-style:normal;}
.MsoChpDefault
	{mso-style-type:export-only;}
@page Section1
	{size:612.0pt 792.0pt;
	margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.Section1
	{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]-->
</head>

<body lang=3DEN-GB link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

<p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Verdana",=
"sans-serif";
color:#632423'>Hi Greg....<o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Verdana",=
"sans-serif";
color:#632423'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Verdana",=
"sans-serif";
color:#632423'>CC per se has little inherent value....but that is
historical.&nbsp; CV does have proper value.&nbsp; CV and RDI however shoul=
d
NOT be mutually dependent messages as the latter cannot be meaningfully ass=
ociated
with (a CV flow on) p2mp connections.<o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Verdana",=
"sans-serif";
color:#632423'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Verdana",=
"sans-serif";
color:#632423'>And BTW AIS (or FDI) has no value whatsoever in any pkt
networks....obvious for cl-ps but this is just as true for co-ps.&nbsp; It =
has
limited value in the co-cs mode with PVCs, where its origins stem from the =
fact
that (i) the fixed time resource (time-slot) allocated by a server to a cli=
ent
link-connection has to be filled with something and (ii) that &#8216;someth=
ing&#8217;
became binary all 1s simply because that was what the early TTL silicon
technology in the PDH produced on failure, ie + 5V.&nbsp; But when one cons=
iders
co-cs SVCs then AIS even here starts to look very silly....the underlying k=
ey point
being that *unless* there is a permanently fixed binding between a server a=
nd
its clients (even after server failure, ie client does not attempt to re-ro=
ute
in *its* layer network) then where does the server know who to send the AIS
(FDI) to?&nbsp; AIS (FDI) should be strongly deprecated in all future work =
on
OAM.&nbsp; It took me a little time to fully realise this point.<o:p></o:p>=
</span></p>

<p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Verdana",=
"sans-serif";
color:#632423'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Verdana",=
"sans-serif";
color:#632423'>regards, Neil<o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Verdana",=
"sans-serif";
color:#632423'><o:p>&nbsp;</o:p></span></p>

<div style=3D'border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm =
4.0pt'>

<div>

<div style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm =
0cm 0cm'>

<p class=3DMsoNormal><b><span lang=3DEN-US style=3D'font-size:10.0pt;font-f=
amily:
"Tahoma","sans-serif"'>From:</span></b><span lang=3DEN-US style=3D'font-siz=
e:10.0pt;
font-family:"Tahoma","sans-serif"'> pwe3-bounces@ietf.org
[mailto:pwe3-bounces@ietf.org] <b>On Behalf Of </b>Greg Mirsky<br>
<b>Sent:</b> 07 January 2013 20:51<br>
<b>To:</b> Bitar, Nabil N<br>
<b>Cc:</b> sajassi@cisco.com; ietf@ietf.org; dinmohan@hotmail.com;
pwe3@ietf.org; gen-art@ietf.org<br>
<b>Subject:</b> Re: [PWE3] Gen-ART review of
draft-ietf-pwe3-mpls-eth-oam-iwk-06<o:p></o:p></span></p>

</div>

</div>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

<p class=3DMsoNormal>Dear Nabil,<br>
can we avoid different interpretation of the same abbreviation (RDI):<o:p><=
/o:p></p>

<p><span style=3D'font-family:"Courier New"'>&nbsp;&nbsp; RDI&nbsp;&nbsp; R=
emote
Defect Indication for Continuity Check Message</span><span style=3D'font-fa=
mily:
"Calibri","sans-serif"'><o:p></o:p></span></p>

<p><span style=3D'font-family:"Courier New"'>&nbsp; &nbsp;RDI &nbsp; Revers=
e
Defect Indication </span><o:p></o:p></p>

<p><span style=3D'font-family:"Courier New"'>AFAIK, the latter form is the
interpretation used by both IEEE 802.1ag and Y.1731. How useful is the firs=
t
form?</span><o:p></o:p></p>

<p><span style=3D'font-family:"Courier New"'>Regards,</span><o:p></o:p></p>

<p><span style=3D'font-family:"Courier New"'>Greg</span><o:p></o:p></p>

<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><o:p>&nbsp;</o:p></p>

<div>

<p class=3DMsoNormal>On Fri, Jan 4, 2013 at 8:17 AM, Bitar, Nabil N &lt;<a
href=3D"mailto:nabil.n.bitar@verizon.com" target=3D"_blank">nabil.n.bitar@v=
erizon.com</a>&gt;
wrote:<o:p></o:p></p>

<div>

<div>

<p class=3DMsoNormal><span style=3D'font-size:10.5pt;font-family:"Calibri",=
"sans-serif"'>Hi
Dave,<o:p></o:p></span></p>

</div>

<div>

<p class=3DMsoNormal><span style=3D'font-size:10.5pt;font-family:"Calibri",=
"sans-serif"'>Related
to abbreviations comment below and to be clearer, I renamed the original
terminology section to &quot;Abbreviations and Terminology&quot;. I also
created a subsection called &quot;Abbreviations&quot; ,and
&quot;Terminology&quot; became the second subsection. &nbsp;Here iis how th=
e
edits look<o:p></o:p></span></p>

</div>

<div>

<p class=3DMsoNormal><span style=3D'font-size:10.5pt;font-family:"Calibri",=
"sans-serif"'><o:p>&nbsp;</o:p></span></p>

</div>

<div>

<h1 style=3D'margin-right:18.95pt'><a name=3D"13c065c123e63175__Toc21875989=
5"></a><a
name=3D"13c065c123e63175__Toc218760256"></a><span style=3D'font-size:10.5pt=
;
font-family:"Calibri","sans-serif"'>3. Abbreviations and Terminology</span>=
<span
style=3D'font-family:"Calibri","sans-serif"'><o:p></o:p></span></h1>

<h2><a name=3D"13c065c123e63175__Toc218759896"></a><a
name=3D"13c065c123e63175__Toc218760257"></a><span style=3D'font-size:10.5pt=
;
font-family:"Calibri","sans-serif"'>3.1. Abbreviations</span><span
style=3D'font-family:"Calibri","sans-serif"'><o:p></o:p></span></h2>

<p><span style=3D'font-size:10.5pt;font-family:"Calibri","sans-serif"'>&nbs=
p;
&nbsp; &nbsp; &nbsp;&nbsp;</span><span style=3D'font-size:10.5pt;font-famil=
y:
"Courier New"'>AIS&nbsp;&nbsp; Alarm Indication Signal</span><span
style=3D'font-size:10.5pt;font-family:"Calibri","sans-serif"'><o:p></o:p></=
span></p>

<p><span style=3D'font-size:10.5pt;font-family:"Courier New"'>&nbsp;&nbsp;
AC&nbsp;&nbsp;&nbsp; Attachment Circuit</span><span style=3D'font-size:10.5=
pt;
font-family:"Calibri","sans-serif"'><o:p></o:p></span></p>

<p><span style=3D'font-size:10.5pt;font-family:"Courier New"'>&nbsp;&nbsp;
BFD&nbsp;&nbsp; Bidirectional Forwarding Detection</span><span
style=3D'font-size:10.5pt;font-family:"Calibri","sans-serif"'><o:p></o:p></=
span></p>

<p><span style=3D'font-size:10.5pt;font-family:"Courier New"'>&nbsp;&nbsp;
CC&nbsp;&nbsp;&nbsp; Continuity Check</span><span style=3D'font-size:10.5pt=
;
font-family:"Calibri","sans-serif"'><o:p></o:p></span></p>

<p><span style=3D'font-size:10.5pt;font-family:"Courier New"'>&nbsp;&nbsp;
CCM&nbsp;&nbsp; Continuity Check Message</span><span style=3D'font-size:10.=
5pt;
font-family:"Calibri","sans-serif"'><o:p></o:p></span></p>

<p><span style=3D'font-size:10.5pt;font-family:"Courier New"'>&nbsp;&nbsp;
CE&nbsp;&nbsp;&nbsp; Customer Equipment</span><span style=3D'font-size:10.5=
pt;
font-family:"Calibri","sans-serif"'><o:p></o:p></span></p>

<p><span style=3D'font-size:10.5pt;font-family:"Courier New"'>&nbsp;&nbsp;
CV&nbsp;&nbsp;&nbsp; Connectivity Verification</span><span style=3D'font-si=
ze:
10.5pt;font-family:"Calibri","sans-serif"'><o:p></o:p></span></p>

<p><span style=3D'font-size:10.5pt;font-family:"Courier New"'>&nbsp;&nbsp; =
E-LMI
Ethernet Local Management Interface</span><span style=3D'font-size:10.5pt;
font-family:"Calibri","sans-serif"'><o:p></o:p></span></p>

<p><span style=3D'font-size:10.5pt;font-family:"Courier New"'>&nbsp;&nbsp;
EVC&nbsp;&nbsp; Ethernet Virtual Circuit</span><span style=3D'font-size:10.=
5pt;
font-family:"Calibri","sans-serif"'><o:p></o:p></span></p>

<p><span style=3D'font-size:10.5pt;font-family:"Courier New"'>&nbsp;&nbsp;
LDP&nbsp;&nbsp; Label Distribution Protocol</span><span style=3D'font-size:=
10.5pt;
font-family:"Calibri","sans-serif"'><o:p></o:p></span></p>

<p><span style=3D'font-size:10.5pt;font-family:"Courier New"'>&nbsp;&nbsp;
LoS&nbsp;&nbsp; Loss of Signal</span><span style=3D'font-size:10.5pt;font-f=
amily:
"Calibri","sans-serif"'><o:p></o:p></span></p>

<p><span style=3D'font-size:10.5pt;font-family:"Courier New"'>&nbsp;&nbsp; =
MA
&nbsp;&nbsp; Maintenance Association</span><span style=3D'font-size:10.5pt;
font-family:"Calibri","sans-serif"'><o:p></o:p></span></p>

<p><span style=3D'font-size:10.5pt;font-family:"Courier New"'>&nbsp;&nbsp;
MD&nbsp;&nbsp;&nbsp; Maintenance Domain</span><span style=3D'font-size:10.5=
pt;
font-family:"Calibri","sans-serif"'><o:p></o:p></span></p>

<p><span style=3D'font-size:10.5pt;font-family:"Courier New"'>&nbsp;&nbsp;
ME&nbsp;&nbsp;&nbsp; Maintenance Entity</span><span style=3D'font-size:10.5=
pt;
font-family:"Calibri","sans-serif"'><o:p></o:p></span></p>

<p><span style=3D'font-size:10.5pt;font-family:"Courier New"'>&nbsp;&nbsp;
MEG&nbsp;&nbsp; Maintenance Entity Group</span><span style=3D'font-size:10.=
5pt;
font-family:"Calibri","sans-serif"'><o:p></o:p></span></p>

<p><span style=3D'font-size:10.5pt;font-family:"Courier New"'>&nbsp;&nbsp;
MEP&nbsp;&nbsp; Maintenance End Point</span><span style=3D'font-size:10.5pt=
;
font-family:"Calibri","sans-serif"'><o:p></o:p></span></p>

<p><span style=3D'font-size:10.5pt;font-family:"Courier New"'>&nbsp;&nbsp;
MIP&nbsp;&nbsp; Maintenance End Point</span><span style=3D'font-size:10.5pt=
;
font-family:"Calibri","sans-serif"'><o:p></o:p></span></p>

<p><span style=3D'font-size:10.5pt;font-family:"Courier New"'>&nbsp;&nbsp;
MPLS&nbsp; Multiprotocol Label Switching</span><span style=3D'font-size:10.=
5pt;
font-family:"Calibri","sans-serif"'><o:p></o:p></span></p>

<p><span style=3D'font-size:10.5pt;font-family:"Courier New"'>&nbsp;&nbsp; =
MS-PW
Multi-Segment Pseudowire</span><span style=3D'font-size:10.5pt;font-family:=
"Calibri","sans-serif"'><o:p></o:p></span></p>

<p><span style=3D'font-size:10.5pt;font-family:"Courier New"'>&nbsp;&nbsp;
NS&nbsp;&nbsp;&nbsp; Native Service</span><span style=3D'font-size:10.5pt;
font-family:"Calibri","sans-serif"'><o:p></o:p></span></p>

<p><span style=3D'font-size:10.5pt;font-family:"Courier New"'>&nbsp;&nbsp;
OAM&nbsp;&nbsp; Operations, Administration, and Maintenance</span><span
style=3D'font-size:10.5pt;font-family:"Calibri","sans-serif"'><o:p></o:p></=
span></p>

<p><span style=3D'font-size:10.5pt;font-family:"Courier New"'>&nbsp;&nbsp;
PE&nbsp;&nbsp;&nbsp; Provider Edge</span><span style=3D'font-size:10.5pt;
font-family:"Calibri","sans-serif"'><o:p></o:p></span></p>

<p><span style=3D'font-size:10.5pt;font-family:"Courier New"'>&nbsp;&nbsp;
PSN&nbsp;&nbsp; Packet Switched Network</span><span style=3D'font-size:10.5=
pt;
font-family:"Calibri","sans-serif"'><o:p></o:p></span></p>

<p><span style=3D'font-size:10.5pt;font-family:"Courier New"'>&nbsp;&nbsp;
PW&nbsp;&nbsp;&nbsp; Pseudowire</span><span style=3D'font-size:10.5pt;font-=
family:
"Calibri","sans-serif"'><o:p></o:p></span></p>

<p><span style=3D'font-size:10.5pt;font-family:"Courier New"'>&nbsp;&nbsp;
RDI&nbsp;&nbsp; Remote Defect Indication for Continuity Check Message</span=
><span
style=3D'font-size:10.5pt;font-family:"Calibri","sans-serif"'><o:p></o:p></=
span></p>

<p><span style=3D'font-size:10.5pt;font-family:"Courier New"'>&nbsp; &nbsp;=
RDI
&nbsp; Reverse Defect Indication&nbsp;</span><span style=3D'font-size:10.5p=
t;
font-family:"Calibri","sans-serif"'><o:p></o:p></span></p>

<p><span style=3D'font-size:10.5pt;font-family:"Courier New"'>&nbsp;&nbsp;
S-PE&nbsp; Switching Provider Edge</span><span style=3D'font-size:10.5pt;
font-family:"Calibri","sans-serif"'><o:p></o:p></span></p>

<p><span style=3D'font-size:10.5pt;font-family:"Courier New"'>&nbsp;&nbsp; =
TLV&nbsp;&nbsp;
Type Length Value</span><span style=3D'font-size:10.5pt;font-family:"Calibr=
i","sans-serif"'><o:p></o:p></span></p>

<p><span style=3D'font-size:10.5pt;font-family:"Courier New"'>&nbsp;&nbsp;
T-PE&nbsp; Terminating Provider Edge</span><span style=3D'font-size:10.5pt;
font-family:"Calibri","sans-serif"'><o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt=
:auto'><span
style=3D'font-size:10.5pt;font-family:"Calibri","sans-serif"'>&nbsp;</span>=
<span
style=3D'font-family:"Calibri","sans-serif"'><o:p></o:p></span></p>

<h2><a name=3D"13c065c123e63175__Toc218759897"></a><a
name=3D"13c065c123e63175__Toc218760258"></a><span style=3D'font-size:10.5pt=
;
font-family:"Calibri","sans-serif"'>3.2. Terminology</span><span
style=3D'font-family:"Calibri","sans-serif"'><o:p></o:p></span></h2>

<p class=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt=
:auto'><span
style=3D'font-size:10.5pt;font-family:"Calibri","sans-serif"'>This document=
 uses
the following terms with corresponding definitions: </span><span
style=3D'font-family:"Calibri","sans-serif"'><o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt=
:auto'><span
style=3D'font-size:10.5pt;font-family:"Calibri","sans-serif"'>- MD Level:&n=
bsp;
Maintenance Domain (MD) Level which identifies a value in the range of 0-7
associated with Ethernet OAM frame. MD Level identifies the span of the
Ethernet OAM frame.</span><span style=3D'font-family:"Calibri","sans-serif"=
'><o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt=
:auto;
text-align:justify'><span style=3D'font-size:10.5pt;font-family:"Calibri","=
sans-serif"'>&nbsp;-
MEP:&nbsp; &nbsp;&nbsp;Maintenance End Point is responsible for origination=
 and
termination of OAM frames for a given MEG.</span><span style=3D'font-family=
:"Calibri","sans-serif"'><o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt=
:auto'><span
style=3D'font-size:10.5pt;font-family:"Calibri","sans-serif"'>&nbsp;- MIP:
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Maintenance Intermediate Point is located bet=
ween
peer MEPs and can process OAM frames but does not initiate or terminate the=
m.</span><span
style=3D'font-family:"Calibri","sans-serif"'><o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt=
:auto'><span
style=3D'font-size:10.5pt;font-family:"Calibri","sans-serif"'>Further, this
document also uses the terminology and conventions used in [RFC6310].</span=
><span
style=3D'font-family:"Calibri","sans-serif"'><o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt=
:auto'><span
style=3D'font-family:"Calibri","sans-serif"'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt=
:auto'><span
style=3D'font-family:"Calibri","sans-serif"'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt=
:auto'><span
style=3D'font-size:10.5pt;font-family:"Calibri","sans-serif"'>Thanks,</span=
><span
style=3D'font-family:"Calibri","sans-serif"'><o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt=
:auto'><span
style=3D'font-size:10.5pt;font-family:"Calibri","sans-serif"'>Nabil</span><=
span
style=3D'font-family:"Calibri","sans-serif"'><o:p></o:p></span></p>

</div>

<div>

<p class=3DMsoNormal><span style=3D'font-size:10.5pt;font-family:"Calibri",=
"sans-serif"'><o:p>&nbsp;</o:p></span></p>

</div>

<div style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm =
0cm 0cm'>

<p class=3DMsoNormal><b><span style=3D'font-size:11.0pt;font-family:"Calibr=
i","sans-serif"'>From:
</span></b><span style=3D'font-size:11.0pt;font-family:"Calibri","sans-seri=
f"'>&lt;Bitar&gt;,
Nabil N &lt;<a href=3D"mailto:nabil.n.bitar@one.verizon.com" target=3D"_bla=
nk">nabil.n.bitar@one.verizon.com</a>&gt;<br>
<b>Date: </b>Wednesday, January 2, 2013 11:28 AM<br>
<b>To: </b>&quot;Black, David&quot; &lt;<a href=3D"mailto:david.black@emc.c=
om"
target=3D"_blank">david.black@emc.com</a>&gt;, &quot;<a
href=3D"mailto:dinmohan@hotmail.com" target=3D"_blank">dinmohan@hotmail.com=
</a>&quot;
&lt;<a href=3D"mailto:dinmohan@hotmail.com" target=3D"_blank">dinmohan@hotm=
ail.com</a>&gt;,
&quot;Bitar, Nabil N&quot; &lt;<a href=3D"mailto:nabil.n.bitar@one.verizon.=
com"
target=3D"_blank">nabil.n.bitar@one.verizon.com</a>&gt;, Sagessi &lt;<a
href=3D"mailto:sajassi@cisco.com" target=3D"_blank">sajassi@cisco.com</a>&g=
t;,
&quot;<a href=3D"mailto:gen-art@ietf.org" target=3D"_blank">gen-art@ietf.or=
g</a>&quot;
&lt;<a href=3D"mailto:gen-art@ietf.org" target=3D"_blank">gen-art@ietf.org<=
/a>&gt;<br>
<b>Cc: </b>&quot;<a href=3D"mailto:pwe3@ietf.org" target=3D"_blank">pwe3@ie=
tf.org</a>&quot;
&lt;<a href=3D"mailto:pwe3@ietf.org" target=3D"_blank">pwe3@ietf.org</a>&gt=
;,
&quot;<a href=3D"mailto:ietf@ietf.org" target=3D"_blank">ietf@ietf.org</a>&=
quot;
&lt;<a href=3D"mailto:ietf@ietf.org" target=3D"_blank">ietf@ietf.org</a>&gt=
;<br>
<b>Subject: </b>Re: Gen-ART review of draft-ietf-pwe3-mpls-eth-oam-iwk-06<o=
:p></o:p></span></p>

</div>

<div>

<p class=3DMsoNormal><span style=3D'font-size:10.5pt;font-family:"Calibri",=
"sans-serif"'><o:p>&nbsp;</o:p></span></p>

</div>

<div>

<div>

<div>

<p class=3DMsoNormal><span style=3D'font-size:10.5pt;font-family:"Calibri",=
"sans-serif"'>Hi
Dave,<o:p></o:p></span></p>

</div>

<div>

<p class=3DMsoNormal><span style=3D'font-size:10.5pt;font-family:"Calibri",=
"sans-serif"'>Sorry
for a late reply addressing your comments. Please, see inline.<o:p></o:p></=
span></p>

</div>

<div>

<p class=3DMsoNormal><span style=3D'font-size:10.5pt;font-family:"Calibri",=
"sans-serif"'><o:p>&nbsp;</o:p></span></p>

</div>

<div>

<p class=3DMsoNormal><span style=3D'font-size:10.5pt;font-family:"Calibri",=
"sans-serif"'>Thanks,<o:p></o:p></span></p>

</div>

<div>

<p class=3DMsoNormal><span style=3D'font-size:10.5pt;font-family:"Calibri",=
"sans-serif"'>Nabil<o:p></o:p></span></p>

</div>

<div>

<p class=3DMsoNormal><span style=3D'font-size:10.5pt;font-family:"Calibri",=
"sans-serif"'><o:p>&nbsp;</o:p></span></p>

</div>

<div style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm =
0cm 0cm'>

<p class=3DMsoNormal><b><span style=3D'font-size:11.0pt;font-family:"Calibr=
i","sans-serif"'>From:
</span></b><span style=3D'font-size:11.0pt;font-family:"Calibri","sans-seri=
f"'>&quot;Black,
David&quot; &lt;<a href=3D"mailto:david.black@emc.com" target=3D"_blank">da=
vid.black@emc.com</a>&gt;<br>
<b>Date: </b>Monday, August 20, 2012 8:57 PM<br>
<b>To: </b>&quot;<a href=3D"mailto:dinmohan@hotmail.com" target=3D"_blank">=
dinmohan@hotmail.com</a>&quot;
&lt;<a href=3D"mailto:dinmohan@hotmail.com" target=3D"_blank">dinmohan@hotm=
ail.com</a>&gt;,
&quot;Bitar, Nabil N&quot; &lt;<a href=3D"mailto:nabil.n.bitar@one.verizon.=
com"
target=3D"_blank">nabil.n.bitar@one.verizon.com</a>&gt;, Sagessi &lt;<a
href=3D"mailto:sajassi@cisco.com" target=3D"_blank">sajassi@cisco.com</a>&g=
t;,
&quot;<a href=3D"mailto:gen-art@ietf.org" target=3D"_blank">gen-art@ietf.or=
g</a>&quot;
&lt;<a href=3D"mailto:gen-art@ietf.org" target=3D"_blank">gen-art@ietf.org<=
/a>&gt;<br>
<b>Cc: </b>&quot;Black, David&quot; &lt;<a href=3D"mailto:david.black@emc.c=
om"
target=3D"_blank">david.black@emc.com</a>&gt;, &quot;<a
href=3D"mailto:pwe3@ietf.org" target=3D"_blank">pwe3@ietf.org</a>&quot; &lt=
;<a
href=3D"mailto:pwe3@ietf.org" target=3D"_blank">pwe3@ietf.org</a>&gt;, &quo=
t;<a
href=3D"mailto:ietf@ietf.org" target=3D"_blank">ietf@ietf.org</a>&quot; &lt=
;<a
href=3D"mailto:ietf@ietf.org" target=3D"_blank">ietf@ietf.org</a>&gt;<br>
<b>Subject: </b>Gen-ART review of draft-ietf-pwe3-mpls-eth-oam-iwk-06<o:p><=
/o:p></span></p>

</div>

<div>

<p class=3DMsoNormal><span style=3D'font-size:10.5pt;font-family:"Calibri",=
"sans-serif"'><o:p>&nbsp;</o:p></span></p>

</div>

<div>

<div>

<div>

<p class=3DMsoNormal><span style=3D'font-size:10.5pt;font-family:"Courier N=
ew";
color:black'>I am the assigned Gen-ART reviewer for this draft. For backgro=
und
on Gen-ART, please<br>
see the FAQ at &lt;<a
href=3D"http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq" target=3D"=
_blank">http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq</a>&gt;.<br=
>
<br>
Please resolve these comments along with any other Last Call comments you m=
ay
receive.<br>
<br>
Document: </span><span lang=3DEN style=3D'font-size:10.5pt;font-family:"Cou=
rier New";
color:black'>draft-ietf-pwe3-mpls-eth-oam-iwk-06</span><span style=3D'font-=
size:
10.5pt;font-family:"Calibri","sans-serif"'><o:p></o:p></span></p>

</div>

<div>

<p class=3DMsoNormal><span style=3D'font-size:10.5pt;font-family:"Courier N=
ew";
color:black'>Reviewer: David L. Black<br>
Review Date: August 20, 2012<br>
IETF LC End Date: August 20, 2012<br>
<br>
Summary:<br>
This draft is basically ready for publication, but has nits that<br>
should be fixed before publication.</span><span style=3D'font-size:10.5pt;
font-family:"Calibri","sans-serif"'><o:p></o:p></span></p>

</div>

</div>

</div>

<div>

<p class=3DMsoNormal><span style=3D'font-size:10.5pt;font-family:"Calibri",=
"sans-serif"'><o:p>&nbsp;</o:p></span></p>

</div>

<div>

<p class=3DMsoNormal><span style=3D'font-size:10.5pt;font-family:"Calibri",=
"sans-serif"'>&lt;NB&gt;
Thanks.<o:p></o:p></span></p>

</div>

<div>

<div>

<p><span style=3D'font-size:10.5pt;font-family:"Calibri","sans-serif"'>&nbs=
p;<o:p></o:p></span></p>

<p><span style=3D'font-size:10.5pt;font-family:"Courier New";color:black'>T=
his
draft covers defect behavior for Ethernet pseudowires,</span><span
style=3D'font-size:10.5pt;font-family:"Calibri","sans-serif"'><o:p></o:p></=
span></p>

<p><span style=3D'font-size:10.5pt;font-family:"Courier New";color:black'>i=
ncluding
defect state mapping and PE defect reporting behavior.</span><span
style=3D'font-size:10.5pt;font-family:"Calibri","sans-serif"'><o:p></o:p></=
span></p>

<p><span style=3D'font-size:10.5pt;font-family:"Courier New";color:black'>T=
he
draft is generally in good shape.&nbsp; I found a few minor nits.</span><sp=
an
style=3D'font-size:10.5pt;font-family:"Calibri","sans-serif"'><o:p></o:p></=
span></p>

<p><span style=3D'font-size:10.5pt;font-family:"Calibri","sans-serif"'>&nbs=
p;<o:p></o:p></span></p>

<p><span style=3D'font-size:10.5pt;font-family:"Courier New"'>1) The draft =
uses a
lot of acronyms - while each acronym appears to</span><span style=3D'font-s=
ize:
10.5pt;font-family:"Calibri","sans-serif"'><o:p></o:p></span></p>

<p><span style=3D'font-size:10.5pt;font-family:"Courier New"'>be expanded o=
n
first use, an additional section near the start of the</span><span
style=3D'font-size:10.5pt;font-family:"Calibri","sans-serif"'><o:p></o:p></=
span></p>

<p><span style=3D'font-size:10.5pt;font-family:"Courier New"'>draft listing=
 all
of them would be helpful.</span><span style=3D'font-size:10.5pt;font-family=
:"Calibri","sans-serif"'><o:p></o:p></span></p>

</div>

</div>

<div>

<p class=3DMsoNormal><span style=3D'font-size:10.5pt;font-family:"Calibri",=
"sans-serif"'><o:p>&nbsp;</o:p></span></p>

</div>

<div>

<p class=3DMsoNormal><span style=3D'font-size:10.5pt;font-family:"Calibri",=
"sans-serif"'>&lt;NB&gt;
Done.<o:p></o:p></span></p>

</div>

<div>

<div>

<p><span style=3D'font-size:10.5pt;font-family:"Calibri","sans-serif"'>&nbs=
p;<o:p></o:p></span></p>

<p><span style=3D'font-size:10.5pt;font-family:"Courier New"'>2) There's&nb=
sp;a
typo in the first paragraph of section 2:</span><span style=3D'font-size:10=
.5pt;
font-family:"Calibri","sans-serif"'><o:p></o:p></span></p>

<p><span style=3D'font-size:10.5pt;font-family:"Calibri","sans-serif"'>&nbs=
p;<o:p></o:p></span></p>

<div>

<p><span lang=3DEN style=3D'font-size:10.5pt;font-family:"Courier New";colo=
r:black'>&nbsp;&nbsp;&nbsp;
&nbsp;covers the following Ethernet OAM (Opertaions, Administration and </s=
pan><span
lang=3DEN style=3D'font-size:10.5pt;font-family:"Calibri","sans-serif";colo=
r:black'><o:p></o:p></span></p>

<p><span lang=3DEN style=3D'font-size:10.5pt;font-family:"Calibri","sans-se=
rif";
color:black'>&nbsp;<o:p></o:p></span></p>

<p><span lang=3DEN style=3D'font-size:10.5pt;font-family:"Courier New";colo=
r:black'>Opertaions&nbsp;-&gt;
Operations.</span><span lang=3DEN style=3D'font-size:10.5pt;font-family:"Ca=
libri","sans-serif";
color:black'><o:p></o:p></span></p>

</div>

</div>

</div>

<div>

<p class=3DMsoNormal><span style=3D'font-size:10.5pt;font-family:"Calibri",=
"sans-serif"'><o:p>&nbsp;</o:p></span></p>

</div>

<div>

<p class=3DMsoNormal><span style=3D'font-size:10.5pt;font-family:"Calibri",=
"sans-serif"'>&lt;NB&gt;
Thanks. Done.<o:p></o:p></span></p>

</div>

<div>

<div>

<div>

<p><span lang=3DEN style=3D'font-size:10.5pt;font-family:"Calibri","sans-se=
rif";
color:black'>&nbsp;<o:p></o:p></span></p>

<p><span lang=3DEN style=3D'font-size:10.5pt;font-family:"Courier New";colo=
r:black'>3)
The following normative reference is incomplete - please add additional</sp=
an><span
lang=3DEN style=3D'font-size:10.5pt;font-family:"Calibri","sans-serif";colo=
r:black'><o:p></o:p></span></p>

<p><span lang=3DEN style=3D'font-size:10.5pt;font-family:"Courier New";colo=
r:black'>information
that will enable a reader to locate the referenced document:</span><span
lang=3DEN style=3D'font-size:10.5pt;font-family:"Calibri","sans-serif";colo=
r:black'><o:p></o:p></span></p>

<p><span lang=3DEN style=3D'font-size:10.5pt;font-family:"Calibri","sans-se=
rif";
color:black'>&nbsp;<o:p></o:p></span></p>

<p><span lang=3DEN style=3D'font-size:10.5pt;font-family:"Courier New";colo=
r:black'>&nbsp;&nbsp;&nbsp;
&nbsp;[MEF16] &quot;Ethernet Local Management Interface&quot;, MEF16, Janua=
ry
2006.<o:p></o:p></span></p>

</div>

</div>

</div>

<div>

<p class=3DMsoNormal><span style=3D'font-size:10.5pt;font-family:"Calibri",=
"sans-serif"'><o:p>&nbsp;</o:p></span></p>

</div>

<div>

<div>

<div>

<p class=3DMsoNormal><span style=3D'font-size:10.5pt;font-family:"Courier N=
ew";
color:black'>[MEF16] &quot;Ethernet Local Management Interface&quot;, Metro
Ethernet Forum Technical Specification MEF16, January 2006.</span><span
lang=3DEN style=3D'font-size:10.5pt;font-family:"Courier New";color:black'>=
<o:p></o:p></span></p>

<p><span lang=3DEN style=3D'font-size:10.5pt;font-family:"Courier New";colo=
r:black'>&lt;NB&gt;
changed it to :&nbsp;<o:p></o:p></span></p>

<p><span lang=3DEN style=3D'font-size:10.5pt;font-family:"Courier New";colo=
r:black'>&nbsp;<o:p></o:p></span></p>

<p><span lang=3DEN style=3D'font-size:10.5pt;font-family:"Courier New";colo=
r:black'>4)&nbsp;idnits
2.12.13 did not like the pagination:<o:p></o:p></span></p>

<p><span lang=3DEN style=3D'font-size:10.5pt;font-family:"Courier New";colo=
r:black'>&nbsp;<o:p></o:p></span></p>

<p><span style=3D'font-size:10.5pt;font-family:"Courier New";color:black'>&=
nbsp;
=3D=3D The page length should not exceed 58 lines per page, but there was 2=
2<br>
&nbsp;&nbsp;&nbsp;&nbsp; longer pages, the longest (page 1) being 61 lines<=
/span><span
style=3D'font-size:10.5pt;font-family:"Calibri","sans-serif";color:black'><=
o:p></o:p></span></p>

</div>

</div>

</div>

<div>

<p class=3DMsoNormal><span style=3D'font-size:10.5pt;font-family:"Calibri",=
"sans-serif"'>&lt;NB&gt;
That will be fixed.<o:p></o:p></span></p>

</div>

<div>

<div>

<div>

<p class=3DMsoNormal><span style=3D'font-size:10.5pt;font-family:"Courier N=
ew";
color:black'>&nbsp;</span><span style=3D'font-size:10.5pt;font-family:"Cali=
bri","sans-serif"'><o:p></o:p></span></p>

</div>

<div>

<p class=3DMsoNormal><span style=3D'font-size:10.5pt;font-family:"Courier N=
ew"'>Thanks,</span><span
style=3D'font-size:10.5pt;font-family:"Calibri","sans-serif"'><o:p></o:p></=
span></p>

</div>

<div>

<p class=3DMsoNormal><span style=3D'font-size:10.5pt;font-family:"Courier N=
ew"'>--David</span><span
style=3D'font-size:10.5pt;font-family:"Calibri","sans-serif"'><o:p></o:p></=
span></p>

</div>

<div>

<p class=3DMsoNormal><span style=3D'font-size:10.5pt;font-family:"Courier N=
ew"'>----------------------------------------------------<br>
David L. Black, Distinguished Engineer<br>
EMC Corporation, 176 South St., Hopkinton, MA&nbsp; 01748<br>
<a href=3D"tel:%2B1%20%28508%29%20293-7953" target=3D"_blank">+1 (508) 293-=
7953</a>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;
FAX: <a href=3D"tel:%2B1%20%28508%29%20293-7786" target=3D"_blank">+1 (508)
293-7786</a><br>
<a href=3D"mailto:david.black@emc.com" target=3D"_blank">david.black@emc.co=
m</a>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Mobile: <a href=3D"tel:%2B1%20%28978%29%20394-7754" target=3D"_blank">+1 (9=
78)
394-7754</a><br>
----------------------------------------------------</span><span
style=3D'font-size:10.5pt;font-family:"Calibri","sans-serif"'><o:p></o:p></=
span></p>

</div>

</div>

</div>

</div>

</div>

</div>

<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><br>
_______________________________________________<br>
pwe3 mailing list<br>
<a href=3D"mailto:pwe3@ietf.org">pwe3@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/pwe3" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/pwe3</a><o:p></o:p></p>

</div>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

</div>

</div>

</body>

</html>

--_000_6D3D47CB84BDE349BC23BF1C94E316E44283E790C0EMV62UKRDdoma_--

From pbryan@anode.ca  Mon Jan  7 17:33:13 2013
Return-Path: <pbryan@anode.ca>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2EBCC11E80D7; Mon,  7 Jan 2013 17:33:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001]
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 LHRa-LOgY6SK; Mon,  7 Jan 2013 17:33:12 -0800 (PST)
Received: from maple.anode.ca (maple.anode.ca [72.14.183.184]) by ietfa.amsl.com (Postfix) with ESMTP id ACA8211E80B8; Mon,  7 Jan 2013 17:33:12 -0800 (PST)
Received: from [10.126.22.206] (nat-204-14-239-210-sfo.net.salesforce.com [204.14.239.210]) by maple.anode.ca (Postfix) with ESMTPSA id 009E8699B; Tue,  8 Jan 2013 01:33:11 +0000 (UTC)
Subject: Re: [apps-discuss] Last Call: <draft-ietf-appsawg-json-pointer-07.txt> (JSON Pointer) to Proposed Standard
From: "Paul C. Bryan" <pbryan@anode.ca>
To: Robert Sayre <sayrer@gmail.com>
In-Reply-To: <CAChr6SyAq=7aQdZn54ihYK+0hDhL--2Oaq0RvehoNFbwKNNShA@mail.gmail.com>
References: <20121211150057.28223.93310.idtracker@ietfa.amsl.com> <50cb04b9.86df440a.72fe.1e20SMTPIN_ADDED_BROKEN@mx.google.com> <CABP7RbeNsZ_rBWRjou=VG+hBhUKaOz+y1a0sSChwWiHte9znnQ@mail.gmail.com> <50cb5f3c.694c420a.38fb.39afSMTPIN_ADDED_BROKEN@mx.google.com> <CAChr6SxZRc3B_HCbw76kLe2dsRSr43r-gLpfMVnCUfJTrZdTLA@mail.gmail.com> <CABP7RbfA33huBFadMeXTTEt=MkjW8-d4DFH7+GLXGurnm9sSRw@mail.gmail.com> <CAOXDeqpPE4eNy_qJpDPdPHbCQakG9-hDcNZ3Sj9r4kWedByVzQ@mail.gmail.com> <CAChr6SwtS_=iS-k4mJm1vHjEvvGVzay5jDYeGheqsPZqO-89CQ@mail.gmail.com> <EABB8F51-C3B4-49F5-8672-5C2ABAC7043A@mnot.net> <CAChr6Sx7JdKM91EwJaSZ0Ra_F4FSqkuc3vzTY1LM=F_8sWho+Q@mail.gmail.com> <1357515310.6827.23.camel@polyglot> <CAChr6SyAq=7aQdZn54ihYK+0hDhL--2Oaq0RvehoNFbwKNNShA@mail.gmail.com>
Content-Type: multipart/alternative; boundary="=-I8ZK7EqkdsYa6okd4xdy"
Date: Mon, 07 Jan 2013 17:33:10 -0800
Message-ID: <1357608790.27936.223.camel@pbryan-wsl.internal.salesforce.com>
Mime-Version: 1.0
X-Mailer: Evolution 2.28.3 
X-Mailman-Approved-At: Tue, 08 Jan 2013 09:25:48 -0800
Cc: Mark Nottingham <mnot@mnot.net>, IETF Discussion <ietf@ietf.org>, IETF Apps Discuss <apps-discuss@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 08 Jan 2013 01:33:13 -0000

--=-I8ZK7EqkdsYa6okd4xdy
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit

On Sun, 2013-01-06 at 16:01 -0800, Robert Sayre wrote:


> This last assertion really isn't qualified very well.


It would have been better for me to state this is my opinion, based on
discussions that were animated from similar objections raised in the
past. 

Paul

--=-I8ZK7EqkdsYa6okd4xdy
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: 7bit

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
  <META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
  <META NAME="GENERATOR" CONTENT="GtkHTML/3.28.3">
</HEAD>
<BODY>
On Sun, 2013-01-06 at 16:01 -0800, Robert Sayre wrote:<BR>
<BR>
<BLOCKQUOTE TYPE=CITE>
<PRE>
This last assertion really isn't qualified very well.
</PRE>
</BLOCKQUOTE>
<BR>
It would have been better for me to state this is my opinion, based on discussions that were animated from similar objections raised in the past. <BR>
<BR>
Paul
</BODY>
</HTML>

--=-I8ZK7EqkdsYa6okd4xdy--


From mmorley@mpcm.com  Mon Jan  7 22:26:32 2013
Return-Path: <mmorley@mpcm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1AA5C21F878F for <ietf@ietfa.amsl.com>; Mon,  7 Jan 2013 22:26:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.976
X-Spam-Level: 
X-Spam-Status: No, score=-2.976 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
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 mFcD3fPfjMBC for <ietf@ietfa.amsl.com>; Mon,  7 Jan 2013 22:26:31 -0800 (PST)
Received: from mail-la0-f52.google.com (mail-la0-f52.google.com [209.85.215.52]) by ietfa.amsl.com (Postfix) with ESMTP id A54A621F87B9 for <ietf@ietf.org>; Mon,  7 Jan 2013 22:26:30 -0800 (PST)
Received: by mail-la0-f52.google.com with SMTP id fq12so68984lab.25 for <ietf@ietf.org>; Mon, 07 Jan 2013 22:26:29 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :x-gm-message-state; bh=tVGR3V0bZ63/hoDM4AfDUCweXtPnFIX93lv4LwUUXP4=; b=BmOAZHXKHRe7BlE40oJku1EYGdg89ZGHvrbkb16xGTpMflkRQ7EcIQ5AthCR3DZVer ryJANI3c0+GVAhCDbHTWnYVD/GuAoYAnWdT1FcLmqMxGuqUh/TWPEiuV7Sg0cv8ONy2u CS53U7PbBXDKHA02H+P5g6dv+SsovSaoEWnaEoLoE5cuI72VUSc0eaAHU2JdqpMNhlcC qlP25ieMyHoOVNVoj7yTSrfurNB8p/yXiqzypzccP0RModsVVnoO9J7/eVj4/MfaqEmI qHJBjZ+yAKOF7qJKzo3h7/kFXHBDjaGz3nsrMTQePaTcAQoWy+KD5gtPnurO632+jcXK oVcg==
MIME-Version: 1.0
Received: by 10.152.110.18 with SMTP id hw18mr60995840lab.22.1357626389332; Mon, 07 Jan 2013 22:26:29 -0800 (PST)
Sender: mmorley@mpcm.com
Received: by 10.114.38.137 with HTTP; Mon, 7 Jan 2013 22:26:29 -0800 (PST)
In-Reply-To: <50EB4E8B.30700@versi.edu.au>
References: <20121211150057.28223.93310.idtracker@ietfa.amsl.com> <50cb04b9.86df440a.72fe.1e20SMTPIN_ADDED_BROKEN@mx.google.com> <CABP7RbeNsZ_rBWRjou=VG+hBhUKaOz+y1a0sSChwWiHte9znnQ@mail.gmail.com> <50cb5f3c.694c420a.38fb.39afSMTPIN_ADDED_BROKEN@mx.google.com> <CAChr6SxZRc3B_HCbw76kLe2dsRSr43r-gLpfMVnCUfJTrZdTLA@mail.gmail.com> <CABP7RbfA33huBFadMeXTTEt=MkjW8-d4DFH7+GLXGurnm9sSRw@mail.gmail.com> <CAOXDeqpPE4eNy_qJpDPdPHbCQakG9-hDcNZ3Sj9r4kWedByVzQ@mail.gmail.com> <CAChr6SwtS_=iS-k4mJm1vHjEvvGVzay5jDYeGheqsPZqO-89CQ@mail.gmail.com> <EABB8F51-C3B4-49F5-8672-5C2ABAC7043A@mnot.net> <CAChr6Sx7JdKM91EwJaSZ0Ra_F4FSqkuc3vzTY1LM=F_8sWho+Q@mail.gmail.com> <1357515310.6827.23.camel@polyglot> <CAChr6SyAq=7aQdZn54ihYK+0hDhL--2Oaq0RvehoNFbwKNNShA@mail.gmail.com> <CAChr6SxorKO20rGYi-e4YNF=HNGrwz8wPGKCFZQYWQwqsetjjg@mail.gmail.com> <CAOXDeqqE2mCLapwvjwQkme5VTpRCfmF0mFQcx02WW0-zi4i5=g@mail.gmail.com> <50EB4E8B.30700@versi.edu.au>
Date: Tue, 8 Jan 2013 01:26:29 -0500
X-Google-Sender-Auth: Hp6htB9KvhJjezXNY49bilk8pH4
Message-ID: <CAOXDeqoOj1K_zBWVZbE2j4Vnp1pYZ1yUEp9nyTKZmp-QrAziqg@mail.gmail.com>
Subject: Re: [apps-discuss] Last Call: <draft-ietf-appsawg-json-pointer-07.txt> (JSON Pointer) to Proposed Standard
From: Matthew Morley <matt@mpcm.com>
To: Conal Tuohy <conal.tuohy@versi.edu.au>
Content-Type: multipart/alternative; boundary=bcaec54d4de8ac81d404d2c10686
X-Gm-Message-State: ALoCoQlfvtJDe0WAn2WPaespR/qfQDLE4XU9DrGet7bjr48ai5GXp+bRPDB/vGr3swhE4Qlmu2Vt
X-Mailman-Approved-At: Tue, 08 Jan 2013 09:25:48 -0800
Cc: IESG <iesg@ietf.org>, Mark Nottingham <mnot@mnot.net>, IETF Discussion <ietf@ietf.org>, IETF Apps Discuss <apps-discuss@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 08 Jan 2013 06:26:32 -0000

--bcaec54d4de8ac81d404d2c10686
Content-Type: text/plain; charset=ISO-8859-1

On Mon, Jan 7, 2013 at 5:39 PM, Conal Tuohy <conal.tuohy@versi.edu.au>wrote:

>  On 07/01/13 13:23, Matthew Morley wrote:
>
>
> For me the deficiency is not in the pointer, but patch format being
> generated.
>
> One approach is to push that *one* test, structure conformity, into the
> pointer syntax. Another is via the type operation.
>
> If a vague patch is generated, vague results are to be expected.
>
> It seems to me, on the contrary, that the deficiency is in the pointer
> syntax, and I think it would be a mistake to try to work around that
> deficiency in JSON Patch. Because aren't there other things which one might
> do with JSON Pointer than use it with JSON Patch? There's been mention of
> having it registered as a URI fragment identifier syntax for JSON for
> example. JSON Pointers could then end up all over the place, outside of
> patches. IMHO JSON Pointer needs to be taken seriously as a technology in
> its own right.
>

Couldn't agree more about it being taken seriously in its own right. :)

JSON Pointer for me exists outside of JSON Patch, always has and will do
the way we think about structures. As it represents both a resolution path
and an identity string (both ends of the path concept). I see value from
the identity view, in describing a location that is aware of being inside
an array.

But JSON Pointer should not be changed just because of issues with JSON
Patch, especially when JSON Patch is attempting to address those issues
with other mechanisms within the specification. That is all I was trying to
express. The syntax change should be for other reasons, if it is going to
be made.

My personal experience (for what its worth): In the past I've tried a
number of syntaxes like JSON Pointer. Mostly a.b.c.0 and even a.b.c:0 at
times to address the same issues suggested here. Though my experiences
pushed me towards a single syntax using a.b.c.0, and thus my support for
/a/b/c/0 over /a/b/c:0.

The system at first used the . or : syntax, combined with dynamic tokens,
being pointers themselves, to resolve other pointers. So it was not
reasonable to know ahead of time if an end point was an array or an object.
 "a.b.c.{d.e.f}" could end up in an array or in an object, depending on the
value at d.e.f at the time of resolution. Especially with many layers of
tokens to resolve, and changing data structures.

I found in practice, it didn't really matter, so the choice of . or : was
phased out. At the end of the day the two syntaxes point to mutually
exclusive points within the data, so that `meta data` about the structure
was removed from the syntax we used. It didn't add value, even if it added
clarity at times. We also had functions at the end of paths, but that goes
beyond the JSON focus of the JSON Pointer goals, so those points are not
relevant here.

This discussion thread seems to be getting overly complicated, but JSON
Pointer changes should come from the JSON Pointer view point and that
specifications goals, not from short comings in JSON Patch.

-- 
Matthew P. C. Morley

--bcaec54d4de8ac81d404d2c10686
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On Mon, Jan 7, 2013 at 5:39 PM, Conal Tuohy <span dir=3D"ltr">&lt;<a href=
=3D"mailto:conal.tuohy@versi.edu.au" target=3D"_blank">conal.tuohy@versi.ed=
u.au</a>&gt;</span> wrote:<br><div class=3D"gmail_quote"><blockquote class=
=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padd=
ing-left:1ex">

 =20
   =20
 =20
  <div bgcolor=3D"#FFFFFF" text=3D"#000000"><div class=3D"im">
    <div>On 07/01/13 13:23, Matthew Morley
      wrote:<br>
    </div>
    <blockquote type=3D"cite">
     =20
      <br>
      For me the deficiency is not in the pointer, but patch format
      being generated.<br>
      <br>
      One approach is to push that *one* test, structure=A0conformity,
      into the pointer syntax.=A0Another is via the type operation.<br>
      <br>
      If a vague patch is generated, vague results are to be expected.<br>
    </blockquote></div>
    It seems to me, on the contrary, that the deficiency is in the
    pointer syntax, and I think it would be a mistake to try to work
    around that deficiency in JSON Patch. Because aren&#39;t there other
    things which one might do with JSON Pointer than use it with JSON
    Patch? There&#39;s been mention of having it registered as a URI
    fragment identifier syntax for JSON for example. JSON Pointers could
    then end up all over the place, outside of patches. IMHO JSON
    Pointer needs to be taken seriously as a technology in its own
    right.=A0</div></blockquote><div><br>Couldn&#39;t agree more about it b=
eing taken seriously in its own right. :)<br><br>JSON Pointer for me exists=
 outside of JSON Patch, always has and will do the way we think about struc=
tures. As it represents both a resolution path and an identity string (both=
 ends of the path concept). I see value from the identity view, in describi=
ng a location that is aware of being inside an array.</div>
<div><br>But JSON Pointer should not be changed just because of issues with=
 JSON Patch, especially when JSON Patch is attempting to address those issu=
es with other mechanisms within the specification. That is all I was trying=
 to express. The syntax change should be for other reasons, if it is going =
to be made.<br>
<br></div><div>My personal experience (for what its worth): In the past I&#=
39;ve tried a number of syntaxes like JSON Pointer. Mostly a.b.c.0 and even=
 a.b.c:0 at times to address the same issues suggested here. Though my expe=
riences pushed me towards a single syntax using a.b.c.0, and thus my suppor=
t for /a/b/c/0 over /a/b/c:0.<br>
<br>The system at first used the . or : syntax, combined with dynamic token=
s, being pointers themselves, to resolve other pointers. So it was not reas=
onable to know ahead of time if an end point was an array or an object. =A0=
&quot;a.b.c.{d.e.f}&quot; could end up in an array or in an object, dependi=
ng on the value at d.e.f at the time of resolution. Especially with many la=
yers of tokens to resolve, and changing data structures.<br>
<br>I found in practice, it didn&#39;t really matter, so the choice of . or=
 : was phased out. At the end of the day the two syntaxes point to mutually=
 exclusive points within the data, so that `meta data` about the structure =
was removed from the syntax we used. It didn&#39;t add value, even if it ad=
ded clarity at times. We also had functions at the end of paths, but that g=
oes beyond the JSON focus of the JSON Pointer goals, so those points are no=
t relevant here.<br>
</div></div><div><br>This discussion thread seems to be getting overly comp=
licated, but JSON Pointer changes should come from the JSON Pointer view po=
int and that specifications goals, not from short comings in JSON Patch.<br=
>
<br></div>-- <br>Matthew P. C. Morley

--bcaec54d4de8ac81d404d2c10686--

From jsr@10gen.com  Tue Jan  8 00:26:39 2013
Return-Path: <jsr@10gen.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8E05F21F88BE for <ietf@ietfa.amsl.com>; Tue,  8 Jan 2013 00:26:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.976
X-Spam-Level: 
X-Spam-Status: No, score=-2.976 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
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 S4EibqQFI1xH for <ietf@ietfa.amsl.com>; Tue,  8 Jan 2013 00:26:35 -0800 (PST)
Received: from mail-vb0-f52.google.com (mail-vb0-f52.google.com [209.85.212.52]) by ietfa.amsl.com (Postfix) with ESMTP id 834A821F88B2 for <ietf@ietf.org>; Tue,  8 Jan 2013 00:26:35 -0800 (PST)
Received: by mail-vb0-f52.google.com with SMTP id ez10so115955vbb.11 for <ietf@ietf.org>; Tue, 08 Jan 2013 00:26:35 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:x-gm-message-state; bh=eoGvVPUa/PXDhUq6iowTaeAsPk3HXROUAbbQHIuwgiI=; b=Cr26VyzJ6woDOL+u1N4tPoNaSQzAOuiLvLzk3Nhx8rIqTi1ewPV6k6dAYl1zNzpWn7 5sHCGhuSfe481qPJ6rSkgDOzgdgEiCykKau5Rd/Nwhf3LoUqcAh8vSFGLz1lZaLL+DvJ 43he4Ra+IEIhkg9k/g+7A20pQN7PjfVo+jBXMI4Eknx6D9NZuzM/nIMrUNkck3IdMqsT ZSjedpj5M3Fxvp1slUyVYS8DdnAInbbK23G9GL7VnwpAftMo53F4p++8nKfoliGvp3FH 2xTUm4Rq6fJkjHpiCAsp1IigfOnuLBNPuuy9yf0mvyTQQ4e+gSKyq3XpF/8t+Ao4eJcU FdDg==
MIME-Version: 1.0
Received: by 10.220.247.204 with SMTP id md12mr86099296vcb.27.1357633594934; Tue, 08 Jan 2013 00:26:34 -0800 (PST)
Received: by 10.59.5.6 with HTTP; Tue, 8 Jan 2013 00:26:34 -0800 (PST)
In-Reply-To: <CAOXDeqoOj1K_zBWVZbE2j4Vnp1pYZ1yUEp9nyTKZmp-QrAziqg@mail.gmail.com>
References: <20121211150057.28223.93310.idtracker@ietfa.amsl.com> <50cb04b9.86df440a.72fe.1e20SMTPIN_ADDED_BROKEN@mx.google.com> <CABP7RbeNsZ_rBWRjou=VG+hBhUKaOz+y1a0sSChwWiHte9znnQ@mail.gmail.com> <50cb5f3c.694c420a.38fb.39afSMTPIN_ADDED_BROKEN@mx.google.com> <CAChr6SxZRc3B_HCbw76kLe2dsRSr43r-gLpfMVnCUfJTrZdTLA@mail.gmail.com> <CABP7RbfA33huBFadMeXTTEt=MkjW8-d4DFH7+GLXGurnm9sSRw@mail.gmail.com> <CAOXDeqpPE4eNy_qJpDPdPHbCQakG9-hDcNZ3Sj9r4kWedByVzQ@mail.gmail.com> <CAChr6SwtS_=iS-k4mJm1vHjEvvGVzay5jDYeGheqsPZqO-89CQ@mail.gmail.com> <EABB8F51-C3B4-49F5-8672-5C2ABAC7043A@mnot.net> <CAChr6Sx7JdKM91EwJaSZ0Ra_F4FSqkuc3vzTY1LM=F_8sWho+Q@mail.gmail.com> <1357515310.6827.23.camel@polyglot> <CAChr6SyAq=7aQdZn54ihYK+0hDhL--2Oaq0RvehoNFbwKNNShA@mail.gmail.com> <CAChr6SxorKO20rGYi-e4YNF=HNGrwz8wPGKCFZQYWQwqsetjjg@mail.gmail.com> <CAOXDeqqE2mCLapwvjwQkme5VTpRCfmF0mFQcx02WW0-zi4i5=g@mail.gmail.com> <50EB4E8B.30700@versi.edu.au> <CAOXDeqoOj1K_zBWVZbE2j4Vnp1pYZ1yUEp9nyTKZmp-QrAziqg@mail.gmail.com>
Date: Tue, 8 Jan 2013 00:26:34 -0800
Message-ID: <CAD5Szk-U1LeBSfUgah8XXE2LZ=utR=0W-V7VsT6j-i2VixZerg@mail.gmail.com>
Subject: Re: [apps-discuss] Last Call: <draft-ietf-appsawg-json-pointer-07.txt> (JSON Pointer) to Proposed Standard
From: Jared Rosoff <jsr@10gen.com>
To: Matthew Morley <matt@mpcm.com>
Content-Type: multipart/alternative; boundary=bcaec54eede829467104d2c2b4ba
X-Gm-Message-State: ALoCoQndF/MNcVdVSHUsSG8irEFlCsHaAGwD2ggMyeKER0exAgOolPT47aU7dNRIQ0LfoD9H/pdn
X-Mailman-Approved-At: Tue, 08 Jan 2013 09:25:45 -0800
Cc: Mark Nottingham <mnot@mnot.net>, Conal Tuohy <conal.tuohy@versi.edu.au>, IESG <iesg@ietf.org>, IETF Apps Discuss <apps-discuss@ietf.org>, IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 08 Jan 2013 08:28:01 -0000

--bcaec54eede829467104d2c2b4ba
Content-Type: text/plain; charset=ISO-8859-1

hi team, i'm new to the discussion here, but wanted to jump in. i work on
mongodb, a json database, and i wanted to share how we deal with these
issues.

mongodb uses almost the same notation for pointers ("a.b.c" instead of
"/a/b/c"). We also index arrays in the same way as json pointer ( "a.0"
refers to the 0th element of the array called "a"). and this works fine in
practice. (ref: http://docs.mongodb.org/manual/core/document/#dot-notation)

our update syntax is different tho. the verbs in mongodb updates for json
documents are more specific:

set / unset / rename (operations on fields)
inc (increment integer values)
push / pop / pull (operations on arrays)
addToSet / removeFromSet (operations on arrays)

(ref http://docs.mongodb.org/manual/reference/operators/#update)

since update operations are more specific and type dependent, it's easy to
throw an error if an unexpected type is encountered (e.g. try to push onto
a field that has a non-array value) and to act smartly on empty fields ( if
path to push is empty, we assume it should be an array, create it, and then
push the value onto it).

i concur the the pointer syntax is fine and ambiguity comes from the
definition of operators in json patch.

-j


On Mon, Jan 7, 2013 at 10:26 PM, Matthew Morley <matt@mpcm.com> wrote:

> On Mon, Jan 7, 2013 at 5:39 PM, Conal Tuohy <conal.tuohy@versi.edu.au>wrote:
>
>>  On 07/01/13 13:23, Matthew Morley wrote:
>>
>>
>> For me the deficiency is not in the pointer, but patch format being
>> generated.
>>
>> One approach is to push that *one* test, structure conformity, into the
>> pointer syntax. Another is via the type operation.
>>
>> If a vague patch is generated, vague results are to be expected.
>>
>> It seems to me, on the contrary, that the deficiency is in the pointer
>> syntax, and I think it would be a mistake to try to work around that
>> deficiency in JSON Patch. Because aren't there other things which one might
>> do with JSON Pointer than use it with JSON Patch? There's been mention of
>> having it registered as a URI fragment identifier syntax for JSON for
>> example. JSON Pointers could then end up all over the place, outside of
>> patches. IMHO JSON Pointer needs to be taken seriously as a technology in
>> its own right.
>>
>
> Couldn't agree more about it being taken seriously in its own right. :)
>
> JSON Pointer for me exists outside of JSON Patch, always has and will do
> the way we think about structures. As it represents both a resolution path
> and an identity string (both ends of the path concept). I see value from
> the identity view, in describing a location that is aware of being inside
> an array.
>
> But JSON Pointer should not be changed just because of issues with JSON
> Patch, especially when JSON Patch is attempting to address those issues
> with other mechanisms within the specification. That is all I was trying to
> express. The syntax change should be for other reasons, if it is going to
> be made.
>
> My personal experience (for what its worth): In the past I've tried a
> number of syntaxes like JSON Pointer. Mostly a.b.c.0 and even a.b.c:0 at
> times to address the same issues suggested here. Though my experiences
> pushed me towards a single syntax using a.b.c.0, and thus my support for
> /a/b/c/0 over /a/b/c:0.
>
> The system at first used the . or : syntax, combined with dynamic tokens,
> being pointers themselves, to resolve other pointers. So it was not
> reasonable to know ahead of time if an end point was an array or an object.
>  "a.b.c.{d.e.f}" could end up in an array or in an object, depending on the
> value at d.e.f at the time of resolution. Especially with many layers of
> tokens to resolve, and changing data structures.
>
> I found in practice, it didn't really matter, so the choice of . or : was
> phased out. At the end of the day the two syntaxes point to mutually
> exclusive points within the data, so that `meta data` about the structure
> was removed from the syntax we used. It didn't add value, even if it added
> clarity at times. We also had functions at the end of paths, but that goes
> beyond the JSON focus of the JSON Pointer goals, so those points are not
> relevant here.
>
> This discussion thread seems to be getting overly complicated, but JSON
> Pointer changes should come from the JSON Pointer view point and that
> specifications goals, not from short comings in JSON Patch.
>
> --
> Matthew P. C. Morley
> _______________________________________________
> apps-discuss mailing list
> apps-discuss@ietf.org
> https://www.ietf.org/mailman/listinfo/apps-discuss
>
>

--bcaec54eede829467104d2c2b4ba
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div>hi team, i&#39;m new to the discussion here, but wanted to jump in. i =
work on mongodb, a json database, and i wanted to share how we deal with th=
ese issues.=A0</div><div><br></div>mongodb uses almost the same notation fo=
r pointers (&quot;a.b.c&quot; instead of &quot;/a/b/c&quot;). We also index=
 arrays in the same way as json pointer ( &quot;a.0&quot; refers to the 0th=
 element of the array called &quot;a&quot;). and this works fine in practic=
e. (ref:=A0<a href=3D"http://docs.mongodb.org/manual/core/document/#dot-not=
ation">http://docs.mongodb.org/manual/core/document/#dot-notation</a>)=A0<d=
iv>
<br></div><div>our update syntax is different tho. the verbs in mongodb upd=
ates for json documents are more specific:=A0</div><div><br></div><div>set =
/ unset / rename (operations on fields)=A0</div><div>inc (increment integer=
 values)=A0</div>
<div>push / pop / pull (operations on arrays)=A0</div><div>addToSet / remov=
eFromSet (operations on arrays)=A0</div><div><br></div><div>(ref <a href=3D=
"http://docs.mongodb.org/manual/reference/operators/#update">http://docs.mo=
ngodb.org/manual/reference/operators/#update</a>)=A0</div>
<div><br></div><div>since update operations are more specific and type depe=
ndent, it&#39;s easy to throw an error if an unexpected type is encountered=
 (e.g. try to push onto a field that has a non-array value) and to act smar=
tly on empty fields ( if path to push is empty, we assume it should be an a=
rray, create it, and then push the value onto it).=A0</div>
<div><br></div><div>i concur the the pointer syntax is fine and ambiguity c=
omes from the definition of operators in json patch.=A0</div><div><br></div=
><div>-j</div><div><br></div><div><br><div class=3D"gmail_quote">On Mon, Ja=
n 7, 2013 at 10:26 PM, Matthew Morley <span dir=3D"ltr">&lt;<a href=3D"mail=
to:matt@mpcm.com" target=3D"_blank">matt@mpcm.com</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div class=3D"im">On Mon, Jan 7, 2013 at 5:3=
9 PM, Conal Tuohy <span dir=3D"ltr">&lt;<a href=3D"mailto:conal.tuohy@versi=
.edu.au" target=3D"_blank">conal.tuohy@versi.edu.au</a>&gt;</span> wrote:<b=
r>
</div><div class=3D"gmail_quote"><div class=3D"im"><blockquote class=3D"gma=
il_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-lef=
t:1ex">

 =20
   =20
 =20
  <div bgcolor=3D"#FFFFFF" text=3D"#000000"><div>
    <div>On 07/01/13 13:23, Matthew Morley
      wrote:<br>
    </div>
    <blockquote type=3D"cite">
     =20
      <br>
      For me the deficiency is not in the pointer, but patch format
      being generated.<br>
      <br>
      One approach is to push that *one* test, structure=A0conformity,
      into the pointer syntax.=A0Another is via the type operation.<br>
      <br>
      If a vague patch is generated, vague results are to be expected.<br>
    </blockquote></div>
    It seems to me, on the contrary, that the deficiency is in the
    pointer syntax, and I think it would be a mistake to try to work
    around that deficiency in JSON Patch. Because aren&#39;t there other
    things which one might do with JSON Pointer than use it with JSON
    Patch? There&#39;s been mention of having it registered as a URI
    fragment identifier syntax for JSON for example. JSON Pointers could
    then end up all over the place, outside of patches. IMHO JSON
    Pointer needs to be taken seriously as a technology in its own
    right.=A0</div></blockquote></div><div><br>Couldn&#39;t agree more abou=
t it being taken seriously in its own right. :)<br><br>JSON Pointer for me =
exists outside of JSON Patch, always has and will do the way we think about=
 structures. As it represents both a resolution path and an identity string=
 (both ends of the path concept). I see value from the identity view, in de=
scribing a location that is aware of being inside an array.</div>

<div><br>But JSON Pointer should not be changed just because of issues with=
 JSON Patch, especially when JSON Patch is attempting to address those issu=
es with other mechanisms within the specification. That is all I was trying=
 to express. The syntax change should be for other reasons, if it is going =
to be made.<br>

<br></div><div>My personal experience (for what its worth): In the past I&#=
39;ve tried a number of syntaxes like JSON Pointer. Mostly a.b.c.0 and even=
 a.b.c:0 at times to address the same issues suggested here. Though my expe=
riences pushed me towards a single syntax using a.b.c.0, and thus my suppor=
t for /a/b/c/0 over /a/b/c:0.<br>

<br>The system at first used the . or : syntax, combined with dynamic token=
s, being pointers themselves, to resolve other pointers. So it was not reas=
onable to know ahead of time if an end point was an array or an object. =A0=
&quot;a.b.c.{d.e.f}&quot; could end up in an array or in an object, dependi=
ng on the value at d.e.f at the time of resolution. Especially with many la=
yers of tokens to resolve, and changing data structures.<br>

<br>I found in practice, it didn&#39;t really matter, so the choice of . or=
 : was phased out. At the end of the day the two syntaxes point to mutually=
 exclusive points within the data, so that `meta data` about the structure =
was removed from the syntax we used. It didn&#39;t add value, even if it ad=
ded clarity at times. We also had functions at the end of paths, but that g=
oes beyond the JSON focus of the JSON Pointer goals, so those points are no=
t relevant here.<br>

</div></div><div><br>This discussion thread seems to be getting overly comp=
licated, but JSON Pointer changes should come from the JSON Pointer view po=
int and that specifications goals, not from short comings in JSON Patch.<sp=
an class=3D"HOEnZb"><font color=3D"#888888"><br>

<br></font></span></div><span class=3D"HOEnZb"><font color=3D"#888888">-- <=
br>Matthew P. C. Morley
</font></span><br>_______________________________________________<br>
apps-discuss mailing list<br>
<a href=3D"mailto:apps-discuss@ietf.org">apps-discuss@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/apps-discuss" target=3D"_b=
lank">https://www.ietf.org/mailman/listinfo/apps-discuss</a><br>
<br></blockquote></div><br></div>

--bcaec54eede829467104d2c2b4ba--

From gregory.mirsky@ericsson.com  Tue Jan  8 08:45:57 2013
Return-Path: <gregory.mirsky@ericsson.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5683F1F0CB3; Tue,  8 Jan 2013 08:45:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.598
X-Spam-Level: 
X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, 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 id6hRikxY2Pf; Tue,  8 Jan 2013 08:45:55 -0800 (PST)
Received: from imr4.ericy.com (imr4.ericy.com [198.24.6.9]) by ietfa.amsl.com (Postfix) with ESMTP id 9D67F21F8758; Tue,  8 Jan 2013 08:45:55 -0800 (PST)
Received: from EUSAAHC005.ericsson.se ([147.117.188.87]) by imr4.ericy.com (8.14.3/8.14.3/Debian-9.1ubuntu1) with ESMTP id r08H0K39001032; Tue, 8 Jan 2013 11:00:28 -0600
Received: from EUSAAMB103.ericsson.se ([147.117.188.120]) by EUSAAHC005.ericsson.se ([147.117.188.87]) with mapi id 14.02.0318.004; Tue, 8 Jan 2013 11:45:46 -0500
From: Gregory Mirsky <gregory.mirsky@ericsson.com>
To: Loa Andersson <loa@pi.nu>
Subject: RE: [PWE3] Gen-ART review of draft-ietf-pwe3-mpls-eth-oam-iwk-06
Thread-Topic: [PWE3] Gen-ART review of draft-ietf-pwe3-mpls-eth-oam-iwk-06
Thread-Index: Ac3pBnav5FvEKm/XSt61rsAl/DM1NgBum98AAKBvoIAAHbUbAAABDUSw
Date: Tue, 8 Jan 2013 16:45:46 +0000
Message-ID: <7347100B5761DC41A166AC17F22DF112039212@eusaamb103.ericsson.se>
References: <CD08F2D5.6DC40%nabil.n.bitar@verizon.com> <CD0C3AE6.6E673%nabil.n.bitar@verizon.com> <CA+RyBmWWUQ+y7Mc1nG3+KndXCytfUkQqnNTg4ezpK2JcGyiCuQ@mail.gmail.com> <50EBFCA0.3060307@pi.nu>
In-Reply-To: <50EBFCA0.3060307@pi.nu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [147.117.188.135]
Content-Type: multipart/alternative; boundary="_000_7347100B5761DC41A166AC17F22DF112039212eusaamb103ericsso_"
MIME-Version: 1.0
X-Mailman-Approved-At: Tue, 08 Jan 2013 09:25:47 -0800
Cc: "pwe3@ietf.org" <pwe3@ietf.org>, "gen-art@ietf.org" <gen-art@ietf.org>, "dinmohan@hotmail.com" <dinmohan@hotmail.com>, "sajassi@cisco.com" <sajassi@cisco.com>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 08 Jan 2013 16:45:57 -0000

--_000_7347100B5761DC41A166AC17F22DF112039212eusaamb103ericsso_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Dear Huub and Loa,
my brain did s/Reverese/Remote/ by itself. Indeed, 802.1ag and Y.1731 use R=
DI for Remote Defect Indication, and nothing in Reverse. And that how draft=
-ietf-pwe3-mpls-eth-oam-iwk-06 should expand RDI as well.

        Regards,
                Greg

-----Original Message-----
From: pwe3-bounces@ietf.org [mailto:pwe3-bounces@ietf.org] On Behalf Of Loa=
 Andersson
Sent: Tuesday, January 08, 2013 3:02 AM
To: Greg Mirsky
Cc: ietf@ietf.org; gen-art@ietf.org; dinmohan@hotmail.com; sajassi@cisco.co=
m; pwe3@ietf.org
Subject: Re: [PWE3] Gen-ART review of draft-ietf-pwe3-mpls-eth-oam-iwk-06

Greg,

RFC 6428 expands RDI as:

    RDI: Remote Defect Indication

/Loa

On 2013-01-07 21:51, Greg Mirsky wrote:
> Dear Nabil,
> can we avoid different interpretation of the same abbreviation (RDI):
>
>     RDI   Remote Defect Indication for Continuity Check Message
>
>     RDI   Reverse Defect Indication
>
> AFAIK, the latter form is the interpretation used by both IEEE 802.1ag
> and Y.1731. How useful is the first form?
>
> Regards,
>
> Greg
>
>
>
> On Fri, Jan 4, 2013 at 8:17 AM, Bitar, Nabil N
> <nabil.n.bitar@verizon.com <mailto:nabil.n.bitar@verizon.com>> wrote:
>
>     Hi Dave,
>     Related to abbreviations comment below and to be clearer, I renamed
>     the original terminology section to "Abbreviations and Terminology".
>     I also created a subsection called "Abbreviations" ,and
>     "Terminology" became the second subsection.  Here iis how the
> edits look
>
>
>       3. Abbreviations and Terminology____
>
>
>         3.1. Abbreviations____
>
>     AISAlarm Indication Signal____
>
>     ACAttachment Circuit____
>
>     BFDBidirectional Forwarding Detection____
>
>     CCContinuity Check____
>
>     CCMContinuity Check Message____
>
>     CECustomer Equipment____
>
>     CVConnectivity Verification____
>
>     E-LMI Ethernet Local Management Interface____
>
>     EVCEthernet Virtual Circuit____
>
>     LDPLabel Distribution Protocol____
>
>     LoSLoss of Signal____
>
>     MAMaintenance Association____
>
>     MDMaintenance Domain____
>
>     MEMaintenance Entity____
>
>     MEGMaintenance Entity Group____
>
>     MEPMaintenance End Point____
>
>     MIPMaintenance End Point____
>
>     MPLSMultiprotocol Label Switching____
>
>     MS-PW Multi-Segment Pseudowire____
>
>     NSNative Service____
>
>     OAMOperations, Administration, and Maintenance____
>
>     PEProvider Edge____
>
>     PSNPacket Switched Network____
>
>     PWPseudowire____
>
>     RDIRemote Defect Indication for Continuity Check Message____
>
>         RDI   Reverse Defect Indication
>
>     S-PESwitching Provider Edge____
>
>     TLVType Length Value____
>
>     T-PETerminating Provider Edge____
>
>     __ __
>
>
>         3.2. Terminology____
>
>     This document uses the following terms with corresponding
>     definitions: ____
>
>     - MD Level:Maintenance Domain (MD) Level which identifies a value in
>     the range of 0-7 associated with Ethernet OAM frame. MD Level
>     identifies the span of the Ethernet OAM frame.____
>
>     - MEP:Maintenance End Point is responsible for origination and
>     termination of OAM frames for a given MEG.____
>
>     - MIP: Maintenance Intermediate Point is located between peer MEPs
>     and can process OAM frames but does not initiate or terminate
> them.____
>
>     Further, this document also uses the terminology and conventions
>     used in [RFC6310].____
>
>
>
>     Thanks,
>
>     Nabil
>
>
>     From: <Bitar>, Nabil N <nabil.n.bitar@one.verizon.com
>     <mailto:nabil.n.bitar@one.verizon.com>>
>     Date: Wednesday, January 2, 2013 11:28 AM
>     To: "Black, David" <david.black@emc.com
>     <mailto:david.black@emc.com>>, "dinmohan@hotmail.com
>     <mailto:dinmohan@hotmail.com>" <dinmohan@hotmail.com
>     <mailto:dinmohan@hotmail.com>>, "Bitar, Nabil N"
>     <nabil.n.bitar@one.verizon.com
>     <mailto:nabil.n.bitar@one.verizon.com>>, Sagessi <sajassi@cisco.com
>     <mailto:sajassi@cisco.com>>, "gen-art@ietf.org
>     <mailto:gen-art@ietf.org>" <gen-art@ietf.org <mailto:gen-art@ietf.org=
>>
>     Cc: "pwe3@ietf.org <mailto:pwe3@ietf.org>" <pwe3@ietf.org
>     <mailto:pwe3@ietf.org>>, "ietf@ietf.org <mailto:ietf@ietf.org>"
>     <ietf@ietf.org <mailto:ietf@ietf.org>>
>     Subject: Re: Gen-ART review of draft-ietf-pwe3-mpls-eth-oam-iwk-06
>
>     Hi Dave,
>     Sorry for a late reply addressing your comments. Please, see inline.
>
>     Thanks,
>     Nabil
>
>     From: "Black, David" <david.black@emc.com <mailto:david.black@emc.com=
>>
>     Date: Monday, August 20, 2012 8:57 PM
>     To: "dinmohan@hotmail.com <mailto:dinmohan@hotmail.com>"
>     <dinmohan@hotmail.com <mailto:dinmohan@hotmail.com>>, "Bitar, Nabil
>     N" <nabil.n.bitar@one.verizon.com
>     <mailto:nabil.n.bitar@one.verizon.com>>, Sagessi <sajassi@cisco.com
>     <mailto:sajassi@cisco.com>>, "gen-art@ietf.org
>     <mailto:gen-art@ietf.org>" <gen-art@ietf.org <mailto:gen-art@ietf.org=
>>
>     Cc: "Black, David" <david.black@emc.com
>     <mailto:david.black@emc.com>>, "pwe3@ietf.org
>     <mailto:pwe3@ietf.org>" <pwe3@ietf.org <mailto:pwe3@ietf.org>>,
>     "ietf@ietf.org <mailto:ietf@ietf.org>" <ietf@ietf.org
>     <mailto:ietf@ietf.org>>
>     Subject: Gen-ART review of draft-ietf-pwe3-mpls-eth-oam-iwk-06
>
>     I am the assigned Gen-ART reviewer for this draft. For background on
>     Gen-ART, please
>     see the FAQ at
>     <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>
>     Please resolve these comments along with any other Last Call
>     comments you may receive.
>
>     Document: draft-ietf-pwe3-mpls-eth-oam-iwk-06
>     Reviewer: David L. Black
>     Review Date: August 20, 2012
>     IETF LC End Date: August 20, 2012
>
>     Summary:
>     This draft is basically ready for publication, but has nits that
>     should be fixed before publication.
>
>     <NB> Thanks.
>
>     This draft covers defect behavior for Ethernet pseudowires,
>
>     including defect state mapping and PE defect reporting behavior.
>
>     The draft is generally in good shape.  I found a few minor nits.
>
>     1) The draft uses a lot of acronyms - while each acronym appears
> to
>
>     be expanded on first use, an additional section near the start of
> the
>
>     draft listing all of them would be helpful.
>
>
>     <NB> Done.
>
>     2) There's a typo in the first paragraph of section 2:
>
>           covers the following Ethernet OAM (Opertaions,
> Administration and
>
>     Opertaions -> Operations.
>
>
>     <NB> Thanks. Done.
>
>     3) The following normative reference is incomplete - please add
>     additional
>
>     information that will enable a reader to locate the referenced docume=
nt:
>
>           [MEF16] "Ethernet Local Management Interface", MEF16, January
>     2006.
>
>
>     [MEF16] "Ethernet Local Management Interface", Metro Ethernet Forum
>     Technical Specification MEF16, January 2006.
>
>     <NB> changed it to :
>
>     4) idnits2.12.13 did not like the pagination:
>
>        =3D=3D The page length should not exceed 58 lines per page, but th=
ere
>     was 22
>           longer pages, the longest (page 1) being 61 lines
>
>     <NB> That will be fixed.
>     Thanks,
>     --David
>     ----------------------------------------------------
>     David L. Black, Distinguished Engineer
>     EMC Corporation, 176 South St., Hopkinton, MA  01748
>     +1 (508) 293-7953 <tel:%2B1%20%28508%29%20293-7953>             FAX:
>     +1 (508) 293-7786 <tel:%2B1%20%28508%29%20293-7786>
>     david.black@emc.com <mailto:david.black@emc.com>        Mobile: +1
>     (978) 394-7754 <tel:%2B1%20%28978%29%20394-7754>
>     ----------------------------------------------------
>
>     _______________________________________________
>     pwe3 mailing list
>     pwe3@ietf.org <mailto:pwe3@ietf.org>
>     https://www.ietf.org/mailman/listinfo/pwe3
>
>
>
>
> _______________________________________________
> pwe3 mailing list
> pwe3@ietf.org
> https://www.ietf.org/mailman/listinfo/pwe3
>

--


Loa Andersson                         email: loa.andersson@ericsson.com
Sr Strategy and Standards Manager            loa@pi.nu
Ericsson Inc                          phone: +46 10 717 52 13
                                              +46 767 72 92 13 ____________=
___________________________________
pwe3 mailing list
pwe3@ietf.org
https://www.ietf.org/mailman/listinfo/pwe3


--_000_7347100B5761DC41A166AC17F22DF112039212eusaamb103ericsso_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Exchange Server">
<!-- converted from rtf -->
<style><!-- .EmailQuote { margin-left: 1pt; padding-left: 4pt; border-left:=
 #800000 2px solid; } --></style>
</head>
<body>
<font face=3D"Arial" size=3D"2"><span style=3D"font-size:10pt;">
<div>Dear Huub and Loa,</div>
<div>my brain did s/Reverese/Remote/ by itself. Indeed, 802.1ag and Y.1731 =
use RDI for Remote Defect Indication, and nothing in Reverse. And that how =
draft-ietf-pwe3-mpls-eth-oam-iwk-06 should expand RDI as well.</div>
<div>&nbsp;</div>
<div>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Regards,</div>
<div>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp; Greg</div>
<div>&nbsp;</div>
<div>-----Original Message-----</div>
<div>From: pwe3-bounces@ietf.org [<a href=3D"mailto:pwe3-bounces@ietf.org">=
<font color=3D"blue"><u>mailto:pwe3-bounces@ietf.org</u></font></a>] On Beh=
alf Of Loa Andersson</div>
<div>Sent: Tuesday, January 08, 2013 3:02 AM</div>
<div>To: Greg Mirsky</div>
<div>Cc: ietf@ietf.org; gen-art@ietf.org; dinmohan@hotmail.com; sajassi@cis=
co.com; pwe3@ietf.org</div>
<div>Subject: Re: [PWE3] Gen-ART review of draft-ietf-pwe3-mpls-eth-oam-iwk=
-06</div>
<div>&nbsp;</div>
<div>Greg,</div>
<div>&nbsp;</div>
<div>RFC 6428 expands RDI as:</div>
<div>&nbsp;</div>
<div>&nbsp;&nbsp;&nbsp; RDI: Remote Defect Indication</div>
<div>&nbsp;</div>
<div>/Loa</div>
<div>&nbsp;</div>
<div>On 2013-01-07 21:51, Greg Mirsky wrote:</div>
<div>&gt; Dear Nabil,</div>
<div>&gt; can we avoid different interpretation of the same abbreviation (R=
DI):</div>
<div>&gt;</div>
<div>&gt;&nbsp;&nbsp;&nbsp;&nbsp; RDI&nbsp;&nbsp; Remote Defect Indication =
for Continuity Check Message</div>
<div>&gt;</div>
<div>&gt;&nbsp;&nbsp;&nbsp;&nbsp; RDI&nbsp;&nbsp; Reverse Defect Indication=
</div>
<div>&gt;</div>
<div>&gt; AFAIK, the latter form is the interpretation used by both IEEE 80=
2.1ag </div>
<div>&gt; and Y.1731. How useful is the first form?</div>
<div>&gt;</div>
<div>&gt; Regards,</div>
<div>&gt;</div>
<div>&gt; Greg</div>
<div>&gt;</div>
<div>&gt;</div>
<div>&gt;</div>
<div>&gt; On Fri, Jan 4, 2013 at 8:17 AM, Bitar, Nabil N </div>
<div>&gt; &lt;nabil.n.bitar@verizon.com &lt;<a href=3D"mailto:nabil.n.bitar=
@verizon.com"><font color=3D"blue"><u>mailto:nabil.n.bitar@verizon.com</u><=
/font></a>&gt;&gt; wrote:</div>
<div>&gt;</div>
<div>&gt;&nbsp;&nbsp;&nbsp;&nbsp; Hi Dave,</div>
<div>&gt;&nbsp;&nbsp;&nbsp;&nbsp; Related to abbreviations comment below an=
d to be clearer, I renamed</div>
<div>&gt;&nbsp;&nbsp;&nbsp;&nbsp; the original terminology section to &quot=
;Abbreviations and Terminology&quot;.</div>
<div>&gt;&nbsp;&nbsp;&nbsp;&nbsp; I also created a subsection called &quot;=
Abbreviations&quot; ,and</div>
<div>&gt;&nbsp;&nbsp;&nbsp;&nbsp; &quot;Terminology&quot; became the second=
 subsection.&nbsp; Here iis how the </div>
<div>&gt; edits look</div>
<div>&gt;</div>
<div>&gt;</div>
<div>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 3. Abbreviations and Terminol=
ogy____</div>
<div>&gt;</div>
<div>&gt;</div>
<div>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 3.1. Abbreviation=
s____</div>
<div>&gt;</div>
<div>&gt;&nbsp;&nbsp;&nbsp;&nbsp; AISAlarm Indication Signal____</div>
<div>&gt;</div>
<div>&gt;&nbsp;&nbsp;&nbsp;&nbsp; ACAttachment Circuit____</div>
<div>&gt;</div>
<div>&gt;&nbsp;&nbsp;&nbsp;&nbsp; BFDBidirectional Forwarding Detection____=
</div>
<div>&gt;</div>
<div>&gt;&nbsp;&nbsp;&nbsp;&nbsp; CCContinuity Check____</div>
<div>&gt;</div>
<div>&gt;&nbsp;&nbsp;&nbsp;&nbsp; CCMContinuity Check Message____</div>
<div>&gt;</div>
<div>&gt;&nbsp;&nbsp;&nbsp;&nbsp; CECustomer Equipment____</div>
<div>&gt;</div>
<div>&gt;&nbsp;&nbsp;&nbsp;&nbsp; CVConnectivity Verification____</div>
<div>&gt;</div>
<div>&gt;&nbsp;&nbsp;&nbsp;&nbsp; E-LMI Ethernet Local Management Interface=
____</div>
<div>&gt;</div>
<div>&gt;&nbsp;&nbsp;&nbsp;&nbsp; EVCEthernet Virtual Circuit____</div>
<div>&gt;</div>
<div>&gt;&nbsp;&nbsp;&nbsp;&nbsp; LDPLabel Distribution Protocol____</div>
<div>&gt;</div>
<div>&gt;&nbsp;&nbsp;&nbsp;&nbsp; LoSLoss of Signal____</div>
<div>&gt;</div>
<div>&gt;&nbsp;&nbsp;&nbsp;&nbsp; MAMaintenance Association____</div>
<div>&gt;</div>
<div>&gt;&nbsp;&nbsp;&nbsp;&nbsp; MDMaintenance Domain____</div>
<div>&gt;</div>
<div>&gt;&nbsp;&nbsp;&nbsp;&nbsp; MEMaintenance Entity____</div>
<div>&gt;</div>
<div>&gt;&nbsp;&nbsp;&nbsp;&nbsp; MEGMaintenance Entity Group____</div>
<div>&gt;</div>
<div>&gt;&nbsp;&nbsp;&nbsp;&nbsp; MEPMaintenance End Point____</div>
<div>&gt;</div>
<div>&gt;&nbsp;&nbsp;&nbsp;&nbsp; MIPMaintenance End Point____</div>
<div>&gt;</div>
<div>&gt;&nbsp;&nbsp;&nbsp;&nbsp; MPLSMultiprotocol Label Switching____</di=
v>
<div>&gt;</div>
<div>&gt;&nbsp;&nbsp;&nbsp;&nbsp; MS-PW Multi-Segment Pseudowire____</div>
<div>&gt;</div>
<div>&gt;&nbsp;&nbsp;&nbsp;&nbsp; NSNative Service____</div>
<div>&gt;</div>
<div>&gt;&nbsp;&nbsp;&nbsp;&nbsp; OAMOperations, Administration, and Mainte=
nance____</div>
<div>&gt;</div>
<div>&gt;&nbsp;&nbsp;&nbsp;&nbsp; PEProvider Edge____</div>
<div>&gt;</div>
<div>&gt;&nbsp;&nbsp;&nbsp;&nbsp; PSNPacket Switched Network____</div>
<div>&gt;</div>
<div>&gt;&nbsp;&nbsp;&nbsp;&nbsp; PWPseudowire____</div>
<div>&gt;</div>
<div>&gt;&nbsp;&nbsp;&nbsp;&nbsp; RDIRemote Defect Indication for Continuit=
y Check Message____</div>
<div>&gt;</div>
<div>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; RDI&nbsp;&nbsp; R=
everse Defect Indication</div>
<div>&gt;</div>
<div>&gt;&nbsp;&nbsp;&nbsp;&nbsp; S-PESwitching Provider Edge____</div>
<div>&gt;</div>
<div>&gt;&nbsp;&nbsp;&nbsp;&nbsp; TLVType Length Value____</div>
<div>&gt;</div>
<div>&gt;&nbsp;&nbsp;&nbsp;&nbsp; T-PETerminating Provider Edge____</div>
<div>&gt;</div>
<div>&gt;&nbsp;&nbsp;&nbsp;&nbsp; __ __</div>
<div>&gt;</div>
<div>&gt;</div>
<div>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 3.2. Terminology_=
___</div>
<div>&gt;</div>
<div>&gt;&nbsp;&nbsp;&nbsp;&nbsp; This document uses the following terms wi=
th corresponding</div>
<div>&gt;&nbsp;&nbsp;&nbsp;&nbsp; definitions: ____</div>
<div>&gt;</div>
<div>&gt;&nbsp;&nbsp;&nbsp;&nbsp; - MD Level:Maintenance Domain (MD) Level =
which identifies a value in</div>
<div>&gt;&nbsp;&nbsp;&nbsp;&nbsp; the range of 0-7 associated with Ethernet=
 OAM frame. MD Level</div>
<div>&gt;&nbsp;&nbsp;&nbsp;&nbsp; identifies the span of the Ethernet OAM f=
rame.____</div>
<div>&gt;</div>
<div>&gt;&nbsp;&nbsp;&nbsp;&nbsp; - MEP:Maintenance End Point is responsibl=
e for origination and</div>
<div>&gt;&nbsp;&nbsp;&nbsp;&nbsp; termination of OAM frames for a given MEG=
.____</div>
<div>&gt;</div>
<div>&gt;&nbsp;&nbsp;&nbsp;&nbsp; - MIP: Maintenance Intermediate Point is =
located between peer MEPs</div>
<div>&gt;&nbsp;&nbsp;&nbsp;&nbsp; and can process OAM frames but does not i=
nitiate or terminate </div>
<div>&gt; them.____</div>
<div>&gt;</div>
<div>&gt;&nbsp;&nbsp;&nbsp;&nbsp; Further, this document also uses the term=
inology and conventions</div>
<div>&gt;&nbsp;&nbsp;&nbsp;&nbsp; used in [RFC6310].____</div>
<div>&gt;</div>
<div>&gt;</div>
<div>&gt;</div>
<div>&gt;&nbsp;&nbsp;&nbsp;&nbsp; Thanks,</div>
<div>&gt;</div>
<div>&gt;&nbsp;&nbsp;&nbsp;&nbsp; Nabil</div>
<div>&gt;</div>
<div>&gt;</div>
<div>&gt;&nbsp;&nbsp;&nbsp;&nbsp; From: &lt;Bitar&gt;, Nabil N &lt;nabil.n.=
bitar@one.verizon.com</div>
<div>&gt;&nbsp;&nbsp;&nbsp;&nbsp; &lt;<a href=3D"mailto:nabil.n.bitar@one.v=
erizon.com"><font color=3D"blue"><u>mailto:nabil.n.bitar@one.verizon.com</u=
></font></a>&gt;&gt;</div>
<div>&gt;&nbsp;&nbsp;&nbsp;&nbsp; Date: Wednesday, January 2, 2013 11:28 AM=
</div>
<div>&gt;&nbsp;&nbsp;&nbsp;&nbsp; To: &quot;Black, David&quot; &lt;david.bl=
ack@emc.com</div>
<div>&gt;&nbsp;&nbsp;&nbsp;&nbsp; &lt;<a href=3D"mailto:david.black@emc.com=
"><font color=3D"blue"><u>mailto:david.black@emc.com</u></font></a>&gt;&gt;=
, &quot;dinmohan@hotmail.com</div>
<div>&gt;&nbsp;&nbsp;&nbsp;&nbsp; &lt;<a href=3D"mailto:dinmohan@hotmail.co=
m"><font color=3D"blue"><u>mailto:dinmohan@hotmail.com</u></font></a>&gt;&q=
uot; &lt;dinmohan@hotmail.com</div>
<div>&gt;&nbsp;&nbsp;&nbsp;&nbsp; &lt;<a href=3D"mailto:dinmohan@hotmail.co=
m"><font color=3D"blue"><u>mailto:dinmohan@hotmail.com</u></font></a>&gt;&g=
t;, &quot;Bitar, Nabil N&quot;</div>
<div>&gt;&nbsp;&nbsp;&nbsp;&nbsp; &lt;nabil.n.bitar@one.verizon.com</div>
<div>&gt;&nbsp;&nbsp;&nbsp;&nbsp; &lt;<a href=3D"mailto:nabil.n.bitar@one.v=
erizon.com"><font color=3D"blue"><u>mailto:nabil.n.bitar@one.verizon.com</u=
></font></a>&gt;&gt;, Sagessi &lt;sajassi@cisco.com</div>
<div>&gt;&nbsp;&nbsp;&nbsp;&nbsp; &lt;<a href=3D"mailto:sajassi@cisco.com">=
<font color=3D"blue"><u>mailto:sajassi@cisco.com</u></font></a>&gt;&gt;, &q=
uot;gen-art@ietf.org</div>
<div>&gt;&nbsp;&nbsp;&nbsp;&nbsp; &lt;<a href=3D"mailto:gen-art@ietf.org"><=
font color=3D"blue"><u>mailto:gen-art@ietf.org</u></font></a>&gt;&quot; &lt=
;gen-art@ietf.org &lt;<a href=3D"mailto:gen-art@ietf.org"><font color=3D"bl=
ue"><u>mailto:gen-art@ietf.org</u></font></a>&gt;&gt;</div>
<div>&gt;&nbsp;&nbsp;&nbsp;&nbsp; Cc: &quot;pwe3@ietf.org &lt;<a href=3D"ma=
ilto:pwe3@ietf.org"><font color=3D"blue"><u>mailto:pwe3@ietf.org</u></font>=
</a>&gt;&quot; &lt;pwe3@ietf.org</div>
<div>&gt;&nbsp;&nbsp;&nbsp;&nbsp; &lt;<a href=3D"mailto:pwe3@ietf.org"><fon=
t color=3D"blue"><u>mailto:pwe3@ietf.org</u></font></a>&gt;&gt;, &quot;ietf=
@ietf.org &lt;<a href=3D"mailto:ietf@ietf.org"><font color=3D"blue"><u>mail=
to:ietf@ietf.org</u></font></a>&gt;&quot;</div>
<div>&gt;&nbsp;&nbsp;&nbsp;&nbsp; &lt;ietf@ietf.org &lt;<a href=3D"mailto:i=
etf@ietf.org"><font color=3D"blue"><u>mailto:ietf@ietf.org</u></font></a>&g=
t;&gt;</div>
<div>&gt;&nbsp;&nbsp;&nbsp;&nbsp; Subject: Re: Gen-ART review of draft-ietf=
-pwe3-mpls-eth-oam-iwk-06</div>
<div>&gt;</div>
<div>&gt;&nbsp;&nbsp;&nbsp;&nbsp; Hi Dave,</div>
<div>&gt;&nbsp;&nbsp;&nbsp;&nbsp; Sorry for a late reply addressing your co=
mments. Please, see inline.</div>
<div>&gt;</div>
<div>&gt;&nbsp;&nbsp;&nbsp;&nbsp; Thanks,</div>
<div>&gt;&nbsp;&nbsp;&nbsp;&nbsp; Nabil</div>
<div>&gt;</div>
<div>&gt;&nbsp;&nbsp;&nbsp;&nbsp; From: &quot;Black, David&quot; &lt;david.=
black@emc.com &lt;<a href=3D"mailto:david.black@emc.com"><font color=3D"blu=
e"><u>mailto:david.black@emc.com</u></font></a>&gt;&gt;</div>
<div>&gt;&nbsp;&nbsp;&nbsp;&nbsp; Date: Monday, August 20, 2012 8:57 PM</di=
v>
<div>&gt;&nbsp;&nbsp;&nbsp;&nbsp; To: &quot;dinmohan@hotmail.com &lt;<a hre=
f=3D"mailto:dinmohan@hotmail.com"><font color=3D"blue"><u>mailto:dinmohan@h=
otmail.com</u></font></a>&gt;&quot;</div>
<div>&gt;&nbsp;&nbsp;&nbsp;&nbsp; &lt;dinmohan@hotmail.com &lt;<a href=3D"m=
ailto:dinmohan@hotmail.com"><font color=3D"blue"><u>mailto:dinmohan@hotmail=
.com</u></font></a>&gt;&gt;, &quot;Bitar, Nabil</div>
<div>&gt;&nbsp;&nbsp;&nbsp;&nbsp; N&quot; &lt;nabil.n.bitar@one.verizon.com=
</div>
<div>&gt;&nbsp;&nbsp;&nbsp;&nbsp; &lt;<a href=3D"mailto:nabil.n.bitar@one.v=
erizon.com"><font color=3D"blue"><u>mailto:nabil.n.bitar@one.verizon.com</u=
></font></a>&gt;&gt;, Sagessi &lt;sajassi@cisco.com</div>
<div>&gt;&nbsp;&nbsp;&nbsp;&nbsp; &lt;<a href=3D"mailto:sajassi@cisco.com">=
<font color=3D"blue"><u>mailto:sajassi@cisco.com</u></font></a>&gt;&gt;, &q=
uot;gen-art@ietf.org</div>
<div>&gt;&nbsp;&nbsp;&nbsp;&nbsp; &lt;<a href=3D"mailto:gen-art@ietf.org"><=
font color=3D"blue"><u>mailto:gen-art@ietf.org</u></font></a>&gt;&quot; &lt=
;gen-art@ietf.org &lt;<a href=3D"mailto:gen-art@ietf.org"><font color=3D"bl=
ue"><u>mailto:gen-art@ietf.org</u></font></a>&gt;&gt;</div>
<div>&gt;&nbsp;&nbsp;&nbsp;&nbsp; Cc: &quot;Black, David&quot; &lt;david.bl=
ack@emc.com</div>
<div>&gt;&nbsp;&nbsp;&nbsp;&nbsp; &lt;<a href=3D"mailto:david.black@emc.com=
"><font color=3D"blue"><u>mailto:david.black@emc.com</u></font></a>&gt;&gt;=
, &quot;pwe3@ietf.org</div>
<div>&gt;&nbsp;&nbsp;&nbsp;&nbsp; &lt;<a href=3D"mailto:pwe3@ietf.org"><fon=
t color=3D"blue"><u>mailto:pwe3@ietf.org</u></font></a>&gt;&quot; &lt;pwe3@=
ietf.org &lt;<a href=3D"mailto:pwe3@ietf.org"><font color=3D"blue"><u>mailt=
o:pwe3@ietf.org</u></font></a>&gt;&gt;,</div>
<div>&gt;&nbsp;&nbsp;&nbsp;&nbsp; &quot;ietf@ietf.org &lt;<a href=3D"mailto=
:ietf@ietf.org"><font color=3D"blue"><u>mailto:ietf@ietf.org</u></font></a>=
&gt;&quot; &lt;ietf@ietf.org</div>
<div>&gt;&nbsp;&nbsp;&nbsp;&nbsp; &lt;<a href=3D"mailto:ietf@ietf.org"><fon=
t color=3D"blue"><u>mailto:ietf@ietf.org</u></font></a>&gt;&gt;</div>
<div>&gt;&nbsp;&nbsp;&nbsp;&nbsp; Subject: Gen-ART review of draft-ietf-pwe=
3-mpls-eth-oam-iwk-06</div>
<div>&gt;</div>
<div>&gt;&nbsp;&nbsp;&nbsp;&nbsp; I am the assigned Gen-ART reviewer for th=
is draft. For background on</div>
<div>&gt;&nbsp;&nbsp;&nbsp;&nbsp; Gen-ART, please</div>
<div>&gt;&nbsp;&nbsp;&nbsp;&nbsp; see the FAQ at</div>
<div>&gt;&nbsp;&nbsp;&nbsp;&nbsp; &lt;<a href=3D"http://wiki.tools.ietf.org=
/area/gen/trac/wiki/GenArtfaq"><font color=3D"blue"><u>http://wiki.tools.ie=
tf.org/area/gen/trac/wiki/GenArtfaq</u></font></a>&gt;.</div>
<div>&gt;</div>
<div>&gt;&nbsp;&nbsp;&nbsp;&nbsp; Please resolve these comments along with =
any other Last Call</div>
<div>&gt;&nbsp;&nbsp;&nbsp;&nbsp; comments you may receive.</div>
<div>&gt;</div>
<div>&gt;&nbsp;&nbsp;&nbsp;&nbsp; Document: draft-ietf-pwe3-mpls-eth-oam-iw=
k-06</div>
<div>&gt;&nbsp;&nbsp;&nbsp;&nbsp; Reviewer: David L. Black</div>
<div>&gt;&nbsp;&nbsp;&nbsp;&nbsp; Review Date: August 20, 2012</div>
<div>&gt;&nbsp;&nbsp;&nbsp;&nbsp; IETF LC End Date: August 20, 2012</div>
<div>&gt;</div>
<div>&gt;&nbsp;&nbsp;&nbsp;&nbsp; Summary:</div>
<div>&gt;&nbsp;&nbsp;&nbsp;&nbsp; This draft is basically ready for publica=
tion, but has nits that</div>
<div>&gt;&nbsp;&nbsp;&nbsp;&nbsp; should be fixed before publication.</div>
<div>&gt;</div>
<div>&gt;&nbsp;&nbsp;&nbsp;&nbsp; &lt;NB&gt; Thanks.</div>
<div>&gt;</div>
<div>&gt;&nbsp;&nbsp;&nbsp;&nbsp; This draft covers defect behavior for Eth=
ernet pseudowires,</div>
<div>&gt;</div>
<div>&gt;&nbsp;&nbsp;&nbsp;&nbsp; including defect state mapping and PE def=
ect reporting behavior.</div>
<div>&gt;</div>
<div>&gt;&nbsp;&nbsp;&nbsp;&nbsp; The draft is generally in good shape.&nbs=
p; I found a few minor nits.</div>
<div>&gt;</div>
<div>&gt;&nbsp;&nbsp;&nbsp;&nbsp; 1) The draft uses a lot of acronyms - whi=
le each acronym appears </div>
<div>&gt; to</div>
<div>&gt;</div>
<div>&gt;&nbsp;&nbsp;&nbsp;&nbsp; be expanded on first use, an additional s=
ection near the start of </div>
<div>&gt; the</div>
<div>&gt;</div>
<div>&gt;&nbsp;&nbsp;&nbsp;&nbsp; draft listing all of them would be helpfu=
l.</div>
<div>&gt;</div>
<div>&gt;</div>
<div>&gt;&nbsp;&nbsp;&nbsp;&nbsp; &lt;NB&gt; Done.</div>
<div>&gt;</div>
<div>&gt;&nbsp;&nbsp;&nbsp;&nbsp; 2) There's a typo in the first paragraph =
of section 2:</div>
<div>&gt;</div>
<div>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; cover=
s the following Ethernet OAM (Opertaions, </div>
<div>&gt; Administration and</div>
<div>&gt;</div>
<div>&gt;&nbsp;&nbsp;&nbsp;&nbsp; Opertaions -&gt; Operations.</div>
<div>&gt;</div>
<div>&gt;</div>
<div>&gt;&nbsp;&nbsp;&nbsp;&nbsp; &lt;NB&gt; Thanks. Done.</div>
<div>&gt;</div>
<div>&gt;&nbsp;&nbsp;&nbsp;&nbsp; 3) The following normative reference is i=
ncomplete - please add</div>
<div>&gt;&nbsp;&nbsp;&nbsp;&nbsp; additional</div>
<div>&gt;</div>
<div>&gt;&nbsp;&nbsp;&nbsp;&nbsp; information that will enable a reader to =
locate the referenced document:</div>
<div>&gt;</div>
<div>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [MEF1=
6] &quot;Ethernet Local Management Interface&quot;, MEF16, January</div>
<div>&gt;&nbsp;&nbsp;&nbsp;&nbsp; 2006.</div>
<div>&gt;</div>
<div>&gt;</div>
<div>&gt;&nbsp;&nbsp;&nbsp;&nbsp; [MEF16] &quot;Ethernet Local Management I=
nterface&quot;, Metro Ethernet Forum</div>
<div>&gt;&nbsp;&nbsp;&nbsp;&nbsp; Technical Specification MEF16, January 20=
06.</div>
<div>&gt;</div>
<div>&gt;&nbsp;&nbsp;&nbsp;&nbsp; &lt;NB&gt; changed it to :</div>
<div>&gt;</div>
<div>&gt;&nbsp;&nbsp;&nbsp;&nbsp; 4) idnits2.12.13 did not like the paginat=
ion:</div>
<div>&gt;</div>
<div>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =3D=3D The page length =
should not exceed 58 lines per page, but there</div>
<div>&gt;&nbsp;&nbsp;&nbsp;&nbsp; was 22</div>
<div>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; longe=
r pages, the longest (page 1) being 61 lines</div>
<div>&gt;</div>
<div>&gt;&nbsp;&nbsp;&nbsp;&nbsp; &lt;NB&gt; That will be fixed.</div>
<div>&gt;&nbsp;&nbsp;&nbsp;&nbsp; Thanks,</div>
<div>&gt;&nbsp;&nbsp;&nbsp;&nbsp; --David</div>
<div>&gt;&nbsp;&nbsp;&nbsp;&nbsp; -----------------------------------------=
-----------</div>
<div>&gt;&nbsp;&nbsp;&nbsp;&nbsp; David L. Black, Distinguished Engineer</d=
iv>
<div>&gt;&nbsp;&nbsp;&nbsp;&nbsp; EMC Corporation, 176 South St., Hopkinton=
, MA&nbsp; 01748</div>
<div>&gt;&nbsp;&nbsp;&nbsp;&nbsp; &#43;1 (508) 293-7953 &lt;tel:%2B1%20%285=
08%29%20293-7953&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp; FAX:</div>
<div>&gt;&nbsp;&nbsp;&nbsp;&nbsp; &#43;1 (508) 293-7786 &lt;tel:%2B1%20%285=
08%29%20293-7786&gt;</div>
<div>&gt;&nbsp;&nbsp;&nbsp;&nbsp; david.black@emc.com &lt;<a href=3D"mailto=
:david.black@emc.com"><font color=3D"blue"><u>mailto:david.black@emc.com</u=
></font></a>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Mobile: &#43;1</=
div>
<div>&gt;&nbsp;&nbsp;&nbsp;&nbsp; (978) 394-7754 &lt;tel:%2B1%20%28978%29%2=
0394-7754&gt;</div>
<div>&gt;&nbsp;&nbsp;&nbsp;&nbsp; -----------------------------------------=
-----------</div>
<div>&gt;</div>
<div>&gt;&nbsp;&nbsp;&nbsp;&nbsp; _________________________________________=
______</div>
<div>&gt;&nbsp;&nbsp;&nbsp;&nbsp; pwe3 mailing list</div>
<div>&gt;&nbsp;&nbsp;&nbsp;&nbsp; pwe3@ietf.org &lt;<a href=3D"mailto:pwe3@=
ietf.org"><font color=3D"blue"><u>mailto:pwe3@ietf.org</u></font></a>&gt;</=
div>
<div>&gt;&nbsp;&nbsp;&nbsp;&nbsp; <a href=3D"https://www.ietf.org/mailman/l=
istinfo/pwe3"><font color=3D"blue"><u>https://www.ietf.org/mailman/listinfo=
/pwe3</u></font></a></div>
<div>&gt;</div>
<div>&gt;</div>
<div>&gt;</div>
<div>&gt;</div>
<div>&gt; _______________________________________________</div>
<div>&gt; pwe3 mailing list</div>
<div>&gt; pwe3@ietf.org</div>
<div>&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/pwe3"><font colo=
r=3D"blue"><u>https://www.ietf.org/mailman/listinfo/pwe3</u></font></a></di=
v>
<div>&gt;</div>
<div>&nbsp;</div>
<div>-- </div>
<div>&nbsp;</div>
<div>&nbsp;</div>
<div>Loa Andersson&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp; email: loa.andersson@ericsson.com</div>
<div>Sr Strategy and Standards Manager&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp; loa@pi.nu</div>
<div>Ericsson Inc&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp; phone: &#43;46 10 717 52 13</div>
<div>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &#43;46 767 72 92 13 ___=
____________________________________________</div>
<div>pwe3 mailing list</div>
<div>pwe3@ietf.org</div>
<div><a href=3D"https://www.ietf.org/mailman/listinfo/pwe3"><font color=3D"=
blue"><u>https://www.ietf.org/mailman/listinfo/pwe3</u></font></a></div>
<div>&nbsp;</div>
</span></font>
</body>
</html>

--_000_7347100B5761DC41A166AC17F22DF112039212eusaamb103ericsso_--

From jsr@10gen.com  Tue Jan  8 09:52:49 2013
Return-Path: <jsr@10gen.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 838E91F0CF5 for <ietf@ietfa.amsl.com>; Tue,  8 Jan 2013 09:52:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.901
X-Spam-Level: 
X-Spam-Status: No, score=-2.901 tagged_above=-999 required=5 tests=[AWL=0.075,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
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 whmvYdFvENRZ for <ietf@ietfa.amsl.com>; Tue,  8 Jan 2013 09:52:48 -0800 (PST)
Received: from mail-vc0-f181.google.com (mail-vc0-f181.google.com [209.85.220.181]) by ietfa.amsl.com (Postfix) with ESMTP id BDC5511E80DF for <ietf@ietf.org>; Tue,  8 Jan 2013 09:52:47 -0800 (PST)
Received: by mail-vc0-f181.google.com with SMTP id gb30so667888vcb.40 for <ietf@ietf.org>; Tue, 08 Jan 2013 09:52:47 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:x-gm-message-state; bh=hWvlWUgyBzGxVf3BD8C5pk42gDKT0VZ0M2m3TadsEPA=; b=TrwoBR9/NiKiPQS3qf+qAJWB6RJLcc7CLvrL/oV8ibW1abV8mNR22UnCTM9TUBwmBQ qsA0/+cS/fx0/0ui7oAfHT8U52mYhUarNWqxZEmoM5efZmGAvxwE6R+ZIVWbqdE8DkEf BWpE6oLokRV4X1Mqg6ddeNwIvjvk2g6s3ClmKCxEuDtu2mT6ZCMn1XMKUH1Vtko9lc19 S5p7ksIzrGpEoFx2XOt0SELa9fx4AhhH6W8nupSZRt9vuuccFeQKYsEVVkgsGkdQwvqW SxmB713dLOhJsPqGAX/gLEB8vRR/cPFCM/0TFXDgoZMlPInqMlnBOkW+yrT+kkPyYMyc zrqw==
MIME-Version: 1.0
Received: by 10.220.247.204 with SMTP id md12mr87769130vcb.27.1357667567088; Tue, 08 Jan 2013 09:52:47 -0800 (PST)
Received: by 10.59.5.6 with HTTP; Tue, 8 Jan 2013 09:52:46 -0800 (PST)
In-Reply-To: <CAChr6SzvXWkkCZU3GPGFJtoqZ=0AOktFhrML6ZMtf7nU9iwxjw@mail.gmail.com>
References: <20121211150057.28223.93310.idtracker@ietfa.amsl.com> <50cb04b9.86df440a.72fe.1e20SMTPIN_ADDED_BROKEN@mx.google.com> <CABP7RbeNsZ_rBWRjou=VG+hBhUKaOz+y1a0sSChwWiHte9znnQ@mail.gmail.com> <50cb5f3c.694c420a.38fb.39afSMTPIN_ADDED_BROKEN@mx.google.com> <CAChr6SxZRc3B_HCbw76kLe2dsRSr43r-gLpfMVnCUfJTrZdTLA@mail.gmail.com> <CABP7RbfA33huBFadMeXTTEt=MkjW8-d4DFH7+GLXGurnm9sSRw@mail.gmail.com> <CAOXDeqpPE4eNy_qJpDPdPHbCQakG9-hDcNZ3Sj9r4kWedByVzQ@mail.gmail.com> <CAChr6SwtS_=iS-k4mJm1vHjEvvGVzay5jDYeGheqsPZqO-89CQ@mail.gmail.com> <EABB8F51-C3B4-49F5-8672-5C2ABAC7043A@mnot.net> <CAChr6Sx7JdKM91EwJaSZ0Ra_F4FSqkuc3vzTY1LM=F_8sWho+Q@mail.gmail.com> <1357515310.6827.23.camel@polyglot> <CAChr6SyAq=7aQdZn54ihYK+0hDhL--2Oaq0RvehoNFbwKNNShA@mail.gmail.com> <CAChr6SxorKO20rGYi-e4YNF=HNGrwz8wPGKCFZQYWQwqsetjjg@mail.gmail.com> <CAOXDeqqE2mCLapwvjwQkme5VTpRCfmF0mFQcx02WW0-zi4i5=g@mail.gmail.com> <50EB4E8B.30700@versi.edu.au> <CAOXDeqoOj1K_zBWVZbE2j4Vnp1pYZ1yUEp9nyTKZmp-QrAziqg@mail.gmail.com> <CAD5Szk-U1LeBSfUgah8XXE2LZ=utR=0W-V7VsT6j-i2VixZerg@mail.gmail.com> <CAChr6SzvXWkkCZU3GPGFJtoqZ=0AOktFhrML6ZMtf7nU9iwxjw@mail.gmail.com>
Date: Tue, 8 Jan 2013 09:52:46 -0800
Message-ID: <CAD5Szk-CTBSeTc-QvDLZ3o5twYq6WF=g6Wr1bsDc=ub=T0pXZg@mail.gmail.com>
Subject: Re: [apps-discuss] Last Call: <draft-ietf-appsawg-json-pointer-07.txt> (JSON Pointer) to Proposed Standard
From: Jared Rosoff <jsr@10gen.com>
To: Robert Sayre <sayrer@gmail.com>
Content-Type: multipart/alternative; boundary=bcaec54eede80f34f104d2ca9dbc
X-Gm-Message-State: ALoCoQlsvnc0p2X9PcSNxLU6KO4OKY5wSBFRU/b8W1/xhQHlzM6y/ELOGRAZcIAeNuTatWa9RSEr
Cc: Mark Nottingham <mnot@mnot.net>, IETF Discussion <ietf@ietf.org>, Matthew Morley <matt@mpcm.com>, IETF Apps Discuss <apps-discuss@ietf.org>, IESG <iesg@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 08 Jan 2013 17:52:49 -0000

--bcaec54eede80f34f104d2ca9dbc
Content-Type: text/plain; charset=ISO-8859-1

I'm definitely not trying to expand the scope beyond the current draft.
More trying to share some experience with an existing implementation of
something similar.

A few comments on path syntax based on this experience.

1) It seems like some of the examples raised on this thread conflate JSON
documents with Javascript objects. According to the json spec, an object
always starts with an "{" and ends with a "}". Therefore, while the json
path "/1" could refer to elements in { "1": "a" } and [1,2], the latter is
not a correct JSON object.

2) Should a JSON pointer be able to refer to the "whole document"? In the
spec, it says that the path "" would refer to the whole JSON document. I
don't think this should be possible. If you want to replace the entire
document, you should be using an HTTP PUT to replace the content, rather
than a patch. Eliminating the ability to refer to the whole document would
also release some ambiguity in certain cases.

For example, earlier it was pointed out that if i have this document

{ "a": 1 }

And then apply this patch

{ op: "add", path: "", value: [1,2,3] }

then it would result in the document after patch being

[1,2,3]

however, this is not a valid json document as it is not enclosed by { }.

Instead, I think that the empty path should refer to the element of the
document named with an empty string.

So with { a: 1 }, and the op { op: "add", path: "", value: [1,2,3] }
would result in this document:

{ a: 1, "": [1,2,3] }

This also means that the leading slash is somewhat superfluous and could be
omitted from the syntax (since the paths "", and "/" would both resolve to
the "" named element of the document. This makes parsing paths easier as
well, since you can just split the path on the "/" and take the count of
parts to figure out how deep you're going.

Given { a: 1, "": [1,2,3] }, i would refer to the 2nd array element with
the path "/2". When parsing this i'd split on "/", which gives me two
tokens, the empty string (on the left of hte /) and the number 2 (on the
right of the /).

-j

On Tue, Jan 8, 2013 at 8:19 AM, Robert Sayre <sayrer@gmail.com> wrote:

> Hi Jared,
>
> Earlier in the thread, I actually directly asked whether software that
> operates on arbitrary JSON was in scope for this WG (my example was
> CouchDB), after having suggested either changing the path syntax or
> renaming the array operations.[0]
>
> The editors didn't respond, except with process points or simple
> contradictions without rationale. My conclusion is that software such
> as MongoDB must be out of scope here. To their credit, the editors did
> point out that anyone is free to try again, and I plan to do just
> that. There's no reason to hold up this WG, since they seem to be
> burnt out.
>
> - Rob
>
> [0]
> http://www.ietf.org/mail-archive/web/apps-discuss/current/msg08552.html
>
>
> On Tue, Jan 8, 2013 at 12:26 AM, Jared Rosoff <jsr@10gen.com> wrote:
> > hi team, i'm new to the discussion here, but wanted to jump in. i work on
> > mongodb, a json database, and i wanted to share how we deal with these
> > issues.
> >
> > mongodb uses almost the same notation for pointers ("a.b.c" instead of
> > "/a/b/c"). We also index arrays in the same way as json pointer ( "a.0"
> > refers to the 0th element of the array called "a"). and this works fine
> in
> > practice. (ref:
> http://docs.mongodb.org/manual/core/document/#dot-notation)
> >
> > our update syntax is different tho. the verbs in mongodb updates for json
> > documents are more specific:
> >
> > set / unset / rename (operations on fields)
> > inc (increment integer values)
> > push / pop / pull (operations on arrays)
> > addToSet / removeFromSet (operations on arrays)
> >
> > (ref http://docs.mongodb.org/manual/reference/operators/#update)
> >
> > since update operations are more specific and type dependent, it's easy
> to
> > throw an error if an unexpected type is encountered (e.g. try to push
> onto a
> > field that has a non-array value) and to act smartly on empty fields ( if
> > path to push is empty, we assume it should be an array, create it, and
> then
> > push the value onto it).
> >
> > i concur the the pointer syntax is fine and ambiguity comes from the
> > definition of operators in json patch.
> >
> > -j
> >
> >
> > On Mon, Jan 7, 2013 at 10:26 PM, Matthew Morley <matt@mpcm.com> wrote:
> >>
> >> On Mon, Jan 7, 2013 at 5:39 PM, Conal Tuohy <conal.tuohy@versi.edu.au>
> >> wrote:
> >>>
> >>> On 07/01/13 13:23, Matthew Morley wrote:
> >>>
> >>>
> >>> For me the deficiency is not in the pointer, but patch format being
> >>> generated.
> >>>
> >>> One approach is to push that *one* test, structure conformity, into the
> >>> pointer syntax. Another is via the type operation.
> >>>
> >>> If a vague patch is generated, vague results are to be expected.
> >>>
> >>> It seems to me, on the contrary, that the deficiency is in the pointer
> >>> syntax, and I think it would be a mistake to try to work around that
> >>> deficiency in JSON Patch. Because aren't there other things which one
> might
> >>> do with JSON Pointer than use it with JSON Patch? There's been mention
> of
> >>> having it registered as a URI fragment identifier syntax for JSON for
> >>> example. JSON Pointers could then end up all over the place, outside of
> >>> patches. IMHO JSON Pointer needs to be taken seriously as a technology
> in
> >>> its own right.
> >>
> >>
> >> Couldn't agree more about it being taken seriously in its own right. :)
> >>
> >> JSON Pointer for me exists outside of JSON Patch, always has and will do
> >> the way we think about structures. As it represents both a resolution
> path
> >> and an identity string (both ends of the path concept). I see value
> from the
> >> identity view, in describing a location that is aware of being inside an
> >> array.
> >>
> >> But JSON Pointer should not be changed just because of issues with JSON
> >> Patch, especially when JSON Patch is attempting to address those issues
> with
> >> other mechanisms within the specification. That is all I was trying to
> >> express. The syntax change should be for other reasons, if it is going
> to be
> >> made.
> >>
> >> My personal experience (for what its worth): In the past I've tried a
> >> number of syntaxes like JSON Pointer. Mostly a.b.c.0 and even a.b.c:0 at
> >> times to address the same issues suggested here. Though my experiences
> >> pushed me towards a single syntax using a.b.c.0, and thus my support for
> >> /a/b/c/0 over /a/b/c:0.
> >>
> >> The system at first used the . or : syntax, combined with dynamic
> tokens,
> >> being pointers themselves, to resolve other pointers. So it was not
> >> reasonable to know ahead of time if an end point was an array or an
> object.
> >> "a.b.c.{d.e.f}" could end up in an array or in an object, depending on
> the
> >> value at d.e.f at the time of resolution. Especially with many layers of
> >> tokens to resolve, and changing data structures.
> >>
> >> I found in practice, it didn't really matter, so the choice of . or :
> was
> >> phased out. At the end of the day the two syntaxes point to mutually
> >> exclusive points within the data, so that `meta data` about the
> structure
> >> was removed from the syntax we used. It didn't add value, even if it
> added
> >> clarity at times. We also had functions at the end of paths, but that
> goes
> >> beyond the JSON focus of the JSON Pointer goals, so those points are not
> >> relevant here.
> >>
> >> This discussion thread seems to be getting overly complicated, but JSON
> >> Pointer changes should come from the JSON Pointer view point and that
> >> specifications goals, not from short comings in JSON Patch.
> >>
> >> --
> >> Matthew P. C. Morley
> >> _______________________________________________
> >> apps-discuss mailing list
> >> apps-discuss@ietf.org
> >> https://www.ietf.org/mailman/listinfo/apps-discuss
> >>
> >
> >
> > _______________________________________________
> > apps-discuss mailing list
> > apps-discuss@ietf.org
> > https://www.ietf.org/mailman/listinfo/apps-discuss
> >
>

--bcaec54eede80f34f104d2ca9dbc
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

I&#39;m definitely not trying to expand the scope beyond the current draft.=
 More trying to share some experience with an existing implementation of so=
mething similar.=A0<div><br></div><div>A few comments on path syntax based =
on this experience.=A0</div>
<div><br></div><div>1) It seems like some of the examples raised on this th=
read conflate JSON documents with Javascript objects. According to the json=
 spec, an object always starts with an &quot;{&quot; and ends with a &quot;=
}&quot;. Therefore, while the json path &quot;/1&quot; could refer to eleme=
nts in { &quot;1&quot;: &quot;a&quot; } and [1,2], the latter is not a corr=
ect JSON object.=A0</div>
<div><br></div><div>2) Should a JSON pointer be able to refer to the &quot;=
whole document&quot;? In the spec, it says that the path &quot;&quot; would=
 refer to the whole JSON document. I don&#39;t think this should be possibl=
e. If you want to replace the entire document, you should be using an HTTP =
PUT to replace the content, rather than a patch. Eliminating the ability to=
 refer to the whole document would also release some ambiguity in certain c=
ases.=A0</div>
<div><br></div><div>For example, earlier it was pointed out that if i have =
this document=A0</div><div><br></div><div>{ &quot;a&quot;: 1 }=A0</div><div=
><br></div><div>And then apply this patch=A0</div><div><br></div><div>{ op:=
 &quot;add&quot;, path: &quot;&quot;, value: [1,2,3] }=A0</div>
<div><br></div><div>then it would result in the document after patch being=
=A0</div><div><br></div><div>[1,2,3]=A0</div><div><br></div><div>however, t=
his is not a valid json document as it is not enclosed by { }.=A0</div><div=
><br>
</div><div>Instead, I think that the empty path should refer to the element=
 of the document named with an empty string.=A0</div><div><br></div><div>So=
 with { a: 1 }, and the op { op: &quot;add&quot;, path: &quot;&quot;, value=
: [1,2,3] }=A0</div>
<div>would result in this document:=A0</div><div><br></div><div>{ a: 1, &qu=
ot;&quot;: [1,2,3] }=A0</div><div><br></div><div>This also means that the l=
eading slash is somewhat superfluous and could be omitted from the syntax (=
since the paths &quot;&quot;, and &quot;/&quot; would both resolve to the &=
quot;&quot; named element of the document. This makes parsing paths easier =
as well, since you can just split the path on the &quot;/&quot; and take th=
e count of parts to figure out how deep you&#39;re going.=A0</div>
<div><br></div><div>Given { a: 1, &quot;&quot;: [1,2,3] }, i would refer to=
 the 2nd array element with the path &quot;/2&quot;. When parsing this i&#3=
9;d split on &quot;/&quot;, which gives me two tokens, the empty string (on=
 the left of hte /) and the number 2 (on the right of the /).=A0</div>
<div><br></div><div>-j=A0</div><div><br><div class=3D"gmail_quote">On Tue, =
Jan 8, 2013 at 8:19 AM, Robert Sayre <span dir=3D"ltr">&lt;<a href=3D"mailt=
o:sayrer@gmail.com" target=3D"_blank">sayrer@gmail.com</a>&gt;</span> wrote=
:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-le=
ft:1px #ccc solid;padding-left:1ex">
Hi Jared,<br>
<br>
Earlier in the thread, I actually directly asked whether software that<br>
operates on arbitrary JSON was in scope for this WG (my example was<br>
CouchDB), after having suggested either changing the path syntax or<br>
renaming the array operations.[0]<br>
<br>
The editors didn&#39;t respond, except with process points or simple<br>
contradictions without rationale. My conclusion is that software such<br>
as MongoDB must be out of scope here. To their credit, the editors did<br>
point out that anyone is free to try again, and I plan to do just<br>
that. There&#39;s no reason to hold up this WG, since they seem to be<br>
burnt out.<br>
<br>
- Rob<br>
<br>
[0] <a href=3D"http://www.ietf.org/mail-archive/web/apps-discuss/current/ms=
g08552.html" target=3D"_blank">http://www.ietf.org/mail-archive/web/apps-di=
scuss/current/msg08552.html</a><br>
<div class=3D"HOEnZb"><div class=3D"h5"><br>
<br>
On Tue, Jan 8, 2013 at 12:26 AM, Jared Rosoff &lt;<a href=3D"mailto:jsr@10g=
en.com">jsr@10gen.com</a>&gt; wrote:<br>
&gt; hi team, i&#39;m new to the discussion here, but wanted to jump in. i =
work on<br>
&gt; mongodb, a json database, and i wanted to share how we deal with these=
<br>
&gt; issues.<br>
&gt;<br>
&gt; mongodb uses almost the same notation for pointers (&quot;a.b.c&quot; =
instead of<br>
&gt; &quot;/a/b/c&quot;). We also index arrays in the same way as json poin=
ter ( &quot;a.0&quot;<br>
&gt; refers to the 0th element of the array called &quot;a&quot;). and this=
 works fine in<br>
&gt; practice. (ref: <a href=3D"http://docs.mongodb.org/manual/core/documen=
t/#dot-notation" target=3D"_blank">http://docs.mongodb.org/manual/core/docu=
ment/#dot-notation</a>)<br>
&gt;<br>
&gt; our update syntax is different tho. the verbs in mongodb updates for j=
son<br>
&gt; documents are more specific:<br>
&gt;<br>
&gt; set / unset / rename (operations on fields)<br>
&gt; inc (increment integer values)<br>
&gt; push / pop / pull (operations on arrays)<br>
&gt; addToSet / removeFromSet (operations on arrays)<br>
&gt;<br>
&gt; (ref <a href=3D"http://docs.mongodb.org/manual/reference/operators/#up=
date" target=3D"_blank">http://docs.mongodb.org/manual/reference/operators/=
#update</a>)<br>
&gt;<br>
&gt; since update operations are more specific and type dependent, it&#39;s=
 easy to<br>
&gt; throw an error if an unexpected type is encountered (e.g. try to push =
onto a<br>
&gt; field that has a non-array value) and to act smartly on empty fields (=
 if<br>
&gt; path to push is empty, we assume it should be an array, create it, and=
 then<br>
&gt; push the value onto it).<br>
&gt;<br>
&gt; i concur the the pointer syntax is fine and ambiguity comes from the<b=
r>
&gt; definition of operators in json patch.<br>
&gt;<br>
&gt; -j<br>
&gt;<br>
&gt;<br>
&gt; On Mon, Jan 7, 2013 at 10:26 PM, Matthew Morley &lt;<a href=3D"mailto:=
matt@mpcm.com">matt@mpcm.com</a>&gt; wrote:<br>
&gt;&gt;<br>
&gt;&gt; On Mon, Jan 7, 2013 at 5:39 PM, Conal Tuohy &lt;<a href=3D"mailto:=
conal.tuohy@versi.edu.au">conal.tuohy@versi.edu.au</a>&gt;<br>
&gt;&gt; wrote:<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; On 07/01/13 13:23, Matthew Morley wrote:<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; For me the deficiency is not in the pointer, but patch format =
being<br>
&gt;&gt;&gt; generated.<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; One approach is to push that *one* test, structure conformity,=
 into the<br>
&gt;&gt;&gt; pointer syntax. Another is via the type operation.<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; If a vague patch is generated, vague results are to be expecte=
d.<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; It seems to me, on the contrary, that the deficiency is in the=
 pointer<br>
&gt;&gt;&gt; syntax, and I think it would be a mistake to try to work aroun=
d that<br>
&gt;&gt;&gt; deficiency in JSON Patch. Because aren&#39;t there other thing=
s which one might<br>
&gt;&gt;&gt; do with JSON Pointer than use it with JSON Patch? There&#39;s =
been mention of<br>
&gt;&gt;&gt; having it registered as a URI fragment identifier syntax for J=
SON for<br>
&gt;&gt;&gt; example. JSON Pointers could then end up all over the place, o=
utside of<br>
&gt;&gt;&gt; patches. IMHO JSON Pointer needs to be taken seriously as a te=
chnology in<br>
&gt;&gt;&gt; its own right.<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt; Couldn&#39;t agree more about it being taken seriously in its own =
right. :)<br>
&gt;&gt;<br>
&gt;&gt; JSON Pointer for me exists outside of JSON Patch, always has and w=
ill do<br>
&gt;&gt; the way we think about structures. As it represents both a resolut=
ion path<br>
&gt;&gt; and an identity string (both ends of the path concept). I see valu=
e from the<br>
&gt;&gt; identity view, in describing a location that is aware of being ins=
ide an<br>
&gt;&gt; array.<br>
&gt;&gt;<br>
&gt;&gt; But JSON Pointer should not be changed just because of issues with=
 JSON<br>
&gt;&gt; Patch, especially when JSON Patch is attempting to address those i=
ssues with<br>
&gt;&gt; other mechanisms within the specification. That is all I was tryin=
g to<br>
&gt;&gt; express. The syntax change should be for other reasons, if it is g=
oing to be<br>
&gt;&gt; made.<br>
&gt;&gt;<br>
&gt;&gt; My personal experience (for what its worth): In the past I&#39;ve =
tried a<br>
&gt;&gt; number of syntaxes like JSON Pointer. Mostly a.b.c.0 and even a.b.=
c:0 at<br>
&gt;&gt; times to address the same issues suggested here. Though my experie=
nces<br>
&gt;&gt; pushed me towards a single syntax using a.b.c.0, and thus my suppo=
rt for<br>
&gt;&gt; /a/b/c/0 over /a/b/c:0.<br>
&gt;&gt;<br>
&gt;&gt; The system at first used the . or : syntax, combined with dynamic =
tokens,<br>
&gt;&gt; being pointers themselves, to resolve other pointers. So it was no=
t<br>
&gt;&gt; reasonable to know ahead of time if an end point was an array or a=
n object.<br>
&gt;&gt; &quot;a.b.c.{d.e.f}&quot; could end up in an array or in an object=
, depending on the<br>
&gt;&gt; value at d.e.f at the time of resolution. Especially with many lay=
ers of<br>
&gt;&gt; tokens to resolve, and changing data structures.<br>
&gt;&gt;<br>
&gt;&gt; I found in practice, it didn&#39;t really matter, so the choice of=
 . or : was<br>
&gt;&gt; phased out. At the end of the day the two syntaxes point to mutual=
ly<br>
&gt;&gt; exclusive points within the data, so that `meta data` about the st=
ructure<br>
&gt;&gt; was removed from the syntax we used. It didn&#39;t add value, even=
 if it added<br>
&gt;&gt; clarity at times. We also had functions at the end of paths, but t=
hat goes<br>
&gt;&gt; beyond the JSON focus of the JSON Pointer goals, so those points a=
re not<br>
&gt;&gt; relevant here.<br>
&gt;&gt;<br>
&gt;&gt; This discussion thread seems to be getting overly complicated, but=
 JSON<br>
&gt;&gt; Pointer changes should come from the JSON Pointer view point and t=
hat<br>
&gt;&gt; specifications goals, not from short comings in JSON Patch.<br>
&gt;&gt;<br>
&gt;&gt; --<br>
&gt;&gt; Matthew P. C. Morley<br>
&gt;&gt; _______________________________________________<br>
&gt;&gt; apps-discuss mailing list<br>
&gt;&gt; <a href=3D"mailto:apps-discuss@ietf.org">apps-discuss@ietf.org</a>=
<br>
&gt;&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/apps-discuss" tar=
get=3D"_blank">https://www.ietf.org/mailman/listinfo/apps-discuss</a><br>
&gt;&gt;<br>
&gt;<br>
&gt;<br>
&gt; _______________________________________________<br>
&gt; apps-discuss mailing list<br>
&gt; <a href=3D"mailto:apps-discuss@ietf.org">apps-discuss@ietf.org</a><br>
&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/apps-discuss" target=
=3D"_blank">https://www.ietf.org/mailman/listinfo/apps-discuss</a><br>
&gt;<br>
</div></div></blockquote></div><br></div>

--bcaec54eede80f34f104d2ca9dbc--

From jasnell@gmail.com  Tue Jan  8 09:58:45 2013
Return-Path: <jasnell@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 747F221F8684; Tue,  8 Jan 2013 09:58:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.987
X-Spam-Level: 
X-Spam-Status: No, score=-3.987 tagged_above=-999 required=5 tests=[AWL=-0.389, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
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 pxPHpQI0F7Wv; Tue,  8 Jan 2013 09:58:45 -0800 (PST)
Received: from mail-ie0-f175.google.com (mail-ie0-f175.google.com [209.85.223.175]) by ietfa.amsl.com (Postfix) with ESMTP id C99DE21F8678; Tue,  8 Jan 2013 09:58:44 -0800 (PST)
Received: by mail-ie0-f175.google.com with SMTP id qd14so894304ieb.34 for <multiple recipients>; Tue, 08 Jan 2013 09:58:44 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=DcNmtxw0FoMdjQxYFdWxxj0M/HMzLPcCqpqp8I00kyk=; b=IBQSxgzYCGQSKb0tRgHkmdbVPsxeR2GM2CD9km27Fo3xINZINnKY+s2VQz7KjbMbJC uhWG+HWCfTZnHpWVKKO8OxsU7b2B4VaUmBqLSexBeQ0URVNxluST1tK/k0VLYVuDUi7N PpFo8vMA4snjY4fj9B9fTPLHUEtTBT74PQrdFtSnw2D5NCh/W9bFkm2Mo+k+vm7A8hkN AgHo+E5cWFxyipRa98e6Y++GgZSvpnpFkwHqektp65DjLavMlTry/fmaK05wBujUjGZ8 gIvhev8C45L17sKxK5bI3aUm4Cj79Pa9QXy4zWhjsBI9y3kC4fkQPYpYv/R4804t1juM vwBQ==
Received: by 10.50.150.174 with SMTP id uj14mr9771408igb.19.1357667924440; Tue, 08 Jan 2013 09:58:44 -0800 (PST)
MIME-Version: 1.0
Received: by 10.64.7.19 with HTTP; Tue, 8 Jan 2013 09:58:24 -0800 (PST)
In-Reply-To: <CAD5Szk-CTBSeTc-QvDLZ3o5twYq6WF=g6Wr1bsDc=ub=T0pXZg@mail.gmail.com>
References: <20121211150057.28223.93310.idtracker@ietfa.amsl.com> <50cb04b9.86df440a.72fe.1e20SMTPIN_ADDED_BROKEN@mx.google.com> <CABP7RbeNsZ_rBWRjou=VG+hBhUKaOz+y1a0sSChwWiHte9znnQ@mail.gmail.com> <50cb5f3c.694c420a.38fb.39afSMTPIN_ADDED_BROKEN@mx.google.com> <CAChr6SxZRc3B_HCbw76kLe2dsRSr43r-gLpfMVnCUfJTrZdTLA@mail.gmail.com> <CABP7RbfA33huBFadMeXTTEt=MkjW8-d4DFH7+GLXGurnm9sSRw@mail.gmail.com> <CAOXDeqpPE4eNy_qJpDPdPHbCQakG9-hDcNZ3Sj9r4kWedByVzQ@mail.gmail.com> <CAChr6SwtS_=iS-k4mJm1vHjEvvGVzay5jDYeGheqsPZqO-89CQ@mail.gmail.com> <EABB8F51-C3B4-49F5-8672-5C2ABAC7043A@mnot.net> <CAChr6Sx7JdKM91EwJaSZ0Ra_F4FSqkuc3vzTY1LM=F_8sWho+Q@mail.gmail.com> <1357515310.6827.23.camel@polyglot> <CAChr6SyAq=7aQdZn54ihYK+0hDhL--2Oaq0RvehoNFbwKNNShA@mail.gmail.com> <CAChr6SxorKO20rGYi-e4YNF=HNGrwz8wPGKCFZQYWQwqsetjjg@mail.gmail.com> <CAOXDeqqE2mCLapwvjwQkme5VTpRCfmF0mFQcx02WW0-zi4i5=g@mail.gmail.com> <50EB4E8B.30700@versi.edu.au> <CAOXDeqoOj1K_zBWVZbE2j4Vnp1pYZ1yUEp9nyTKZmp-QrAziqg@mail.gmail.com> <CAD5Szk-U1LeBSfUgah8XXE2LZ=utR=0W-V7VsT6j-i2VixZerg@mail.gmail.com> <CAChr6SzvXWkkCZU3GPGFJtoqZ=0AOktFhrML6ZMtf7nU9iwxjw@mail.gmail.com> <CAD5Szk-CTBSeTc-QvDLZ3o5twYq6WF=g6Wr1bsDc=ub=T0pXZg@mail.gmail.com>
From: James M Snell <jasnell@gmail.com>
Date: Tue, 8 Jan 2013 09:58:24 -0800
Message-ID: <CABP7RbeHFmWhfwUcn6mEZEFES+0d_HpP5XCZUanQ9FQozYtD-Q@mail.gmail.com>
Subject: Re: [apps-discuss] Last Call: <draft-ietf-appsawg-json-pointer-07.txt> (JSON Pointer) to Proposed Standard
To: Jared Rosoff <jsr@10gen.com>
Content-Type: multipart/alternative; boundary=f46d043d644b5bf4f504d2cab295
Cc: IESG <iesg@ietf.org>, Mark Nottingham <mnot@mnot.net>, IETF Discussion <ietf@ietf.org>, IETF Apps Discuss <apps-discuss@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 08 Jan 2013 17:58:45 -0000

--f46d043d644b5bf4f504d2cab295
Content-Type: text/plain; charset=UTF-8

On Tue, Jan 8, 2013 at 9:52 AM, Jared Rosoff <jsr@10gen.com> wrote:

> [snip]
> then it would result in the document after patch being
>
> [1,2,3]
>
> however, this is not a valid json document as it is not enclosed by { }.
> [snip]
>

The root of a JSON Document can be either an object or an array.

- James

--f46d043d644b5bf4f504d2cab295
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra"><br><br><div class=3D"gmail_quo=
te">On Tue, Jan 8, 2013 at 9:52 AM, Jared Rosoff <span dir=3D"ltr">&lt;<a h=
ref=3D"mailto:jsr@10gen.com" target=3D"_blank">jsr@10gen.com</a>&gt;</span>=
 wrote:<br>

<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;p=
adding-left:1ex"><div style>[snip]</div><div>then it would result in the do=
cument after patch being=C2=A0</div>

<div><br></div><div>[1,2,3]=C2=A0</div><div><br></div><div>however, this is=
 not a valid json document as it is not enclosed by { }.=C2=A0</div><div st=
yle>[snip]</div></blockquote><div><br></div><div style>The root of a JSON D=
ocument can be either an object or an array.</div>

<div><br></div><div style>- James</div></div><br></div></div>

--f46d043d644b5bf4f504d2cab295--

From jsr@10gen.com  Tue Jan  8 10:14:12 2013
Return-Path: <jsr@10gen.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0A6E411E80EF for <ietf@ietfa.amsl.com>; Tue,  8 Jan 2013 10:14:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.926
X-Spam-Level: 
X-Spam-Status: No, score=-2.926 tagged_above=-999 required=5 tests=[AWL=0.050,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
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 ghmyQicLzHrK for <ietf@ietfa.amsl.com>; Tue,  8 Jan 2013 10:14:11 -0800 (PST)
Received: from mail-vb0-f46.google.com (mail-vb0-f46.google.com [209.85.212.46]) by ietfa.amsl.com (Postfix) with ESMTP id D249F11E80D9 for <ietf@ietf.org>; Tue,  8 Jan 2013 10:14:09 -0800 (PST)
Received: by mail-vb0-f46.google.com with SMTP id b13so702941vby.33 for <ietf@ietf.org>; Tue, 08 Jan 2013 10:14:00 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:x-gm-message-state; bh=32UVGIeS12HBR4tosl5xnEuOE9iA2UC8x5TpSYEB1M4=; b=o5GgOqgliSC6/xf02TycXeniwcK1VkkbTswxo+P3eOxp84C0wpNwc9+wL7OxpJuxel vft49y78EuevASp2lFmXFWvGPpqprb4oPXnDzMn2GOo24HOhLz0S2rhUmZu3a4qOTCMu j9xsWDMdt/DKfaimPqwA3NwEqMbZXqfQmaE+NIwegMmu+j05iyFq4dD907uhPJ9q4DdR a2AKVE3UwbuNa4rDE0YfpaTrv9Alm4zHCLxDq2i9Pgri/8nA8XBsAd7rkTiVebMkunuV gxl4og+qW0EbNDBMMWpiEl90d99z9lo77w9q4MBq3s6ziuV4NwpcZoQORKTntNN1zEDw KYYg==
MIME-Version: 1.0
Received: by 10.220.151.83 with SMTP id b19mr86396979vcw.25.1357668839893; Tue, 08 Jan 2013 10:13:59 -0800 (PST)
Received: by 10.59.5.6 with HTTP; Tue, 8 Jan 2013 10:13:59 -0800 (PST)
In-Reply-To: <CABP7RbeHFmWhfwUcn6mEZEFES+0d_HpP5XCZUanQ9FQozYtD-Q@mail.gmail.com>
References: <20121211150057.28223.93310.idtracker@ietfa.amsl.com> <50cb04b9.86df440a.72fe.1e20SMTPIN_ADDED_BROKEN@mx.google.com> <CABP7RbeNsZ_rBWRjou=VG+hBhUKaOz+y1a0sSChwWiHte9znnQ@mail.gmail.com> <50cb5f3c.694c420a.38fb.39afSMTPIN_ADDED_BROKEN@mx.google.com> <CAChr6SxZRc3B_HCbw76kLe2dsRSr43r-gLpfMVnCUfJTrZdTLA@mail.gmail.com> <CABP7RbfA33huBFadMeXTTEt=MkjW8-d4DFH7+GLXGurnm9sSRw@mail.gmail.com> <CAOXDeqpPE4eNy_qJpDPdPHbCQakG9-hDcNZ3Sj9r4kWedByVzQ@mail.gmail.com> <CAChr6SwtS_=iS-k4mJm1vHjEvvGVzay5jDYeGheqsPZqO-89CQ@mail.gmail.com> <EABB8F51-C3B4-49F5-8672-5C2ABAC7043A@mnot.net> <CAChr6Sx7JdKM91EwJaSZ0Ra_F4FSqkuc3vzTY1LM=F_8sWho+Q@mail.gmail.com> <1357515310.6827.23.camel@polyglot> <CAChr6SyAq=7aQdZn54ihYK+0hDhL--2Oaq0RvehoNFbwKNNShA@mail.gmail.com> <CAChr6SxorKO20rGYi-e4YNF=HNGrwz8wPGKCFZQYWQwqsetjjg@mail.gmail.com> <CAOXDeqqE2mCLapwvjwQkme5VTpRCfmF0mFQcx02WW0-zi4i5=g@mail.gmail.com> <50EB4E8B.30700@versi.edu.au> <CAOXDeqoOj1K_zBWVZbE2j4Vnp1pYZ1yUEp9nyTKZmp-QrAziqg@mail.gmail.com> <CAD5Szk-U1LeBSfUgah8XXE2LZ=utR=0W-V7VsT6j-i2VixZerg@mail.gmail.com> <CAChr6SzvXWkkCZU3GPGFJtoqZ=0AOktFhrML6ZMtf7nU9iwxjw@mail.gmail.com> <CAD5Szk-CTBSeTc-QvDLZ3o5twYq6WF=g6Wr1bsDc=ub=T0pXZg@mail.gmail.com> <CABP7RbeHFmWhfwUcn6mEZEFES+0d_HpP5XCZUanQ9FQozYtD-Q@mail.gmail.com>
Date: Tue, 8 Jan 2013 10:13:59 -0800
Message-ID: <CAD5Szk8hRn731uiv_p561N7Va4UWF4xbxRRRhVu1CPDBc4dPHw@mail.gmail.com>
Subject: Re: [apps-discuss] Last Call: <draft-ietf-appsawg-json-pointer-07.txt> (JSON Pointer) to Proposed Standard
From: Jared Rosoff <jsr@10gen.com>
To: James M Snell <jasnell@gmail.com>
Content-Type: multipart/alternative; boundary=f46d0434bf1eeca99404d2cae8d7
X-Gm-Message-State: ALoCoQk595bUL4m5DdhlfqVa3cPfiFAo4YvD8m7o4NMeE3lyHsJcWvqhj7X/EQb2CYztSCUT1jtX
Cc: IESG <iesg@ietf.org>, Mark Nottingham <mnot@mnot.net>, IETF Discussion <ietf@ietf.org>, IETF Apps Discuss <apps-discuss@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 08 Jan 2013 18:14:12 -0000

--f46d0434bf1eeca99404d2cae8d7
Content-Type: text/plain; charset=ISO-8859-1

my bad.

regardless, if you want to replace the whole document, is that a patch? or
should that better be done with PUT?

On Tue, Jan 8, 2013 at 9:58 AM, James M Snell <jasnell@gmail.com> wrote:

>
>
> The root of a JSON Document can be either an object or an array.
>
> - James
>
>

--f46d0434bf1eeca99404d2cae8d7
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

my bad.=A0<div><br></div><div>regardless, if you want to replace the whole =
document, is that a patch? or should that better be done with PUT?=A0<br><b=
r><div class=3D"gmail_quote">On Tue, Jan 8, 2013 at 9:58 AM, James M Snell =
<span dir=3D"ltr">&lt;<a href=3D"mailto:jasnell@gmail.com" target=3D"_blank=
">jasnell@gmail.com</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div dir=3D"ltr"><div class=3D"gmail_extra">=
<div class=3D"gmail_quote"><br><div><br></div><div>The root of a JSON Docum=
ent can be either an object or an array.</div>
<span class=3D"HOEnZb"><font color=3D"#888888">

<div><br></div><div>- James</div></font></span></div><br></div></div>
</blockquote></div><br></div>

--f46d0434bf1eeca99404d2cae8d7--

From jasnell@gmail.com  Tue Jan  8 10:15:20 2013
Return-Path: <jasnell@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5C8B71F0CFA; Tue,  8 Jan 2013 10:15:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.948
X-Spam-Level: 
X-Spam-Status: No, score=-3.948 tagged_above=-999 required=5 tests=[AWL=-0.350, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
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 PmDIXymg6fj2; Tue,  8 Jan 2013 10:15:19 -0800 (PST)
Received: from mail-ia0-f174.google.com (mail-ia0-f174.google.com [209.85.210.174]) by ietfa.amsl.com (Postfix) with ESMTP id AAEE91F0CB3; Tue,  8 Jan 2013 10:15:19 -0800 (PST)
Received: by mail-ia0-f174.google.com with SMTP id y25so619502iay.5 for <multiple recipients>; Tue, 08 Jan 2013 10:15:19 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=BRlfGcHRkZ4zfzqSPWMpGPzKrrkT6e2ejNKUXdSKH74=; b=U/wdJoeu4Wf2EgeH5NdQm3nR54aApDT0jzg/J4KHa5l9gPphZ+Jae+PHAYroFn2XXm wfDOkkytT4YYEK4bYLfAzzk+caf81Fk5jIRFuiu8z7gVryF7t5efenLxEQBF14Zf69t3 g2m/xzN+aRbdLiRr70tTcJGXBad3UQNfC5GOGIXcxpG4ONRm7Tpbzz3gx5fYNpZWuZ6Q 20WxR/LECi/5GSAV6F40g8QrKXZNWwZLG7SLlLmIrxpvpnDCrioLzKwdRx72BcZsbcN8 EumO21UbKTkgPPsXYVicljwZkGJmj43sKeENbYIhlJ2O1+VTT2zdUFXwsGlkhwBgCiL3 vFlg==
Received: by 10.50.158.170 with SMTP id wv10mr10077538igb.75.1357668919260; Tue, 08 Jan 2013 10:15:19 -0800 (PST)
MIME-Version: 1.0
Received: by 10.64.7.19 with HTTP; Tue, 8 Jan 2013 10:14:59 -0800 (PST)
In-Reply-To: <CAD5Szk8hRn731uiv_p561N7Va4UWF4xbxRRRhVu1CPDBc4dPHw@mail.gmail.com>
References: <20121211150057.28223.93310.idtracker@ietfa.amsl.com> <50cb04b9.86df440a.72fe.1e20SMTPIN_ADDED_BROKEN@mx.google.com> <CABP7RbeNsZ_rBWRjou=VG+hBhUKaOz+y1a0sSChwWiHte9znnQ@mail.gmail.com> <50cb5f3c.694c420a.38fb.39afSMTPIN_ADDED_BROKEN@mx.google.com> <CAChr6SxZRc3B_HCbw76kLe2dsRSr43r-gLpfMVnCUfJTrZdTLA@mail.gmail.com> <CABP7RbfA33huBFadMeXTTEt=MkjW8-d4DFH7+GLXGurnm9sSRw@mail.gmail.com> <CAOXDeqpPE4eNy_qJpDPdPHbCQakG9-hDcNZ3Sj9r4kWedByVzQ@mail.gmail.com> <CAChr6SwtS_=iS-k4mJm1vHjEvvGVzay5jDYeGheqsPZqO-89CQ@mail.gmail.com> <EABB8F51-C3B4-49F5-8672-5C2ABAC7043A@mnot.net> <CAChr6Sx7JdKM91EwJaSZ0Ra_F4FSqkuc3vzTY1LM=F_8sWho+Q@mail.gmail.com> <1357515310.6827.23.camel@polyglot> <CAChr6SyAq=7aQdZn54ihYK+0hDhL--2Oaq0RvehoNFbwKNNShA@mail.gmail.com> <CAChr6SxorKO20rGYi-e4YNF=HNGrwz8wPGKCFZQYWQwqsetjjg@mail.gmail.com> <CAOXDeqqE2mCLapwvjwQkme5VTpRCfmF0mFQcx02WW0-zi4i5=g@mail.gmail.com> <50EB4E8B.30700@versi.edu.au> <CAOXDeqoOj1K_zBWVZbE2j4Vnp1pYZ1yUEp9nyTKZmp-QrAziqg@mail.gmail.com> <CAD5Szk-U1LeBSfUgah8XXE2LZ=utR=0W-V7VsT6j-i2VixZerg@mail.gmail.com> <CAChr6SzvXWkkCZU3GPGFJtoqZ=0AOktFhrML6ZMtf7nU9iwxjw@mail.gmail.com> <CAD5Szk-CTBSeTc-QvDLZ3o5twYq6WF=g6Wr1bsDc=ub=T0pXZg@mail.gmail.com> <CABP7RbeHFmWhfwUcn6mEZEFES+0d_HpP5XCZUanQ9FQozYtD-Q@mail.gmail.com> <CAD5Szk8hRn731uiv_p561N7Va4UWF4xbxRRRhVu1CPDBc4dPHw@mail.gmail.com>
From: James M Snell <jasnell@gmail.com>
Date: Tue, 8 Jan 2013 10:14:59 -0800
Message-ID: <CABP7Rbf4N3KCP=5s64uhrFjsnB5mG5AbTVC0BDo37h+gjVa=Hg@mail.gmail.com>
Subject: Re: [apps-discuss] Last Call: <draft-ietf-appsawg-json-pointer-07.txt> (JSON Pointer) to Proposed Standard
To: Jared Rosoff <jsr@10gen.com>
Content-Type: multipart/alternative; boundary=14dae9340f21a7b5f704d2caed7f
Cc: IESG <iesg@ietf.org>, Mark Nottingham <mnot@mnot.net>, IETF Discussion <ietf@ietf.org>, IETF Apps Discuss <apps-discuss@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 08 Jan 2013 18:15:20 -0000

--14dae9340f21a7b5f704d2caed7f
Content-Type: text/plain; charset=UTF-8

+1


On Tue, Jan 8, 2013 at 10:13 AM, Jared Rosoff <jsr@10gen.com> wrote:

> my bad.
>
> regardless, if you want to replace the whole document, is that a patch? or
> should that better be done with PUT?
>
>
> On Tue, Jan 8, 2013 at 9:58 AM, James M Snell <jasnell@gmail.com> wrote:
>
>>
>>
>> The root of a JSON Document can be either an object or an array.
>>
>> - James
>>
>>
>

--14dae9340f21a7b5f704d2caed7f
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><font face=3D"courier new,monospace">+1=C2=A0<br></font><d=
iv class=3D"gmail_extra"><br><br><div class=3D"gmail_quote">On Tue, Jan 8, =
2013 at 10:13 AM, Jared Rosoff <span dir=3D"ltr">&lt;<a href=3D"mailto:jsr@=
10gen.com" target=3D"_blank">jsr@10gen.com</a>&gt;</span> wrote:<br>

<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">my bad.=C2=A0<div><br></div><div>regardless,=
 if you want to replace the whole document, is that a patch? or should that=
 better be done with PUT?=C2=A0<div class=3D"im">

<br><br><div class=3D"gmail_quote">On Tue, Jan 8, 2013 at 9:58 AM, James M =
Snell <span dir=3D"ltr">&lt;<a href=3D"mailto:jasnell@gmail.com" target=3D"=
_blank">jasnell@gmail.com</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div dir=3D"ltr"><div class=3D"gmail_extra">=
<div class=3D"gmail_quote"><br><div><br></div><div>The root of a JSON Docum=
ent can be either an object or an array.</div>


<span><font color=3D"#888888">

<div><br></div><div>- James</div></font></span></div><br></div></div>
</blockquote></div><br></div></div>
</blockquote></div><br></div></div>

--14dae9340f21a7b5f704d2caed7f--

From sayrer@gmail.com  Tue Jan  8 10:57:03 2013
Return-Path: <sayrer@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C396421F8446; Tue,  8 Jan 2013 10:57:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.099
X-Spam-Level: 
X-Spam-Status: No, score=-3.099 tagged_above=-999 required=5 tests=[AWL=0.500,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 72cswcpjSDeB; Tue,  8 Jan 2013 10:57:03 -0800 (PST)
Received: from mail-lb0-f171.google.com (mail-lb0-f171.google.com [209.85.217.171]) by ietfa.amsl.com (Postfix) with ESMTP id 2F6D221F8442; Tue,  8 Jan 2013 10:57:01 -0800 (PST)
Received: by mail-lb0-f171.google.com with SMTP id gf7so641234lbb.30 for <multiple recipients>; Tue, 08 Jan 2013 10:57:01 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=WRDPit+3DGAsj/F43jvA6CbBefrcpcSZELhCupHfJeI=; b=VQSjKdnccxSHIg0dyCkaw1Jph28q5v6J9R1Sbd+zLEBDgxKctzDfZkFppkyNM/FbC2 qa2+NV9w9qfbT6ujfQD7lOFJoRYJcwOKqK2Zy2nXv6UAq0wzZp6w7yhIZfY9KzrVSIja spmQWXMusU4xPK5SU3ofxahys6csLXrqBcL76yZdZjPNVgF6qF7RZOwdfhkQXDZq1Q4i yDJvv7ydVZ2ah/WXDHJHyveyHTIuiUOfVsD4TFDSuTyyuQ5eJBLxJrwfucsyxSQm42Gv cPzO06m33n5RQzC2Qpiw2wVGVAkMb69yuT2Dpl691FM2gE+jjJk1sX6GBRC32Pa+QWKh YEmw==
MIME-Version: 1.0
Received: by 10.152.121.212 with SMTP id lm20mr61998011lab.42.1357671421098; Tue, 08 Jan 2013 10:57:01 -0800 (PST)
Received: by 10.112.43.226 with HTTP; Tue, 8 Jan 2013 10:57:00 -0800 (PST)
In-Reply-To: <CAD5Szk-CTBSeTc-QvDLZ3o5twYq6WF=g6Wr1bsDc=ub=T0pXZg@mail.gmail.com>
References: <20121211150057.28223.93310.idtracker@ietfa.amsl.com> <50cb04b9.86df440a.72fe.1e20SMTPIN_ADDED_BROKEN@mx.google.com> <CABP7RbeNsZ_rBWRjou=VG+hBhUKaOz+y1a0sSChwWiHte9znnQ@mail.gmail.com> <50cb5f3c.694c420a.38fb.39afSMTPIN_ADDED_BROKEN@mx.google.com> <CAChr6SxZRc3B_HCbw76kLe2dsRSr43r-gLpfMVnCUfJTrZdTLA@mail.gmail.com> <CABP7RbfA33huBFadMeXTTEt=MkjW8-d4DFH7+GLXGurnm9sSRw@mail.gmail.com> <CAOXDeqpPE4eNy_qJpDPdPHbCQakG9-hDcNZ3Sj9r4kWedByVzQ@mail.gmail.com> <CAChr6SwtS_=iS-k4mJm1vHjEvvGVzay5jDYeGheqsPZqO-89CQ@mail.gmail.com> <EABB8F51-C3B4-49F5-8672-5C2ABAC7043A@mnot.net> <CAChr6Sx7JdKM91EwJaSZ0Ra_F4FSqkuc3vzTY1LM=F_8sWho+Q@mail.gmail.com> <1357515310.6827.23.camel@polyglot> <CAChr6SyAq=7aQdZn54ihYK+0hDhL--2Oaq0RvehoNFbwKNNShA@mail.gmail.com> <CAChr6SxorKO20rGYi-e4YNF=HNGrwz8wPGKCFZQYWQwqsetjjg@mail.gmail.com> <CAOXDeqqE2mCLapwvjwQkme5VTpRCfmF0mFQcx02WW0-zi4i5=g@mail.gmail.com> <50EB4E8B.30700@versi.edu.au> <CAOXDeqoOj1K_zBWVZbE2j4Vnp1pYZ1yUEp9nyTKZmp-QrAziqg@mail.gmail.com> <CAD5Szk-U1LeBSfUgah8XXE2LZ=utR=0W-V7VsT6j-i2VixZerg@mail.gmail.com> <CAChr6SzvXWkkCZU3GPGFJtoqZ=0AOktFhrML6ZMtf7nU9iwxjw@mail.gmail.com> <CAD5Szk-CTBSeTc-QvDLZ3o5twYq6WF=g6Wr1bsDc=ub=T0pXZg@mail.gmail.com>
Date: Tue, 8 Jan 2013 10:57:00 -0800
Message-ID: <CAChr6Sxnj=tbV1fUPHzVh4N_0T_13x2nGDCs0LQ92t5wKmfb5A@mail.gmail.com>
Subject: Re: [apps-discuss] Last Call: <draft-ietf-appsawg-json-pointer-07.txt> (JSON Pointer) to Proposed Standard
From: Robert Sayre <sayrer@gmail.com>
To: Jared Rosoff <jsr@10gen.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: Mark Nottingham <mnot@mnot.net>, IETF Discussion <ietf@ietf.org>, Matthew Morley <matt@mpcm.com>, IETF Apps Discuss <apps-discuss@ietf.org>, IESG <iesg@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 08 Jan 2013 18:57:03 -0000

On Tue, Jan 8, 2013 at 9:52 AM, Jared Rosoff <jsr@10gen.com> wrote:
>
> 1) It seems like some of the examples raised on this thread conflate JSON
> documents with Javascript objects. According to the json spec, an object
> always starts with an "{" and ends with a "}". Therefore, while the json
> path "/1" could refer to elements in { "1": "a" } and [1,2], the latter is
> not a correct JSON object.

>From a JS shell session:

% JSON.stringify([1,2])
"[1,2]"

- Rob

From abdussalambaryun@gmail.com  Tue Jan  8 10:57:47 2013
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 42FD421F8447 for <ietf@ietfa.amsl.com>; Tue,  8 Jan 2013 10:57:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.582
X-Spam-Level: 
X-Spam-Status: No, score=-3.582 tagged_above=-999 required=5 tests=[AWL=0.017,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 9GKOoCx7aqWT for <ietf@ietfa.amsl.com>; Tue,  8 Jan 2013 10:57:46 -0800 (PST)
Received: from mail-vb0-f53.google.com (mail-vb0-f53.google.com [209.85.212.53]) by ietfa.amsl.com (Postfix) with ESMTP id 9BCCB21F8446 for <ietf@ietf.org>; Tue,  8 Jan 2013 10:57:46 -0800 (PST)
Received: by mail-vb0-f53.google.com with SMTP id b23so731166vbz.26 for <ietf@ietf.org>; Tue, 08 Jan 2013 10:57:46 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=kdP0gb68/BKUebxt+ENnLmYRMv8xz6tDxQnWBIEXTP0=; b=gzIfa5bKEqnCRCVGUgOWPDyKkpE+2m9KwDsnkeN++OGZDBsX7dOGPCRIS/7NE4U5jh 6FVKWgpQ29+hiyOqji9410FLenJVVehXsVU3NOAKzSLOyHLOgUTcwidKIdyybLe1Xyaw PoBZNTFOtNAvF/DrZXFhlSW2VMzhL/Tttdu/e9MSpQp2nn3aZmAnbksV1TIfc0Z4LvBm NUiCStpxe224JRhn9K8nHw8HoHZ3opFerqTmJBMxtdA+GtZQxJ1Kk/xZGEIfTiymZZOg 94TaDlmEVNUfHOr+yonq0nfq+wdDGizruRgGL1lwZNV751rP/E0kr9KyORytKalYaI66 dZrw==
MIME-Version: 1.0
Received: by 10.220.149.69 with SMTP id s5mr87851886vcv.23.1357671466118; Tue, 08 Jan 2013 10:57:46 -0800 (PST)
Received: by 10.220.145.5 with HTTP; Tue, 8 Jan 2013 10:57:46 -0800 (PST)
In-Reply-To: <CADnDZ88BVr6wj_RTGh8bMEkUt-sobWuDH-v0wyHVabSETVHrkA@mail.gmail.com>
References: <CADnDZ8_GgVeapUKefFMqOvwOo00X8_rFDWMR0vb-Zvu_p=yT3A@mail.gmail.com> <a062408a2cd10003cf574@10.0.1.3> <CADnDZ88BVr6wj_RTGh8bMEkUt-sobWuDH-v0wyHVabSETVHrkA@mail.gmail.com>
Date: Tue, 8 Jan 2013 19:57:46 +0100
Message-ID: <CADnDZ88PJ4yCNp+6TSBFYNn_QMOZM_BFB4p3nmFy4R3XeApYLQ@mail.gmail.com>
Subject: Re: A proposal for a scientific approach to this question [was Re: I'm struggling with 2219 language again]
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: John Day <jeanjour@comcast.net>
Content-Type: text/plain; charset=ISO-8859-1
Cc: ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 08 Jan 2013 18:57:47 -0000

>but the question of
> error in process is; does the RFC lack communication requirement with
> the community?
>

Sorry if not clear. I mean that as some participant are requesting a
scientific approach to struggling with 2119 (i.e. thread-subject),
does that mean in some RFCs the use or not use (i.e. we see that
participant use different approaches to follow the 2119) that it may
add communication confuse with some of community?

AB

From abdussalambaryun@gmail.com  Tue Jan  8 11:01:36 2013
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4BA4F21F8447 for <ietf@ietfa.amsl.com>; Tue,  8 Jan 2013 11:01:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.582
X-Spam-Level: 
X-Spam-Status: No, score=-3.582 tagged_above=-999 required=5 tests=[AWL=0.017,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 4cL0xICBRgQc for <ietf@ietfa.amsl.com>; Tue,  8 Jan 2013 11:01:35 -0800 (PST)
Received: from mail-vc0-f178.google.com (mail-vc0-f178.google.com [209.85.220.178]) by ietfa.amsl.com (Postfix) with ESMTP id AC9BC21F8446 for <ietf@ietf.org>; Tue,  8 Jan 2013 11:01:35 -0800 (PST)
Received: by mail-vc0-f178.google.com with SMTP id l6so746163vcl.23 for <ietf@ietf.org>; Tue, 08 Jan 2013 11:01:35 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=CbgUtqqR6rFsKhLlCxiDA7OwLh+BytG2ckaop9JRiZA=; b=RiAATMF8tL19YD23GWLyNskk7sD6TA+UP1FvTIQSGunh3+r7CroNw/eXT7ufEymMhw m8FKTEYY/Xjq1EyvVHVLy1RPeKyk7tfYi+jqyf4D3xpSnrIgU38UY9FVaYXNBZ6V60s0 uMGE+fIpC8f9xuI95Vxs4gISMvIUUHiSWDdjN2X3JyYLqSMOJoxHM1u07GD6j1cWo8Rr nMThwUZ7XHcHYO13HV8w1teHp/DkjLKdLaCv+0xpidw6ZYeMGrH8uLwkw7VYeDkRce/T 5by8BEq3UgWW80C5NxguYo5Hfb/nRBzpja6cHtZJ76UifAvC98AU1IxpsNYCAdW5pP8p zK4w==
MIME-Version: 1.0
Received: by 10.52.27.50 with SMTP id q18mr77081347vdg.20.1357671695201; Tue, 08 Jan 2013 11:01:35 -0800 (PST)
Received: by 10.220.145.5 with HTTP; Tue, 8 Jan 2013 11:01:35 -0800 (PST)
In-Reply-To: <CADnDZ88PJ4yCNp+6TSBFYNn_QMOZM_BFB4p3nmFy4R3XeApYLQ@mail.gmail.com>
References: <CADnDZ8_GgVeapUKefFMqOvwOo00X8_rFDWMR0vb-Zvu_p=yT3A@mail.gmail.com> <a062408a2cd10003cf574@10.0.1.3> <CADnDZ88BVr6wj_RTGh8bMEkUt-sobWuDH-v0wyHVabSETVHrkA@mail.gmail.com> <CADnDZ88PJ4yCNp+6TSBFYNn_QMOZM_BFB4p3nmFy4R3XeApYLQ@mail.gmail.com>
Date: Tue, 8 Jan 2013 20:01:35 +0100
Message-ID: <CADnDZ8_7NJEo4qYWpQyKLrpZ9g80XY3UjNW2vK6J2sNd6nzWgQ@mail.gmail.com>
Subject: Re: A proposal for a scientific approach to this question [was Re: I'm struggling with 2219 language again]
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: ietf <ietf@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 08 Jan 2013 19:01:36 -0000

Why not participant follow one approach to use 2119 in IDs and done,
and if not/another, then please specify in the language section.

AB

From dean.willis@softarmor.com  Tue Jan  8 15:39:27 2013
Return-Path: <dean.willis@softarmor.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0F27121F84E9 for <ietf@ietfa.amsl.com>; Tue,  8 Jan 2013 15:39:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.599
X-Spam-Level: 
X-Spam-Status: No, score=-103.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
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 i9fACChADx4h for <ietf@ietfa.amsl.com>; Tue,  8 Jan 2013 15:39:26 -0800 (PST)
Received: from mail-ob0-f174.google.com (mail-ob0-f174.google.com [209.85.214.174]) by ietfa.amsl.com (Postfix) with ESMTP id 0F4C821F84E6 for <ietf@ietf.org>; Tue,  8 Jan 2013 15:39:25 -0800 (PST)
Received: by mail-ob0-f174.google.com with SMTP id ta14so1547221obb.33 for <ietf@ietf.org>; Tue, 08 Jan 2013 15:39:25 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=softarmor.com; s=google; h=x-received:content-type:mime-version:subject:from:in-reply-to:date :cc:content-transfer-encoding:message-id:references:to:x-mailer; bh=bV3BKkrE13mv3XFduOZCCmUHjq/k516D+30CsPjCbr4=; b=C3DAdeEBsSggHnjcHzoKo3mdJBPHp9eAJ5WXcpth/jsM/iyB48IqDgQGJwtnvawNhB bT+Qloxwtpk3P/03/9U06hNmp04NJXGwAVnfAQrt6iShmnOLKCUlnBzqG3bgk09TCo9t woTVjlMcABLIXbUxtQYy3GvPvCTNZDvSwZQ78=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:content-type:mime-version:subject:from:in-reply-to:date :cc:content-transfer-encoding:message-id:references:to:x-mailer :x-gm-message-state; bh=bV3BKkrE13mv3XFduOZCCmUHjq/k516D+30CsPjCbr4=; b=CQusc0vzOeqo44oPPKFHxr/nRF9vGGZrj5NuNl8QBQL4PcCznvQl5952CQZEKsVKEw 9vJ+O8Gb96VfPR4Eectd3u7I4bcIzZSL758aSW2Mh+H7NRmriu4OQt5iHkyKJ54pDV+i 61AYzK2dO5Kdg+KctBK5LDTxcNKWJ2EK6XVpAu1QCBYr3nHHlDa7kX11XZamOD1r1WZl afe8gJaKSDlK5G4xTuU2HC0woHfs3HNgoDw2SSG5GjPGCRDY/6zpue4frBYAnDRElE05 TAkvzEGbYreAtw8eyypUxHb4XosvojoPlx3mZmIoF3hayaJ/xOa07FsLcMabQN9ZNu8k E8RQ==
X-Received: by 10.60.3.168 with SMTP id d8mr36742195oed.112.1357688365558; Tue, 08 Jan 2013 15:39:25 -0800 (PST)
Received: from [192.168.2.115] (cpe-72-181-157-19.tx.res.rr.com. [72.181.157.19]) by mx.google.com with ESMTPS id jd1sm34634808obb.8.2013.01.08.15.39.23 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 08 Jan 2013 15:39:24 -0800 (PST)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Subject: Re: A proposal for a scientific approach to this question [was Re: I'm struggling with 2219 language again]
From: Dean Willis <dean.willis@softarmor.com>
In-Reply-To: <50EAA93C.6060206@cisco.com>
Date: Tue, 8 Jan 2013 17:39:23 -0600
Content-Transfer-Encoding: quoted-printable
Message-Id: <21761F34-2D84-42BB-A149-BCF6A49ECD0D@softarmor.com>
References: <CADnDZ8_GgVeapUKefFMqOvwOo00X8_rFDWMR0vb-Zvu_p=yT3A@mail.gmail.com> <a062408a2cd10003cf574@[10.0.1.3]> <50EAA93C.6060206@cisco.com>
To: stbryant@cisco.com
X-Mailer: Apple Mail (2.1499)
X-Gm-Message-State: ALoCoQlopDs265QJZMwT7EaDIg3Rm3OxXgUHXewovrDbN5gMlIkgO70gHb/DBqti4KxwSUGZ7xlM
Cc: ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 08 Jan 2013 23:39:27 -0000

On Jan 7, 2013, at 4:53 AM, Stewart Bryant <stbryant@cisco.com> wrote:

> Speaking as both a reviewer and an author, I would like
> to ground this thread to some form of reality.
>=20
> Can anyone point to specific cases where absence or over
> use of an RFC2119 key word caused an interoperability failure,
> or excessive development time?


I'm anecdotally familiar with some early pre-RFC 2543 SIP =
implementations where the implementors ignored everything that didn't =
say MUST and got something that didn't work. At all. But it was =
apparently really easy to develop, as the spec only had a few dozen MUST =
clauses, and the developers didn't include-by-reference any of the cited =
specs, such as SDP.

When we were trying to decide whether to make RFC 3261 (the replacement =
of RFC 2543) a "draft standards" instead of a "proposed standard", I =
recall Robert Sparks and some others attempting to define a "fully =
interoperable implementation" test that tabulated all of the RFC 2119 =
invocations that had sprouted in FC 3261. They then immediately gave up =
the idea as impractical, we recycled at "proposed", and gave up on every =
making "full". The testing methodology has greatly improved since then, =
and it makes lithe use of RFC 2119 language for test definition or =
construction.=20

--
Dean



From dean.willis@softarmor.com  Tue Jan  8 15:54:38 2013
Return-Path: <dean.willis@softarmor.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AC62B11E80CC for <ietf@ietfa.amsl.com>; Tue,  8 Jan 2013 15:54:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.599
X-Spam-Level: 
X-Spam-Status: No, score=-103.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
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 HQXuZwBpuAGM for <ietf@ietfa.amsl.com>; Tue,  8 Jan 2013 15:54:38 -0800 (PST)
Received: from mail-ob0-f169.google.com (mail-ob0-f169.google.com [209.85.214.169]) by ietfa.amsl.com (Postfix) with ESMTP id EE8B911E80AE for <ietf@ietf.org>; Tue,  8 Jan 2013 15:54:37 -0800 (PST)
Received: by mail-ob0-f169.google.com with SMTP id v19so1552559obq.28 for <ietf@ietf.org>; Tue, 08 Jan 2013 15:54:37 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=softarmor.com; s=google; h=x-received:content-type:mime-version:subject:from:in-reply-to:date :cc:content-transfer-encoding:message-id:references:to:x-mailer; bh=YNhgWsu8ps8SfFFcvD37nretIx1ypeRPKFaRnootDG4=; b=WYn/6hw3SlP0Yxk8LFVb7bR9klBII6SUwqjoqRiG9LkQS1oxklOiHH7Xk2cZguZ49X YOaJRLTRd4HPNNLp5xuqOQr4bGToPLcEN5JkaR0IhOHkwISOydTL4f4VU+OtSslVm7Yt d6Vko5NMeUm3Lho+fDP+lLWwNeKUFyg/nIBdI=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:content-type:mime-version:subject:from:in-reply-to:date :cc:content-transfer-encoding:message-id:references:to:x-mailer :x-gm-message-state; bh=YNhgWsu8ps8SfFFcvD37nretIx1ypeRPKFaRnootDG4=; b=cf9/ocrEDDrGsIeh9UhMhhuxTGcq5+lgMF/X1WI4sZSPrVLeJx9Gwo95dwaNov8Sxj N9vcTtKCivvH4FftNaulloP5wXDOCIF3zw2mSq5AsCYF0zyNJtNzAuR/IN9dFaR/jXxW /KrtEmA9ac76x9qj7y2NOgNroVouHtuK3pCW4D9xJmlqZnPQ254+MHtPjVYPO8F3mDYQ sE7Z2Mz+oA0HntVqQxIqpMO70N1zneS4MfY7KAg7jK7ZqyhM9aQM7uzVZCOf21BFnkAE QU8EvX0TH/U9PB7y1xm/n+Jk1YQiYnrxTMpMlNrGbiG9ssyoJ2izLj4gQT6GS8t7hfhB /GBg==
X-Received: by 10.182.69.71 with SMTP id c7mr45812510obu.92.1357689277371; Tue, 08 Jan 2013 15:54:37 -0800 (PST)
Received: from [192.168.2.115] (cpe-72-181-157-19.tx.res.rr.com. [72.181.157.19]) by mx.google.com with ESMTPS id aw4sm35623950oec.9.2013.01.08.15.54.36 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 08 Jan 2013 15:54:36 -0800 (PST)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Subject: Re: A proposal for a scientific approach to this question [was Re: I'm struggling with 2219 language again]
From: Dean Willis <dean.willis@softarmor.com>
In-Reply-To: <CADnDZ88PJ4yCNp+6TSBFYNn_QMOZM_BFB4p3nmFy4R3XeApYLQ@mail.gmail.com>
Date: Tue, 8 Jan 2013 17:54:35 -0600
Content-Transfer-Encoding: quoted-printable
Message-Id: <3D453E57-252A-467C-B64A-6671C85FD4BB@softarmor.com>
References: <CADnDZ8_GgVeapUKefFMqOvwOo00X8_rFDWMR0vb-Zvu_p=yT3A@mail.gmail.com> <a062408a2cd10003cf574@10.0.1.3> <CADnDZ88BVr6wj_RTGh8bMEkUt-sobWuDH-v0wyHVabSETVHrkA@mail.gmail.com> <CADnDZ88PJ4yCNp+6TSBFYNn_QMOZM_BFB4p3nmFy4R3XeApYLQ@mail.gmail.com>
To: Abdussalam Baryun <abdussalambaryun@gmail.com>
X-Mailer: Apple Mail (2.1499)
X-Gm-Message-State: ALoCoQnK6yxpQOdheE5UqPOEPPv2YRf5f1n68aIlCzcB8Z8SKwyMc1xlNwmhjikWhc6ulaH/updz
Cc: ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 08 Jan 2013 23:54:38 -0000

On Jan 8, 2013, at 12:57 PM, Abdussalam Baryun =
<abdussalambaryun@gmail.com> wrote:

>> but the question of
>> error in process is; does the RFC lack communication requirement with
>> the community?
>>=20
>=20
> Sorry if not clear. I mean that as some participant are requesting a
> scientific approach to struggling with 2119 (i.e. thread-subject),
> does that mean in some RFCs the use or not use (i.e. we see that
> participant use different approaches to follow the 2119) that it may
> add communication confuse with some of community?
>=20

I'm absolutely certain that some of our community is confused about =
something related to this thread. Given the absence of information that =
would help in a decision, might preference would be just to pick one, =
and provide a stick for hitting those who do it the other way.

--
Dean



From hsantos@isdg.net  Tue Jan  8 15:59:43 2013
Return-Path: <hsantos@isdg.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2864D11E80D1 for <ietf@ietfa.amsl.com>; Tue,  8 Jan 2013 15:59:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.484
X-Spam-Level: 
X-Spam-Status: No, score=-102.484 tagged_above=-999 required=5 tests=[AWL=0.115, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 H+0w2V41hrNX for <ietf@ietfa.amsl.com>; Tue,  8 Jan 2013 15:59:42 -0800 (PST)
Received: from mail.winserver.com (pop3.winserver.com [208.247.131.9]) by ietfa.amsl.com (Postfix) with ESMTP id B525411E809A for <ietf@ietf.org>; Tue,  8 Jan 2013 15:59:41 -0800 (PST)
DKIM-Signature: v=1; d=isdg.net; s=tms1; a=rsa-sha1; c=simple/relaxed; l=5502; t=1357689567; h=Received:Received: Received:Received:Message-ID:Date:From:Organization:To:Subject: List-ID; bh=27BlMqfqTE51ywf8xIdHQ0NIWKY=; b=lOwxhY/N0e1XWkbxmfkP UfT0IKtTB2vozRMKzT8vEm1urEuxEvbZf+XnuyiDw8C9ypfKjMmoZ82P1h80RPXt ePfQ/UVPX3UM8ZHXm1mRKLHPF+GspyZBTTSKjFmp/ijW45Xkc1qXMGEqah3KVek0 iDglpmkqG+wP6xKbU+KDAMA=
Received: by winserver.com (Wildcat! SMTP Router v7.0.454.4) for ietf@ietf.org; Tue, 08 Jan 2013 18:59:27 -0500
Authentication-Results: dkim.winserver.com; dkim=pass header.d=beta.winserver.com header.s=tms1 header.i=beta.winserver.com;  adsp=pass policy=all author.d=isdg.net asl.d=beta.winserver.com;
Received: from hector.wildcatblog.com ([208.247.131.23]) by winserver.com (Wildcat! SMTP v7.0.454.4) with ESMTP id 826326093.4432.3612; Tue, 08 Jan 2013 18:59:26 -0500
DKIM-Signature: v=1; d=beta.winserver.com; s=tms1; a=rsa-sha256; c=simple/relaxed; l=5502; t=1357689512; h=Received:Received: Message-ID:Date:From:Organization:To:Subject:List-ID; bh=Kr35vII is8N1NpWkcVLX790CpKiA8xmP3OZ0VZmLcAs=; b=RMzBNMa68zfWSPd4lb6eTYY hPZSi9a9dLtrpiPOoC7RH1F575BMag4MJhX+rSjKdGqMoWmDLgthDxoo3aa4OV/r fSZo4r2YIuLIwxciYRjDo1clwHNV4cLryUXE2nzVdlhRlY8wO3aPrKFAJDuWT8X/ /ulfacc8JZSWqVzTES8U=
Received: by beta.winserver.com (Wildcat! SMTP Router v7.0.454.4) for ietf@ietf.org; Tue, 08 Jan 2013 18:58:32 -0500
Received: from [192.168.1.101] ([99.3.147.93]) by beta.winserver.com (Wildcat! SMTP v7.0.454.4) with ESMTP id 1425027679.10.5212; Tue, 08 Jan 2013 18:58:31 -0500
Message-ID: <50ECB2CD.7090700@isdg.net>
Date: Tue, 08 Jan 2013 18:59:09 -0500
From: Hector Santos <hsantos@isdg.net>
Organization: Santronics Software, Inc.
User-Agent: Thunderbird 2.0.0.24 (Windows/20100228)
MIME-Version: 1.0
To: Carsten Bormann <cabo@tzi.org>
Subject: Re: [apps-discuss] Last Call:	<draft-ietf-appsawg-json-pointer-07.txt> (JSON Pointer) to	Proposed Standard
References: <20121211150057.28223.93310.idtracker@ietfa.amsl.com>	<50cb04b9.86df440a.72fe.1e20SMTPIN_ADDED_BROKEN@mx.google.com>	<CABP7RbeNsZ_rBWRjou=VG+hBhUKaOz+y1a0sSChwWiHte9znnQ@mail.gmail.com>	<50cb5f3c.694c420a.38fb.39afSMTPIN_ADDED_BROKEN@mx.google.com>	<CAChr6SxZRc3B_HCbw76kLe2dsRSr43r-gLpfMVnCUfJTrZdTLA@mail.gmail.com> <018651D6-83D4-42D6-86EB-0FAA5DE10DDA@tzi.org>
In-Reply-To: <018651D6-83D4-42D6-86EB-0FAA5DE10DDA@tzi.org>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Cc: IETF Discussion <ietf@ietf.org>, Markus Lanthaler <markus.lanthaler@gmx.net>, IETF Apps Discuss <apps-discuss@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 08 Jan 2013 23:59:43 -0000

Thanks Carsten for your explanations.  As having experience with both 
styles of programming as you describe and also interpretive vs p-code 
vs static compiler writing for our servers and clients, it would seem 
to me that if the both syntaxes are possible, then the solution is 
more implementator specific. In other words, implementators can deal 
with both if robustness is desired.  It sounds "kludgy" but it sounds 
like there exist both styles in practice already, so unless breaking 
existing implementators is not a concern in the name of going with the 
"correct and prefer" syntax, then both need to be supported.

The first thing that came to mind when this interesting thread started 
is whether a solution is desired for a public open-ended query 
client/server system versus this being more proprietary (presuming the 
idea of "patching" is an high authentication required concept).  It 
would seem to me that they might be various clients used against a 
server and it would be up to the server to support all possibilities 
to remain robust.   The client itself is probably having its "JIT" 
(Just-In-Time) parsing/compiling/error trapping, etc or it might be 
more static to catch canned solutions.  The client can perhaps have 
all its data I/O resolved by the "ide" new JSON support for data C/S 
(including "AJAX") transactions.  Come to think to it, the server 
implementation itself COULD have its syntax checking before release 
the page for production and/or if dynamically generated then it would 
probably use a preferred syntax.

It seems the answer is to support both syntaxes IFF there is compiler 
or interpretation logic capability to trapping both and if there are 
already existing clients and servers, note (highlight) that servers 
|need to|SHOULD| be ready for both.

I will say one thing, if we ever needed a HTTP based patching need or 
requirement to add support to our product web server component, it 
doesn't seem I have any choice - it would be prudent to support both 
especially on the client side.  What method I would use for our own 
data exchanges may be preferred method, but the server would need to 
do both.

--
HLS


Carsten Bormann wrote:
> For those who wonder what all the fuzz in this thread is about, let me try to explain this with some different terminology, exposing what kind of intuition these widely diverging value judgements might derive from.
> 
> In programming, there are two camps: static typers and dynamic typers.  Static typers want to annotate their programs with information about the objects being manipulated so the compiler can help them catch careless mistakes even before the program runs.  Dynamic typers don't care about that as much, because they know they have to write tests anyway (not all programming errors are exposable as type errors) and these will uncover the same careless mistakes.  [The runtime system will actually check types once the specific context of execution is available, that's why it's called "dynamic typing".]
> 
> The programming debate is beside the point here for a number of reasons*), but it does shape the thinking of programmers, and it seems in particular it shaped the thinking of some of the commenters here.
> 
> /a/1/b/2 is something that a dynamic typer would come up with.  The specific semantics are well-defined, but only in the specific execution context (what JSON document this is being applied to).
> /a:1/b:2 (to use James' strawman syntax that distinguishes JSON object keys from array indices) exposes more typing info, so it is more statically typed, and it will catch mismatches between the types that the JSON pointer assumed to be present and those that actually are.
> 
> For a static-typing fundamentalist, it is viscerally unacceptable to forego the opportunity of catching this kind of "type error".
> 
> For a non-fundamentalist, this is more of an issue of probabilities, and the interlocking of mechanisms.  
> Which percentage of usage errors will be caught by this?
> Many, many mismatches between JSON pointers and JSON instances to will just not happen to trigger this particular type error.
> So it can be argued that the ability to catch it doesn't really help much: If you care about mismatch errors, you already need to have something else in place to catch them -- relying only on the likelihood of a mismatch to trigger an array/object mismatch would be imprudent. So in reality, the ability to catch the type error buys you nothing.
> (Or, actually, very little, as improved diagnostics is always worth something in a debugging situation.)
> 
> TL;DR: there is no "ambiguity" at all.  Please stop referring to an "ambiguity".  There is none.
> Just a missed opportunity to catch an error, caused by not sending along (redundant) type information.
> 
> (You will gather that my 2 cents for this change are "not worth it", but I was more interested in explaining the mere existence of this discussion, first.  Applying the wrong intuitions to an engineering decision is one of the major causes of suboptimal design...)
> 
> Grï¿½ï¿½e, Carsten
> 
> *) Well, for a start, we are not here to catch errors in programming.  Programming languages are difficult because they are the human interface to the computer's programmability.  JSON pointers are a pure machine-to-machine mechanism, so most of the issues in programming just don't arise.  Porting your intuitions from programming to this is not going to work very well.
> 
> 
> 

-- 
HLS



From mrex@sap.com  Tue Jan  8 16:36:13 2013
Return-Path: <mrex@sap.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6A8B211E809A for <ietf@ietfa.amsl.com>; Tue,  8 Jan 2013 16:36:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.249
X-Spam-Level: 
X-Spam-Status: No, score=-10.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_HI=-8]
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 oQAutbrWaLwl for <ietf@ietfa.amsl.com>; Tue,  8 Jan 2013 16:36:12 -0800 (PST)
Received: from smtpde02.sap-ag.de (smtpde02.sap-ag.de [155.56.68.140]) by ietfa.amsl.com (Postfix) with ESMTP id A763E1F0CAF for <ietf@ietf.org>; Tue,  8 Jan 2013 16:36:11 -0800 (PST)
Received: from mail05.wdf.sap.corp by smtpde02.sap-ag.de (26) with ESMTP id r090a9x2014661 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 9 Jan 2013 01:36:09 +0100 (MET)
Subject: Re: A proposal for a scientific approach to this question [was Re: I'm struggling with 2219 language again]
In-Reply-To: <CAF4+nEE9uq_811ZMX4ShCqoprL_FZFhY4XW9W2U0TZmpf86uTQ@mail.gmail.com>
To: Donald Eastlake <d3e3e3@gmail.com>
Date: Wed, 9 Jan 2013 01:36:09 +0100 (CET)
X-Mailer: ELM [version 2.4ME+ PL125 (25)]
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="US-ASCII"
Message-Id: <20130109003609.2BFF41A445@ld9781.wdf.sap.corp>
From: mrex@sap.com (Martin Rex)
X-SAP: out
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: mrex@sap.com
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 09 Jan 2013 00:36:13 -0000

 
>John Day <jeanjour@comcast.net> wrote:
>>
>> The reasons have been discussed or at least alluded to previously in this
>> thread.  The short answer is we have been there and done that: 30 years ago.
>>
>> All those tools were developed and used successfully in the 80s.
>> I know of cases where doing the formal specification alongside the
>> design phase caught lots of problems.   However, there are two
>> central problems:  First, in general, programmers are lazy and just
>> want to code. ;-)  Using a formal method is a lot more work.
>> Second, the complexity of the formal statements that must be written
>> down is greater than the code.  So there is a higher probability
>> of mistakes in the formal description than in the code.
>> Admittedly, if those statements are made, one has a far greater
>> understanding of what you are doing.

I believe that the problem with the formal logic is that it is difficult
to both write as well as read/understand, and to verify that the chosen
"axioms" actually reflect (and lead to) the desired behaviour/outcome,
the relative of scarcity of suitable tools, the complexity of the
underlying theory and tools, and the tools' resulting lack of
"intuitive usability".


>>
>> Once you have both, there is still the problem that if a bug or ambiguity
>> shows up,

For any formal proofing system worth its dime, this can be 100% ruled out,
since the proofing system will emit a 100% bugfree implementation of the
spec in the programming language of your choice as a result/byproduct of the
formal proofing process.


>>
>>  neither the code nor the formal spec nor a prose spec can be taken
>> be the right one.  What is right is still in the heads of the authors.

But maybe you're not really thinking of a defect in the implementation
(commonly called "bug") but rather a "gap" in the specification that
leads to unintended or undesired behaviour of a 100% bug-free
implementation of your spec.

(see Section 4 of this paper for an example:
  http://digbib.ubka.uni-karlsruhe.de/volltexte/documents/1827
)


Donald Eastlake wrote:
>
> Another problem is maintenance. Protocols change. Having to maintain a
> formal specification is commonly at least an order of magnitude more
> effort than maintaining a prose description.

Definitely.  Discussing protocols at the level of formal specification
language would be quite challenging (typically impossible in an open
forum, I believe it is even be difficult in a small and well-trained
design team).


> 
> And, as has been mentioned before, I'd like to emphasize that the IETF
> experience and principal is that, if you want interoperation,
> compliance testing is useless.

Ouch.  I believe this message is misleading or wrong.

Compliance testing is VERY important, rather than useless,

Compliance testing would actually be perfectly sufficient iff the spec
was formally proven to be free of conflicts and ambiguities among
specified protocol elements -- plus a significant effort spent on
ensuring there were no "gaps" in the specification.

As it turns out, however, a significant amount of implementations will
be created by humans interpreting natural language specifications,
rather than implemenations created as 100% bug-free by-products of a
formal proof tool, and often, interop with such buggy, and often
spec-incompliant implementations is desirable and necessary since
they make up a significant part of the installed base.


>
> The way to interoperation is interoperation testing between
> implementations and, to a first approximation, the more and the
> earlier you do interoperation testing, the better.


The #1 reason for interop problems and road-block to evolution of
protocols is the wide-spread lack of compliance testing (on the flawed
assumption that it is useless) and focus on black-box interop testing
of the intersection of two subsets of protocol features.

The problem with interop testing is that it really doesn't provide
much of a clue, and the results can _not_ be extrapolated to features
and areas that were not interop tested (typically the other 90% of the
specification, many optional features and most of the extensibility).


The near complete breakage of TLS protocol version negotiation is a
result of the narrow-minded interop testing in companion with a complete
lack of compliance testing.


If done right, pure compliance testing can go a long way to providing
interop.  The only area where real interop testing is necessary is
those protocol areas where the spec contains conflicts/inconsistencies
that implementors didn't notice or ignored, or where there is a
widespread inconsistencies of implementations with the specification,
of created by careless premature shipping of a defective implementation
and factual creation of an installed base that is too large to ignore.


-Martin

From dean.willis@softarmor.com  Tue Jan  8 16:57:05 2013
Return-Path: <dean.willis@softarmor.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F2A1F21F8464 for <ietf@ietfa.amsl.com>; Tue,  8 Jan 2013 16:57:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.599
X-Spam-Level: 
X-Spam-Status: No, score=-103.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
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 dA1k61tbWAjk for <ietf@ietfa.amsl.com>; Tue,  8 Jan 2013 16:57:04 -0800 (PST)
Received: from mail-ob0-f179.google.com (mail-ob0-f179.google.com [209.85.214.179]) by ietfa.amsl.com (Postfix) with ESMTP id 43C4E21F8467 for <ietf@ietf.org>; Tue,  8 Jan 2013 16:57:04 -0800 (PST)
Received: by mail-ob0-f179.google.com with SMTP id x4so1632886obh.24 for <ietf@ietf.org>; Tue, 08 Jan 2013 16:57:03 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=softarmor.com; s=google; h=x-received:content-type:mime-version:subject:from:in-reply-to:date :cc:content-transfer-encoding:message-id:references:to:x-mailer; bh=KVH6l8JolUbSmkR3TAJyRqRLCpbFc49ZRNTAfPwsbL0=; b=KTIAy3RDSlfwNzK5eh2BSMfWcAXDxgHo99KhLZ9kaK5RkzjJHo9t+17i5FISAi+H2g BQ6OHT0e9qd1T3vrbKEliAgkyevSSiPkUKbaxB8lw0gJNXc0ibZb7XbjQBSVzie4/FJ5 gNQLSyU8up+amvwpvR4UlwfzQLevQUwYrTWoc=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:content-type:mime-version:subject:from:in-reply-to:date :cc:content-transfer-encoding:message-id:references:to:x-mailer :x-gm-message-state; bh=KVH6l8JolUbSmkR3TAJyRqRLCpbFc49ZRNTAfPwsbL0=; b=e/OPjvAW4cMuI8UJvy1HfVWxAHnZaeYGRcRY6uFHPqRdeEo27o+PsO8tofhggxxdut AQBxXHVRBBIk+HV+8ra4fbGBQ21Rfejl2TQIfKFIfZnYJ15Qw4P9IGxI3v6j1Z6G+ApJ ZOErw9/44LVf4C54fHgToEbVXnXrD/lVOBjLuChR9U+h2AmQl9mHSCU6SxcNhvD8/sy+ g1JiaW8DSE3Hi3CMb3/o9ZDe8yj/CkwWevOB0uco9/J+tVzl7CwGPibJc12LWW64L+Jl ditaS6eQQVAMzQKFfoNVDjsrZB+dy1qMvli2KccjJxnutINHAXj+JO9O+OHQYbNvtLKx 5SNg==
X-Received: by 10.182.194.2 with SMTP id hs2mr46371571obc.97.1357693023866; Tue, 08 Jan 2013 16:57:03 -0800 (PST)
Received: from [192.168.2.115] (cpe-72-181-157-19.tx.res.rr.com. [72.181.157.19]) by mx.google.com with ESMTPS id b6sm35756411oee.3.2013.01.08.16.57.02 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 08 Jan 2013 16:57:03 -0800 (PST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Subject: Re: travel guide for the next IETF...
From: Dean Willis <dean.willis@softarmor.com>
In-Reply-To: <4613980CFC78314ABFD7F85CC30277210EE27C34@IL-EX10.ad.checkpoint.com>
Date: Tue, 8 Jan 2013 18:57:01 -0600
Content-Transfer-Encoding: quoted-printable
Message-Id: <D62C90BC-9035-4826-BA2D-9F56778A6438@softarmor.com>
References: <50DF09C7.1060009@dcrocker.net> <20200.1356985377@sandelman.ca> <4613980CFC78314ABFD7F85CC30277210EE27C34@IL-EX10.ad.checkpoint.com>
To: Yoav Nir <ynir@checkpoint.com>
X-Mailer: Apple Mail (2.1499)
X-Gm-Message-State: ALoCoQkSpzTmw0pS+JwRZSZOVblH6NhdqUsSmFphgDZnXb1A5acusLZYK5yB6/Czo4uO+6tQFmx5
Cc: Michael Richardson <mcr@sandelman.ca>, IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 09 Jan 2013 00:57:05 -0000

On Jan 4, 2013, at 4:14 PM, Yoav Nir <ynir@checkpoint.com> wrote:

>=20
> Looking in Google Earth, you'll still need a car. Even with those =
hotels that are within walking distance, there are big stretches of road =
without any sidewalks.


Having a car won't do any good. There is, as far as I can tell, no place =
to park it but the hotel valet. Staying somewhere else doesn't sound =
like much of an option, either due to the park-and-ride situation.

This may be a new record in "really awkward" location; it could top the =
Dublin golf course (which was saved only by a shuttle bus to reality).

--
Dean


From petithug@acm.org  Tue Jan  8 17:01:54 2013
Return-Path: <petithug@acm.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5A59A1F0CAF for <ietf@ietfa.amsl.com>; Tue,  8 Jan 2013 17:01:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.277
X-Spam-Level: 
X-Spam-Status: No, score=-102.277 tagged_above=-999 required=5 tests=[AWL=0.323, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
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 mFtQz01MqgmF for <ietf@ietfa.amsl.com>; Tue,  8 Jan 2013 17:01:53 -0800 (PST)
Received: from implementers.org (implementers.org [IPv6:2604:3400:dc1:41:216:3eff:fe5b:8240]) by ietfa.amsl.com (Postfix) with ESMTP id 184EA21F865D for <ietf@ietf.org>; Tue,  8 Jan 2013 17:01:53 -0800 (PST)
Received: from [IPv6:2601:9:4b80:32:6c2d:621f:2867:7eb7] (unknown [IPv6:2601:9:4b80:32:6c2d:621f:2867:7eb7]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (Client CN "Marc Petit-Huguenin", Issuer "implementers.org" (verified OK)) by implementers.org (Postfix) with ESMTPS id 02A9020493; Wed,  9 Jan 2013 01:01:50 +0000 (UTC)
Message-ID: <50ECC18A.7050301@acm.org>
Date: Tue, 08 Jan 2013 17:02:02 -0800
From: Marc Petit-Huguenin <petithug@acm.org>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.11) Gecko/20121122 Icedove/10.0.11
MIME-Version: 1.0
To: Dick Franks <rwfranks@acm.org>
Subject: Re: A proposal for a scientific approach to this question [was Re: I'm struggling with 2219 language again]
References: <7ED55FF1-3E1A-4DF7-918E-07790517B848@softarmor.com> <50E87B7B.5070605@acm.org> <CAKW6Ri6mb2468ScH8zcfQFzerA-wsVqOTY56vgXgQ1OrX8mEdw@mail.gmail.com>
In-Reply-To: <CAKW6Ri6mb2468ScH8zcfQFzerA-wsVqOTY56vgXgQ1OrX8mEdw@mail.gmail.com>
X-Enigmail-Version: 1.4.1
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 09 Jan 2013 01:01:54 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On 01/08/2013 05:41 AM, Dick Franks wrote:
> On 5 January 2013 19:14, Marc Petit-Huguenin <petithug@acm.org> wrote: 
> [snip]
>> 
>> Another way to look at it would be to run the following experiment:
>> 
>> 1. Someone design a new protocol, something simple but not obvious, and
>> write in a formal language and keep it secret.
>> 
> Which raises the obvious question:  Why do we not write protocol specs in a
> formal specification language instead of struggling with the ambiguities of
> natural language?
> 
> Theorem provers and automated verification tools could then be brought to
> bear on both specifiations and implementations.
> 

IMO, the main problem with using a formal specification language is that it
would made RFCs a little bit too close to mathematics for some people, as math
is not patentable.  So do not expect any change in this direction.

- -- 
Marc Petit-Huguenin
Email: marc@petit-huguenin.org
Blog: http://blog.marc.petit-huguenin.org
Profile: http://www.linkedin.com/in/petithug
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iQIcBAEBCAAGBQJQ7MGHAAoJECnERZXWan7EFSEP/0fyEuzFAQMoGvgKFxZG5ZKZ
H94ALXz6pFiSyBC9xImwlUR1TzcKqQbu5BMkPjirsWq/Xt8vlRIEuv7DzpHg0Dp6
A4IuU6t/ddtf9FEHRdvmkUEkHrKd99BjiIBywRoPCRgnqPhYrk+Q7OmyFZzz6BI4
tobQLgIiS9EPZDync9iu8atfubMhuy95VM+v6VfIfOLkdw6HcJWUArRXMP5j2rgK
AD7vQ9SmYXI1x3ZFVjTzWDg4KCAk1uET7+r2QyvmYMgWS3B+bMTl0vCO6kz8TDzw
B8f6thEXZ2/VzLOmoklFxN3ZhR+VDyMzHC0BWgD1Ro1YNogB2G2En8HLlxrmoj6e
T2PIZNnT9xgzkVRkTDmerwLlg7dwUjn8nK/462WTlCRcrAVQ52PHzfDUlBDBdX+A
l10Teah5PbpE1cK285b2CX+nbXbaR3HrhXFdTwvfLruExgsm571isfH3WVmfxXsI
z+3hl+HW92FQ7nreV+BrX/BqwAMpcjG4lkNlM1GgduDuv/rv1nh0lKD9dazNvwmg
r7Qx8pi6TyYL2YbKb0GPRSUACNR8qAXOWHWD3TMuJqiuzIZFj1wCm0mqwzNt7KFG
6RFyTez/7jZWqXx8RPJ1awRnDSv5wiKcH2lgI0h6kvxWdVtnwGyWb3e/W/uY3//p
hcBfwtvCdfw/OiwxicJv
=PDy4
-----END PGP SIGNATURE-----

From rdroms.ietf@gmail.com  Tue Jan  8 17:05:54 2013
Return-Path: <rdroms.ietf@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BE57D21F8202 for <ietf@ietfa.amsl.com>; Tue,  8 Jan 2013 17:05:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.599
X-Spam-Level: 
X-Spam-Status: No, score=-103.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
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 9K--kaww7sXK for <ietf@ietfa.amsl.com>; Tue,  8 Jan 2013 17:05:54 -0800 (PST)
Received: from mail-qc0-f179.google.com (mail-qc0-f179.google.com [209.85.216.179]) by ietfa.amsl.com (Postfix) with ESMTP id EA37F21F81FF for <ietf@ietf.org>; Tue,  8 Jan 2013 17:05:53 -0800 (PST)
Received: by mail-qc0-f179.google.com with SMTP id b14so1211592qcs.38 for <ietf@ietf.org>; Tue, 08 Jan 2013 17:05:53 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:content-type:mime-version:subject:from:in-reply-to:date :cc:content-transfer-encoding:message-id:references:to:x-mailer; bh=uDWMahvpmPeA3EZu70Oww6QTOTrFgEuqIkiKVAi9GEA=; b=pfclkONJUrW0aqzEuTz5PjXHU3zFljISWYDcLstzNeDIhEYSfK6klo/7FZaE1oVxDF tvCnm/rI3O12XB/KRhVMLwZcqWkCC7/Be+9t7OtaZ/cLsEUXcpJ8LEI+WapKPNqfOApj 0j6ljXd7sXMY46W2EDnmUqbp6X4AbHMm33qExKUfWES5lx4yPFubeNTUBTd8gmRq//yX qUCDBn4mseFIrC2Q/7gHPke7PlStrtBlXYOn76jS0+tsh4p0YA6d1RJ4n0O37jhMTNxg 8xKdT83WawZFT21CZ1853XPORrLHZXCMatHeysdrEpfSngW/4QEHrFb15V02qbPV9loU tAiw==
X-Received: by 10.224.58.69 with SMTP id f5mr23056932qah.87.1357693553374; Tue, 08 Jan 2013 17:05:53 -0800 (PST)
Received: from ?IPv6:2001:420:2481:20:5850:556f:2a3a:166d? ([2001:420:2481:20:5850:556f:2a3a:166d]) by mx.google.com with ESMTPS id ou3sm18048561qeb.0.2013.01.08.17.05.49 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 08 Jan 2013 17:05:52 -0800 (PST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Subject: Re: travel guide for the next IETF...
From: Ralph Droms <rdroms.ietf@gmail.com>
In-Reply-To: <alpine.OSX.2.01.1301032354480.80268@173-11-110-132-sfba.hfc.comcastbusiness.net>
Date: Tue, 8 Jan 2013 20:05:46 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <FFD9072E-0C54-4040-BAB8-5219D318F4E2@gmail.com>
References: <20130102231451.24327.qmail@joyce.lan> <alpine.OSX.2.01.1301032354480.80268@173-11-110-132-sfba.hfc.comcastbusiness.net>
To: Ole Jacobsen <ole@cisco.com>
X-Mailer: Apple Mail (2.1499)
Cc: John Levine <johnl@taugh.com>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 09 Jan 2013 01:05:54 -0000

On Jan 4, 2013, at 2:55 AM 1/4/13, Ole Jacobsen <ole@cisco.com> wrote:

>=20
> You have been warned.
>=20
> =
http://news.yahoo.com/video/request-ketchup-philly-cheesesteak-leads-00120=
4299.html

I'm sorry - seeing the words "Philly cheesesteak" and "Subway" in the =
same title are such a non sequitor for this long-time Phillies, Eagles =
and Flyers fan that I couldn't bring myself to watch the video.

- Ralph

>=20
>=20
> Ole J. Jacobsen
> Editor and Publisher,  The Internet Protocol Journal
> Cisco Systems
> Tel: +1 408-527-8972   Mobile: +1 415-370-4628
> E-mail: ole@cisco.com  URL: http://www.cisco.com/ipj
> Skype: organdemo
>=20
>=20


From shanna@juniper.net  Tue Jan  8 17:27:59 2013
Return-Path: <shanna@juniper.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4F9CB11E80BA for <ietf@ietfa.amsl.com>; Tue,  8 Jan 2013 17:27:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.467
X-Spam-Level: 
X-Spam-Status: No, score=-103.467 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, UNRESOLVED_TEMPLATE=3.132, USER_IN_WHITELIST=-100]
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 j4j0c3bh5Npv for <ietf@ietfa.amsl.com>; Tue,  8 Jan 2013 17:27:58 -0800 (PST)
Received: from exprod7og107.obsmtp.com (exprod7og107.obsmtp.com [64.18.2.167]) by ietfa.amsl.com (Postfix) with ESMTP id 5B17C11E809C for <ietf@ietf.org>; Tue,  8 Jan 2013 17:27:58 -0800 (PST)
Received: from P-EMHUB03-HQ.jnpr.net ([66.129.224.36]) (using TLSv1) by exprod7ob107.postini.com ([64.18.6.12]) with SMTP ID DSNKUOzHntGSx519XisIWe4dPnSL+XUG4wUQ@postini.com; Tue, 08 Jan 2013 17:27:58 PST
Received: from P-CLDFE02-HQ.jnpr.net (172.24.192.60) by P-EMHUB03-HQ.jnpr.net (172.24.192.37) with Microsoft SMTP Server (TLS) id 8.3.213.0; Tue, 8 Jan 2013 17:26:45 -0800
Received: from o365mail.juniper.net (207.17.137.149) by o365mail.juniper.net (172.24.192.60) with Microsoft SMTP Server id 14.1.355.2; Tue, 8 Jan 2013 17:26:45 -0800
Received: from db3outboundpool.messaging.microsoft.com (213.199.154.139) by o365mail.juniper.net (207.17.137.149) with Microsoft SMTP Server (TLS) id 14.1.355.2; Tue, 8 Jan 2013 17:28:52 -0800
Received: from mail1-db3-R.bigfish.com (10.3.81.227) by DB3EHSOBE005.bigfish.com (10.3.84.25) with Microsoft SMTP Server id 14.1.225.23; Wed, 9 Jan 2013 01:26:43 +0000
Received: from mail1-db3 (localhost [127.0.0.1])	by mail1-db3-R.bigfish.com (Postfix) with ESMTP id 603E82203CC	for <ietf@ietf.org.FOPE.CONNECTOR.OVERRIDE>; Wed,  9 Jan 2013 01:26:43 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.234.117; KIP:(null); UIP:(null); (null); H:SN2PRD0510HT002.namprd05.prod.outlook.com; R:internal; EFV:INT
X-SpamScore: -1
X-BigFish: PS-1(zz98dIda00h4015Izz1ee6h1de0h1202h1e76h1d1ah1d2ahzz8275bh17326ah17598diz2dh2a8h668h839h944hd25hf0ah1220h1288h12a5h12a9h12bdh137ah13b6h1441h1504h1537h153bh15d0h162dh1631h1758h1155h)
Received: from mail1-db3 (localhost.localdomain [127.0.0.1]) by mail1-db3 (MessageSwitch) id 1357694801282675_11624; Wed,  9 Jan 2013 01:26:41 +0000 (UTC)
Received: from DB3EHSMHS019.bigfish.com (unknown [10.3.81.250])	by mail1-db3.bigfish.com (Postfix) with ESMTP id 426E88004A; Wed,  9 Jan 2013 01:26:41 +0000 (UTC)
Received: from SN2PRD0510HT002.namprd05.prod.outlook.com (157.56.234.117) by DB3EHSMHS019.bigfish.com (10.3.87.119) with Microsoft SMTP Server (TLS) id 14.1.225.23; Wed, 9 Jan 2013 01:26:41 +0000
Received: from SN2PRD0510MB372.namprd05.prod.outlook.com ([169.254.9.200]) by SN2PRD0510HT002.namprd05.prod.outlook.com ([10.255.116.37]) with mapi id 14.16.0245.002; Wed, 9 Jan 2013 01:26:39 +0000
From: Stephen Hanna <shanna@juniper.net>
To: Dean Willis <dean.willis@softarmor.com>, Yoav Nir <ynir@checkpoint.com>
Subject: RE: travel guide for the next IETF...
Thread-Topic: travel guide for the next IETF...
Thread-Index: AQHN5dfSzFwNuN1gJ0ShBzgvwHQCkZgzXY6AgAZol4CABnaigIAABpzw
Date: Wed, 9 Jan 2013 01:26:39 +0000
Message-ID: <F1DFC16DCAA7D3468651A5A776D5796E069A03BF@SN2PRD0510MB372.namprd05.prod.outlook.com>
References: <50DF09C7.1060009@dcrocker.net> <20200.1356985377@sandelman.ca> <4613980CFC78314ABFD7F85CC30277210EE27C34@IL-EX10.ad.checkpoint.com> <D62C90BC-9035-4826-BA2D-9F56778A6438@softarmor.com>
In-Reply-To: <D62C90BC-9035-4826-BA2D-9F56778A6438@softarmor.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [66.129.232.2]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-FOPE-CONNECTOR: Id%0$Dn%*$RO%0$TLS%0$FQDN%$TlsDn%
X-FOPE-CONNECTOR: Id%12219$Dn%SOFTARMOR.COM$RO%2$TLS%5$FQDN%onpremiseedge-1018244.customer.frontbridge.com$TlsDn%o365mail.juniper.net
X-FOPE-CONNECTOR: Id%12219$Dn%CHECKPOINT.COM$RO%2$TLS%5$FQDN%onpremiseedge-1018244.customer.frontbridge.com$TlsDn%o365mail.juniper.net
X-FOPE-CONNECTOR: Id%12219$Dn%SANDELMAN.CA$RO%2$TLS%5$FQDN%onpremiseedge-1018244.customer.frontbridge.com$TlsDn%o365mail.juniper.net
X-FOPE-CONNECTOR: Id%12219$Dn%IETF.ORG$RO%2$TLS%5$FQDN%onpremiseedge-1018244.customer.frontbridge.com$TlsDn%o365mail.juniper.net
Cc: Michael Richardson <mcr@sandelman.ca>, IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 09 Jan 2013 01:27:59 -0000

Dean Willis wrote:
> Having a car won't do any good. There is, as far as I can tell, no
> place to park it but the hotel valet.

According to this web page, complimentary self-parking is available
at the Caribe Royale.

http://www.cariberoyale.com/accommodations/services/

Thanks,

Steve

=20



From jeanjour@comcast.net  Tue Jan  8 17:29:29 2013
Return-Path: <jeanjour@comcast.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 36F2B21F84DD for <ietf@ietfa.amsl.com>; Tue,  8 Jan 2013 17:29:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.653
X-Spam-Level: 
X-Spam-Status: No, score=-100.653 tagged_above=-999 required=5 tests=[AWL=-0.216, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_NET=0.611, RDNS_NONE=0.1, USER_IN_WHITELIST=-100]
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 Z8igQ-Q-nriC for <ietf@ietfa.amsl.com>; Tue,  8 Jan 2013 17:29:28 -0800 (PST)
Received: from qmta04.westchester.pa.mail.comcast.net (qmta04.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:43:76:96:62:40]) by ietfa.amsl.com (Postfix) with ESMTP id E562C21F84C9 for <ietf@ietf.org>; Tue,  8 Jan 2013 17:29:27 -0800 (PST)
Received: from omta17.westchester.pa.mail.comcast.net ([76.96.62.89]) by qmta04.westchester.pa.mail.comcast.net with comcast id lQTv1k0051vXlb854dVTsm; Wed, 09 Jan 2013 01:29:27 +0000
Received: from [10.0.1.3] ([98.229.211.49]) by omta17.westchester.pa.mail.comcast.net with comcast id ldVS1k00x14WE023ddVSAj; Wed, 09 Jan 2013 01:29:27 +0000
Mime-Version: 1.0
Message-Id: <a06240827cd126dacfce3@[10.0.1.3]>
In-Reply-To: <20130109003609.2BFF41A445@ld9781.wdf.sap.corp>
References: <20130109003609.2BFF41A445@ld9781.wdf.sap.corp>
Date: Tue, 8 Jan 2013 20:19:29 -0500
To: mrex@sap.com, Donald Eastlake <d3e3e3@gmail.com>
From: John Day <jeanjour@comcast.net>
Subject: Re: A proposal for a scientific approach to this question 	[was Re: I'm struggling with 2219 language again]
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20121106; t=1357694967; bh=/d/FRIK8my0PqVa28qazUmxQwMFK1mRY3w/FSQCxwgc=; h=Received:Received:Mime-Version:Message-Id:Date:To:From:Subject: Content-Type; b=sCPPh17wG6SW+N26XyiM8814mLYRFZirH72GrHtUQPy/npTlb0hZ4a8kkDvDOxL2n NgoDtkCCNONvwRQoce01YUCRkZ532EiVtxViBA1bSo6xz/ZttXtD7hTc5X6RMeQxBr DR8hoRNM1STDFh5ZgpPDHZxkoDf0JSqJq6ajMGRHwCaqAGgM4XSeAb3pFEjQsQRlUC TCBkktlNNjWaEd0nHUWtkKDIurPRweNp9BdRRdbgoG9IuqULCrov0pjBbHJxATFyLB bLeFxIRgaxGZgtETuwLlZIWRNvfI2WwuHw3wPvxWOvDbgEEFLXbwslGU1EXfCeTjGK 0AF+R4nmdOlrQ==
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 09 Jan 2013 01:29:29 -0000

At 1:36 AM +0100 1/9/13, Martin Rex wrote:
>
>>John Day <jeanjour@comcast.net> wrote:
>>>
>>>  The reasons have been discussed or at least alluded to previously in this
>>>  thread.  The short answer is we have been there and done that: 30 
>>>years ago.
>>>
>>>  All those tools were developed and used successfully in the 80s.
>>>  I know of cases where doing the formal specification alongside the
>>>  design phase caught lots of problems.   However, there are two
>>>  central problems:  First, in general, programmers are lazy and just
>>>  want to code. ;-)  Using a formal method is a lot more work.
>>>  Second, the complexity of the formal statements that must be written
>>>  down is greater than the code.  So there is a higher probability
>>>  of mistakes in the formal description than in the code.
>>>  Admittedly, if those statements are made, one has a far greater
>>>  understanding of what you are doing.
>
>I believe that the problem with the formal logic is that it is difficult
>to both write as well as read/understand, and to verify that the chosen
>"axioms" actually reflect (and lead to) the desired behaviour/outcome,
>the relative of scarcity of suitable tools, the complexity of the
>underlying theory and tools, and the tools' resulting lack of
>"intuitive usability".


The tools have been available for quite some time.  It is still very difficult.

>
>>>
>>>  Once you have both, there is still the problem that if a bug or ambiguity
>>>  shows up,
>
>For any formal proofing system worth its dime, this can be 100% ruled out,
>since the proofing system will emit a 100% bugfree implementation of the
>spec in the programming language of your choice as a result/byproduct of the
>formal proofing process.

C'mon. You don't really believe that do you? The statement either is 
a tautology or naive.  Ever see a compiler with bugs?  Who verified 
the verifier?  How do you know the verifier is bug free?

As I indicated before, I have been working on this problem since we 
discovered Telnet wasn't as good as we thought it was.  For data 
transfer protocols, it is relatively straightforward and can be 
considered solved for anyone who wants to bother.  The problem is 
most don't.

The real problem is the so-called application protocols where dealing 
the different semantics of objects in different systems makes the 
problem very hard and very subtle.  The representation of the 
semantics is always of what you think its seminal properties are. 
This is not always obvious.

>
>>>
>>>   neither the code nor the formal spec nor a prose spec can be taken
>>>  be the right one.  What is right is still in the heads of the authors.
>
>But maybe you're not really thinking of a defect in the implementation
>(commonly called "bug") but rather a "gap" in the specification that
>leads to unintended or undesired behaviour of a 100% bug-free
>implementation of your spec.

One person's gap is another person's bug.  What may be obvious to one 
as something that must occur may not be so to the other.  Then there 
is that fine line between what part of the specification is required 
for the specification and what part is the environment of the 
implementation.

The human mind has an amazing ability to convince us that how we see 
the world is the way others do.  Having been on the Net when there 
were 15-20 very different machine architectures, I can assure you 
that implementation strategies can differ wildly.

I had had great hopes for the Temporal ordering approaches to 
specification since they said the least about the implementation. 
(the specification is entirely in terms of ordering events) However, 
I never met anyone who could design in them.

>
>(see Section 4 of this paper for an example:
>   http://digbib.ubka.uni-karlsruhe.de/volltexte/documents/1827
>)
>
>
>Donald Eastlake wrote:
>>
>>  Another problem is maintenance. Protocols change. Having to maintain a
>  > formal specification is commonly at least an order of magnitude more
>>  effort than maintaining a prose description.
>
>Definitely.  Discussing protocols at the level of formal specification
>language would be quite challenging (typically impossible in an open
>forum, I believe it is even be difficult in a small and well-trained
>design team).

Which means there will always be a danger of "lost in translation."

>
>>
>>  And, as has been mentioned before, I'd like to emphasize that the IETF
>>  experience and principal is that, if you want interoperation,
>>  compliance testing is useless.
>
>Ouch.  I believe this message is misleading or wrong.
>
>Compliance testing is VERY important, rather than useless,
>
>Compliance testing would actually be perfectly sufficient iff the spec
>was formally proven to be free of conflicts and ambiguities among
>specified protocol elements -- plus a significant effort spent on
>ensuring there were no "gaps" in the specification.

Do you realize the cost of this amount of testing? (Not saying it 
isn't a good idea, just the probability of convincing a development 
manager to do it is pretty slim.)  ;-)

>
>As it turns out, however, a significant amount of implementations will
>be created by humans interpreting natural language specifications,
>rather than implemenations created as 100% bug-free by-products of a
>formal proof tool, and often, interop with such buggy, and often
>spec-incompliant implementations is desirable and necessary since
>they make up a significant part of the installed base.

My impression is that few implementations these days are done from 
scratch.  Available software is commandeered and adapted.  So it 
would seem getting the core aspects of the protocol well implemented 
and let laziness takes its course!  ;-)

>
>>
>>  The way to interoperation is interoperation testing between
>>  implementations and, to a first approximation, the more and the
>>  earlier you do interoperation testing, the better.
>
>
>The #1 reason for interop problems and road-block to evolution of
>protocols is the wide-spread lack of compliance testing (on the flawed
>assumption that it is useless) and focus on black-box interop testing
>of the intersection of two subsets of protocol features.
>
>The problem with interop testing is that it really doesn't provide
>much of a clue, and the results can _not_ be extrapolated to features
>and areas that were not interop tested (typically the other 90% of the
>specification, many optional features and most of the extensibility).
>
>
>The near complete breakage of TLS protocol version negotiation is a
>result of the narrow-minded interop testing in companion with a complete
>lack of compliance testing.
>
>
>If done right, pure compliance testing can go a long way to providing
>interop.  The only area where real interop testing is necessary is
>those protocol areas where the spec contains conflicts/inconsistencies
>that implementors didn't notice or ignored, or where there is a
>widespread inconsistencies of implementations with the specification,
>of created by careless premature shipping of a defective implementation
>and factual creation of an installed base that is too large to ignore.

That last sentence is a doozy.  You are saying that interop testing 
will be required with bad implementations with sufficiently large 
installed base that you have to live with it?

John

>
>-Martin


From rwfranks@gmail.com  Tue Jan  8 18:47:02 2013
Return-Path: <rwfranks@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B1E0221F853E for <ietf@ietfa.amsl.com>; Tue,  8 Jan 2013 18:47:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.977
X-Spam-Level: 
X-Spam-Status: No, score=-102.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
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 9Fc+xOi384Cl for <ietf@ietfa.amsl.com>; Tue,  8 Jan 2013 18:47:02 -0800 (PST)
Received: from mail-wi0-f178.google.com (mail-wi0-f178.google.com [209.85.212.178]) by ietfa.amsl.com (Postfix) with ESMTP id E9A2321F8525 for <ietf@ietf.org>; Tue,  8 Jan 2013 18:47:01 -0800 (PST)
Received: by mail-wi0-f178.google.com with SMTP id hn3so232077wib.5 for <ietf@ietf.org>; Tue, 08 Jan 2013 18:47:01 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:cc:content-type; bh=R1kIKHF4gvAxFp5WP4TCZL72QqwJA8/+nbESf7N+acw=; b=mXYlP4oQMwFxsDMgG5FGC1Vy4Jg4sS+mKBwPK318qth9xBdxCxdnJyKhBmX+387IdB pp4FaRmA8eHDv4GoUcDGlEpOz7ivWmXYiHVc2wWtd1bxJgA1swQjbJqyfsrIZiFfPCdO KzlsjG8fHda1Cz7f+GHhGZAMH+ENoIXUXirjQxlQsp1lECcfVaSDkCP+046lis4OZMfV 1/CtUx+wiI6if4zQi4qQEC50Tyvt7dFBXCjS8/hP8cgX4ugJmsvdYC9uuKopbYVkJ7ng bOHGTG55BLUT3U0657AFWvTs1qBZVEqND/XDwiy/kwRUWZQaSL10CRhfbA55Rhzf/85F jPfA==
Received: by 10.194.242.69 with SMTP id wo5mr105627549wjc.10.1357699621026; Tue, 08 Jan 2013 18:47:01 -0800 (PST)
MIME-Version: 1.0
Sender: rwfranks@gmail.com
Received: by 10.194.18.65 with HTTP; Tue, 8 Jan 2013 18:46:40 -0800 (PST)
In-Reply-To: <a06240827cd126dacfce3@10.0.1.3>
References: <20130109003609.2BFF41A445@ld9781.wdf.sap.corp> <a06240827cd126dacfce3@10.0.1.3>
From: Dick Franks <rwfranks@acm.org>
Date: Wed, 9 Jan 2013 02:46:40 +0000
X-Google-Sender-Auth: LDboY4owBU1QkZX44fLuVqVpPz0
Message-ID: <CAKW6Ri6DwayieOTUqY_sjOo_cgZqK30X5n-9QLxfMsmrq7zDaA@mail.gmail.com>
Subject: Re: A proposal for a scientific approach to this question [was Re: I'm struggling with 2219 language again]
To: John Day <jeanjour@comcast.net>
Content-Type: text/plain; charset=UTF-8
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 09 Jan 2013 02:47:02 -0000

On 9 January 2013 01:19, John Day <jeanjour@comcast.net> wrote:
[snip]
>
> One person's gap is another person's bug.  What may be obvious to one as
> something that must occur may not be so to the other.  Then there is that
> fine line between what part of the specification is required for the
> specification and what part is the environment of the implementation.

Disagree

A gap in the specification will result in all implementations having
the same unintended behaviour, because the developers understood and
followed the spec 100%.

Bugs are distinguishable from gaps because they occur in some
implementations but not others and arise from misinterpretation of
some aspect of the specification.  In this context, over-engineering
is a bug, as distinct from competitive advantage.


Dick
--

From jeanjour@comcast.net  Tue Jan  8 20:38:35 2013
Return-Path: <jeanjour@comcast.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1B20721F8514 for <ietf@ietfa.amsl.com>; Tue,  8 Jan 2013 20:38:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.634
X-Spam-Level: 
X-Spam-Status: No, score=-100.634 tagged_above=-999 required=5 tests=[AWL=-0.197, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_NET=0.611, RDNS_NONE=0.1, USER_IN_WHITELIST=-100]
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 NMiBWyjZV2Hg for <ietf@ietfa.amsl.com>; Tue,  8 Jan 2013 20:38:34 -0800 (PST)
Received: from qmta12.westchester.pa.mail.comcast.net (qmta12.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:44:76:96:59:227]) by ietfa.amsl.com (Postfix) with ESMTP id 5052121F8510 for <ietf@ietf.org>; Tue,  8 Jan 2013 20:38:34 -0800 (PST)
Received: from omta21.westchester.pa.mail.comcast.net ([76.96.62.72]) by qmta12.westchester.pa.mail.comcast.net with comcast id lgba1k0011ZXKqc5CgeZwX; Wed, 09 Jan 2013 04:38:33 +0000
Received: from [10.0.1.3] ([98.229.211.49]) by omta21.westchester.pa.mail.comcast.net with comcast id lgeY1k00U14WE023hgeZ1Q; Wed, 09 Jan 2013 04:38:33 +0000
Mime-Version: 1.0
Message-Id: <a06240830cd12a2e375b9@[10.0.1.3]>
In-Reply-To: <CAKW6Ri6DwayieOTUqY_sjOo_cgZqK30X5n-9QLxfMsmrq7zDaA@mail.gmail.com>
References: <20130109003609.2BFF41A445@ld9781.wdf.sap.corp> <a06240827cd126dacfce3@10.0.1.3> <CAKW6Ri6DwayieOTUqY_sjOo_cgZqK30X5n-9QLxfMsmrq7zDaA@mail.gmail.com>
Date: Tue, 8 Jan 2013 23:38:25 -0500
To: Dick Franks <rwfranks@acm.org>, John Day <jeanjour@comcast.net>
From: John Day <jeanjour@comcast.net>
Subject: Re: A proposal for a scientific approach to this question [was Re:  I'm struggling with 2219 language again]
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20121106; t=1357706313; bh=7VOmL3lppP4TFce5aCaXjMctfn4ciA5k6mYr/An3BpM=; h=Received:Received:Mime-Version:Message-Id:Date:To:From:Subject: Content-Type; b=h8mi6VbPgK+tNn+Bgo7Wc6ixOdqjiJh/J2A+ywgeGBfOcdo0rP34BiD7IArg5HJga ub7KCRYIKEg8lzq6XzFljIYcLhGKOLZaU8DF1ClRC8ZfF0BRQGlgpxsw6iQAZqyYlO U57I1eZlJSXkB4YBbs+P9M4oipjHLqtrA815FVcnr8n3S+c7pPIyyuZuEW+Jg0jSmT 9jbvcC/8HTbENaqMr/AEq+5RDUzMUkQt3oRNI6kbRXB8PV4eWBKhFM1c5DXJyuTPx0 U4tbjamb6Ya/IxZpf5d0W00AHCqkqdg4bJmsP62K8f9c8aUim6QW+Y/kZJ5dwwFFAz hp/EoV4XmUdeA==
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 09 Jan 2013 04:38:35 -0000

It would be interesting to see you apply that.

This is what I have been talking about.  The human mind's ability to 
believe that the whole world sees everything the same way they do. 
It really is quite amazing.

These so-called gaps often arise because they were unstated 
assumptions or things that the author believed were patently obvious 
and didn't need to be stated. Actually didn't know needed to be 
stated.  From his point of view, no one would do it differently. 
Nothing had been left out and he didn't make the "mistake."   What 
the other guys did was a bug.

There is a much greater range of interpreting these things than it 
appears that you imagine.

At 2:46 AM +0000 1/9/13, Dick Franks wrote:
>On 9 January 2013 01:19, John Day <jeanjour@comcast.net> wrote:
>[snip]
>>
>>  One person's gap is another person's bug.  What may be obvious to one as
>>  something that must occur may not be so to the other.  Then there is that
>>  fine line between what part of the specification is required for the
>>  specification and what part is the environment of the implementation.
>
>Disagree
>
>A gap in the specification will result in all implementations having
>the same unintended behaviour, because the developers understood and
>followed the spec 100%.
>
>Bugs are distinguishable from gaps because they occur in some
>implementations but not others and arise from misinterpretation of
>some aspect of the specification.  In this context, over-engineering
>is a bug, as distinct from competitive advantage.
>
>
>Dick
>--


From sm@resistor.net  Tue Jan  8 23:31:20 2013
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5988921F86F6; Tue,  8 Jan 2013 23:31:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.574
X-Spam-Level: 
X-Spam-Status: No, score=-102.574 tagged_above=-999 required=5 tests=[AWL=0.025, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 qEcz1Yg5bcXS; Tue,  8 Jan 2013 23:31:19 -0800 (PST)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 81AD621F878F; Tue,  8 Jan 2013 23:31:18 -0800 (PST)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r097VCPu007191; Tue, 8 Jan 2013 23:31:15 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1357716678; bh=G7d/Yxa+9TLn8tyYk07NNZajk1dfZUFm1cTgpKzYAwI=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=GeAtWcw3RfRfTcHU6GBRRYVLP/dS3NTqcsm+o35nBnzSiPDIbpnqzILQqvECFfeoy kxDQiMxbt+STQK/P8EVAvJt5zt77Lh0Z4VLRD9QHveLSv8qduWCiZmuH4kM/hy3LUN coqK+CeNwHP7qSzuTYzzQ27Naddgc2h6lipEzPgE=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1357716678; i=@resistor.net; bh=G7d/Yxa+9TLn8tyYk07NNZajk1dfZUFm1cTgpKzYAwI=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=HqNDDH8qShpT8Xh1Pg2mLyucCHjG+vjAXaMJitsVJOGndeu+hw5KoG1JlJFe2pwMQ dFK2au3DyC8BqVaij0g4Wwq+AiY+DAMibgbayPmniEatJpBlTsGEXGuv5GUrc4WAuc uTF9CccIV6YBvcNFdCD4LbrZwQyftuDfK7+2i1cg=
Message-Id: <6.2.5.6.2.20130108225436.0b31f008@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Tue, 08 Jan 2013 23:25:24 -0800
To: ietf@ietf.org
From: SM <sm@resistor.net>
Subject: Re: Last Call: <draft-ietf-nea-pt-eap-06.txt> (PT-EAP: Posture Transport (PT) Protocol For EAP Tunnel Methods) to Proposed Standard
In-Reply-To: <20130102144303.25143.30944.idtracker@ietfa.amsl.com>
References: <20130102144303.25143.30944.idtracker@ietfa.amsl.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: nea@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 09 Jan 2013 07:31:20 -0000

At 06:43 02-01-2013, The IESG wrote:
>The IESG has received a request from the Network Endpoint Assessment WG
>(nea) to consider the following document:
>- 'PT-EAP: Posture Transport (PT) Protocol For EAP Tunnel Methods'
>   <draft-ietf-nea-pt-eap-06.txt> as Proposed Standard
>
>The IESG plans to make a decision in the next few weeks, and solicits
>final comments on this action. Please send substantive comments to the
>ietf@ietf.org mailing lists by 2013-01-16. Exceptionally, comments may be

This is a quick comment.

In Section 1:

   "The PT-EAP protocol MUST be protected by an outer
    TLS-based EAP tunnel method to ensure the exchanged messages are
    protected from a variety of threats from hostile intermediaries."

The RFC 2119 boilerplate is after that "MUST".

In Section 1.1:

   "This document does not define an architecture or reference model.
    Instead, it defines a protocol that works within the reference model
    described in the NEA Requirements specification [RFC5209]."

The reference is informative.

In Section 6:

   "PT-EAP does not directly utilize or require direct knowledge of
    any personally identifiable information (PII).  PT-EAP will
    typically be used in conjunction with other EAP methods
    that provide for the user authentication (if bi-directional
    authentication is used), so the user's credentials are not
    directly seen by the PT-EAP inner method."

Section 9 RFC 5209 mentions that:

   "However, in situations where the endpoint is owned by the user
    or where local laws protect the rights of the user even when
    using endpoints owned by another party, it is critical that the NEA
    implementation enable the user to control what endpoint information
    is shared with the network."

I didn't find any information in the draft to assess the privacy 
implications.  Are there any such implications?

Regards,
-sm 


From abdussalambaryun@gmail.com  Tue Jan  8 23:54:22 2013
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DBD5D21F877B for <ietf@ietfa.amsl.com>; Tue,  8 Jan 2013 23:54:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.583
X-Spam-Level: 
X-Spam-Status: No, score=-3.583 tagged_above=-999 required=5 tests=[AWL=0.016,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 BA+vEcAf0W+T for <ietf@ietfa.amsl.com>; Tue,  8 Jan 2013 23:54:22 -0800 (PST)
Received: from mail-vc0-f176.google.com (mail-vc0-f176.google.com [209.85.220.176]) by ietfa.amsl.com (Postfix) with ESMTP id CBB6121F8775 for <ietf@ietf.org>; Tue,  8 Jan 2013 23:54:21 -0800 (PST)
Received: by mail-vc0-f176.google.com with SMTP id fo13so1253124vcb.7 for <ietf@ietf.org>; Tue, 08 Jan 2013 23:54:21 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=TauQtn29cuVD+z+mAo/4ATXdzsZTTmXBdksZNiUbI1Y=; b=t81YeyirYK03Va2hJF9izdoF4FcNXBNVMgjY1HWlQHZQigPabsHgvoHYrRSbL7QoIa kykGx8MbHc7zh3duBvwNF6n5Xw3YYJ2PZj7OBfBJ/L7SxLysCMdr1f+VJfoAHNsGuOvl aIDrtc1bCBH4swlM1isITAy8GiypmpUvaj3G93biB3yq6+YyhFXQpiFNFl0TmBdCQ5T1 U7avLAhcz6nkpP8kzCI+wHiFu4lBhDuLrMuEkgCPSJifjYtzxnGfGd/RhAsqnXAmNckb tX36/ubgWjttL8rBNj/CGN4mFxOFZ1bOe+mBs37QrNJMxdhOY3i+UixhBtmMEqHzxkls XviA==
MIME-Version: 1.0
Received: by 10.52.175.106 with SMTP id bz10mr76220498vdc.125.1357718061133; Tue, 08 Jan 2013 23:54:21 -0800 (PST)
Received: by 10.220.145.5 with HTTP; Tue, 8 Jan 2013 23:54:21 -0800 (PST)
In-Reply-To: <3D453E57-252A-467C-B64A-6671C85FD4BB@softarmor.com>
References: <CADnDZ8_GgVeapUKefFMqOvwOo00X8_rFDWMR0vb-Zvu_p=yT3A@mail.gmail.com> <a062408a2cd10003cf574@10.0.1.3> <CADnDZ88BVr6wj_RTGh8bMEkUt-sobWuDH-v0wyHVabSETVHrkA@mail.gmail.com> <CADnDZ88PJ4yCNp+6TSBFYNn_QMOZM_BFB4p3nmFy4R3XeApYLQ@mail.gmail.com> <3D453E57-252A-467C-B64A-6671C85FD4BB@softarmor.com>
Date: Wed, 9 Jan 2013 08:54:21 +0100
Message-ID: <CADnDZ89_VzT4d7fKa8qvPbM_27ZVDAArqG-sGr-qhPbzvo0-Yw@mail.gmail.com>
Subject: Re: A proposal for a scientific approach to this question [was Re: I'm struggling with 2219 language again]
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: ietf <ietf@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 09 Jan 2013 07:54:23 -0000

>This is what I have been talking about. The human mind's ability to believ=
e that the whole world sees everything the same way they do. It really is q=
uite amazing.

>These so-called gaps often arise because they were unstated assumptions or=
 things that the author believed were patently obvious and didn't need to b=
e stated. Actually didn't know needed to be stated. From his point of view,=
 no one would do it differently. Nothing had been left out and he didn't ma=
ke the "mistake." What the other guys did was a bug.

That is why I think the IETF names the RFC or standards or
specifications as *Request For Comments*, if there is a gap or the
human mind failed, then it should communicate to the world and report
such gap/bug.

AB

From abdussalambaryun@gmail.com  Wed Jan  9 00:03:25 2013
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AF03721F8799 for <ietf@ietfa.amsl.com>; Wed,  9 Jan 2013 00:03:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.584
X-Spam-Level: 
X-Spam-Status: No, score=-3.584 tagged_above=-999 required=5 tests=[AWL=0.015,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 HmPpMlXApMNO for <ietf@ietfa.amsl.com>; Wed,  9 Jan 2013 00:03:24 -0800 (PST)
Received: from mail-vc0-f182.google.com (mail-vc0-f182.google.com [209.85.220.182]) by ietfa.amsl.com (Postfix) with ESMTP id 69A2C21F8792 for <ietf@ietf.org>; Wed,  9 Jan 2013 00:03:24 -0800 (PST)
Received: by mail-vc0-f182.google.com with SMTP id fy27so1288534vcb.27 for <ietf@ietf.org>; Wed, 09 Jan 2013 00:03:23 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:cc:content-type; bh=NSvXJ9k9tiUZ47R1g+Wv+3EBYr4AL0cOecc1Vy6I0PU=; b=X8qEstr8JDz5Er6M8dEBvMGGj5A1H/U/56zYPul6/AzaVPwufRXTVTecvO9AKYGlbP fZQX3HO5yddkAYKh/zfvqtiv5sNONcJT8oiraQI14E9YV1XLr/KkJpsIeVEmKYS+lEfT RV3ln0jGLYHklM0XSNL3zNNIxKxyImNjlQDRqMug5HkJ1EPHdcS1qAJcNUoWNB6Mk9wR 88vRlJI5p4kWwqM4I6pz/kxs7mmopWaBWLb6rGbdEib58xB10LfNpy602q/UdiKSG7ez y8NdntDKCgn+DTZFCPFNN5HrhSys96EuYPBrAkKEVTP58SU2tAealg7kaVKX7qsblI53 mnPA==
MIME-Version: 1.0
Received: by 10.58.31.200 with SMTP id c8mr8134635vei.23.1357718603820; Wed, 09 Jan 2013 00:03:23 -0800 (PST)
Received: by 10.220.145.5 with HTTP; Wed, 9 Jan 2013 00:03:23 -0800 (PST)
Date: Wed, 9 Jan 2013 09:03:23 +0100
Message-ID: <CADnDZ89r3ZobS7aL6SkQzMdf-1vXoAtq5BZna6yXvSZQ2HAPBw@mail.gmail.com>
Subject: Re: Making RFC2119 key language easier to Protocol Readers
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: ietf <ietf@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 09 Jan 2013 08:03:25 -0000

Hi Martin,

I agree with your points below, if any one finds an error in IETF
standards then should report it on this list or write an ID about that
to community,

AB
++++++++++++++++++++++++++

Sub: Re: A proposal for a scientific approach to this question [was
Re: I'm struggling with 2219 language again]

http://www.ietf.org/mail-archive/web/ietf/current/msg76710.html

>I believe that the problem with the formal logic is that it is difficult
to both write as well as read/understand, and to verify that the chosen
"axioms" actually reflect (and lead to) the desired behaviour/outcome,
the relative of scarcity of suitable tools, the complexity of the
underlying theory and tools, and the tools' resulting lack of
"intuitive usability".

>> Once you have both, there is still the problem that if a bug or ambiguity
>> shows up,

For any formal proofing system worth its dime, this can be 100% ruled out,
since the proofing system will emit a 100% bugfree implementation of the
spec in the programming language of your choice as a result/byproduct of the
formal proofing process.


>>
>>  neither the code nor the formal spec nor a prose spec can be taken
>> be the right one.  What is right is still in the heads of the authors.

But maybe you're not really thinking of a defect in the implementation
(commonly called "bug") but rather a "gap" in the specification that
leads to unintended or undesired behaviour of a 100% bug-free
implementation of your spec.

(see Section 4 of this paper for an example:
  http://digbib.ubka.uni-karlsruhe.de/volltexte/documents/1827
)


Donald Eastlake wrote:
>
> Another problem is maintenance. Protocols change. Having to maintain a
> formal specification is commonly at least an order of magnitude more
> effort than maintaining a prose description.

Definitely.  Discussing protocols at the level of formal specification
language would be quite challenging (typically impossible in an open
forum, I believe it is even be difficult in a small and well-trained
design team).


>
> And, as has been mentioned before, I'd like to emphasize that the IETF
> experience and principal is that, if you want interoperation,
> compliance testing is useless.

Ouch.  I believe this message is misleading or wrong.

Compliance testing is VERY important, rather than useless,

Compliance testing would actually be perfectly sufficient iff the spec
was formally proven to be free of conflicts and ambiguities among
specified protocol elements -- plus a significant effort spent on
ensuring there were no "gaps" in the specification.

As it turns out, however, a significant amount of implementations will
be created by humans interpreting natural language specifications,
rather than implemenations created as 100% bug-free by-products of a
formal proof tool, and often, interop with such buggy, and often
spec-incompliant implementations is desirable and necessary since
they make up a significant part of the installed base.


>
> The way to interoperation is interoperation testing between
> implementations and, to a first approximation, the more and the
> earlier you do interoperation testing, the better.


The #1 reason for interop problems and road-block to evolution of
protocols is the wide-spread lack of compliance testing (on the flawed
assumption that it is useless) and focus on black-box interop testing
of the intersection of two subsets of protocol features.

The problem with interop testing is that it really doesn't provide
much of a clue, and the results can _not_ be extrapolated to features
and areas that were not interop tested (typically the other 90% of the
specification, many optional features and most of the extensibility).


The near complete breakage of TLS protocol version negotiation is a
result of the narrow-minded interop testing in companion with a complete
lack of compliance testing.


If done right, pure compliance testing can go a long way to providing
interop.  The only area where real interop testing is necessary is
those protocol areas where the spec contains conflicts/inconsistencies
that implementors didn't notice or ignored, or where there is a
widespread inconsistencies of implementations with the specification,
of created by careless premature shipping of a defective implementation
and factual creation of an installed base that is too large to ignore.


-Martin

From abdussalambaryun@gmail.com  Wed Jan  9 00:09:30 2013
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8F39521F84FD for <ietf@ietfa.amsl.com>; Wed,  9 Jan 2013 00:09:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.584
X-Spam-Level: 
X-Spam-Status: No, score=-3.584 tagged_above=-999 required=5 tests=[AWL=0.015,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 hpMVYyf6EAyd for <ietf@ietfa.amsl.com>; Wed,  9 Jan 2013 00:09:30 -0800 (PST)
Received: from mail-vc0-f169.google.com (mail-vc0-f169.google.com [209.85.220.169]) by ietfa.amsl.com (Postfix) with ESMTP id 844DB21F86A6 for <ietf@ietf.org>; Wed,  9 Jan 2013 00:09:29 -0800 (PST)
Received: by mail-vc0-f169.google.com with SMTP id gb23so1267882vcb.14 for <ietf@ietf.org>; Wed, 09 Jan 2013 00:09:29 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=YizRBeNAjl35w3wWDZ99foZBZC8/9hdOsMTBs3N/bcU=; b=Ov+N4md0/Nd0lwVnTK0WJWWgNCLugnsY3o6zadrZHxqmgAdbxfLhR3JKBE+EpCGRP7 KoueRrj/ywaGe1L2iDgocCIMAccJ9egPM8gd7b6ZGXlTru+AfSrhs43dz5KesH2XUMLz 8s8dNUCwyVvP6w6/9l+qtxafTAu8owH3/gKxSWwK9ZojFYNvVQogcoD0pMiGMIaVgkHs bJTTQlMKqE0bOaxV0QGvWDyR8MsuJbn4Dr0Z+V6sbA/gWS+1yt0nim9DOpi9WL7fByGv Yd61l6BOyXjMd7SNjvP+KxMT6xpP29NYnkqY/jKxBckiZx08h33cfXsaesQZGEeyG6pS yfAQ==
MIME-Version: 1.0
Received: by 10.52.70.46 with SMTP id j14mr76199898vdu.99.1357718968962; Wed, 09 Jan 2013 00:09:28 -0800 (PST)
Received: by 10.220.145.5 with HTTP; Wed, 9 Jan 2013 00:09:28 -0800 (PST)
In-Reply-To: <3D453E57-252A-467C-B64A-6671C85FD4BB@softarmor.com>
References: <CADnDZ8_GgVeapUKefFMqOvwOo00X8_rFDWMR0vb-Zvu_p=yT3A@mail.gmail.com> <a062408a2cd10003cf574@10.0.1.3> <CADnDZ88BVr6wj_RTGh8bMEkUt-sobWuDH-v0wyHVabSETVHrkA@mail.gmail.com> <CADnDZ88PJ4yCNp+6TSBFYNn_QMOZM_BFB4p3nmFy4R3XeApYLQ@mail.gmail.com> <3D453E57-252A-467C-B64A-6671C85FD4BB@softarmor.com>
Date: Wed, 9 Jan 2013 09:09:28 +0100
Message-ID: <CADnDZ8_B+e13hXSzX9rdCGZULYkpv_QAG6QcCGp_0XYs9h1ppg@mail.gmail.com>
Subject: Re: A proposal for a scientific approach to this question [was Re: I'm struggling with 2219 language again]
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: Dean Willis <dean.willis@softarmor.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 09 Jan 2013 08:09:30 -0000

>might preference would be just to pick one, and
> provide a stick for hitting those who do it the other way.

I think that IESG is already using that stick :)

AB

On 1/9/13, Dean Willis <dean.willis@softarmor.com> wrote:
>
> On Jan 8, 2013, at 12:57 PM, Abdussalam Baryun <abdussalambaryun@gmail.com>
> wrote:
>
>>> but the question of
>>> error in process is; does the RFC lack communication requirement with
>>> the community?
>>>
>>
>> Sorry if not clear. I mean that as some participant are requesting a
>> scientific approach to struggling with 2119 (i.e. thread-subject),
>> does that mean in some RFCs the use or not use (i.e. we see that
>> participant use different approaches to follow the 2119) that it may
>> add communication confuse with some of community?
>>
>
> I'm absolutely certain that some of our community is confused about
> something related to this thread. Given the absence of information that
> would help in a decision, might preference would be just to pick one, and
> provide a stick for hitting those who do it the other way.
>
> --
> Dean
>
>
>

From sayrer@gmail.com  Wed Jan  9 00:17:26 2013
Return-Path: <sayrer@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9D39721F877B; Wed,  9 Jan 2013 00:17:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.349
X-Spam-Level: 
X-Spam-Status: No, score=-3.349 tagged_above=-999 required=5 tests=[AWL=0.250,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 6c+cgWolmuY2; Wed,  9 Jan 2013 00:17:26 -0800 (PST)
Received: from mail-wi0-f175.google.com (mail-wi0-f175.google.com [209.85.212.175]) by ietfa.amsl.com (Postfix) with ESMTP id 9126A21F8775; Wed,  9 Jan 2013 00:17:25 -0800 (PST)
Received: by mail-wi0-f175.google.com with SMTP id hm11so357393wib.8 for <multiple recipients>; Wed, 09 Jan 2013 00:17:24 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=Xd1RihbKxaiTnnczkWg1Ms9fnSNzd/y+XVcnC4a+y5Y=; b=Pkiq8hizfI5z8Yt9jv45FhnHBe6zP7pieMvMeAZGaGXStnQ/xQxt4C4wIGz6y7kXXa fieI2+ettD+SwRTGzGSZL0f9lomHpwQfftzMZRwMlHpDCp6D5ysTsshI8lQbYhkC9ASr cuGJIyxzAfCzV+qYwj8b3cCiajIVm5QnFRZo5tFMu43tbISfSRiJkK9Hy6KfCdiJeUc4 uLBsI2EmY/Co3vXrCAZnF0G/r6+SUtgTXGsengicuwG1wMLa/I2mGzKavXLOhLgK9m+L dn6L2/i6+kGb7iUPBjXqTOm3W7Ujs+X37n96vpmkxZ2LCizYiSIHb22x2NkMcQX3pZ/P tY7g==
MIME-Version: 1.0
X-Received: by 10.180.72.146 with SMTP id d18mr1618720wiv.33.1357719444742; Wed, 09 Jan 2013 00:17:24 -0800 (PST)
Received: by 10.194.32.100 with HTTP; Wed, 9 Jan 2013 00:17:24 -0800 (PST)
In-Reply-To: <CAC4RtVCTx6yx3h92ROiMc5zDh9GcJzHcKO=SEjc3D+x9g2HhxA@mail.gmail.com>
References: <20121211150057.28223.93310.idtracker@ietfa.amsl.com> <50cb04b9.86df440a.72fe.1e20SMTPIN_ADDED_BROKEN@mx.google.com> <CABP7RbeNsZ_rBWRjou=VG+hBhUKaOz+y1a0sSChwWiHte9znnQ@mail.gmail.com> <50cb5f3c.694c420a.38fb.39afSMTPIN_ADDED_BROKEN@mx.google.com> <CAChr6SxZRc3B_HCbw76kLe2dsRSr43r-gLpfMVnCUfJTrZdTLA@mail.gmail.com> <CABP7RbfA33huBFadMeXTTEt=MkjW8-d4DFH7+GLXGurnm9sSRw@mail.gmail.com> <CAOXDeqpPE4eNy_qJpDPdPHbCQakG9-hDcNZ3Sj9r4kWedByVzQ@mail.gmail.com> <CAChr6SwtS_=iS-k4mJm1vHjEvvGVzay5jDYeGheqsPZqO-89CQ@mail.gmail.com> <EABB8F51-C3B4-49F5-8672-5C2ABAC7043A@mnot.net> <CAChr6Sx7JdKM91EwJaSZ0Ra_F4FSqkuc3vzTY1LM=F_8sWho+Q@mail.gmail.com> <1357515310.6827.23.camel@polyglot> <CAChr6SyAq=7aQdZn54ihYK+0hDhL--2Oaq0RvehoNFbwKNNShA@mail.gmail.com> <CAChr6SxorKO20rGYi-e4YNF=HNGrwz8wPGKCFZQYWQwqsetjjg@mail.gmail.com> <CAOXDeqqE2mCLapwvjwQkme5VTpRCfmF0mFQcx02WW0-zi4i5=g@mail.gmail.com> <50EB4E8B.30700@versi.edu.au> <CAOXDeqoOj1K_zBWVZbE2j4Vnp1pYZ1yUEp9nyTKZmp-QrAziqg@mail.gmail.com> <CAD5Szk-U1LeBSfUgah8XXE2LZ=utR=0W-V7VsT6j-i2VixZerg@mail.gmail.com> <CAChr6SzvXWkkCZU3GPGFJtoqZ=0AOktFhrML6ZMtf7nU9iwxjw@mail.gmail.com> <CAD5Szk-CTBSeTc-QvDLZ3o5twYq6WF=g6Wr1bsDc=ub=T0pXZg@mail.gmail.com> <CABP7RbeHFmWhfwUcn6mEZEFES+0d_HpP5XCZUanQ9FQozYtD-Q@mail.gmail.com> <CAD5Szk8hRn731uiv_p561N7Va4UWF4xbxRRRhVu1CPDBc4dPHw@mail.gmail.com> <CABP7Rbf4N3KCP=5s64uhrFjsnB5mG5AbTVC0BDo37h+gjVa=Hg@mail.gmail.com> <CAC4RtVCTx6yx3h92ROiMc5zDh9GcJzHcKO=SEjc3D+x9g2HhxA@mail.gmail.com>
Date: Wed, 9 Jan 2013 00:17:24 -0800
Message-ID: <CAChr6SzkwEP38mtDhhYzS7_6Ro1B1mKUUYpW2SPZ+KQV0QNbxQ@mail.gmail.com>
Subject: Re: [apps-discuss] Last Call: <draft-ietf-appsawg-json-pointer-07.txt> (JSON Pointer) to Proposed Standard
From: Robert Sayre <sayrer@gmail.com>
To: Barry Leiba <barryleiba@computer.org>
Content-Type: text/plain; charset=ISO-8859-1
Cc: James M Snell <jasnell@gmail.com>, IESG <iesg@ietf.org>, IETF Apps Discuss <apps-discuss@ietf.org>, IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 09 Jan 2013 08:17:26 -0000

Awesome news: JSON Patch has enough IESG votes to become a standards
track document, even though JSON Pointer still has a discuss. This way
of doing things is very efficient--lots of documents can be approved
this way.

- Rob

On Tue, Jan 8, 2013 at 1:41 PM, Barry Leiba <barryleiba@computer.org> wrote:
> Let me suggest that y'all remove the IESG and the main IETF discussion list
> (and me) from the CC list if you continue this discussion (which you're
> welcome to do).  Actually, I suggest that if you do continue it, you start a
> new thread with a new subject, on apps-discuss only.
>
> Thanks.
>
> Barry
>
> _______________________________________________
> apps-discuss mailing list
> apps-discuss@ietf.org
> https://www.ietf.org/mailman/listinfo/apps-discuss
>

From mrex@sap.com  Wed Jan  9 00:46:08 2013
Return-Path: <mrex@sap.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1E2B021F85E7 for <ietf@ietfa.amsl.com>; Wed,  9 Jan 2013 00:46:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.832
X-Spam-Level: 
X-Spam-Status: No, score=-9.832 tagged_above=-999 required=5 tests=[AWL=-0.417, BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_HI=-8, SARE_OBFU_CODEINE=0.833]
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 Fo+baFPgOnmZ for <ietf@ietfa.amsl.com>; Wed,  9 Jan 2013 00:46:06 -0800 (PST)
Received: from smtpde01.sap-ag.de (smtpde01.sap-ag.de [155.56.68.170]) by ietfa.amsl.com (Postfix) with ESMTP id BE95221F85E6 for <ietf@ietf.org>; Wed,  9 Jan 2013 00:46:05 -0800 (PST)
Received: from mail05.wdf.sap.corp by smtpde01.sap-ag.de (26) with ESMTP id r098k06V028942 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 9 Jan 2013 09:46:01 +0100 (MET)
Subject: Re: A proposal for a scientific approach to this question [was Re: I'm struggling with 2219 language again]
In-Reply-To: <a06240827cd126dacfce3@[10.0.1.3]>
To: John Day <jeanjour@comcast.net>
Date: Wed, 9 Jan 2013 09:46:00 +0100 (CET)
X-Mailer: ELM [version 2.4ME+ PL125 (25)]
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="US-ASCII"
Message-Id: <20130109084600.D698E1A444@ld9781.wdf.sap.corp>
From: mrex@sap.com (Martin Rex)
X-SAP: out
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: mrex@sap.com
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 09 Jan 2013 08:46:08 -0000

John Day wrote:
>>
>>For any formal proofing system worth its dime, this can be 100% ruled out,
>>since the proofing system will emit a 100% bugfree implementation of the
>>spec in the programming language of your choice as a result/byproduct of the
>>formal proofing process.
> 
> C'mon. You don't really believe that do you?

Which one in particular.

The KIV-tool, which I was shown and explained in 1996 by a student doing
his master thesis with it on a module of our software, can output
source code at the end of its processing.  Code that is a guaranteed
bug-free implementation of the spec.  (which MUST NOT be confused
with the given spec providing the desired behaviour and being free
of unintended (and unthough-of) behaviour).

(While the tool's name appears to originate from the University of
 Karlsruhe (->Karlsruhe Interactive Verifier), and that student back
 then was from Karlsruhe, the current homepage of the tool appears
 to be at the University of Augsburg:

  http://www.informatik.uni-augsburg.de/lehrstuehle/swt/se/kiv/
)

>
> Ever see a compiler with bugs?

Compiler bugs are comparatively rare, many of them are problems
of the optimizer (therefore avoidable) and many happen under
obscure situations that can be avoided by defensive programming
style.  Code generators often produce "defensive style code".
Using a robust and mature programming language, such as C89,
may also help to avoid compiler problems of fancy or complex
languagues or fancy features.

Look at the long list of defects of modern CPUs.  Apps programmers
that use a compiler rarely have to know (let alone take into account)
those CPU defects because most compiler code generators use only
a subset of CPU features anyway.


>
> Who verified the verifier?  How do you know the verifier is bug free?

Now you must be kidding.

Are you suggesting that anyone using the programming language Prolog
would be gambling and could never expect deterministic results?


With a decent amount of expertise and the right mindset,
even mere mortal humans can produce code with a very low error rate.
IIRC, Donald E. Knuth didn't need a formal specification and a
formal proofing tool to achieve a low error rate for TeX and Metafont.

Having started assembler programming at the age of 12 myself, I could
easily understand why DEK used Assembler for his algorithm code examples
in TAOCP when I first encountered these books at age 21.


> 
> As I indicated before, I have been working on this problem since we 
> discovered Telnet wasn't as good as we thought it was.  For data 
> transfer protocols, it is relatively straightforward and can be 
> considered solved for anyone who wants to bother.  The problem is 
> most don't.

There is a perverted conditioning in our education system and
business life by rewarding mediocrity (cheating, improvising, being
superficial) which is IMO one of the underlying causes for
  http://en.wikipedia.org/wiki/Dunning_Kruger
and impairs many implementors' motivation to watch out and compensate for
defects in the spec and to recognize and respect design limits of a spec,
i.e. avoid underspecified protocol features or require official
clarification and adjust the code accordingly before shipping
implementations of underspecified protocol features.


> 
> The real problem is the so-called application protocols where dealing 
> the different semantics of objects in different systems makes the 
> problem very hard and very subtle.  The representation of the 
> semantics is always of what you think its seminal properties are. 
> This is not always obvious.


I believe that the real difficulty is about designing and discussing
at the abstract level and then performing formally correct transitions
from abstract spec level to concrete specification proposla level
and comparing implementation options at the spec level ... and getting
everyone that wants to participate to understand the abstraction
and how to perform transitions from and to concrete spec proposals.


I'm experiencing that difficulty myself every once in a while.
In 1995/1996 I had a adopted notion/bias for the uselessness of
traditional GSS-API channel bindings (as defined in GSS-APIv1 rfc1508/1509
and GSS-APIv2 rfc2743/2744) and it took me a few weeks of discussion
to really understand what Nico was trying to accomplish with
cryptographic channel bindings, such as tls-unique, its prerequisites
and real properties and its benefits.


> 
>>But maybe you're not really thinking of a defect in the implementation
>>(commonly called "bug") but rather a "gap" in the specification that
>>leads to unintended or undesired behaviour of a 100% bug-free
>>implementation of your spec.
> 
> One person's gap is another person's bug.  What may be obvious to one 
> as something that must occur may not be so to the other.

There is a significant difference between a bug in an implementation
and an unintended consequence due to a "gap" in the specification.

The SSLv3 protocol and the IETF successor TLS contains a somewhat
underspecified protocol option called renegotiation, and some apps folks
had the not very bright idea to abuse that protocol option and
made flawed assumptions about protocol properties that did not
actually exist.

Had those apps folks, rather than shortcutting on flawed assumptions,
simply collected the description of the renegotiation properties that
are sprinkeled throughout the TLS spec and put them into a single list,
and then thought about it for an hour, then the problem (the absence of
the property that they wanted to rely on) should have become obvious to them.

It became obvious for me as soon as I had put together that list and
thought about the consequences during discussion of TLS channel bindings.


> 
> The human mind has an amazing ability to convince us that how we see 
> the world is the way others do.


The Dunnin-Kruger effect, "Routine", "habits", are all variations
of trainig a neural network and improving the pattern recognition
over time.  The strength of neural networks, to recognize also
variations of known patterns, is also its weakness, a bias/preference
to recognize stuff as something that is already known.
Fixing training errors and trying to add similar distinct patterns
very late usually result in a significant (re-)trainig effort --
and this is where the constant conditioning for cheating, improvising,
superficialness frequently kicks in.

"If all you have is a hammer, everything looks like a nail."

Technically, humans are capable of overcoming the Dunning-Kruger effect
and becoming aware of the limits/boundaries of their knowledge, but
many enjoy a happy life without ever trying to.


>
> Having been on the Net when there were 15-20 very different machine
> architectures, I can assure you that implementation strategies can
> differ wildly.

I'm well aware that the amount of bad code out there outnumbers
the amount of good code.  While I don't think that differing implementation
approaches imply causality for interop problems, there certainly is
the problem of ad-hoc/poor/dangerous/error-prone implementation design
that causes plenty of bugs and interop problems and unexpected
behaviours, neither of which a result of a conscious decisions,
getting shipped into the installed base.

Good specifications are sufficiently clear and precise to enable
smooth interop, yet sufficiently abstract to provide a high level
of implementation freedom as well as future extensibility.

What is much more of a problem is the common lack in recognizing
and respecting limits of a design/specification, and a lack of
compensating for relatively easy to recognize spec defects.
Relatively easy to recognize for a careful implementer, that is,
not necessarily easy to recognize for a mere reviewer.


>>>
>>> Another problem is maintenance. Protocols change. Having to maintain a
>>> formal specification is commonly at least an order of magnitude more
>>> effort than maintaining a prose description.
>>
>>Definitely.  Discussing protocols at the level of formal specification
>>language would be quite challenging (typically impossible in an open
>>forum, I believe it is even be difficult in a small and well-trained
>>design team).
> 
> Which means there will always be a danger of "lost in translation."

The danger is real.  If there is a lack of decent leadership,
the resulting spec (defects) may sometimes pose a significant
challenge to implementations&interop.

For consumers of the spec outside of the SDO, the option to
ask for clarification/fix might be non-obvious -- and regularly
is non-trivial for someone who has not previously participated
in the particular SDO (or any SDO at all) -- which is actually
quite common.  There are easily two magnitudes more implementors
of specs distributed by the IETF than there are individuals who have
participated in the IETF over the past 30 years.
 


>>>
>>>  And, as has been mentioned before, I'd like to emphasize that the IETF
>>>  experience and principal is that, if you want interoperation,
>>>  compliance testing is useless.
>>
>>Ouch.  I believe this message is misleading or wrong.
>>
>>Compliance testing is VERY important, rather than useless,
>>
>>Compliance testing would actually be perfectly sufficient iff the spec
>>was formally proven to be free of conflicts and ambiguities among
>>specified protocol elements -- plus a significant effort spent on
>>ensuring there were no "gaps" in the specification.
> 
> Do you realize the cost of this amount of testing? (Not saying it 
> isn't a good idea, just the probability of convincing a development 
> manager to do it is pretty slim.)  ;-)

I fail to follow.  Compliance testing does not necessarily require
code or a test tool.  Often, compliance will be as simple as actually
_reading_and_following_ the spec, how to process some PDU element.
And compliance testing may be as simple as a code review of less than
an hour and cross-checking a handful MUST and MUST NOTs.

Or what to do with a protocol option/feature one's own implementation
does not recognize, and then _do_what_the_spec_says_
rather than doing what a number of implementations are doing: regularly
aborting with a fatal error rather than doing what the spec says.

Example: the optional TLS protocol extension "Server Name Indication",
first specified here:  http://tools.ietf.org/html/rfc3546#section-3.1


   "HostName" contains the fully qualified DNS hostname of the server,
   as understood by the client. 

Doing what the spec says with respect to this requirement:

                                                                     If
   the server only needs to match the HostName against names containing
   exclusively ASCII characters, it MUST compare ASCII names case-
   insensitively.

If that is not sufficiently clear for an average implemetor to realize
that a case-sensitive comparison (strcmp,strncmp) will be incompliant
with the spec and a case-insensitive comparison (strcasecmp,strncasecmp,
_stricmp,_strnicmp) will have to be used instead, then we might have to
give up and close down the IETF SDO.


According to http://en.wikipedia.org/wiki/Server_Name_Indication#Support
support for this protocol option was originally designed in 2004,
and added into the main codeline of OpenSSL 0.9.8 in 2007.

However, OpenSSL-1.0.1c today still does a case-sensitive comparison...


>>>
>>>  The way to interoperation is interoperation testing between
>>>  implementations and, to a first approximation, the more and the
>>>  earlier you do interoperation testing, the better.
>>
>>The #1 reason for interop problems and road-block to evolution of
>>protocols is the wide-spread lack of compliance testing (on the flawed
>>assumption that it is useless) and focus on black-box interop testing
>>of the intersection of two subsets of protocol features.
>>
>>The problem with interop testing is that it really doesn't provide
>>much of a clue, and the results can _not_ be extrapolated to features
>>and areas that were not interop tested (typically the other 90% of the
>>specification, many optional features and most of the extensibility).
>>
>>
>>The near complete breakage of TLS protocol version negotiation is a
>>result of the narrow-minded interop testing in companion with a complete
>>lack of compliance testing.

Being aware of the breakage of the TLS protocol version negotiation
within the installed base in 2009, an explicit reminder was added
into rfc5746 that processing TLS protocol version numbers correctly
in the TLS handshake was vitally important and has always been a
requirement in the TLS protocol spec.

   TLS servers implementing this specification MUST ignore any unknown
   extensions offered by the client and they MUST accept version numbers
   higher than their highest version number and negotiate the highest
   common version.  These two requirements reiterate preexisting
   requirements in RFC 5246 and are merely stated here in the interest
   of forward compatibility.

The necessity for the TLS renegotiation info extension had become
painfully obvious after it had been realized that the two TLS connection
states involved in a TLS renegotiation had been completely independent,
enabling an MitM attacker to inject/prefix data of his choice at the
beginning of a TLS session, and the document is very explicit which
precise state information of the previous/enclosing session is carried
over into the successor TLS session and how.

Curiously, one vendor happened to actually break the TLS protocol
version negotiation much worse than it already was, by performing
a check on the client_version in the premaster secret of the
renegotiation ClientKeyExchange message not against the client_version
from the ClientHello from the very same TLS handshake, but instead
check against the client_version of the initial handshake, that had
been found to have painfully independent state and created the
necessity for the rfc5746 fix in the first place...

Simply following what the spec says during implementation would have
avoided the problem.  Performing a code review of the reminded
TLS protocol version negotiation would have noticed that breakage.
Interop testing the protocol version negotiation in a meaningful
fashion, even with earlier TLS implementations from the very same
vendor would have clearly shown the breakage prior to shipment.
As it turns out, the vendor failed on all three accounts,
and this _new_ breakage got shipped...


>
>>If done right, pure compliance testing can go a long way to providing
>>interop.  The only area where real interop testing is necessary is
>>those protocol areas where the spec contains conflicts/inconsistencies
>>that implementors didn't notice or ignored, or where there is a
>>widespread inconsistencies of implementations with the specification,
>>of created by careless premature shipping of a defective implementation
>>and factual creation of an installed base that is too large to ignore.
> 
> That last sentence is a doozy.  You are saying that interop testing 
> will be required with bad implementations with sufficiently large 
> installed base that you have to live with it?


It seems to be a recurring event that one or more vendors create
an installed base that is clearly non-compliant with the original
spec, but too large to ignore, and as a result, everyelse adapts
to that behaviour for the sake of interoperability with that
installed base.

e.g.  http://tools.ietf.org/html/rfc4178#appendix-C
      http://tools.ietf.org/html/rfc5929#section-8

There may be others, but I'm actively tracking only very few
topics in the IETF, so these two are ones I know from the top
of my head.


-Martin

From mrex@sap.com  Wed Jan  9 01:15:29 2013
Return-Path: <mrex@sap.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8957121F8A6E for <ietf@ietfa.amsl.com>; Wed,  9 Jan 2013 01:15:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.145
X-Spam-Level: 
X-Spam-Status: No, score=-10.145 tagged_above=-999 required=5 tests=[AWL=0.104, BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_HI=-8]
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 3HQzb6hVjHbX for <ietf@ietfa.amsl.com>; Wed,  9 Jan 2013 01:15:28 -0800 (PST)
Received: from smtpde02.sap-ag.de (smtpde02.sap-ag.de [155.56.68.140]) by ietfa.amsl.com (Postfix) with ESMTP id 5427421F8667 for <ietf@ietf.org>; Wed,  9 Jan 2013 01:15:26 -0800 (PST)
Received: from mail05.wdf.sap.corp by smtpde02.sap-ag.de (26) with ESMTP id r099FKiC029227 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 9 Jan 2013 10:15:20 +0100 (MET)
Subject: Re: A proposal for a scientific approach to this question [was Re: I'm struggling with 2219 language again]
In-Reply-To: <a06240830cd12a2e375b9@[10.0.1.3]>
To: John Day <jeanjour@comcast.net>
Date: Wed, 9 Jan 2013 10:15:20 +0100 (CET)
X-Mailer: ELM [version 2.4ME+ PL125 (25)]
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="US-ASCII"
Message-Id: <20130109091520.3DC4F1A444@ld9781.wdf.sap.corp>
From: mrex@sap.com (Martin Rex)
X-SAP: out
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: mrex@sap.com
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 09 Jan 2013 09:15:29 -0000

John Day wrote:
>
> It would be interesting to see you apply that.
> 
> This is what I have been talking about.  The human mind's ability to 
> believe that the whole world sees everything the same way they do. 
> It really is quite amazing.
> 
> These so-called gaps often arise because they were unstated 
> assumptions or things that the author believed were patently obvious 
> and didn't need to be stated. Actually didn't know needed to be 
> stated.  From his point of view, no one would do it differently. 
> Nothing had been left out and he didn't make the "mistake."   What 
> the other guys did was a bug.
> 
> There is a much greater range of interpreting these things than it 
> appears that you imagine.

With "bug", I mean behaviour that is non-compliant with the spec,
where the difference is not to accomodate for a defect of the spec,
and where this behaviour is detrimental to the operation of that
implementation (vulnerability or robustness issue) or detrimental
to the interop with other implementations.

With "conflict" in a spec, I refer to distinct statements in a
spec that contradict each other (such as the same symbolic protocol
element is assigned two different values in two seperate locations
of the spec).

With "ambiguity" in a spec, I refer to an omission that precludes
that a certain feature can be implemented at all.  Such as a symbolic
protocol element that represents an integer value in a PDU, but
the spec lacks the definition of the numeric value for the 
on-the-wire representation.

With "gap" in a spec, I refer to omissions that do not preclude
the implementation, but can lead to unexpected behaviour of an
implementation.  This result is vaguely similar to what happens when
a switch() statement lacks a default: case and is unexpectedly faced
with a value that is not covered by case statements.  The result
can be "undefined" / "unpredictable", yet remain formally provable
correct with respect to the given specification.


Finally, there are "omissions" in a spec, i.e. properties that a
protocol does and can not provide, yet consumers of the protocol may
believe in "magic security pixie dust" and develop a flawed assumption
about a non-existing protocol property, as it happened in with the
TLS renegotiation.  TLS renegotiation being secure/protected against
MitM was a property that was retrofitted into SSLv3/TLS with rfc5746,
and could not possibly have existed "by accident" in any of the existing
implementations.  (Although servers that did not support renegotiation
at all never were vunerable to the "interesting" attacks.)



-Martin

From hsantos@isdg.net  Wed Jan  9 05:05:25 2013
Return-Path: <hsantos@isdg.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9148A21F86CB for <ietf@ietfa.amsl.com>; Wed,  9 Jan 2013 05:05:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.507
X-Spam-Level: 
X-Spam-Status: No, score=-102.507 tagged_above=-999 required=5 tests=[AWL=0.092, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 rTENK5kztkbU for <ietf@ietfa.amsl.com>; Wed,  9 Jan 2013 05:05:21 -0800 (PST)
Received: from dkim.winserver.com (listserv.winserver.com [208.247.131.9]) by ietfa.amsl.com (Postfix) with ESMTP id 797EE21F86D4 for <ietf@ietf.org>; Wed,  9 Jan 2013 05:05:21 -0800 (PST)
DKIM-Signature: v=1; d=isdg.net; s=tms1; a=rsa-sha1; c=simple/relaxed; l=3694; t=1357736713; h=Received:Received: Received:Received:Message-ID:Date:From:Organization:To:Subject: List-ID; bh=DE66zmJF2vRF4tCX/iyhBSHcvTI=; b=G9tyTHZLf2PliztYCD/p 4mr1vBVRIAbiAxBRybDaymfRE2rhZ98VpkfwkliOR2MGChKhb1RGAH12+MH2XXxv OhXXKHBxoSi012P5MWw1Jaw7Fem5e8r9hg6ZJsPi/0AetuAezyasGHJLO+KLsRxg YyVAOjiL96lJEZTRFlsF0wk=
Received: by winserver.com (Wildcat! SMTP Router v7.0.454.4) for ietf@ietf.org; Wed, 09 Jan 2013 08:05:13 -0500
Authentication-Results: dkim.winserver.com; dkim=pass header.d=beta.winserver.com header.s=tms1 header.i=beta.winserver.com;  adsp=pass policy=all author.d=isdg.net asl.d=beta.winserver.com;
Received: from opensite.winserver.com ([208.247.131.23]) by winserver.com (Wildcat! SMTP v7.0.454.4) with ESMTP id 873471764.3.4664; Wed, 09 Jan 2013 08:05:12 -0500
DKIM-Signature: v=1; d=beta.winserver.com; s=tms1; a=rsa-sha256; c=simple/relaxed; l=3694; t=1357736657; h=Received:Received: Message-ID:Date:From:Organization:To:Subject:List-ID; bh=5KFdXgR vv44LVhQbzGY/sY4vRBHlnqeOTcaB4d9F0II=; b=KfqlITQ8Fz6+sN+r8SzQN4q li+2F1avO+T+PPdU4oH2yqOUJRGn96FzwVvWU9cU2qBldbfBLeGva43aM1ozL3pw luh4+DNND1eTKX3HtDoiIdVn7gz6VX7t5owR3aSecfeSIVOVqPGT0V/YYYajzJoM r05aAH68XCl8IpWSEemg=
Received: by beta.winserver.com (Wildcat! SMTP Router v7.0.454.4) for ietf@ietf.org; Wed, 09 Jan 2013 08:04:17 -0500
Received: from [192.168.1.101] ([99.3.147.93]) by beta.winserver.com (Wildcat! SMTP v7.0.454.4) with ESMTP id 1472173336.10.5920; Wed, 09 Jan 2013 08:04:17 -0500
Message-ID: <50ED6B0A.2020708@isdg.net>
Date: Wed, 09 Jan 2013 08:05:14 -0500
From: Hector Santos <hsantos@isdg.net>
Organization: Santronics Software, Inc.
User-Agent: Thunderbird 2.0.0.24 (Windows/20100228)
MIME-Version: 1.0
To: mrex@sap.com
Subject: Re: A proposal for a scientific approach to this question	[was Re: I'm struggling with 2219 language again]
References: <20130109091520.3DC4F1A444@ld9781.wdf.sap.corp>
In-Reply-To: <20130109091520.3DC4F1A444@ld9781.wdf.sap.corp>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 09 Jan 2013 13:05:25 -0000

Maybe the survey to be done is a review of all the RFC, STD and see 
which ones

- had a great abstract and introduction,
- had the better writing styles
- had the least endorsement resistance
- progress faster than most,
- had the most implementators,
- with least support/questions need to be asked,

etc, etc.

Are the RFCs that followed 2119 the more successful ones, the ones 
written with clarity and knew how to separate functional and technical 
descriptions?  Had the right target audience(s) in mind?

Maybe we can also review which I-D and RFCs have high failure or have 
trouble getting industry endorsement, and even if it did, why has it 
failed in the market place?

What is the overall problem anyway?   Is this part of the reason why 
there are efforts to fast track documents? Because there are so much 
resistance by such a broad range of disciplines with different level 
mindsets and philosophies?

-- 
HLS

Martin Rex wrote:
> John Day wrote:
>> It would be interesting to see you apply that.
>>
>> This is what I have been talking about.  The human mind's ability to 
>> believe that the whole world sees everything the same way they do. 
>> It really is quite amazing.
>>
>> These so-called gaps often arise because they were unstated 
>> assumptions or things that the author believed were patently obvious 
>> and didn't need to be stated. Actually didn't know needed to be 
>> stated.  From his point of view, no one would do it differently. 
>> Nothing had been left out and he didn't make the "mistake."   What 
>> the other guys did was a bug.
>>
>> There is a much greater range of interpreting these things than it 
>> appears that you imagine.
> 
> With "bug", I mean behaviour that is non-compliant with the spec,
> where the difference is not to accomodate for a defect of the spec,
> and where this behaviour is detrimental to the operation of that
> implementation (vulnerability or robustness issue) or detrimental
> to the interop with other implementations.
> 
> With "conflict" in a spec, I refer to distinct statements in a
> spec that contradict each other (such as the same symbolic protocol
> element is assigned two different values in two seperate locations
> of the spec).
> 
> With "ambiguity" in a spec, I refer to an omission that precludes
> that a certain feature can be implemented at all.  Such as a symbolic
> protocol element that represents an integer value in a PDU, but
> the spec lacks the definition of the numeric value for the 
> on-the-wire representation.
> 
> With "gap" in a spec, I refer to omissions that do not preclude
> the implementation, but can lead to unexpected behaviour of an
> implementation.  This result is vaguely similar to what happens when
> a switch() statement lacks a default: case and is unexpectedly faced
> with a value that is not covered by case statements.  The result
> can be "undefined" / "unpredictable", yet remain formally provable
> correct with respect to the given specification.
> 
> 
> Finally, there are "omissions" in a spec, i.e. properties that a
> protocol does and can not provide, yet consumers of the protocol may
> believe in "magic security pixie dust" and develop a flawed assumption
> about a non-existing protocol property, as it happened in with the
> TLS renegotiation.  TLS renegotiation being secure/protected against
> MitM was a property that was retrofitted into SSLv3/TLS with rfc5746,
> and could not possibly have existed "by accident" in any of the existing
> implementations.  (Although servers that did not support renegotiation
> at all never were vunerable to the "interesting" attacks.)
> 
> 
> 
> -Martin
> 
> 




From benl@google.com  Tue Jan  8 09:54:13 2013
Return-Path: <benl@google.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0F90111E80F2 for <ietf@ietfa.amsl.com>; Tue,  8 Jan 2013 09:54:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.977
X-Spam-Level: 
X-Spam-Status: No, score=-102.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
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 20dE1Vnzcraq for <ietf@ietfa.amsl.com>; Tue,  8 Jan 2013 09:54:10 -0800 (PST)
Received: from mail-we0-f170.google.com (mail-we0-f170.google.com [74.125.82.170]) by ietfa.amsl.com (Postfix) with ESMTP id D577121F8583 for <ietf@ietf.org>; Tue,  8 Jan 2013 09:54:09 -0800 (PST)
Received: by mail-we0-f170.google.com with SMTP id r1so584148wey.15 for <ietf@ietf.org>; Tue, 08 Jan 2013 09:54:08 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:date:message-id:subject:from:to:cc:content-type; bh=il9sSMkxMTnkX6x3l0wpDb1HWnKd9cbymzRxCIcOwAQ=; b=NSLybn6GocImTIvJfhC6oaijKrnU05pnsvyehD+ykhI7eTqd7ahSgnSXZoiwjBz7x0 ZSOO682XkExcHLzVyauc4l/q+x3MxfNnHWrEYWz8McGwUNRoobRdIXxnD6wyZiggFdtN Ul7slZ2qvXgviox3n7Pz49Tok/lpHchldm+yFUB9rj+bF6yI2VwIOvcHz9LlMIPhxRW3 vLpE8qOYHO4pVLDEJ7NXk3FrxCOyk52hzv5fb3emijhpmb22kpH8ZR9lItwjIrQwR+5E xQB9uiUxVf81QQQkzX/JSr2APC8Ius0VQ8pPEmSlg7l2+LB6kqk1OCKbO2rgwDNCeax1 vQsA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:date:message-id:subject:from:to:cc:content-type :x-gm-message-state; bh=il9sSMkxMTnkX6x3l0wpDb1HWnKd9cbymzRxCIcOwAQ=; b=hLcV4iKLdNbOY9xkj0STFB/ieRegEuXZ+DdlXBEPQOi6KwiAo9FSaarjeyXT2Mg+wu 2/Kr43BRbKTV1fRfdu6WLBCg6AkoVSAMeu/oxYK2qFV3t4cZZTrD4yqlb+83htW6XDqu 8qj6a3R7Y+7uaRMq/c6WN202uJXIyyFGCE6u6g1K/yl132zbLpN7SEgwN3q154TXopqa J/mRkJTVlMy+CePXPZbYCSk67sGZEYuAsj1oWpzwk9Suue0zJsFL3YDOYbJ6Wn5uD19q 1a+COSHOhu2bMMfJ2B8b9qbvxTEpKxwhdVScAJCCzBgRlgOy4UtEpNpdTMxGhQ3cZWM5 v5wQ==
MIME-Version: 1.0
Received: by 10.180.106.34 with SMTP id gr2mr16194827wib.18.1357667648747; Tue, 08 Jan 2013 09:54:08 -0800 (PST)
Received: by 10.194.22.36 with HTTP; Tue, 8 Jan 2013 09:54:08 -0800 (PST)
Date: Tue, 8 Jan 2013 17:54:08 +0000
Message-ID: <CABrd9STRdENwQanrk4BuVA7Taz_r=vC6VeiZrOaLprfhfucYug@mail.gmail.com>
Subject: Re: LC comments on draft-laurie-pki-sunlight-05
From: Ben Laurie <benl@google.com>
To: "=JeffH" <Jeff.Hodges@kingsmountain.com>
Content-Type: text/plain; charset=ISO-8859-1
X-Gm-Message-State: ALoCoQkoGF+aa3j/dxqTpPraqNbrJD8l1aGHcjYyjGyatA0KutiX1UHZcbOsOUTuzVNLOC+Z91DDqPMo5/4jk5n/e1Y5HmAolgN1xmOLVbry951IdKFVPifMqeIyX6DEVnBXr7+JIoC6PLXkWkSRjxkLXdTrHqvacuHPJunWA5ggmBSG3nfh2LZHGIYl48ZRUQYqTbGCMAxh
X-Mailman-Approved-At: Wed, 09 Jan 2013 08:04:45 -0800
Cc: Emilia Kasper <ekasper@google.com>, "therightkey@ietf.org" <therightkey@ietf.org>, IETF Discussion List <ietf@ietf.org>, Adam Langley <agl@google.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 08 Jan 2013 17:54:13 -0000

On 1 January 2013 21:50, =JeffH <Jeff.Hodges@kingsmountain.com> wrote:
> Hi,
>
> Here are some last call comments on draft-laurie-pki-sunlight-05.
>
> Overall the spec is in basically overall reasonable shape but I do have some
> substantive comments that if I'm not totally misunderstanding things (which
> could be the case) ought to be discussed and addressed in some fashion.
>
> The plain overall comments are to some degree "take 'em or leave 'em"
> depending upon folks' sense of urgency to get the spec through the IETF
> pipeline, but the degree likely depends upon the observer.
>
> I hope this is helpful,

It is indeed,  thankyou.

> =JeffH
> ------
>
> comments on draft-laurie-pki-sunlight-05
>
> substantive comments (in somewhat arbitrary order)
> --------------------------------------------------
>
> 1. The client messages S4 don't explicitly lay out the syntax for request
> messages or responses. E.g., for S4.1 "Add Chain to Log", is the input a
> stand-alone JSON text array, or a JSON text object containing a JSON text
> array?
>
> The term "JSON object" as used in the first paragraph is ambiguous and
> perhaps what is mean is simply "JSON texts" or "JSON text objects or JSON
> text arrays". RFC4627 clearly defines "JSON text", and should be cited. But
> RFC4627 is a little ambiguous itself regarding "JSON object" and so I
> suggest these definitions:
>
>     JSON text object:   A JSON text matching the "object" ABNF production
>        in Section 2.2 of [RFC4627].
>
>     JSON text array:   A JSON text matching the "array" ABNF production
>        in Section 2.3 of [RFC4627].

I agree that RFC 4627 should be cited and I will correct that. The
rest of this confuses me: JSON is a textual representation of
structured data, as it states in the RFC. It defines an object quite
clearly

" An object is an unordered collection of zero or more name/value
   pairs, where a name is a string and a value is a string, number,
   boolean, null, object, or array."

Defining a "JSON text object" seems pointless to me - clearly a JSON
object is an object as defined by JSON, surely? Introducing another
term seems like to add confusion rather than remove it.

>
> Also, the syntax for GETS isn't fully specified. Are the URL parameters to
> be encoded as (order independent) key-value pairs, or just as
> order-dependent values?  Which separator character is to be used between
> parameters? RFC3986 should be cited.

RFC 3986 says nothing about parameter format, though - is there a
standard reference for that? I've refereced HTML 4.01, but perhaps
there's a better one?

> Examples for both JSON text inputs and outputs, as well as URL parameters
> would be helpful.

Yes, we will provide some.

> 2. "4. Client Messages" doesn't define error handling, i.e., responses to
> inputs the log service doesn't understand and/or is unable to parse, and/or
> have other errors. If the log service is to simply return a 4xx or 5xx error
> code, this should at least be mentioned.

For now, I will specify 4xx/5xx. We may have more to say once we've
gained some experience.

> 3. There appear to be three defined methods for TLS servers to provide TLS
> clients with CT data, in S3.2.  For this experiment, which approach is
> mandatory to implement for servers and clients?  Or, is it the case that
> participating TLS clients (ie web browsers etc) implement all three methods,
> and TLS servers can choose any of them?

The latter.

>
> Also, S3.2 probably doesn't belong in S3 and perhaps should be a separate
> top-level section on its own, and have three subsections, one for each
> method.

Maybe.

> 4. "Leaf Hash" as used in S4.5 appears to be formally undefined. It
> apparently would be:
>
>       SHA-256(0x00 || MerkleTreeLeaf)
>
> ..it should also be noted in S3.3.

You are right.

> 5. The recursive equations in S2.1 describe how to calculate a Merkle Tree
> Hash (MTH) (aka "root hash"), and thus as a side effect generate a Merkle
> Tree, for a given set of input data. However, there doesn't seem to be a
> defined algorithm (or even hints, really) for adding further inputs to an
> existing tree. Even though this may be reasonably left as an exercise for
> implementers, it should probably be discussed to some degree in the spec.
> E.g., note that leaf hashes are "frozen" and various interior tree node
> hashes become "frozen" as the tree grows. Is it not sub-optimal to employ
> the obvious default brute-force mechanism of rebuilding a tree entirely from
> scratch when new inputs are available?  Would not a recursive algorithm for
> adding new inputs to an existing tree be straightforward to provide?

I dunno about straightforward. I'll think about it.

> 6. Signed tree heads (STHs) are denoted in terms of "tree size" (number of
> entries), but SCTs are denoted in terms of a timestamp.  Should there be a
> log client message supporting the return of the nearest STH (and thus tree
> size) to a given timestamp?

I'm not sure why? Any STH (that includes that SCT) will do.

> 7. S3 paragraph 2 states that "TLS clients MUST reject certificates that do
> not have a valid SCT for the end-entity certificate" (i.e., hard-fail).
> Presummably this requirement is only for TLS clients participating in the CT
> experiment and that understand this protocol.

Of course - what other way could it be? In other words, all RFCs can
only say what implementations that conform with them do.

> This, or whatever the
> requirement actually is, should be further explained.

?

> For example, does the simple presence of SCT(s) in the TLS handshake serve
> to signal to participating TLS clients that hard-fail is expected if there
> are any issues with CT validation?

We are not saying what action a client should take when it rejects a
certificate, as is, I believe the usual practice.

> 8. The spec implies, but doesn't clearly describe, especially in S3.1, that
> the hashes are "labels" for tree entries, and that given a leaf hash, the
> log implementation should be able to look up and present the LogEntry data
> defined in that section.

We actually only require an entry to be retrievable by hash (in
effect) for the message in 4.7, which we (at least currently) label as
a debugging message - so I am not sure that logs really are required
to be able to do that - certainly the system would work fine if they
couldn't, I believe (other than being unable to provide the debugging
data).

> 9. Validating an SCT presummably requires having the Log Service's public
> key, yes?  This isn't clearly discussed, and also the mention of how one
> obtains a log service's public key is out of scope is buried in 2nd para of
> S4 -- it should be discussed in a separate clearly entitled subsection.

Good point.

>
>
> 10. Unless I'm totally missing it, there isn't an explicit description of
> how one (eg a TLS client) goes about validating/verifying an SCT.

Indeed, fixing that also fixes the above point.

> Various overall comments:
> --------------------------
>
> O-1. The phrase "this experiment" is used in S2.1 -- should describing this
> as an experiment be more explicitly done in the abstract and introduction
> sections?  What about the document title?

The plan is this will be an Experimental RFC, which seems clear enough to me?

> O-2. Should explicitly say in abstract and introduction that operationally,
> the logs are to be materialized as (experimental?) network services having
> the protocol operations for submissions and queries that are defined in this
> spec.

Seems a little redundant, but I have added something anyway.

>
>
> O-3. The bare term "client" is used in various places where either the term
> "log client" or "TLS client" is being implied -- these should be made
> explicit. Also the roles of log clients and TLS clients should be more
> thoroughly presented/explored, in part because they can intersect.

Section 5 "Clients" is an attempt to document the various client
roles, one or more of which may be embodied by any particular client
implementation, rather than try to deal with this intersection.

I have gone over mentions of "client" elsewhere to try to deal with
your point, though. Sometimes it just means "any client" so not all
instances have been changed.

>
>
> O-4. These things seem to be duplicate names:
>
>      "root hash" and "Merkle Tree Hash (MTH)"

Yes,

>
>      "Tree Head Signature" and "Signed Tree Head (STH)"

These are not the same - you are probably confused by the
digitally-signed struct, which is only used as input for a signature
and never appears in its own right. However, we haven't been super
clear about what's going on here and I've tried to clean that up.

>
> ..which makes parsing the spec more difficult than if one name is used
> consistently for each.
>
>
> O-5. The terms "leaf certificate" and "final certificate" appear to be used
> where..
>
>   End Entity certificate
>
>   final End Entity certificate
>
> ..would be clearer and more consistent with TLS and PKIX terminology, and
> perhaps less confusing with the terms "leaf" and "leaf node" which are used
> when discussing the Merkle trees and their components.

Good point.

> O-6. I found the "history tree" paper (aka "[1]", cited here as
> [CrosbyWallach]) helpful in understanding how such trees are constructed,
> perhaps it should be more prominently mentioned. Plus the differences
> between the two algorithms should perhaps be more explicitly mentioned. E.g.
> in [CrosbyWallach] version-n tree stores n+1 inputs, while in CT a version-n
> tree (D[n]) stores n inputs.
>
> [CrosbyWallach]  <http://tamperevident.cs.rice.edu/Logging.html>
>
>
> O-7. The note mentioning "dummy leaves" in [CrosbyWallach] seems misleading.
> The difference is AFAICT that in [CrosbyWallach] all nodes at layer 1 and
> above (leaf entries are at layer 0), are "interior nodes", and have hashes
> created using 0x01. Thus in a tree with an odd number of entries (ie leaf
> nodes at layer 0), there will be one leaf node under an interior node having
> only that one child. It's not that there is a "dummy leaf", it's that such
> an interior node's hash is constructed from just one child rather than two.

Not sure I really agree with this, but in any case I have reworded it
slightly. I've also changed the reference to be a "proper" one, shown
at the end of the I-D.

> While in CT, if the input set is an odd number of entries, then the hash of
> the final single leaf is at layer 1, and is calculated as a leaf hash using
> 0x00. Thus CT "interior nodes" always have two children, but if the tree has
> an odd number of entries, the rightmost hash at layer 1 ("j" in the "binary
> Merkle tree with 7 leaves" figure) is a leaf node hash rather than an
> interior node hash.
>
>
> O-8. [CrosbyWallach] discusses auditing and gossiping and could be cited as
> a source for further discussion on those topics.
>
>
> O-9. The notion of "commitments" isn't well defined, and where "add a
> commitment to D[k:n]"  couldn't  "add an interior/intermediate node to
> D[k:n}"  be used?
>
> Is not the term "commitment" used in [CrosbyWallach] equivalent to the
> sha256_root_hash (an STH component) in the spec?
>
> [CrosbyWallach] uses the term "interior node(s)" while the spec uses
> "intermediate nodes" (in one place).

CT is not actually derived from [CrosbyWallach], we just mention it as
a useful reference.

"commitment" is a term of cryptographic art.

> O-10. The recursive algorithms in S2 are dense and take effort to work
> through, perhaps adding simplistic example code (in an appendix) which
> implements, and/or actually working through the algorithms to arrive at some
> of the audit paths and consistency proofs in S2.1.3, would be helpful.

We have actual working code - would a reference to that be better?

> I desk-checked S2.1, and it seems correct, but didn't do S2.1.1 or S2.1.2.
> The examples in S2.1.3 appear nominally correct but I didn't desk check
> them.
>
> Should there be a reference to
> <https://code.google.com/p/certificate-transparency/> ?   And/or a note
> regarding available code and to contact the authors for more information?
> (as is done in RFC 2154)

I couldn't find such a thing in RFC 2154. My only concern about such a
reference is whether it would live as long as the RFC does :-)

> O-11. S3.3 should mention the Maximum Merge Delay MMD where it says
> "periodically append". Also, in S3.3, "Signed Merkle Tree Update" should be
> a "Tree Head Signature" aka "signed tree head (STH)"?

I just removed that, as it is immediately repeated in the next section.

>
>
> O-12. S3.3, S3.4, S4.4, S4.5, and S4.7 mention the notion of logs
> "publishing" STHs, but no mechanism is described for explicitly
> "publishing". Is this meant to mean only that a "published" STH is available
> for retrieval by clients using the "Retrieve Latest Signed Tree Head" log
> client message?
>
> Or, would there be a use case, eg introducing an existing log service to a
> log monitor, for requesting (or being able to enumerate) all published STHs
> from the log?

I don't believe there is: the latest STH tells you everything you need
to know at that point. I have removed mention of publishing.

>
>
> O-13. signed tree heads (STHs) are denoted in terms of "tree size" (number
> of entries), but SCTs are denoted in terms of a timestamp.  Should there be
> a log client message supporting the return of the nearest STH (and thus tree
> size) to a given timestamp?

I don't believe this is needed.

>
>
>
> O-14. Detailed comments on S2...
> ------------------------------
>
>> 2. Cryptographic components
>>
>>
>> 2.1. Merkle Hash Trees
>>
>>
>>    Logs use a binary Merkle hash tree for efficient auditing.  The
>>    hashing algorithm is SHA-256 (note that this is fixed for this
>>    experiment but it is anticipated that each log would be able to
>>    specify a hash algorithm).  The input to the Merkle tree hash is a
>>    list of data entries; these entries will be hashed to form the leaves
>>    of the Merkle hash tree.  The output is a single 32-byte root hash.
>>    Given an ordered list of n inputs, D[n] = {d(0), d(1), ..., d(n-1)},
>>    the Merkle Tree Hash (MTH) is thus defined as follows:
>>
>>    The hash of an empty list is the hash of an empty string:
>>
>>    MTH({}) = SHA-256().
>
>
> This MTH({}) construct doesn't appear to be used anywhere else in the spec
> (yes?), and so does it really need mentioning?

If it is not defined, then we cannot represent an empty tree.

>>    The hash of a list with one entry is:
>>
>>    MTH({d(0)}) = SHA-256(0x00 || d(0)).
>
>
> The immediately above equation is for leaf entries (yes?),

Yes.

> where in this
> notation n = 1, perhaps it should be stated explicitly:
>
>     When n = 1, a leaf entry is denoted, and D[1] = {d(0)}. The leaf hash
>     (LH) for a leaf entry is calculated as:
>
>     MTH(D[1]) = LH(D[1]) = SHA-256( 0x00 || d(0) )

Ugh. LH(D[1]) seems meaningless to me. A leaf hash is always of a "1
entry tree".

>
>
>
>>    For n > 1, let k be the largest power of two smaller than n.
>
>
> The unqualified "power of two" phrase is arguably ambiguous.

It is?

> Suggested rephrase for this where it occurs throughout section 2..
>
>     For n > 1, let k be a number which is the largest power of two
>     such that k = 2^i, 0 <= i < n, and k < n.

If we're going to go down that path, then it should say:

For n > 1, let k be the largest number such that k = 2^i and k < n.

or

For n > 1, let k = 2^i s.t. k < n and 2k >= n.

surely?

>>    The Merkle Tree Hash of an n-element list D[n] is then defined
>>    recursively as
>
>
> The above statement applies to the combination of the n = 1 equation above
> and the equation below, and so should perhaps be moved up above the n = 1
> equation.

? It says n > 1, so doesn't apply to n = 1?

>>    MTH(D[n]) = SHA-256(0x01 || MTH(D[0:k]) || MTH(D[k:n])),
>>
>>    where || is concatenation and D[k1:k2] denotes the length (k2 - k1)
>>    list {d(k1), d(k1+1),..., d(k2-1)}.
>
>
> The above phrase doesn't parse well and is somewhat ambiguous, here it is
> extracted for clarity:
>
>  "D[k1:k2] denotes the length (k2 - k1) list {d(k1), d(k1+1),..., d(k2-1)}"
>
>
> How about rephrasing it along the lines of this:
>
>     D[k1:k2] denotes a sublist {d(k1), d(k1+1),..., d(k2-1)}, having
>     (k2 - k1) elements, of the original input list D[n]. When (k2 - k1)
>     is 1, a leaf hash is calculated.

We tried lots of different ways of saying this and they were all a
little messy. Yours mixes concerns and is rather verbose, so not
convinced it is actually an improvement.

>
>
>                                          (Note that the hash calculation
>>
>>    for leaves and nodes differ.  This domain separation is required to
>>    give second preimage resistance.)
>>
>>    Note that we do not require the length of the input list to be a
>>    power of two.  The resulting Merkle tree may thus not be balanced,
>>    however, its shape is uniquely determined by the number of leaves.
>>    [This Merkle tree is essentially the same as the history tree [1]
>>    proposal, except our definition omits dummy leaves.]
>
>
> I suggest re-writing the first above Note along with the next paragraph in
> light of all above comments on S2 and [CrosbyWallach].

It was already partly rewritten as a result of above comments, so
let's see how you like the next version?

> O-15.  Some comments on S3:
> ------------------------------------
>
>> 3. Log Format
>
>
> this section isn't just about "format" of log - it's also about log
> behavior/operation

Good point.

>
>
>>    Anyone can submit certificates to certificate logs for public
>>    auditing, however, since certificates will not be accepted by clients
>>    unless logged, it is expected that certificate owners or their CAs
>>    will usually submit them.  A log is a single, ever-growing, append-
>>    only Merkle Tree of such certificates.
>>
>>    When a valid certificate is submitted to a log, the log MUST
>>    immediately return a Signed Certificate Timestamp (SCT).  The SCT is
>>    the log's promise to incorporate the certificate in the Merkle Tree
>>    within a fixed amount of time known as the Maximum Merge Delay (MMD).
>>    If the log has previously seen the certificate, it MAY return the
>>    same SCT as it returned before.
>
>
> What if the submitted end entity cert is the same, but the certificate chain
> is different (yet valid)?

The purpose of the chain is to:

a) Prevent spam, and

b) Identify who to blame in the event of a misissue.

Alternate chains presumably don't actually change the direct blame,
and so I see no reason to do other than what the I-D says - i.e.
return the same SCT as before.

>>                                     TLS servers MUST present an SCT from
>>    one or more logs to the client together with the certificate.  TLS
>>    clients MUST reject certificates that do not have a valid SCT for the
>>    end-entity certificate.
>
>
> [ see comment (7) above ]
>
>
>>    Periodically, each log appends all its new entries to the Merkle
>>    Tree, and signs the root of the tree.  Clients and auditors can thus
>
>
> Should "Clients and auditors" actually be "TLS Clients, log monitors, and
> log auditors" ?

Bearing in mind that these are actually roles rather than distinct
entities, it should probably just say "auditors".

>
>
>>    verify that each certificate for which an SCT has been issued indeed
>>    appears in the log.
>
>
> Add forward reference here to S4 and S5 ?
>
>
>
>>                         The log MUST incorporate a certificate in its
>>    Merkle Tree within the Maximum Merge Delay period after the issuance
>>    of the SCT.
>>
>>    Logs MUST NOT impose any conditions on copying data retrieved from
>>    the log.
>
>
> s/copying data retrieved/retrieving or sharing data/

OK.

>> 3.1. Log Entries
>>
>>
>>    Anyone can submit a certificate to any log.  In order to enable
>>    attribution of each logged certificate to its issuer, the log SHALL
>>    publish a list of acceptable root certificates (this list might
>>    usefully be the union of root certificates trusted by major browser
>>    vendors).  Each submitted certificate MUST be accompanied by all
>>    additional certificates required to verify the certificate chain up
>>    to an accepted root certificate.  The root certificate itself MAY be
>>    omitted from this list.
>>
>>    Alternatively, (root as well as intermediate) Certificate Authorities
>
>
> Additionally?  which manner is the experiment going to operate, or is it TBD
> ?

Not sure what you mean? The log will accept either type of submission.

>>    may submit a certificate to logs prior to issuance.  To do so, a
>>    Certificate Authority constructs a Precertificate by adding a special
>>    critical poison extension (OID 1.3.6.1.4.1.11129.2.4.3, whose
>>    extnValue OCTET STRING contains ASN.1 NULL data (0x05 0x00)) to the
>>    leaf TBSCertificate (this extension is to ensure that the
>
>
> leaf == end entity ?
>
> s/leaf certificate/end entity certificate/g   ?

Yes.

>>    Precertificate cannot be validated by a standard X.509v3 client), and
>>    signing the resulting TBSCertificate [RFC5280] with either
>
>
>
>>    o  a special-purpose (Extended Key Usage: Certificate Transparency,
>>       OID 1.3.6.1.4.1.11129.2.4.4) Precertificate Signing Certificate.
>>       The Precertificate Signing Certificate MUST be certified by the CA
>>       certificate that will ultimately sign the leaf TBSCertificate
>
>
> "sign the leaf TBSCertificate"  means to say "sign the actual
> issued-to-the-customer TBSCertificate component of the End Entity
> certificate" ?

Well, it means something like that, I have added some words.

>
>>       (note that the log may relax standard validation rules to allow
>>       this, so long as the final signed certificate will be valid),
>>
>>    o  or, the CA certificate that will sign the final certificate.
>
>
> "final certificate" is the "issued-to-the-customer End Entity certificate" ?

I have changed this to "issued certificate".

>
>
>>    Structure of the Signed Certificate Timestamp:
>
>
> The SCT discussion here should probably be its own subsection.

OK.

>
>
>>
>>        enum { certificate_timestamp(0), tree_hash(1), 255 }
>>          SignatureType;
>>
>>        enum { v1(0), 255 }
>>          Version;
>
>>
>>
>>          struct {
>>              opaque key_id[32];
>>          } LogID;
>>
>>          opaque CtExtensions<0..2^16-1>;
>>
>>    "key_id" is the SHA-256 hash of the log's public key, calculated over
>>    the DER encoding of the key represented as SubjectPublicKeyInfo.
>
>
> I'd place the above paragraph regarding "key_id" down below the
> SignedCertificateTimestamp definition.
>
>
>>        struct {
>>            Version sct_version;
>>            LogID id;
>>            uint64 timestamp;
>>            CtExtensions extensions;
>>            digitally-signed struct {
>>                Version sct_version;
>>                SignatureType signature_type = certificate_timestamp;
>>                uint64 timestamp;
>>                LogEntryType entry_type;
>>                select(entry_type) {
>>                    case x509_entry: ASN.1Cert;
>>                    case precert_entry: ASN.1Cert;
>>                } signed_entry;
>>               CtExtensions extensions;
>>            };
>>        } SignedCertificateTimestamp;
>>
>>    The encoding of the digitally-signed element is defined in [RFC5246].
>
>
> I would add a few words here summarizing that what happens here is that the
> digitally-signed struct here is replaced in the actual serialized binary
> structure by a struct DigitallySigned and cross-ref to S4.7 of RFC5246.

Except it isn't :-)

And we already reference RFC5246.

>> 3.2. Including the Signed Certificate Timestamp in the TLS Handshake
>
>
> This should be it's own top-level section as mentioned in comment (3).
>
>
>>    The SCT data from at least one log must be included in the TLS
>>    handshake, either by using an Authorization Extension [RFC5878] with
>>    type 182, or by using OCSP Stapling (section 8 of [RFC6066]),
>
>
> add to above sentence:
>
>   or by embedding the the SCT(s) in the presented End Entity cert,

Addressed earlier.

>>                                                                  where
>>    the response includes an OCSP extension with OID
>>    1.3.6.1.4.1.11129.2.4.5 (see [RFC2560]) and body:
>>
>>        SignedCertificateTimestampList ::= OCTET STRING
>>
>>    At least one SCT MUST be included.  Server operators MAY include more
>>    than one SCT.
>>
>>    Similarly, a Certificate Authority MAY submit the precertificate to
>
>
> s/the precertificate/a precertificate/

Yes.

>>    more than one log, and all obtained SCTs can be directly embedded in
>>    the final certificate, by encoding the SignedCertificateTimestampList
>
>
> s/final certificate/actual End Entity certificate/   ?

Addressed earlier.

>>    structure as an ASN.1 OCTET STRING and inserting the resulting data
>>    in the TBSCertificate as an X.509v3 certificate extension (OID
>>    1.3.6.1.4.1.11129.2.4.2).  Upon receiving the certificate, clients
>>    can reconstruct the original TBSCertificate to verify the SCT
>>    signature.
>
>
> This last step of "clients can reconstruct the original TBSCertificate"
> probably should be more thoroughly explained.

Yeah, it probably should.

> O-15.  Some comments on S4:
> ---------------------------
>
>
>> 4. Client Messages
>
>
> title should be "Log Client Messages" ?

Yes.

>>    Messages are sent as HTTPS GET or POST requests.  Parameters for
>>    POSTs and all responses are encoded as JSON objects.  Parameters for
>
>
> s/JSON objects/JSON texts/

I don't agree with this. See above.

> see <https://tools.ietf.org/html/rfc4627>  (it should be cited)
>
>>    GETs are encoded as URL parameters.  Binary data is base64 encoded as
>>    specified in the individual messages.
>>
>>    The <log server> prefix can include a path as well as a server name
>>    and a port.  It must map one-to-one to a known public key (how this
>>    mapping is distributed is out of scope for this document).
>
>
> s/distributed/constructed and distributed/  ?
>
>
>>    In general, where needed, the "version" is v1 and the "id" is the log
>>    id for the log server queried.
>
>
>
>
>
>> 4.1. Add Chain to Log
>>
>>
>>    POST https://<log server>/ct/v1/add-chain
>>
>>    Inputs
>>
>>    chain  An array of base64 encoded certificates.  The first element is
>
>
> a JSON text array?

It is already defined to be a field in a JSON object and hence that is
all it could be.

>>       the leaf certificate, the second chains to the first and so on to
>>       the last, which is either the root certificate or a certificate
>>       that chains to a known root certificate.
>>
>>    Outputs
>>
>>    sct_version  The version of the SignedCertificateTimestamp structure,
>>       in decimal.  A compliant v1 implementation MUST NOT expect this to
>>       be 0 (i.e. v1).
>>
>>    id The log ID, base64 encoded.  Since clients who request an SCT for
>
>
> s/clients/log clients/  ?

That seems obvious, but I have added it anyway.

>>       inclusion in the TLS handshake are not required to verify it, we
>
>
> s/the TLS handshake/subsequent TLS handshakes/   ?
>
>
>
>>       do not assume they know the ID of the log.
>>
>>    timestamp  The SCT timestamp, in decimal.
>>
>>    extensions  An opaque type for future expansion.  It is likely that
>>       not all participants will need to understand data in this field.
>>       Logs should set this to the empty string.  Clients should decode
>>       the base64 encoded data and include it in the SCT.
>>
>>    signature  The SCT signature, base64 encoded.
>
>
> "The SCT signature" means a SignedCertificateTimestamp structure ?

No, the signature that is a component of the structure.

>>    If the "sct_version" is not v1, then a v1 client may be unable to
>>    verify the signature.  It MUST NOT construe this as an error.  [Note:
>>    log clients don't need to be able to verify this structure, only TLS
>>    clients do - if we were to serve the structure binary, then we could
>>    completely change it without requiring an upgrade to v1 clients].
>
>
> Does this "if we were to serve the structure binary...."  statement mean to
> say that since v1 log clients don't need to be able to verify the SCT
> signature over the various returned data items, that this operation could
> instead return an opaque binary blob?

Indeed.

> O-16.  Some comments on S5:
> ---------------------------
>
>
>> 5. Clients
>>
>>
>>    There are various different functions clients of logs might perform.
>
>
> Perhaps this section should be entitled "Log Client Roles" ?

Since you persuaded me to include TLS clients, no :-)

> this section doesn't mention the role of a (CA) log client that submits
> "certs and cert chains" to logs. Even though the latter role is mentioned
> elsewhere in the spec it should perhaps be mentioned here also.

OK.

>
>
>> 5.1. Monitor
>>
>>
>>    Monitors watch logs and check that they behave correctly.  They also
>>    watch for certificates of interest.
>
>
> "Monitor" should be "Log Monitor" ?

There's no other kind of monitor :-)

>
>>
>> 5.2. Auditor
>>
>>
>>    Auditors take partial information about a log as input and verify
>>    that this information is consistent with other partial information
>>    they have.  An auditor might be an integral component of a TLS
>>    client, it might be a standalone service or it might be a secondary
>>    function of a monitor.
>
>
> "Auditor" should be "Log Auditor" ?

And there's no other kind of auditor.

>
>
>
>> 8. Efficiency Considerations
>>
>>
>>    The Merkle tree design serves the purpose of keeping communication
>>    overhead low.
>>
>>    Auditing logs for integrity does not require third parties to
>>    maintain a copy of each entire log.  The Signed Tree Heads can be
>>    updated as new entries become available, without recomputing entire
>>    trees.  Third party auditors need only fetch the Merkle consistency
>>    proofs against a log's existing STH to efficiently verify the append-
>>    only property of updates to their Merkle Trees, without auditing the
>>    entire tree.
>
>
> The above could be explained in more detail, and S5.1 should be
> cross-referenced. Is the last sentence above essentially a summary of step
> #8 in S5.1? Or are there differences?

It is a summary of 5.1

>
>
> ---
> end
>
>

From touch@isi.edu  Wed Jan  9 09:57:51 2013
Return-Path: <touch@isi.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B0F2721F873E for <ietf@ietfa.amsl.com>; Wed,  9 Jan 2013 09:57:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 IcAIq1pykRRi for <ietf@ietfa.amsl.com>; Wed,  9 Jan 2013 09:57:51 -0800 (PST)
Received: from darkstar.isi.edu (darkstar.isi.edu [128.9.128.127]) by ietfa.amsl.com (Postfix) with ESMTP id 25C1A21F873B for <ietf@ietf.org>; Wed,  9 Jan 2013 09:57:43 -0800 (PST)
Received: from [192.168.1.95] (pool-71-105-87-221.lsanca.dsl-w.verizon.net [71.105.87.221]) (authenticated bits=0) by darkstar.isi.edu (8.13.8/8.13.8) with ESMTP id r09HvDbe018907 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 9 Jan 2013 09:57:16 -0800 (PST)
Message-ID: <50EDAF56.70103@isi.edu>
Date: Wed, 09 Jan 2013 09:56:38 -0800
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130107 Thunderbird/17.0.2
MIME-Version: 1.0
To: John Day <jeanjour@comcast.net>
Subject: Re: A proposal for a scientific approach to this question [was Re: I'm struggling with 2219 language again]
References: <CADnDZ8_GgVeapUKefFMqOvwOo00X8_rFDWMR0vb-Zvu_p=yT3A@mail.gmail.com> <a062408a2cd10003cf574@[10.0.1.3]> <50EAA93C.6060206@cisco.com> <a062408a5cd106d980f2d@[10.0.1.3]> <50EAC2C3.2080807@cisco.com> <201301072146.r07LkXff020987@cichlid.raleigh.ibm.com> <a06240801cd112ca0edab@[10.0.1.3]>
In-Reply-To: <a06240801cd112ca0edab@[10.0.1.3]>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: Thomas Narten <narten@us.ibm.com>, ietf <ietf@ietf.org>, stbryant@cisco.com
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 09 Jan 2013 17:57:51 -0000

On 1/7/2013 6:01 PM, John Day wrote:
> All standards groups that I am aware of have had the same view.  This is
> not uncommon.
>
> Although, I would point out that the TCP specification nor do most
> protocols specifications of this type follow this rule.  State
> transitions are not visible on the wire.  The rules for sliding window
> are not described entirely in terms of the behavior seen on the line, etc.
>
> I have seen specifications that attempted this and the implementations
> built from them were very different and did not come close to
> interoperating or in some cases of even doing the same thing.
>
> In fact, I remember that we thought the new Telnet spec (1973) was a
> paragon of clarity until a new site joined the Net that had not been
> part of the commuity and came up with an implementation that bore no
> relation to what anyone else had done.
>
> This problem is a lot more subtle than you imagine.

+1

A protocol *is*:

	- the states at the endpoints
	- the messages on the wire
	- a description of input events (message arrival, upper-layer
		interface requests, timer expiration) that indicates
		the subsequent change of state and output event
		(message departure, upper layer indication,
		or timers to set)

(i.e., a Mealy machine, attaching events to arcs)

The "wire" is the second of these, and entirely insufficient as a 
protocol spec.

Yes, there are two ways to try to write a protocol spec:
	- procedural
		defining the above explicitly
	- behavioral
		defining a protocol only from its external
		behavior

The difference between these is easy to see for sort algorithms:

	procedural:
		quicksort
		heapsort
		etc.

	behavioral:
		sort

AFAICT, "on the wire" often implies behavioral equivalence, but it's a 
lot more complicated than just the on-wire messages. A behavioral 
description of a protocol would treat the protocol as a black box and 
explain its behavior under every possible input.

I'll take procedural descriptions of protocols over behavioral any day.

Joe

From chair@ietf.org  Wed Jan  9 15:27:31 2013
Return-Path: <chair@ietf.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3161B21F84FB; Wed,  9 Jan 2013 15:27:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 aocf7NNjvluu; Wed,  9 Jan 2013 15:27:30 -0800 (PST)
Received: from mail.amsl.com (mail.amsl.com [IPv6:2001:1890:123a::1:14]) by ietfa.amsl.com (Postfix) with ESMTP id 7370D21F8495; Wed,  9 Jan 2013 15:27:27 -0800 (PST)
Received: from localhost (c8a.amsl.com [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id 32A6F127944; Wed,  9 Jan 2013 15:27:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from c8a.amsl.com ([127.0.0.1]) by localhost (c8a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id b6p3JqF3TmJc; Wed,  9 Jan 2013 15:27:26 -0800 (PST)
Received: from [64.170.98.160] (unknown [64.170.98.160]) by c8a.amsl.com (Postfix) with ESMTPSA id 18872124A14; Wed,  9 Jan 2013 15:27:26 -0800 (PST)
Content-Type: text/plain; charset=us-ascii
Subject: Orlando IETF Codesprint
Mime-Version: 1.0 (Apple Message framework v1085)
From: IETF Chair <chair@ietf.org>
Date: Wed, 9 Jan 2013 18:27:25 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <73EDFA93-8F96-4FD3-BDE0-7B6DD4BA66C1@ietf.org>
To: IETF Announcement list <ietf-announce@ietf.org>
X-Mailer: Apple Mail (2.1085)
Cc: IETF <ietf@ietf.org>, 86all@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: ietf@ietf.org
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 09 Jan 2013 23:27:31 -0000

Orlando IETF Codesprint

When:  Saturday, 9 March 2013, starting at 9:30 AM

Where: IETF Hotel

What:  A bunch of hackers get together to work on code for the
  IETF.  All code will become part of the open source IETF tools.

Who:   Hopefully you can help

Many of the results of previous codesprint activities are being used =
every day by the IETF community.  Shortly before the Paris meeting, we =
transitioned to a new database schema.  It makes many tasks much easier. =
 Please come to the codesprint and work to polish or improve existing =
tools, fix bugs, or make altogether new tools.  All efforts are =
appreciated and most welcome.

Steve Conte and Robert Sparks will be helping with advance planning.  =
Henrik Levkowetz will be coordinating the event in Orlando.  You can =
find more information here:

 http://trac.tools.ietf.org/tools/ietfdb/wiki/IETF86Sprint

If you are able to participate, please sign up on the wiki at:

 http://trac.tools.ietf.org/tools/ietfdb/wiki/IETF86SprintSignUp

Please support the tools development effort,
Russ


From sm@resistor.net  Thu Jan 10 09:34:17 2013
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6052521F8A3F for <ietf@ietfa.amsl.com>; Thu, 10 Jan 2013 09:34:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.582
X-Spam-Level: 
X-Spam-Status: No, score=-102.582 tagged_above=-999 required=5 tests=[AWL=0.017, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 NQRnNen074CV for <ietf@ietfa.amsl.com>; Thu, 10 Jan 2013 09:34:16 -0800 (PST)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id D1FA721F8A41 for <ietf@ietf.org>; Thu, 10 Jan 2013 09:34:15 -0800 (PST)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r0AHYAgP002955 for <ietf@ietf.org>; Thu, 10 Jan 2013 09:34:13 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1357839254; bh=8ygLomVqnaMtg1p2iKDiYUh/0+OXGrHmKN6ME35ETTY=; h=Date:To:From:Subject:In-Reply-To:References; b=OWI0/vBBW2rEx80f6ArdNJRsc0TjZj3CrM/XYPpuSdjZID/qCAQARhzvLyie72Io0 M7Hrlhz+FPCOOqjPXC4t9nhZxIIlZCuyEQY8IlJqpXQJc9CM9TtHNi1RY50H9c9D1p 47Hm4rWrGi/a/6Q8IDCkTdArFtKA54mk5JL0mLxA=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1357839254; i=@resistor.net; bh=8ygLomVqnaMtg1p2iKDiYUh/0+OXGrHmKN6ME35ETTY=; h=Date:To:From:Subject:In-Reply-To:References; b=yIh6Ri3UNvgZy2J/C0yelNyScee5LaKktJonE85E+RBA3au0pPe3qS2qk0OB8iJ/p 2Vx1lm2Li3UsnUhmel917q2BkpLZ8m6O3XHWFCErwFn9OWyEDns/UjVN0ftOwDE+BY N2bayKxCMuO/S+XZjpd1iQFfAc/uBSuPN1W7eJqk=
Message-Id: <6.2.5.6.2.20130110065213.0ad01a90@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Thu, 10 Jan 2013 09:10:32 -0800
To: ietf@ietf.org
From: SM <sm@resistor.net>
Subject: Re: Last Call: <draft-laurie-pki-sunlight-05.txt> (Certificate Transparency) to Experimental RFC
In-Reply-To: <20121220193358.31474.25301.idtracker@ietfa.amsl.com>
References: <20121220193358.31474.25301.idtracker@ietfa.amsl.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 10 Jan 2013 17:34:17 -0000

At 11:33 20-12-2012, The IESG wrote:
>The IESG has received a request from an individual submitter to consider
>the following document:
>- 'Certificate Transparency'
>   <draft-laurie-pki-sunlight-05.txt> as Experimental RFC
>
>The IESG plans to make a decision in the next few weeks, and solicits
>final comments on this action. Please send substantive comments to the
>ietf@ietf.org mailing lists by 2013-01-24. Exceptionally, comments may be

In Section 1:

   "Certificate Transparency aims to mitigate the problem of misissued
    certificates by providing publicly auditable, append-only, untrusted
    logs of all issued certificates."

It seems that CAs are having trust issues.  ETSI TS 102 042 audits 
looks like paperwork instead of assessing what could go wrong 
[1].  Isn't Certificate Transparency trying to mitigate the problem 
of CAs issuing fake certificates instead of "misissued" certificates?

In Section 3:

   "Logs MUST NOT impose any conditions on copying data retrieved from
    the log."

I am reading the above as meaning that the data retrieved is in the 
public domain.  Is that correct?  The wording could be improved as 
logs do not have any consciousness.

In Section 3.1:

  "In order to enable attribution of each logged certificate to its
   issuer, the log SHALL publish a list of acceptable root certificates
   (this list might usefully be the union of root certificates trusted
   by major browser vendors)."

Why is this a "SHALL" instead of a "MUST"?  I suggest a better 
wording for "log" in the above as "log" is defined as "a single, 
ever-growing, append-only Merkle Tree of such certificates".  There 
are other occurrences of "log" in the draft that should be reviewed.

In Section 4:

   "Messages are sent as HTTPS GET or POST requests.  Parameters for
    POSTs and all responses are encoded as JSON objects.

I suggest adding a reference for JSON objects.

   "It must map one-to-one to a known public key (how this
    mapping is distributed is out of scope for this document)."

This looks like a requirement.

   "A compliant v1 implementation MUST NOT expect this to
    be 0 (i.e. v1)."

What happens if the v1 implementation gets a zero?

In Section 7.3:

   "Violation of the append-only property is detected by global gossiping,
    i.e., everyone auditing logs comparing their versions of the latest
    signed tree heads."

In my humble opinion that's a practical approach.

Section 7 is about security and privacy considerations.  I didn't see 
any privacy considerations in Section 7.  I don't think that it is 
really needed as the document is about publicly auditable logs.  If 
there is any concern about information disclosure it could be 
mentioned that Certificate Transparency is for public end-entities.

Regards,
-sm

1. Confirm that there are automatic blocks in place for high-profile 
domain names (including those targeted in the DigiNotar and Comodo 
attacks in 2011) 


From worley@shell01.TheWorld.com  Thu Jan 10 13:23:08 2013
Return-Path: <worley@shell01.TheWorld.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7E81B21F88BF for <ietf@ietfa.amsl.com>; Thu, 10 Jan 2013 13:23:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.773
X-Spam-Level: 
X-Spam-Status: No, score=-1.773 tagged_above=-999 required=5 tests=[AWL=-1.207, BAYES_40=-0.185, RCVD_IN_DNSWL_LOW=-1, RCVD_IN_SORBS_WEB=0.619]
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 gEU82zH4b1XK for <ietf@ietfa.amsl.com>; Thu, 10 Jan 2013 13:23:07 -0800 (PST)
Received: from TheWorld.com (pcls5.std.com [192.74.137.145]) by ietfa.amsl.com (Postfix) with ESMTP id A02ED21F8632 for <ietf@ietf.org>; Thu, 10 Jan 2013 13:23:06 -0800 (PST)
Received: from shell.TheWorld.com (root@shell01.theworld.com [192.74.137.71]) by TheWorld.com (8.14.5/8.14.5) with ESMTP id r0ALMsd8020008 for <ietf@ietf.org>; Thu, 10 Jan 2013 16:22:57 -0500
Received: from shell01.TheWorld.com (localhost.theworld.com [127.0.0.1]) by shell.TheWorld.com (8.13.6/8.12.8) with ESMTP id r0ALMs2Z4936697 for <ietf@ietf.org>; Thu, 10 Jan 2013 16:22:54 -0500 (EST)
Received: (from worley@localhost) by shell01.TheWorld.com (8.13.6/8.13.6/Submit) id r0ALMsW44942968; Thu, 10 Jan 2013 16:22:54 -0500 (EST)
Date: Thu, 10 Jan 2013 16:22:54 -0500 (EST)
Message-Id: <201301102122.r0ALMsW44942968@shell01.TheWorld.com>
From: worley@ariadne.com (Dale R. Worley)
Sender: worley@ariadne.com (Dale R. Worley)
To: ietf@ietf.org
Subject: Standards-essential patents under RAND licensing
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 10 Jan 2013 21:23:08 -0000

Recent actions by the US Department of Justice, the US Patent Office,
the US Federal Trade Commission (which handles antitrust and consumer
protection matters), and the US International Trade Commission (which
has the power to exclude imports which violate US patents) suggest
that US officials are starting to understand the proper way to handle
"standards-essential patents", that is, patented inventions which are
incorporated into standards and the patent owner has promised to
license under "reasonable and non-discriminatory" terms.  It seems
that in some cases, patent owners have not followed through to issue
the required licenses, and then prosecuted other standard-users based
on patent infringement.

In particular (from the New York Times article linked below):

    Over the years [...] companies took Motorola at its word and
    developed products assuming they could routinely license Motorola's
    patents. But Motorola later refused to license its standard-essential
    patents and sought court injunctions to stop shipment of rival
    products.

    "After Google purchased Motorola [...] it continued these same
    abusive practices."

    In recent months, the F.T.C. has issued position papers and filed
    friend-of-the-court briefs, opposing the motions for injunctions using
    standard patents. The Justice Department and European regulators have
    echoed the commission's stance.

"Justice Department and Patent Office Issue Policy Statement on
Patents"
http://bits.blogs.nytimes.com/2013/01/08/justice-department-and-patent-office-issue-policy-statement-on-patents/
"On Google, F.T.C. Set Rules of War Over Patents"
http://www.nytimes.com/2013/01/05/technology/in-google-patent-case-ftc-set-rules-of-engagement-for-battles.html?_r=0
"United States Department of Justice and United States Patent &
Trademark Office Policy Statement on Remedies for Standards-Essential
Patents Subject to Voluntary F/RAND Commitments"
http://www.justice.gov/atr/public/guidelines/290994.pdf

Dale

From tglassey@earthlink.net  Thu Jan 10 14:04:14 2013
Return-Path: <tglassey@earthlink.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CC83921F87ED for <ietf@ietfa.amsl.com>; Thu, 10 Jan 2013 14:04:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599]
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 JXWqiis3Gqie for <ietf@ietfa.amsl.com>; Thu, 10 Jan 2013 14:04:14 -0800 (PST)
Received: from elasmtp-mealy.atl.sa.earthlink.net (elasmtp-mealy.atl.sa.earthlink.net [209.86.89.69]) by ietfa.amsl.com (Postfix) with ESMTP id 4551121F882B for <ietf@ietf.org>; Thu, 10 Jan 2013 14:04:13 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net; b=QdfLWfPLMtffx6qe1QR2kEnpss8Iudh0VJxA4uYUFJ147PCPgHIcOjlMCTv+AaSb; h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding:X-ELNK-Trace:X-Originating-IP;
Received: from [67.180.133.21] (helo=[192.168.15.2]) by elasmtp-mealy.atl.sa.earthlink.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.67) (envelope-from <tglassey@earthlink.net>) id 1TtQEO-0007Vk-K7 for ietf@ietf.org; Thu, 10 Jan 2013 17:04:12 -0500
Message-ID: <50EF3ADA.3030502@earthlink.net>
Date: Thu, 10 Jan 2013 14:04:10 -0800
From: tglassey <tglassey@earthlink.net>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:13.0) Gecko/20120614 Thunderbird/13.0.1
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Standards-essential patents under RAND licensing
References: <201301102122.r0ALMsW44942968@shell01.TheWorld.com>
In-Reply-To: <201301102122.r0ALMsW44942968@shell01.TheWorld.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ELNK-Trace: 01b7a7e171bdf5911aa676d7e74259b7b3291a7d08dfec794f937aab8d151f8cf337e52fbf191283350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 67.180.133.21
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 10 Jan 2013 22:04:14 -0000

On 1/10/2013 1:22 PM, Dale R. Worley wrote:
> Recent actions by the US Department of Justice, the US Patent Office,
> the US Federal Trade Commission (which handles antitrust and consumer
> protection matters), and the US International Trade Commission (which
> has the power to exclude imports which violate US patents) suggest
> that US officials are starting to understand the proper way to handle
> "standards-essential patents", that is, patented inventions which are
> incorporated into standards and the patent owner has promised to
> license under "reasonable and non-discriminatory" terms.  It seems
> that in some cases, patent owners have not followed through to issue
> the required licenses, and then prosecuted other standard-users based
> on patent infringement.
>
> In particular (from the New York Times article linked below):
>
>      Over the years [...] companies took Motorola at its word and
>      developed products assuming they could routinely license Motorola's
>      patents. But Motorola later refused to license its standard-essential
>      patents and sought court injunctions to stop shipment of rival
>      products.
>
>      "After Google purchased Motorola [...] it continued these same
>      abusive practices."
>
>      In recent months, the F.T.C. has issued position papers and filed
>      friend-of-the-court briefs, opposing the motions for injunctions using
>      standard patents. The Justice Department and European regulators have
>      echoed the commission's stance.
>
> "Justice Department and Patent Office Issue Policy Statement on
> Patents"
> http://bits.blogs.nytimes.com/2013/01/08/justice-department-and-patent-office-issue-policy-statement-on-patents/
> "On Google, F.T.C. Set Rules of War Over Patents"
> http://www.nytimes.com/2013/01/05/technology/in-google-patent-case-ftc-set-rules-of-engagement-for-battles.html?_r=0
> "United States Department of Justice and United States Patent &
> Trademark Office Policy Statement on Remedies for Standards-Essential
> Patents Subject to Voluntary F/RAND Commitments"
> http://www.justice.gov/atr/public/guidelines/290994.pdf
>
> Dale
>


What do you do where a patent predates any standards use of the IP. I 
understand the issues of developing IP but what about IP that already 
existed before the standards processes incorporated it into their work 
product?

Todd

-- 
Regards TSG
"Ex-Cruce-Leo"

//Confidential Mailing - Please destroy this if you are not the intended recipient.


From mcr@sandelman.ca  Thu Jan 10 17:16:34 2013
Return-Path: <mcr@sandelman.ca>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 725F521F8922 for <ietf@ietfa.amsl.com>; Thu, 10 Jan 2013 17:16:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 vYiDvNIOvymG for <ietf@ietfa.amsl.com>; Thu, 10 Jan 2013 17:16:33 -0800 (PST)
Received: from tuna.sandelman.ca (unknown [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) by ietfa.amsl.com (Postfix) with ESMTP id BAD5F21F8920 for <ietf@ietf.org>; Thu, 10 Jan 2013 17:16:33 -0800 (PST)
Received: from sandelman.ca (unknown [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 1318A2016D; Thu, 10 Jan 2013 20:20:56 -0500 (EST)
Received: by sandelman.ca (Postfix, from userid 179) id 7A31663765; Thu, 10 Jan 2013 20:15:44 -0500 (EST)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id 6BC50636B6; Thu, 10 Jan 2013 20:15:44 -0500 (EST)
From: Michael Richardson <mcr@sandelman.ca>
To: tglassey <tglassey@earthlink.net>
Subject: Re: Standards-essential patents under RAND licensing
In-Reply-To: <50EF3ADA.3030502@earthlink.net>
References: <201301102122.r0ALMsW44942968@shell01.TheWorld.com> <50EF3ADA.3030502@earthlink.net>
X-Mailer: MH-E 8.3; nmh 1.3-dev; XEmacs 21.4 (patch 22)
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
Date: Thu, 10 Jan 2013 20:15:44 -0500
Message-ID: <25863.1357866944@sandelman.ca>
Sender: mcr@sandelman.ca
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 11 Jan 2013 01:16:34 -0000

>>>>> "tglassey" == tglassey  <tglassey@earthlink.net> writes:
    tglassey> What do you do where a patent predates any standards use of the IP. I
    tglassey> understand the issues of developing IP but what about IP that already existed
    tglassey> before the standards processes incorporated it into their work product?

I think that it depends upon whether the owner of the patent was
involved in producing the standard.  If not, and nobody knew of the
patent, there is certainly a problem.

-- 
]               Never tell me the odds!                 | ipv6 mesh networks [ 
]   Michael Richardson, Sandelman Software Works        | network architect  [ 
]     mcr@sandelman.ca  http://www.sandelman.ca/        |   ruby on rails    [ 
	

From narten@us.ibm.com  Thu Jan 10 21:53:12 2013
Return-Path: <narten@us.ibm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4DF7421F85EA for <ietf@ietfa.amsl.com>; Thu, 10 Jan 2013 21:53:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.599
X-Spam-Level: 
X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
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 YYhVTzWLKBIK for <ietf@ietfa.amsl.com>; Thu, 10 Jan 2013 21:53:11 -0800 (PST)
Received: from e32.co.us.ibm.com (e32.co.us.ibm.com [32.97.110.150]) by ietfa.amsl.com (Postfix) with ESMTP id B25A821F8480 for <ietf@ietf.org>; Thu, 10 Jan 2013 21:53:08 -0800 (PST)
Received: from /spool/local by e32.co.us.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for <ietf@ietf.org> from <narten@us.ibm.com>; Thu, 10 Jan 2013 22:53:07 -0700
Received: from d03dlp03.boulder.ibm.com (9.17.202.179) by e32.co.us.ibm.com (192.168.1.132) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted;  Thu, 10 Jan 2013 22:53:07 -0700
Received: from d03relay01.boulder.ibm.com (d03relay01.boulder.ibm.com [9.17.195.226]) by d03dlp03.boulder.ibm.com (Postfix) with ESMTP id 35C3919D803E for <ietf@ietf.org>; Thu, 10 Jan 2013 22:53:06 -0700 (MST)
Received: from d03av05.boulder.ibm.com (d03av05.boulder.ibm.com [9.17.195.85]) by d03relay01.boulder.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id r0B5r6T3251734 for <ietf@ietf.org>; Thu, 10 Jan 2013 22:53:06 -0700
Received: from d03av05.boulder.ibm.com (loopback [127.0.0.1]) by d03av05.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP id r0B5r54G009865 for <ietf@ietf.org>; Thu, 10 Jan 2013 22:53:06 -0700
Received: from rotala.raleigh.ibm.com (rotala.raleigh.ibm.com [9.44.115.148]) by d03av05.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVin) with ESMTP id r0B5r5Ot009850 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Thu, 10 Jan 2013 22:53:05 -0700
Received: from rotala.raleigh.ibm.com (localhost.localdomain [127.0.0.1]) by rotala.raleigh.ibm.com (8.14.5/8.12.5) with ESMTP id r0B5r4BV017317 for <ietf@ietf.org>; Fri, 11 Jan 2013 00:53:04 -0500
Received: (from narten@localhost) by rotala.raleigh.ibm.com (8.14.5/8.14.5/Submit) id r0B5r4RP017263 for ietf@ietf.org; Fri, 11 Jan 2013 00:53:04 -0500
From: Thomas Narten <narten@us.ibm.com>
Message-Id: <201301110553.r0B5r4RP017263@rotala.raleigh.ibm.com>
Date: Fri, 11 Jan 2013 00:53:03 -0500
To: ietf@ietf.org
Subject: Weekly posting summary for ietf@ietf.org
User-Agent: Heirloom mailx 12.5 7/5/10
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Content-Scanned: Fidelis XPS MAILER
x-cbid: 13011105-5406-0000-0000-000004121C44
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 11 Jan 2013 05:53:12 -0000

Total of 166 messages in the last 7 days.
 
script run at: Fri Jan 11 00:53:03 EST 2013
 
    Messages   |      Bytes        | Who
--------+------+--------+----------+------------------------
 11.45% |   19 |  7.53% |   127480 | abdussalambaryun@gmail.com
  7.23% |   12 |  7.18% |   121646 | sayrer@gmail.com
  4.22% |    7 |  8.90% |   150674 | jasnell@gmail.com
  6.02% |   10 |  4.63% |    78379 | jeanjour@comcast.net
  0.60% |    1 |  7.60% |   128690 | nabil.n.bitar@verizon.com
  3.01% |    5 |  3.17% |    53598 | mnot@mnot.net
  3.01% |    5 |  3.06% |    51892 | hsantos@isdg.net
  3.01% |    5 |  2.22% |    37592 | dean.willis@softarmor.com
  2.41% |    4 |  2.72% |    46130 | mrex@sap.com
  1.81% |    3 |  3.04% |    51406 | jsr@10gen.com
  2.41% |    4 |  1.71% |    29026 | sm@resistor.net
  2.41% |    4 |  1.38% |    23413 | ole@cisco.com
  2.41% |    4 |  1.35% |    22925 | johnl@taugh.com
  1.20% |    2 |  2.50% |    42369 | ted.ietf@gmail.com
  1.20% |    2 |  2.49% |    42242 | gregimirsky@gmail.com
  0.60% |    1 |  2.67% |    45175 | neil.2.harrison@bt.com
  1.81% |    3 |  1.44% |    24414 | petithug@acm.org
  1.81% |    3 |  1.40% |    23650 | narten@us.ibm.com
  1.81% |    3 |  1.37% |    23260 | ned+ietf@mauve.mrochek.com
  1.81% |    3 |  1.34% |    22738 | huubatwork@gmail.com
  1.20% |    2 |  1.76% |    29738 | matt@mpcm.com
  1.81% |    3 |  1.06% |    17893 | glenzorn@gmail.com
  1.81% |    3 |  1.00% |    16855 | worley@ariadne.com
  0.60% |    1 |  2.16% |    36597 | benl@google.com
  1.81% |    3 |  0.93% |    15686 | swmike@swm.pp.se
  0.60% |    1 |  1.99% |    33745 | gregory.mirsky@ericsson.com
  1.20% |    2 |  1.11% |    18750 | eng.mahmoudemam@yahoo.com
  1.20% |    2 |  1.10% |    18668 | lear@cisco.com
  1.20% |    2 |  0.96% |    16314 | pbryan@anode.ca
  1.20% |    2 |  0.88% |    14906 | john-ietf@jck.com
  1.20% |    2 |  0.80% |    13623 | brian.e.carpenter@gmail.com
  1.20% |    2 |  0.77% |    13020 | stbryant@cisco.com
  1.20% |    2 |  0.76% |    12869 | swb@internet2.edu
  1.20% |    2 |  0.70% |    11872 | rwfranks@acm.org
  1.20% |    2 |  0.68% |    11451 | ynir@checkpoint.com
  1.20% |    2 |  0.66% |    11250 | rbarnes@bbn.com
  1.20% |    2 |  0.65% |    11078 | mcr@sandelman.ca
  1.20% |    2 |  0.64% |    10769 | randy@psg.com
  0.60% |    1 |  0.85% |    14372 | superuser@gmail.com
  0.60% |    1 |  0.74% |    12562 | loa@pi.nu
  0.60% |    1 |  0.70% |    11785 | alh-ietf@tndh.net
  0.60% |    1 |  0.66% |    11201 | thegreatall@gmail.com
  0.60% |    1 |  0.62% |    10452 | presnick@qti.qualcomm.com
  0.60% |    1 |  0.58% |     9838 | conal.tuohy@versi.edu.au
  0.60% |    1 |  0.57% |     9572 | daedulus@btconnect.com
  0.60% |    1 |  0.53% |     8965 | paf@frobbit.se
  0.60% |    1 |  0.51% |     8609 | cabo@tzi.org
  0.60% |    1 |  0.48% |     8127 | d3e3e3@gmail.com
  0.60% |    1 |  0.47% |     7950 | shanna@juniper.net
  0.60% |    1 |  0.45% |     7590 | markus.lanthaler@gmx.net
  0.60% |    1 |  0.44% |     7525 | tglassey@earthlink.net
  0.60% |    1 |  0.44% |     7519 | dave@cridland.net
  0.60% |    1 |  0.44% |     7418 | jgs@juniper.net
  0.60% |    1 |  0.43% |     7324 | ben@nostrum.com
  0.60% |    1 |  0.42% |     7099 | melinda.shore@gmail.com
  0.60% |    1 |  0.42% |     7041 | adrian@olddog.co.uk
  0.60% |    1 |  0.41% |     7007 | touch@isi.edu
  0.60% |    1 |  0.41% |     6861 | lberger@labn.net
  0.60% |    1 |  0.37% |     6335 | bclaise@cisco.com
  0.60% |    1 |  0.37% |     6287 | uyeshiro@ifa.hawaii.edu
  0.60% |    1 |  0.37% |     6267 | braden@isi.edu
  0.60% |    1 |  0.37% |     6234 | rdroms.ietf@gmail.com
  0.60% |    1 |  0.34% |     5829 | framefritti@gmail.com
  0.60% |    1 |  0.34% |     5756 | chair@ietf.org
  0.60% |    1 |  0.33% |     5623 | kent@bbn.com
  0.60% |    1 |  0.31% |     5222 | stpeter@stpeter.im
  0.60% |    1 |  0.30% |     5117 | heard@pobox.com
--------+------+--------+----------+------------------------
100.00% |  166 |100.00% |  1693270 | Total


From adrian@olddog.co.uk  Fri Jan 11 08:21:59 2013
Return-Path: <adrian@olddog.co.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1CC5221F842B for <ietf@ietfa.amsl.com>; Fri, 11 Jan 2013 08:21:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.553
X-Spam-Level: 
X-Spam-Status: No, score=-2.553 tagged_above=-999 required=5 tests=[AWL=0.046,  BAYES_00=-2.599]
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 wwb5+xrLx6rm for <ietf@ietfa.amsl.com>; Fri, 11 Jan 2013 08:21:57 -0800 (PST)
Received: from asmtp2.iomartmail.com (asmtp2.iomartmail.com [62.128.201.249]) by ietfa.amsl.com (Postfix) with ESMTP id E3E3E21F8470 for <ietf@ietf.org>; Fri, 11 Jan 2013 08:21:55 -0800 (PST)
Received: from asmtp2.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp2.iomartmail.com (8.13.8/8.13.8) with ESMTP id r0BGLoUw002817;  Fri, 11 Jan 2013 16:21:50 GMT
Received: from 950129200 (089144192060.atnat0001.highway.a1.net [89.144.192.60]) (authenticated bits=0) by asmtp2.iomartmail.com (8.13.8/8.13.8) with ESMTP id r0BGLldX002780 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 11 Jan 2013 16:21:49 GMT
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: <amorris@amsl.com>
Subject: FW: Last Call: <draft-farrell-ft-03.txt> (A Fast-Track way to RFC with Running Code) to Experimental RFC
Date: Fri, 11 Jan 2013 16:21:49 -0000
Message-ID: <017001cdf017$c394df00$4abe9d00$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: Ac3wFdOP9tSRE1tiRE+NhIh/RtqHrg==
Content-Language: en-gb
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: adrian@olddog.co.uk
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 11 Jan 2013 16:21:59 -0000

Hi Alexa,

Please be aware of this document that has just entered a four-week IETF last
call. The document describes a proposed IETF process experiment under the rules
of RFC 3933.

The proposed experiment calls on the IETF Secretariat to take specific actions
under certain circumstances in corner cases of the experiment. Could you please
have someone in the Secretariat look at the draft and comment on the
practicalities of the actions. Note that, at this stage, no changes to the tools
are proposed so any actions would require manual intervention (if the experiment
were successful and resulted in permanent changes to IETF process we might make
changes to the tools at some future time).

Thanks,
Adrian

> -----Original Message-----
> From: ietf-announce-bounces@ietf.org [mailto:ietf-announce-
> bounces@ietf.org] On Behalf Of The IESG
> Sent: 11 January 2013 15:15
> To: IETF-Announce
> Subject: Last Call: <draft-farrell-ft-03.txt> (A Fast-Track way to RFC with
Running
> Code) to Experimental RFC
> 
> 
> The IESG has received a request from an individual submitter to consider
> the following document:
> - 'A Fast-Track way to RFC with Running Code'
>   <draft-farrell-ft-03.txt> as Experimental RFC
> 
> The IESG plans to make a decision in the next few weeks, and solicits
> final comments on this action. Please send substantive comments to the
> ietf@ietf.org mailing lists by 2013-02-08. Exceptionally, comments may be
> sent to iesg@ietf.org instead. In either case, please retain the
> beginning of the Subject line to allow automated sorting.
> 
> Abstract
> 
>    This memo describes an optional, fast-track way to progress a working
>    group document to IESG review.  It is provided as a process
>    experiment as defined in RFC 3933 for use when working group chairs
>    believe that there is running code that implements a working group
>    Internet-Draft.  The motivation is to have the IETF process
>    explicitly consider running code, consistent with the IETF's overall
>    philosophy of running code and rough consensus.
> 
>    In this process all of working group last call, IETF last call, and
>    Area Director review are carried out in the same two week period.
>    Only comments that meet IESG Discuss criteria need to be addressed
>    during this stage, and authors are required to make any changes
>    within two weeks.
> 
>    This experiment will run for one year.
> 
> 
> The file can be obtained via
> http://datatracker.ietf.org/doc/draft-farrell-ft/
> 
> IESG discussion can be tracked via
> http://datatracker.ietf.org/doc/draft-farrell-ft/ballot/
> 
> No IPR declarations have been submitted directly on this I-D.


From sm@resistor.net  Fri Jan 11 11:59:33 2013
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CF09A21F8732 for <ietf@ietfa.amsl.com>; Fri, 11 Jan 2013 11:59:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.58
X-Spam-Level: 
X-Spam-Status: No, score=-102.58 tagged_above=-999 required=5 tests=[AWL=0.019, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 LsvSd0e+7K3H for <ietf@ietfa.amsl.com>; Fri, 11 Jan 2013 11:59:25 -0800 (PST)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 8B90421F8715 for <ietf@ietf.org>; Fri, 11 Jan 2013 11:59:25 -0800 (PST)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r0BJvxFH003559; Fri, 11 Jan 2013 11:58:02 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1357934285; bh=KYd5q2lcuWbXcqn7xI5MGWTH1zXYiANHYmRfoXW8Ya8=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=25Kc7XpwkYJbF5mG3dp5x8mkABZXlSVIHmmrX1Cr7mFxxWvrjkYG789vQyFxj6UaV nO7sa1BSO2m/98h38zQnAuUDZabqH+SsCye81V6Cx8vn37yEewock2kxtEDY9UFgNQ TXmltrasxLw4s12ZXoUfUUXSHR6V2QBmxDm6tBEs=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1357934285; i=@resistor.net; bh=KYd5q2lcuWbXcqn7xI5MGWTH1zXYiANHYmRfoXW8Ya8=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=LYvvXuDDbNUmvk3143NE7UBqXFoUCwZa7tGd0l7778juIue8AUoiZZ1OnXNpSZ124 NdnQhUIrMiFq+ipYPdmyFJcti/h7KLgmzezU5Lqx+CraID3hedVmU8b7paF348qiAh T0oioDyyVuqt93jr3VZUwQ/xHFtLFfK1iXo0BV8E=
Message-Id: <6.2.5.6.2.20130111094647.095f60e0@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Fri, 11 Jan 2013 11:33:23 -0800
To: ietf@ietf.org
From: SM <sm@resistor.net>
Subject: Re: Last Call: <draft-farrell-ft-03.txt> (A Fast-Track way to RFC with Running Code) to Experimental RFC
In-Reply-To: <20130111151453.22161.50884.idtracker@ietfa.amsl.com>
References: <20130111151453.22161.50884.idtracker@ietfa.amsl.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 11 Jan 2013 19:59:33 -0000

At 07:14 11-01-2013, The IESG wrote:
>The IESG has received a request from an individual submitter to consider
>the following document:
>- 'A Fast-Track way to RFC with Running Code'
>   <draft-farrell-ft-03.txt> as Experimental RFC
>
>The IESG plans to make a decision in the next few weeks, and solicits
>final comments on this action. Please send substantive comments to the
>ietf@ietf.org mailing lists by 2013-02-08. Exceptionally, comments may be

In Section 1:

   "Additionally, the experiment will only require issues raised
    during these three stages to be addressed if they meet the
    IESG's Discuss criteria."

Does this mean that a document does not have to represent consensus?

   "In contrast, a "-bis" RFC that aims for Proposed Standard or
    Experimental is likely to be a fine candidate."

I read what the document proposes as lowering the barrier of entry 
for first publication.  My preference is to say nothing about "-bis" 
RFCs (see quoted text).  Some of the "-bis" drafts I have come across 
(note that this is not related to a draft being discussed currently) 
are not well-written even though there is running code.  The running 
code might be due to author intervention instead of a blind test of 
the specification.

In Section 2:

   "Implementations developed during the production of an Internet-draft
    can indicate that a working group has had the opportunity to get
    early confirmation of its engineering choices."

Agreed.

In Section 3:

   "Any Working Group Last Call (WGLC) or Area Director (AD) review
   (which are routinely done, though not part of the formal [BCP9]
   process) will run in parallel with the two-week IETF Last Call
   (IETF-LC) period."

I am not suggesting changing the two weeks.  It can cause logistical 
problems.  I'll take the risk of trying this experiment.

   "Only comments that would be "DISCUSS-worthy" according to the
    IESG Discuss Criteria [DCRIT] need be handled during last call.
    Other comments can be handled or not, at the authors/editors
    discretion."

See my previous comment about this criteria.

In Section 4:

   "The fast-track process can be used for "bis" RFCs and might well
    be quite suitable for those."

I suggest removing this.

   "If the timers (IETF LC or the two-weeks after IETF LC for fixing
    things) co-incide with a major holiday period or IETF meeting
    then the responsible AD can add a week or two as appropriate."

I suggest not using the Fast-Track if it is less than two weeks 
before or after an IETF meeting.  Some people only do IETF work 
during that period and that results in a spike.  I don't think that 
it is a good idea for this experiment to encourage work during the 
meeting phase instead of the mailing list.

In Section 5:

   "An AD who wishes to do her review in parallel with Last Call is
    always free to make that choice."

"his" or a gender neutral term.

   "This memo itself has no impact on appeal processes.  However, in
    considering an appeal that relates to a document that has been
    fast-track processed, the relevant judge (WG chair, AD, IESG or
    IAB as appropriate) should consider the requirements posited here."

The WG Chair is not a judge in such cases as it would be his/her 
decision being appealed.

Some people are discouraged from bringing work into the IETF because 
of the long debates (which I likely contributed to).  Big companies 
have an incentive to do work within the IETF.  There is a perception 
in open source circles than there isn't much to gain in having a 
specification published as a RFC.

The young, free and wild will not listen to the fogies.  The better 
approach, in my opinion, is not to act as a gatekeeper or encourage a 
wall-garden attitude.

Regards,
-sm 


From stephen.farrell@cs.tcd.ie  Fri Jan 11 12:36:52 2013
Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 888E321F8A3F for <ietf@ietfa.amsl.com>; Fri, 11 Jan 2013 12:36:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.131
X-Spam-Level: 
X-Spam-Status: No, score=-103.131 tagged_above=-999 required=5 tests=[AWL=-0.532, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 nhNJxA-LKvRf for <ietf@ietfa.amsl.com>; Fri, 11 Jan 2013 12:36:51 -0800 (PST)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) by ietfa.amsl.com (Postfix) with ESMTP id 74B9B21F89FD for <ietf@ietf.org>; Fri, 11 Jan 2013 12:36:51 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id 4F781BE47; Fri, 11 Jan 2013 20:36:29 +0000 (GMT)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qWkTMA+Be9TP; Fri, 11 Jan 2013 20:36:28 +0000 (GMT)
Received: from [10.87.48.11] (unknown [86.44.70.182]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 2AF73BE3F; Fri, 11 Jan 2013 20:36:28 +0000 (GMT)
Message-ID: <50F077CC.7050206@cs.tcd.ie>
Date: Fri, 11 Jan 2013 20:36:28 +0000
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130106 Thunderbird/17.0.2
MIME-Version: 1.0
To: SM <sm@resistor.net>
Subject: Re: Last Call: <draft-farrell-ft-03.txt> (A Fast-Track way to RFC with Running Code) to Experimental RFC
References: <20130111151453.22161.50884.idtracker@ietfa.amsl.com> <6.2.5.6.2.20130111094647.095f60e0@resistor.net>
In-Reply-To: <6.2.5.6.2.20130111094647.095f60e0@resistor.net>
X-Enigmail-Version: 1.5
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 11 Jan 2013 20:36:52 -0000

Hiya,

On 01/11/2013 07:33 PM, SM wrote:
> At 07:14 11-01-2013, The IESG wrote:
>> The IESG has received a request from an individual submitter to consider
>> the following document:
>> - 'A Fast-Track way to RFC with Running Code'
>>   <draft-farrell-ft-03.txt> as Experimental RFC
>>
>> The IESG plans to make a decision in the next few weeks, and solicits
>> final comments on this action. Please send substantive comments to the
>> ietf@ietf.org mailing lists by 2013-02-08. Exceptionally, comments may be
> 
> In Section 1:
> 
>   "Additionally, the experiment will only require issues raised
>    during these three stages to be addressed if they meet the
>    IESG's Discuss criteria."
> 
> Does this mean that a document does not have to represent consensus?

You mean rough consensus of the IETF I guess? Good question.

First, WG rough consensus is formally unaffected. As is IESG
review. And if IETF LC comments are received that do meet the
IESG discuss criteria then those should be handled as now.

So I guess we're left with cases where there's a lack of
rough consensus during IETF LC but where the meat of the
disagreement is something that doesn't qualify for an IESG
discuss ballot.

I'd say that'd be quite likely to allow the responsible AD
to say that there had been so much debate during IETF LC that
this experiment ought not be used.

So, I don't think this experiment has any major effect
there really but maybe has a subtle one.

I'll be interested in seeing if this happens if we do the
experiment.

>   "In contrast, a "-bis" RFC that aims for Proposed Standard or
>    Experimental is likely to be a fine candidate."
> 
> I read what the document proposes as lowering the barrier of entry for
> first publication.  My preference is to say nothing about "-bis" RFCs
> (see quoted text).  Some of the "-bis" drafts I have come across (note
> that this is not related to a draft being discussed currently) are not
> well-written even though there is running code.  The running code might
> be due to author intervention instead of a blind test of the specification.

I don't get what you mean. Can you explain? (I get that you don't want
to mention -bis cases, but I don't get why.)

> In Section 2:
> 
>   "Implementations developed during the production of an Internet-draft
>    can indicate that a working group has had the opportunity to get
>    early confirmation of its engineering choices."
> 
> Agreed.
> 
> In Section 3:
> 
>   "Any Working Group Last Call (WGLC) or Area Director (AD) review
>   (which are routinely done, though not part of the formal [BCP9]
>   process) will run in parallel with the two-week IETF Last Call
>   (IETF-LC) period."
> 
> I am not suggesting changing the two weeks.  It can cause logistical
> problems.  I'll take the risk of trying this experiment.
> 
>   "Only comments that would be "DISCUSS-worthy" according to the
>    IESG Discuss Criteria [DCRIT] need be handled during last call.
>    Other comments can be handled or not, at the authors/editors
>    discretion."
> 
> See my previous comment about this criteria.
> 
> In Section 4:
> 
>   "The fast-track process can be used for "bis" RFCs and might well
>    be quite suitable for those."
> 
> I suggest removing this.
> 
>   "If the timers (IETF LC or the two-weeks after IETF LC for fixing
>    things) co-incide with a major holiday period or IETF meeting
>    then the responsible AD can add a week or two as appropriate."
> 
> I suggest not using the Fast-Track if it is less than two weeks before
> or after an IETF meeting.  Some people only do IETF work during that
> period and that results in a spike.  I don't think that it is a good
> idea for this experiment to encourage work during the meeting phase
> instead of the mailing list.

Not a bad idea. Something like "fast-track must be started at least
one month (longer?) before an IETF meeting starts" ?

I guess the only problem I'd have with that is that for an experiment
that'd run for one year, that takes out about 4 months (3 meetings
and the year-end holidays) which is a lot.

If we extended the experiment to 18 months duration I'd have no
problem with something like that though. Or with leaving it as-is.
Let's see if we get any other opinions.

> In Section 5:
> 
>   "An AD who wishes to do her review in parallel with Last Call is
>    always free to make that choice."
> 
> "his" or a gender neutral term.

I'll leave that to the rfc editor. He'll fix it:-)

>   "This memo itself has no impact on appeal processes.  However, in
>    considering an appeal that relates to a document that has been
>    fast-track processed, the relevant judge (WG chair, AD, IESG or
>    IAB as appropriate) should consider the requirements posited here."
> 
> The WG Chair is not a judge in such cases as it would be his/her
> decision being appealed.

Can be. If a WG participant says "the decision you made on that
draft is broken: I appeal" then they first send that to the WG
chair.

> Some people are discouraged from bringing work into the IETF because of
> the long debates (which I likely contributed to).  Big companies have an
> incentive to do work within the IETF.  There is a perception in open
> source circles than there isn't much to gain in having a specification
> published as a RFC.
> 
> The young, free and wild will not listen to the fogies.  The better
> approach, in my opinion, is not to act as a gatekeeper or encourage a
> wall-garden attitude.

I don't see any text change being suggested there. Correct me if
I'm wrong.

Cheers,
S.

> 
> Regards,
> -sm
> 
> 

From stewe@stewe.org  Fri Jan 11 13:02:26 2013
Return-Path: <stewe@stewe.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CB4EF21F8A3F for <ietf@ietfa.amsl.com>; Fri, 11 Jan 2013 13:02:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[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 NyCrOrbiy3sM for <ietf@ietfa.amsl.com>; Fri, 11 Jan 2013 13:02:25 -0800 (PST)
Received: from tx2outboundpool.messaging.microsoft.com (tx2ehsobe003.messaging.microsoft.com [65.55.88.13]) by ietfa.amsl.com (Postfix) with ESMTP id 94AFC21F8A0C for <ietf@ietf.org>; Fri, 11 Jan 2013 13:02:25 -0800 (PST)
Received: from mail222-tx2-R.bigfish.com (10.9.14.252) by TX2EHSOBE012.bigfish.com (10.9.40.32) with Microsoft SMTP Server id 14.1.225.23; Fri, 11 Jan 2013 21:02:24 +0000
Received: from mail222-tx2 (localhost [127.0.0.1])	by mail222-tx2-R.bigfish.com (Postfix) with ESMTP id 928453C020F; Fri, 11 Jan 2013 21:02:24 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.236.133; KIP:(null); UIP:(null); IPV:NLI; H:BY2PRD0710HT004.namprd07.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: -19
X-BigFish: PS-19(z10d0kz98dI542I13fcI1432I4015Izz1ee6h1de0h1202h1e76h1d1ah1d2ah1082kzz8275dh1033IL17326ahz2fh2a8h668h839h944hd25hf0ah1220h1288h12a5h12a9h12bdh137ah13b6h1441h1504h1537h153bh15d0h162dh1631h1758h1155h)
Received-SPF: pass (mail222-tx2: domain of stewe.org designates 157.56.236.133 as permitted sender) client-ip=157.56.236.133; envelope-from=stewe@stewe.org; helo=BY2PRD0710HT004.namprd07.prod.outlook.com ; .outlook.com ; 
Received: from mail222-tx2 (localhost.localdomain [127.0.0.1]) by mail222-tx2 (MessageSwitch) id 1357938141267045_32181; Fri, 11 Jan 2013 21:02:21 +0000 (UTC)
Received: from TX2EHSMHS034.bigfish.com (unknown [10.9.14.249])	by mail222-tx2.bigfish.com (Postfix) with ESMTP id 333A6400079; Fri, 11 Jan 2013 21:02:21 +0000 (UTC)
Received: from BY2PRD0710HT004.namprd07.prod.outlook.com (157.56.236.133) by TX2EHSMHS034.bigfish.com (10.9.99.134) with Microsoft SMTP Server (TLS) id 14.1.225.23; Fri, 11 Jan 2013 21:02:16 +0000
Received: from BY2PRD0710MB354.namprd07.prod.outlook.com ([169.254.9.165]) by BY2PRD0710HT004.namprd07.prod.outlook.com ([10.255.86.39]) with mapi id 14.16.0257.004; Fri, 11 Jan 2013 21:02:10 +0000
From: Stephan Wenger <stewe@stewe.org>
To: "adrian@olddog.co.uk" <adrian@olddog.co.uk>, "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: Last Call: <draft-farrell-ft-03.txt> (A Fast-Track way to RFC with Running Code) to Experimental RFC
Thread-Topic: Last Call: <draft-farrell-ft-03.txt> (A Fast-Track way to RFC with Running Code) to Experimental RFC
Thread-Index: AQHN8D7r3XY8HwCadU+f4XzrwHls7g==
Date: Fri, 11 Jan 2013 21:02:09 +0000
Message-ID: <FDBFA77C7400C74F87BC297393B53E3532B13559@BY2PRD0710MB354.namprd07.prod.outlook.com>
In-Reply-To: <017001cdf017$c394df00$4abe9d00$@olddog.co.uk>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.255.102.5]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <D8DD53005CE58E489CBA07410D2C3700@namprd07.prod.outlook.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: stewe.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 11 Jan 2013 21:02:26 -0000

Hi,

Sorry for replying to this "advise to secretariat" thread and not to the
ietf-announce thread--I'm not subscribed to ietf-announce.
I have three comments, and regret that I have not followed all of the
discussions regarding this draft before, so please advise if those
comments have already been raised and/or resolved.


First, I'm glad that the direct preferences of open source implementations
over implementations compliant with other business models are mostly gone.
 Still, there is one reference that worries me, and that is the reference
to GPLv3 code as an "extreme" in section 2.1.  Yes, the GPL (and similar
copyleft licenses) is an extreme, at least in terms of open source
licensing models.  However, it is not an extreme of openness or
accessibility of the source code for review by WG chair, AD, and
community.  I would hope that we are all aware that many (most?)
commercial software developers, by company policy or common sense, avoid
looking at GPL-ed code, out of fear of contamination of their own closed
source code.  GPL-ed code  is, therefore, inaccessible for verification by
a large part of the IETF community, and does not serve as a good example
for "openness", which is how I interpret the spectrum laid out in section
2.1.  A better example would be source code that is almost universally
accessible.  The extreme here would be source code in the public domain.
Somewhat less convincing but perhaps a bit more realistically, source code
under a BSD-style license like the one the IETF Trust is using.

Second, the draft suggest that the existence of an implementation of the
specification should serve as a shortcut towards RFC, presumably because
such an implementation speak favorably to the implementability of the
specification.  That, however, is not universally true.  Specifically, if
implementer and spec writer are the same person (or part of the same
team), it is quite likely that the spec takes certain assumptions made by
the implementers for granted, and does not document it.  That would be a
bad spec, accessible implementation or not.  The solution to this issue is
IMO not, as the draft appears to be to suggest, to put burden on WG chairs
and ADs to ensure that the spec and the implementation match.  Both WG
chairs and ADs have enough to do, and the incentive for rubber-stamping is
quite high.  A more sensible solution may be to require that the
implementer is unaffiliated with the spec author; in other words, the
implementation is derived from the spec + IETF discussion context.

A third comment would be that, if you interpret the draft strictly, it is
highly unlikely that the experiment would ever be exercised, as the
implementation needs to "match" the draft to be advanced, and that would
mean that the implementation has to follow in lockstep with the draft
development up until the final version.  With respect to the core subject
matter of a draft, that may be fine.  However, many of the final edits in
a draft come as input from IETF wide community review; things like
security, congestion control, and the like.  Those are often trivial to
write down, but can have a major implementation impact.  To cure this, it
would IMO be acceptable if the implementation would be required to match
the latest or a reasonably young, i.e. a few months old version of the
draft.

Please consider this.
Thanks,
Stephan
 =20

On 1.11.2013 08:21 , "Adrian Farrel" <adrian@olddog.co.uk> wrote:

>Hi Alexa,
>
>Please be aware of this document that has just entered a four-week IETF
>last
>call. The document describes a proposed IETF process experiment under the
>rules
>of RFC 3933.
>
>The proposed experiment calls on the IETF Secretariat to take specific
>actions
>under certain circumstances in corner cases of the experiment. Could you
>please
>have someone in the Secretariat look at the draft and comment on the
>practicalities of the actions. Note that, at this stage, no changes to
>the tools
>are proposed so any actions would require manual intervention (if the
>experiment
>were successful and resulted in permanent changes to IETF process we
>might make
>changes to the tools at some future time).
>
>Thanks,
>Adrian
>
>> -----Original Message-----
>> From: ietf-announce-bounces@ietf.org [mailto:ietf-announce-
>> bounces@ietf.org] On Behalf Of The IESG
>> Sent: 11 January 2013 15:15
>> To: IETF-Announce
>> Subject: Last Call: <draft-farrell-ft-03.txt> (A Fast-Track way to RFC
>>with
>Running
>> Code) to Experimental RFC
>>=20
>>=20
>> The IESG has received a request from an individual submitter to consider
>> the following document:
>> - 'A Fast-Track way to RFC with Running Code'
>>   <draft-farrell-ft-03.txt> as Experimental RFC
>>=20
>> The IESG plans to make a decision in the next few weeks, and solicits
>> final comments on this action. Please send substantive comments to the
>> ietf@ietf.org mailing lists by 2013-02-08. Exceptionally, comments may
>>be
>> sent to iesg@ietf.org instead. In either case, please retain the
>> beginning of the Subject line to allow automated sorting.
>>=20
>> Abstract
>>=20
>>    This memo describes an optional, fast-track way to progress a working
>>    group document to IESG review.  It is provided as a process
>>    experiment as defined in RFC 3933 for use when working group chairs
>>    believe that there is running code that implements a working group
>>    Internet-Draft.  The motivation is to have the IETF process
>>    explicitly consider running code, consistent with the IETF's overall
>>    philosophy of running code and rough consensus.
>>=20
>>    In this process all of working group last call, IETF last call, and
>>    Area Director review are carried out in the same two week period.
>>    Only comments that meet IESG Discuss criteria need to be addressed
>>    during this stage, and authors are required to make any changes
>>    within two weeks.
>>=20
>>    This experiment will run for one year.
>>=20
>>=20
>> The file can be obtained via
>> http://datatracker.ietf.org/doc/draft-farrell-ft/
>>=20
>> IESG discussion can be tracked via
>> http://datatracker.ietf.org/doc/draft-farrell-ft/ballot/
>>=20
>> No IPR declarations have been submitted directly on this I-D.
>
>



From abdussalambaryun@gmail.com  Fri Jan 11 13:25:41 2013
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1366321F8864; Fri, 11 Jan 2013 13:25:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.577
X-Spam-Level: 
X-Spam-Status: No, score=-3.577 tagged_above=-999 required=5 tests=[AWL=0.022,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 uiCJl3uByrgD; Fri, 11 Jan 2013 13:25:40 -0800 (PST)
Received: from mail-vb0-f54.google.com (mail-vb0-f54.google.com [209.85.212.54]) by ietfa.amsl.com (Postfix) with ESMTP id 9E52E21F846E; Fri, 11 Jan 2013 13:25:39 -0800 (PST)
Received: by mail-vb0-f54.google.com with SMTP id l1so1876407vba.41 for <multiple recipients>; Fri, 11 Jan 2013 13:25:39 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=bpqcODSkbE/SV5iwAQRXv86P9fDo5IFf56tWGFU1WEo=; b=VPK46MacXFdvpcy3c26jvWp6SBtjecf86La5LsEOb0OsYCiCOswCmpjeaWCX4GhL+U XYtEKLnytbNDoRZI0S6/BwQkV/Qok1LqB2oKw8bVbSMvZCT/q7kD1+MuLoZHtDUVUOGg IR2MtyuoykcPE8sVk+twfNjaucGecVW4jX54Jjww2ygTgB0/+u8rTwQWzqheaYb9zA04 sYzsqD4Y74MG1FOmdDLOcanf4yDoQa/EFPs4eg/lj/Kgux737UMZP6zxpNzq1+ptzQkP BmqVO2MGxa/NisSk7vvPPAtH8GSpZO4xmbwtCx1a/11ajk+dPEaqAP5jI2RFKoLNm2oF SaQQ==
MIME-Version: 1.0
Received: by 10.52.21.179 with SMTP id w19mr83902602vde.55.1357939538912; Fri, 11 Jan 2013 13:25:38 -0800 (PST)
Received: by 10.220.145.5 with HTTP; Fri, 11 Jan 2013 13:25:38 -0800 (PST)
In-Reply-To: <20130111151453.22161.50884.idtracker@ietfa.amsl.com>
References: <20130111151453.22161.50884.idtracker@ietfa.amsl.com>
Date: Fri, 11 Jan 2013 22:25:38 +0100
Message-ID: <CADnDZ8-w4Nu0RCgE94yZuBT+y6s176V0_kQsk7d_oBwPtUPhNg@mail.gmail.com>
Subject: Re: Last Call: <draft-farrell-ft-03.txt> (A Fast-Track way to RFC with Running Code) to Experimental RFC
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: sm@resistor.net
Content-Type: text/plain; charset=ISO-8859-1
Cc: ietf@ietf.org, "iesg@ietf.org" <iesg@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 11 Jan 2013 21:25:41 -0000

Hi SM,

I totally agree with your comments and suggestions, the draft SHOULD
mention the important clarifications and the answers to SM's
questions. This is an important draft and SHUOLD be clear about such
important details in sections, why it ignores them without refering to
informative procedure items to link things for understanding. How do
authors write these drafts are they done with following procedure,

AB

++++++++
In Section 1:

  "Additionally, the experiment will only require issues raised
   during these three stages to be addressed if they meet the
   IESG's Discuss criteria."

Does this mean that a document does not have to represent consensus?

  "In contrast, a "-bis" RFC that aims for Proposed Standard or
   Experimental is likely to be a fine candidate."


I read what the document proposes as lowering the barrier of entry for
first publication. My preference is to say nothing about "-bis" RFCs
(see quoted text). Some of the "-bis" drafts I have come across (note
that this is not related to a draft being discussed currently) are not
well-written even though there is running code. The running code might
be due to author intervention instead of a blind test of the
specification.
In Section 2:

  "Implementations developed during the production of an Internet-draft
   can indicate that a working group has had the opportunity to get
   early confirmation of its engineering choices."

Agreed.

In Section 3:

  "Any Working Group Last Call (WGLC) or Area Director (AD) review
  (which are routinely done, though not part of the formal [BCP9]
  process) will run in parallel with the two-week IETF Last Call
  (IETF-LC) period."


I am not suggesting changing the two weeks. It can cause logistical
problems. I'll take the risk of trying this experiment.
  "Only comments that would be "DISCUSS-worthy" according to the
   IESG Discuss Criteria [DCRIT] need be handled during last call.
   Other comments can be handled or not, at the authors/editors
   discretion."

See my previous comment about this criteria.

In Section 4:

  "The fast-track process can be used for "bis" RFCs and might well
   be quite suitable for those."

I suggest removing this.

  "If the timers (IETF LC or the two-weeks after IETF LC for fixing
   things) co-incide with a major holiday period or IETF meeting
   then the responsible AD can add a week or two as appropriate."


I suggest not using the Fast-Track if it is less than two weeks before
or after an IETF meeting. Some people only do IETF work during that
period and that results in a spike. I don't think that it is a good
idea for this experiment to encourage work during the meeting phase
instead of the mailing list.
In Section 5:

  "An AD who wishes to do her review in parallel with Last Call is
   always free to make that choice."

"his" or a gender neutral term.

  "This memo itself has no impact on appeal processes.  However, in
   considering an appeal that relates to a document that has been
   fast-track processed, the relevant judge (WG chair, AD, IESG or
   IAB as appropriate) should consider the requirements posited here."


The WG Chair is not a judge in such cases as it would be his/her
decision being appealed.

Some people are discouraged from bringing work into the IETF because
of the long debates (which I likely contributed to). Big companies
have an incentive to do work within the IETF. There is a perception in
open source circles than there isn't much to gain in having a
specification published as a RFC.

The young, free and wild will not listen to the fogies. The better
approach, in my opinion, is not to act as a gatekeeper or encourage a
wall-garden attitude.
Regards,

-sm

From sm@resistor.net  Fri Jan 11 14:05:41 2013
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4EF0621F8ABA for <ietf@ietfa.amsl.com>; Fri, 11 Jan 2013 14:05:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.581
X-Spam-Level: 
X-Spam-Status: No, score=-102.581 tagged_above=-999 required=5 tests=[AWL=0.018, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 4iiTV59VsHBF for <ietf@ietfa.amsl.com>; Fri, 11 Jan 2013 14:05:40 -0800 (PST)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 74BEB21F8A94 for <ietf@ietf.org>; Fri, 11 Jan 2013 14:05:40 -0800 (PST)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r0BM4E0Q011562; Fri, 11 Jan 2013 14:04:17 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1357941859; bh=KdUX7xxk5wOU9qnnCMw54p3+63/k1uzCx12OSpHqWCw=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=SWqanR1W5baF/Vl1l1gC++vwbHyXxC3oTZwcDXfICYVQ1qYq9zBavfYE8fYb5SH0u V8KAv/IZKO0UplSZwK7fbnvuCLhd63f6FGJsFFXI9J7y39Q8bQn5rb7+wZzSDX5UKA KgKnGCRtQVepuBObePeUEcy5u3xTDYuLeVAxlJk4=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1357941859; i=@resistor.net; bh=KdUX7xxk5wOU9qnnCMw54p3+63/k1uzCx12OSpHqWCw=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=mZUdDrsSxGp1SSQx8QPK9mn4gx/KEUHKs+9A/PusXyy8tjsc9+MByGv1t2q26Figh B7yTgzKP4OmW/6kD5u2n+XX4NvCMt721oQqjlPFZSlaK36aGi7bE8X18Ns4fyq0PIV 6gcrW3MV6R+4GX3muql7K1YkmEzptbRHzvipKzN4=
Message-Id: <6.2.5.6.2.20130111125127.0a5828f8@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Fri, 11 Jan 2013 13:34:29 -0800
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
From: SM <sm@resistor.net>
Subject: Re: Last Call: <draft-farrell-ft-03.txt> (A Fast-Track way to RFC with Running Code) to Experimental RFC
In-Reply-To: <50F077CC.7050206@cs.tcd.ie>
References: <20130111151453.22161.50884.idtracker@ietfa.amsl.com> <6.2.5.6.2.20130111094647.095f60e0@resistor.net> <50F077CC.7050206@cs.tcd.ie>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 11 Jan 2013 22:05:41 -0000

Hi Stephen,
At 12:36 11-01-2013, Stephen Farrell wrote:
>You mean rough consensus of the IETF I guess? Good question.

No, I mean consensus as that's also part what is gauged during a Last Call.

>First, WG rough consensus is formally unaffected. As is IESG
>review. And if IETF LC comments are received that do meet the
>IESG discuss criteria then those should be handled as now.

I am not concerned about the WG rough consensus angle (for the 
experiment) as it is a subset of a Last Call.

>So I guess we're left with cases where there's a lack of
>rough consensus during IETF LC but where the meat of the
>disagreement is something that doesn't qualify for an IESG
>discuss ballot.

Hmm, you mentioned "rough consensus" on an IETF Last Call.  The IETF 
Last Call is about "consensus".  I may have misunderstood the 
experiment as I did not read it as "rough consensus and running 
code".  To say it differently, there isn't any change to the IETF 
Last Call; this is more about fast-tracking the WGLC and the IETF Last Call.

>I'd say that'd be quite likely to allow the responsible AD
>to say that there had been so much debate during IETF LC that
>this experiment ought not be used.

Ok.

>So, I don't think this experiment has any major effect
>there really but maybe has a subtle one.
>
>I'll be interested in seeing if this happens if we do the
>experiment.

Let's see how the experiment works out.

>I don't get what you mean. Can you explain? (I get that you don't want
>to mention -bis cases, but I don't get why.)

What the experiment can do is make it easier to move from unpublished 
specification to RFC.  The "-bis" draft is from a previous RFC.  If 
you try to cover it the experiment can turn into a significant 
process change.  I prefer to leave that unspecified and see how the 
experiment works out instead of telling people to use it for "-bis" 
drafts.  In a "-bis" document is in good shape it should not be a 
significant problem to get it through the process.

>Not a bad idea. Something like "fast-track must be started at least
>one month (longer?) before an IETF meeting starts" ?

   The fast-track process cannot be initiated within two weeks of an
   IETF meeting.

You lose five weeks, two before, one for the meeting, and two after.

>I guess the only problem I'd have with that is that for an experiment
>that'd run for one year, that takes out about 4 months (3 meetings
>and the year-end holidays) which is a lot.

Ok, make it one week then (see my previous comment).

>If we extended the experiment to 18 months duration I'd have no
>problem with something like that though. Or with leaving it as-is.

It can be left out as an implementation detail if it is easier to 
keep the experiment to 12 months.

>Can be. If a WG participant says "the decision you made on that
>draft is broken: I appeal" then they first send that to the WG
>chair.

Ok.

>I don't see any text change being suggested there. Correct me if
>I'm wrong.

You're not wrong.

Regards,
-sm 


From lars@netapp.com  Sat Jan 12 01:35:30 2013
Return-Path: <lars@netapp.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CBDFD21F8525 for <ietf@ietfa.amsl.com>; Sat, 12 Jan 2013 01:35:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.484
X-Spam-Level: 
X-Spam-Status: No, score=-10.484 tagged_above=-999 required=5 tests=[AWL=0.115, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 SNa83rXVW11f for <ietf@ietfa.amsl.com>; Sat, 12 Jan 2013 01:35:29 -0800 (PST)
Received: from mx12.netapp.com (mx12.netapp.com [216.240.18.77]) by ietfa.amsl.com (Postfix) with ESMTP id D436621F8514 for <ietf@ietf.org>; Sat, 12 Jan 2013 01:35:28 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.84,456,1355126400";  d="scan'208";a="6977996"
Received: from smtp1.corp.netapp.com ([10.57.156.124]) by mx12-out.netapp.com with ESMTP; 12 Jan 2013 01:35:28 -0800
Received: from vmwexceht03-prd.hq.netapp.com (vmwexceht03-prd.hq.netapp.com [10.106.76.241]) by smtp1.corp.netapp.com (8.13.1/8.13.1/NTAP-1.6) with ESMTP id r0C9ZR8w026617; Sat, 12 Jan 2013 01:35:27 -0800 (PST)
Received: from VMWEXCEHT06-PRD.hq.netapp.com (10.106.77.104) by vmwexceht03-prd.hq.netapp.com (10.106.76.241) with Microsoft SMTP Server (TLS) id 14.2.328.9; Sat, 12 Jan 2013 01:35:27 -0800
Received: from SACEXCMBX01-PRD.hq.netapp.com ([169.254.2.51]) by vmwexceht06-prd.hq.netapp.com ([10.106.77.104]) with mapi id 14.02.0328.009; Sat, 12 Jan 2013 01:35:27 -0800
From: "Eggert, Lars" <lars@netapp.com>
To: Stephan Wenger <stewe@stewe.org>
Subject: Re: Last Call: <draft-farrell-ft-03.txt> (A Fast-Track way to RFC with Running Code) to Experimental RFC
Thread-Topic: Last Call: <draft-farrell-ft-03.txt> (A Fast-Track way to RFC with Running Code) to Experimental RFC
Thread-Index: Ac3wFdOP9tSRE1tiRE+NhIh/RtqHrgAbCXiAABpO4QA=
Date: Sat, 12 Jan 2013 09:35:26 +0000
Message-ID: <D4D47BCFFE5A004F95D707546AC0D7E91F616BED@SACEXCMBX01-PRD.hq.netapp.com>
References: <FDBFA77C7400C74F87BC297393B53E3532B13559@BY2PRD0710MB354.namprd07.prod.outlook.com>
In-Reply-To: <FDBFA77C7400C74F87BC297393B53E3532B13559@BY2PRD0710MB354.namprd07.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.104.60.118]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <6D77DF8F5CA0CB4AB64F5A3FB2ECF61C@tahoe.netapp.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "adrian@olddog.co.uk" <adrian@olddog.co.uk>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 12 Jan 2013 09:35:30 -0000

Full agreement with Stephan.

Lars

On Jan 11, 2013, at 22:02, Stephan Wenger <stewe@stewe.org> wrote:

> Hi,
>=20
> Sorry for replying to this "advise to secretariat" thread and not to the
> ietf-announce thread--I'm not subscribed to ietf-announce.
> I have three comments, and regret that I have not followed all of the
> discussions regarding this draft before, so please advise if those
> comments have already been raised and/or resolved.
>=20
>=20
> First, I'm glad that the direct preferences of open source implementation=
s
> over implementations compliant with other business models are mostly gone=
.
> Still, there is one reference that worries me, and that is the reference
> to GPLv3 code as an "extreme" in section 2.1.  Yes, the GPL (and similar
> copyleft licenses) is an extreme, at least in terms of open source
> licensing models.  However, it is not an extreme of openness or
> accessibility of the source code for review by WG chair, AD, and
> community.  I would hope that we are all aware that many (most?)
> commercial software developers, by company policy or common sense, avoid
> looking at GPL-ed code, out of fear of contamination of their own closed
> source code.  GPL-ed code  is, therefore, inaccessible for verification b=
y
> a large part of the IETF community, and does not serve as a good example
> for "openness", which is how I interpret the spectrum laid out in section
> 2.1.  A better example would be source code that is almost universally
> accessible.  The extreme here would be source code in the public domain.
> Somewhat less convincing but perhaps a bit more realistically, source cod=
e
> under a BSD-style license like the one the IETF Trust is using.
>=20
> Second, the draft suggest that the existence of an implementation of the
> specification should serve as a shortcut towards RFC, presumably because
> such an implementation speak favorably to the implementability of the
> specification.  That, however, is not universally true.  Specifically, if
> implementer and spec writer are the same person (or part of the same
> team), it is quite likely that the spec takes certain assumptions made by
> the implementers for granted, and does not document it.  That would be a
> bad spec, accessible implementation or not.  The solution to this issue i=
s
> IMO not, as the draft appears to be to suggest, to put burden on WG chair=
s
> and ADs to ensure that the spec and the implementation match.  Both WG
> chairs and ADs have enough to do, and the incentive for rubber-stamping i=
s
> quite high.  A more sensible solution may be to require that the
> implementer is unaffiliated with the spec author; in other words, the
> implementation is derived from the spec + IETF discussion context.
>=20
> A third comment would be that, if you interpret the draft strictly, it is
> highly unlikely that the experiment would ever be exercised, as the
> implementation needs to "match" the draft to be advanced, and that would
> mean that the implementation has to follow in lockstep with the draft
> development up until the final version.  With respect to the core subject
> matter of a draft, that may be fine.  However, many of the final edits in
> a draft come as input from IETF wide community review; things like
> security, congestion control, and the like.  Those are often trivial to
> write down, but can have a major implementation impact.  To cure this, it
> would IMO be acceptable if the implementation would be required to match
> the latest or a reasonably young, i.e. a few months old version of the
> draft.
>=20
> Please consider this.
> Thanks,
> Stephan
>=20
>=20
> On 1.11.2013 08:21 , "Adrian Farrel" <adrian@olddog.co.uk> wrote:
>=20
>> Hi Alexa,
>>=20
>> Please be aware of this document that has just entered a four-week IETF
>> last
>> call. The document describes a proposed IETF process experiment under th=
e
>> rules
>> of RFC 3933.
>>=20
>> The proposed experiment calls on the IETF Secretariat to take specific
>> actions
>> under certain circumstances in corner cases of the experiment. Could you
>> please
>> have someone in the Secretariat look at the draft and comment on the
>> practicalities of the actions. Note that, at this stage, no changes to
>> the tools
>> are proposed so any actions would require manual intervention (if the
>> experiment
>> were successful and resulted in permanent changes to IETF process we
>> might make
>> changes to the tools at some future time).
>>=20
>> Thanks,
>> Adrian
>>=20
>>> -----Original Message-----
>>> From: ietf-announce-bounces@ietf.org [mailto:ietf-announce-
>>> bounces@ietf.org] On Behalf Of The IESG
>>> Sent: 11 January 2013 15:15
>>> To: IETF-Announce
>>> Subject: Last Call: <draft-farrell-ft-03.txt> (A Fast-Track way to RFC
>>> with
>> Running
>>> Code) to Experimental RFC
>>>=20
>>>=20
>>> The IESG has received a request from an individual submitter to conside=
r
>>> the following document:
>>> - 'A Fast-Track way to RFC with Running Code'
>>>  <draft-farrell-ft-03.txt> as Experimental RFC
>>>=20
>>> The IESG plans to make a decision in the next few weeks, and solicits
>>> final comments on this action. Please send substantive comments to the
>>> ietf@ietf.org mailing lists by 2013-02-08. Exceptionally, comments may
>>> be
>>> sent to iesg@ietf.org instead. In either case, please retain the
>>> beginning of the Subject line to allow automated sorting.
>>>=20
>>> Abstract
>>>=20
>>>   This memo describes an optional, fast-track way to progress a working
>>>   group document to IESG review.  It is provided as a process
>>>   experiment as defined in RFC 3933 for use when working group chairs
>>>   believe that there is running code that implements a working group
>>>   Internet-Draft.  The motivation is to have the IETF process
>>>   explicitly consider running code, consistent with the IETF's overall
>>>   philosophy of running code and rough consensus.
>>>=20
>>>   In this process all of working group last call, IETF last call, and
>>>   Area Director review are carried out in the same two week period.
>>>   Only comments that meet IESG Discuss criteria need to be addressed
>>>   during this stage, and authors are required to make any changes
>>>   within two weeks.
>>>=20
>>>   This experiment will run for one year.
>>>=20
>>>=20
>>> The file can be obtained via
>>> http://datatracker.ietf.org/doc/draft-farrell-ft/
>>>=20
>>> IESG discussion can be tracked via
>>> http://datatracker.ietf.org/doc/draft-farrell-ft/ballot/
>>>=20
>>> No IPR declarations have been submitted directly on this I-D.
>>=20
>>=20
>=20
>=20


From brian.e.carpenter@gmail.com  Sat Jan 12 01:35:51 2013
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E1C9121F85D9 for <ietf@ietfa.amsl.com>; Sat, 12 Jan 2013 01:35:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.691
X-Spam-Level: 
X-Spam-Status: No, score=-101.691 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_ILLEGAL_IP=1.908, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
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 u09ZF5krsN9g for <ietf@ietfa.amsl.com>; Sat, 12 Jan 2013 01:35:51 -0800 (PST)
Received: from mail-wg0-f46.google.com (mail-wg0-f46.google.com [74.125.82.46]) by ietfa.amsl.com (Postfix) with ESMTP id 10BE421F85D2 for <ietf@ietf.org>; Sat, 12 Jan 2013 01:35:50 -0800 (PST)
Received: by mail-wg0-f46.google.com with SMTP id dr13so1179078wgb.13 for <ietf@ietf.org>; Sat, 12 Jan 2013 01:35:50 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:organization:user-agent :mime-version:to:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=bXWFC1SUn/N7T5ws8MYYPEbUNasX58YU4KbT28GywL0=; b=OGbfXWCnSk0rZPRuDN8jXpTEURnR4UMyrGZ4VN280SX2HcTzk/D/Ta32IMqmA21oKu 2llUZoXaa0xJEe8Qmie/qlNsMl27azaSIhoTIfWveZ4f/KX2OHdaWGeqA09hTGgKBzwN A9JNblHud7qoy37kQmvoQ2S9QoEfHemzVFruWTa7JYHpTEck+ir4sBbXNH9jgmMgp7Ar pG7o4KGCKIzN2YXDbbxaLxa2M9g9LE10awnPe+9T67RTZXMk2GXXymdSUmEjYVN50dKq L2I0EXU7I+wdubsP1okBIlM00aua7pev+W5tZ+GdHkQdiLwj71j7GZ6tszDlmLvi9K4i oXVw==
X-Received: by 10.180.72.146 with SMTP id d18mr3030970wiv.33.1357983350003; Sat, 12 Jan 2013 01:35:50 -0800 (PST)
Received: from [192.168.1.65] (host-2-101-188-89.as13285.net. [2.101.188.89]) by mx.google.com with ESMTPS id bd7sm2984172wib.8.2013.01.12.01.35.48 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sat, 12 Jan 2013 01:35:48 -0800 (PST)
Message-ID: <50F12E80.8080007@gmail.com>
Date: Sat, 12 Jan 2013 09:36:00 +0000
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: IETF discussion list <ietf@ietf.org>
Subject: Re: I-D Action: draft-moonesamy-rfc2050-historic-00.txt
References: <20130112085109.7357.35960.idtracker@ietfa.amsl.com>
In-Reply-To: <20130112085109.7357.35960.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 12 Jan 2013 09:35:52 -0000

I object to making RFC 2050 historic without retaining at least the
content of its Section 1 as an IETF BCP.

While the IETF did formally hand over details of address
allocation policy to IANA, we did so knowing that the RIRs
themselves, and IANA, considered themselves bound by RFC 2050
(see the list of authors of that document).

An update of RFC 2050, within the scope set by the IETF-IANA
MoU, would be reasonable. Abrogation is not reasonable.

Regards
   Brian Carpenter (speaking only for myself)

On 12/01/2013 08:51, internet-drafts@ietf.org wrote:
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
> 
> 
> 	Title           : Reclassifying Internet Registry Allocation Guidelines to Historic
> 	Author(s)       : S. Moonesamy
> 	Filename        : draft-moonesamy-rfc2050-historic-00.txt
> 	Pages           : 4
> 	Date            : 2013-01-12
> 
> Abstract:
> RFC 2050 describes the registry system for the distribution of globally
> unique Internet address space and registry operations.  It also
> discusses about policy issues which are outside the scope of the IETF.
> This document reclassifies RFC 2050 as Historic.  It also reclassifies
> RFC 1366 and RFC 1466 as Historic.
> 
> 
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-moonesamy-rfc2050-historic
> 
> There's also a htmlized version available at:
> http://tools.ietf.org/html/draft-moonesamy-rfc2050-historic-00
> 
> 
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
> 
> _______________________________________________
> I-D-Announce mailing list
> I-D-Announce@ietf.org
> https://www.ietf.org/mailman/listinfo/i-d-announce
> Internet-Draft directories: http://www.ietf.org/shadow.html
> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
> 

From abdussalambaryun@gmail.com  Sat Jan 12 03:44:49 2013
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 58F6621F850C for <ietf@ietfa.amsl.com>; Sat, 12 Jan 2013 03:44:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.577
X-Spam-Level: 
X-Spam-Status: No, score=-3.577 tagged_above=-999 required=5 tests=[AWL=0.022,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 RWeKHXdhcqKI for <ietf@ietfa.amsl.com>; Sat, 12 Jan 2013 03:44:48 -0800 (PST)
Received: from mail-vc0-f174.google.com (mail-vc0-f174.google.com [209.85.220.174]) by ietfa.amsl.com (Postfix) with ESMTP id B540D21F84CA for <ietf@ietf.org>; Sat, 12 Jan 2013 03:44:48 -0800 (PST)
Received: by mail-vc0-f174.google.com with SMTP id d16so2203836vcd.19 for <ietf@ietf.org>; Sat, 12 Jan 2013 03:44:48 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:cc:content-type; bh=/C7B9OSG1pcBejAvMHAXUW6a9etJi4hWnc2+tIWz5wc=; b=mnIoMakzQDb8Wyq34BAayrW9Az1h0V2LV15022M0Lw5hujDg0Fph/lnrWhkJdY565S NsUtPAVpZjMkO5KE5kMkUZD0Av8UeD5p7lwmxPgGWkFhPfGb9x80IbNw/+7rSH0zisuE q1QQR8E1HWNSbNAGSOdpJEnhmwNsTfvNVGhFCPZh6zVvflPa4ZlGEjxvGLrNDei1ojSX tr+q9WT9qUJmawLXsvEhRCrnKC45Hda7ETm7BEtVy9jWJNTkRUwckx2Pwu4afZ3SNT8Z lI//KBW2eSJfrTXI9IDGnx+cZVZvzH6SZPo4N/uCpzbDkd1XTgW7RT2RQfPyoMe3Xfeg m4vw==
MIME-Version: 1.0
Received: by 10.52.27.50 with SMTP id q18mr85245899vdg.20.1357991088110; Sat, 12 Jan 2013 03:44:48 -0800 (PST)
Received: by 10.220.145.5 with HTTP; Sat, 12 Jan 2013 03:44:47 -0800 (PST)
Date: Sat, 12 Jan 2013 12:44:47 +0100
Message-ID: <CADnDZ88jBeZQkzpxRt5Ru34VCwdoLG0+er=U95YgEUsA4Kx5Hg@mail.gmail.com>
Subject: Re: I-D Action: draft-moonesamy-rfc2050-historic-00.txt
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: sm+ietf@elandsys.com
Content-Type: text/plain; charset=ISO-8859-1
Cc: ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 12 Jan 2013 11:44:49 -0000

Hi Moonesamy,

I also think similar with Carpenter, why reclassify to historic.
rfc2050 is still valid, and why limiting the ietf?

AB

From abdussalambaryun@gmail.com  Sat Jan 12 03:50:14 2013
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1719621F85D0 for <ietf@ietfa.amsl.com>; Sat, 12 Jan 2013 03:50:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.578
X-Spam-Level: 
X-Spam-Status: No, score=-3.578 tagged_above=-999 required=5 tests=[AWL=0.021,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 uGQNuayMI0xb for <ietf@ietfa.amsl.com>; Sat, 12 Jan 2013 03:50:13 -0800 (PST)
Received: from mail-vb0-f42.google.com (mail-vb0-f42.google.com [209.85.212.42]) by ietfa.amsl.com (Postfix) with ESMTP id 472A121F85CB for <ietf@ietf.org>; Sat, 12 Jan 2013 03:50:13 -0800 (PST)
Received: by mail-vb0-f42.google.com with SMTP id fa15so2251593vbb.15 for <ietf@ietf.org>; Sat, 12 Jan 2013 03:50:12 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:cc:content-type; bh=h3a2xyd/nm68ALhHCFjDsT0DkSfB7rUNHRsBRoWKqn4=; b=qfC7QnmCvEUpP72hIEoVHeeoX0tZRG3Q2e8ircWsXHjqZIwKHPgvumkJmKFHZgXrU4 Z+T31RPYkKp9YzoQHowfMFBSMj1kum/hzWjNmZcPjn1lEGkbt4hX/Zn1PiTRJNYw9y/4 2vmFRbczGD8nNUdICcvfNRxvqyzG3XzKUTTTzwz9Px16tUNoZOi0hRek/v7g+09D4qW2 CWdRQoSvdqgT83bt96jU1gVtVzon68612b/QQR7qOwQqwVxwmSlHQ6ivutcfcznfE+Ys hXHiRsnOWXrbiNX9qTDbxNzymqJibhzqrS/G0DBtHVaCVqgDWwLuVfbRvfgMZ//fdFSF tG7w==
MIME-Version: 1.0
Received: by 10.58.243.166 with SMTP id wz6mr99895734vec.28.1357991412629; Sat, 12 Jan 2013 03:50:12 -0800 (PST)
Received: by 10.220.145.5 with HTTP; Sat, 12 Jan 2013 03:50:12 -0800 (PST)
Date: Sat, 12 Jan 2013 12:50:12 +0100
Message-ID: <CADnDZ8-Hw+FC1OYqLOQEeHnZ-LdMw2=1moucNBxfdrSHXo=Heg@mail.gmail.com>
Subject: draft-moonesamy-mail-list-protocol-00
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: sm+ietf@elandsys.com
Content-Type: text/plain; charset=ISO-8859-1
Cc: ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 12 Jan 2013 11:50:14 -0000

Hi Moonesamy,

I like the draft, and suggest that you add that the WG chair SHOULD
contribute to the WG list. Also that any question in the list SHOULD
be answered by the responsible (e.g. author of the ID discussed).
However, I have many suggestions to make the ID valuable. Thanks for
the input :)

AB

From sm@elandsys.com  Sat Jan 12 10:24:29 2013
Return-Path: <sm@elandsys.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E641621F8713 for <ietf@ietfa.amsl.com>; Sat, 12 Jan 2013 10:24:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.495
X-Spam-Level: 
X-Spam-Status: No, score=-102.495 tagged_above=-999 required=5 tests=[AWL=0.104, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 tAz3vcwQCgk5 for <ietf@ietfa.amsl.com>; Sat, 12 Jan 2013 10:24:29 -0800 (PST)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id D398B21F8830 for <ietf@ietf.org>; Sat, 12 Jan 2013 10:24:28 -0800 (PST)
Received: from SUBMAN.elandsys.com ([197.224.141.182]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r0CIOC80029581 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 12 Jan 2013 10:24:23 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1358015065; bh=gozRoE4e8jhiQ8HMutMvOAmbhCUFj0rB4FZLjpc+95U=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=OqMaQikxFZzc+iWYqihQkGUmhBbSuKltyLllPp3IblVQD9Nesqq9DByA+CUDw33UJ RSJG3lj9bBrP+szG3M7ScOpJAKLFPd80zqCcl/Uf5eXIPY53GhscV0Yn/5t7ABKDXD +63dGGTNhJWnqpE98kw+Vr6FKoIx5CQZ6Y0RMicM=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1358015065; i=@elandsys.com; bh=gozRoE4e8jhiQ8HMutMvOAmbhCUFj0rB4FZLjpc+95U=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=q81jce6aXXGYl/3GQNg8yvaD/mveFa1zIZUR/78G0SbqntfZib47eSVMbAfPxl1px n4a1IW8LbfZGL+z8TOvCH+HfLQoK4/8HjxWz8QciEXY5bpxn6z5vYkg2dTdasr0y0S PvoP6Qa69O2ujNJCCxS9W/y8PFBN3ycslTxeJjMM=
Message-Id: <6.2.5.6.2.20130112064815.05ffc568@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Sat, 12 Jan 2013 10:18:10 -0800
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, Abdussalam Baryun <abdussalambaryun@gmail.com>
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: I-D Action: draft-moonesamy-rfc2050-historic-00.txt
In-Reply-To: <50F12E80.8080007@gmail.com>
References: <20130112085109.7357.35960.idtracker@ietfa.amsl.com> <50F12E80.8080007@gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 12 Jan 2013 18:24:30 -0000

At 01:36 12-01-2013, Brian E Carpenter wrote:
>I object to making RFC 2050 historic without retaining at least the
>content of its Section 1 as an IETF BCP.

 From Section 1 of RFC 2050:

   "Currently there are three regional IRs established;
    InterNIC serving North America, RIPE NCC serving Europe,
    and APNIC serving the Asian Pacific region."

The above information is outdated.

>While the IETF did formally hand over details of address
>allocation policy to IANA, we did so knowing that the RIRs
>themselves, and IANA, considered themselves bound by RFC 2050
>(see the list of authors of that document).

That was in 1996.  The question is whether BCP 12 reflects current practices.

>An update of RFC 2050, within the scope set by the IETF-IANA
>MoU, would be reasonable. Abrogation is not reasonable.

Noted.

At 03:44 12-01-2013, Abdussalam Baryun wrote:
>I also think similar with Carpenter, why reclassify to historic.
>rfc2050 is still valid, and why limiting the ietf?

IETF participants have not decided about policies regarding IP 
address allocation since well over 10 years.  Such matters are 
determined within other communities.  It would only be limiting to 
the IETF if it is a matter directly related to IETF protocols.

Regards,
S. Moonesamy  


From stephen.farrell@cs.tcd.ie  Sat Jan 12 10:33:26 2013
Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D5B0D21F8750 for <ietf@ietfa.amsl.com>; Sat, 12 Jan 2013 10:33:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 fycZvi5nUDBA for <ietf@ietfa.amsl.com>; Sat, 12 Jan 2013 10:33:26 -0800 (PST)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) by ietfa.amsl.com (Postfix) with ESMTP id 7F28E21F874F for <ietf@ietf.org>; Sat, 12 Jan 2013 10:33:25 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id 879FEBE3F; Sat, 12 Jan 2013 18:33:02 +0000 (GMT)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yLqIlWIl895P; Sat, 12 Jan 2013 18:33:00 +0000 (GMT)
Received: from [10.87.48.11] (unknown [86.42.19.92]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 35A76BE3C; Sat, 12 Jan 2013 18:33:00 +0000 (GMT)
Message-ID: <50F1AC5B.3070608@cs.tcd.ie>
Date: Sat, 12 Jan 2013 18:32:59 +0000
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130106 Thunderbird/17.0.2
MIME-Version: 1.0
To: Stephan Wenger <stewe@stewe.org>
Subject: Re: Last Call: <draft-farrell-ft-03.txt> (A Fast-Track way to RFC with Running Code) to Experimental RFC
References: <FDBFA77C7400C74F87BC297393B53E3532B13559@BY2PRD0710MB354.namprd07.prod.outlook.com>
In-Reply-To: <FDBFA77C7400C74F87BC297393B53E3532B13559@BY2PRD0710MB354.namprd07.prod.outlook.com>
X-Enigmail-Version: 1.5
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: "adrian@olddog.co.uk" <adrian@olddog.co.uk>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 12 Jan 2013 18:33:26 -0000

Hiya,

On 01/11/2013 09:02 PM, Stephan Wenger wrote:
> Hi,
> 
> Sorry for replying to this "advise to secretariat" thread and not to the
> ietf-announce thread--I'm not subscribed to ietf-announce.
> I have three comments, and regret that I have not followed all of the
> discussions regarding this draft before, so please advise if those
> comments have already been raised and/or resolved.
> 
> 
> First, I'm glad that the direct preferences of open source implementations
> over implementations compliant with other business models are mostly gone.

FWIW, I'm not at all glad about that personally but the text we have
probably does represent a consensus. Note, there are others like me
who'd prefer to favour open-source here, as well as some, presumably
including you, that would prefer something like the opposite.

>  Still, there is one reference that worries me, and that is the reference
> to GPLv3 code as an "extreme" in section 2.1.  Yes, the GPL (and similar
> copyleft licenses) is an extreme, at least in terms of open source
> licensing models.  However, it is not an extreme of openness or
> accessibility of the source code for review by WG chair, AD, and
> community.  I would hope that we are all aware that many (most?)
> commercial software developers, by company policy or common sense, avoid
> looking at GPL-ed code, out of fear of contamination of their own closed
> source code.  

<rant>

I am aware that lawyers and others do encourage ignorance in such
ways. Its an incredibly stupid way to behave IMO even if understandable
in a horrendously short-sighted kind of way.

Thankfully I don't work in a place that has to deal with such
anti-scientific idiocy. (Being a university we have our own
idiocies:-) And there are even many commercial companies that
have yet to adopt such silliness. So there's hope for us all
yet.

</rant>

> GPL-ed code  is, therefore, inaccessible for verification by
> a large part of the IETF community, and does not serve as a good example
> for "openness", which is how I interpret the spectrum laid out in section
> 2.1.  A better example would be source code that is almost universally
> accessible.  The extreme here would be source code in the public domain.
> Somewhat less convincing but perhaps a bit more realistically, source code
> under a BSD-style license like the one the IETF Trust is using.

I'm not at all sure what concrete suggestion you're making, other
than disparaging GPL. If your suggestion is s/GPLv3/BSD license/
then that could be done but would make no difference at all to
this draft, so I plan to leave this as-is.

> Second, the draft suggest that the existence of an implementation of the
> specification should serve as a shortcut towards RFC, presumably because
> such an implementation speak favorably to the implementability of the
> specification.  That, however, is not universally true.  

Very few things in the IETF are universally true;-)

> Specifically, if
> implementer and spec writer are the same person (or part of the same
> team), it is quite likely that the spec takes certain assumptions made by
> the implementers for granted, and does not document it.  That would be a
> bad spec, accessible implementation or not.  The solution to this issue is
> IMO not, as the draft appears to be to suggest, to put burden on WG chairs
> and ADs to ensure that the spec and the implementation match.  Both WG
> chairs and ADs have enough to do, and the incentive for rubber-stamping is
> quite high.  A more sensible solution may be to require that the
> implementer is unaffiliated with the spec author; in other words, the
> implementation is derived from the spec + IETF discussion context.

That's a fair point but, a) we don't consider affiliations like that
in the IETF, at least not in a written-rules kind of way, and b) there's
nothing in principle wrong with the editor writing code. While it
is better if the code is written independent of the editor and even
better if someone who hasn't been involved in the WG has done the
coding, that'd be too high a burden to require IMO, especially given
that this is an experiment.

I'd have no problem adding text that encouraged some form of
independence though, if you'd like to provide some.

> A third comment would be that, if you interpret the draft strictly, it is
> highly unlikely that the experiment would ever be exercised, as the
> implementation needs to "match" the draft to be advanced, and that would
> mean that the implementation has to follow in lockstep with the draft
> development up until the final version.  With respect to the core subject
> matter of a draft, that may be fine.  However, many of the final edits in
> a draft come as input from IETF wide community review; things like
> security, congestion control, and the like.  Those are often trivial to
> write down, but can have a major implementation impact.  To cure this, it
> would IMO be acceptable if the implementation would be required to match
> the latest or a reasonably young, i.e. a few months old version of the
> draft.

Another fair point but again one where its not really possible to
describe a rule that'd be better and more precise than "match."
I don't think a rule mentioning earlier or older drafts would be
useful for this.

I'll see if I can come up with something better than "match" but
if you have text to suggest, that might help.

Cheers,
S.

> 
> Please consider this.
> Thanks,
> Stephan
>   
> 
> On 1.11.2013 08:21 , "Adrian Farrel" <adrian@olddog.co.uk> wrote:
> 
>> Hi Alexa,
>>
>> Please be aware of this document that has just entered a four-week IETF
>> last
>> call. The document describes a proposed IETF process experiment under the
>> rules
>> of RFC 3933.
>>
>> The proposed experiment calls on the IETF Secretariat to take specific
>> actions
>> under certain circumstances in corner cases of the experiment. Could you
>> please
>> have someone in the Secretariat look at the draft and comment on the
>> practicalities of the actions. Note that, at this stage, no changes to
>> the tools
>> are proposed so any actions would require manual intervention (if the
>> experiment
>> were successful and resulted in permanent changes to IETF process we
>> might make
>> changes to the tools at some future time).
>>
>> Thanks,
>> Adrian
>>
>>> -----Original Message-----
>>> From: ietf-announce-bounces@ietf.org [mailto:ietf-announce-
>>> bounces@ietf.org] On Behalf Of The IESG
>>> Sent: 11 January 2013 15:15
>>> To: IETF-Announce
>>> Subject: Last Call: <draft-farrell-ft-03.txt> (A Fast-Track way to RFC
>>> with
>> Running
>>> Code) to Experimental RFC
>>>
>>>
>>> The IESG has received a request from an individual submitter to consider
>>> the following document:
>>> - 'A Fast-Track way to RFC with Running Code'
>>>   <draft-farrell-ft-03.txt> as Experimental RFC
>>>
>>> The IESG plans to make a decision in the next few weeks, and solicits
>>> final comments on this action. Please send substantive comments to the
>>> ietf@ietf.org mailing lists by 2013-02-08. Exceptionally, comments may
>>> be
>>> sent to iesg@ietf.org instead. In either case, please retain the
>>> beginning of the Subject line to allow automated sorting.
>>>
>>> Abstract
>>>
>>>    This memo describes an optional, fast-track way to progress a working
>>>    group document to IESG review.  It is provided as a process
>>>    experiment as defined in RFC 3933 for use when working group chairs
>>>    believe that there is running code that implements a working group
>>>    Internet-Draft.  The motivation is to have the IETF process
>>>    explicitly consider running code, consistent with the IETF's overall
>>>    philosophy of running code and rough consensus.
>>>
>>>    In this process all of working group last call, IETF last call, and
>>>    Area Director review are carried out in the same two week period.
>>>    Only comments that meet IESG Discuss criteria need to be addressed
>>>    during this stage, and authors are required to make any changes
>>>    within two weeks.
>>>
>>>    This experiment will run for one year.
>>>
>>>
>>> The file can be obtained via
>>> http://datatracker.ietf.org/doc/draft-farrell-ft/
>>>
>>> IESG discussion can be tracked via
>>> http://datatracker.ietf.org/doc/draft-farrell-ft/ballot/
>>>
>>> No IPR declarations have been submitted directly on this I-D.
>>
>>
> 
> 
> 

From drc@virtualized.org  Sat Jan 12 11:36:44 2013
Return-Path: <drc@virtualized.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4FDDA21F87BA for <ietf@ietfa.amsl.com>; Sat, 12 Jan 2013 11:36:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 qzkCxC1c3dl1 for <ietf@ietfa.amsl.com>; Sat, 12 Jan 2013 11:36:43 -0800 (PST)
Received: from trantor.virtualized.org (trantor.virtualized.org [199.48.134.42]) by ietfa.amsl.com (Postfix) with ESMTP id 6ED0821F87A9 for <ietf@ietf.org>; Sat, 12 Jan 2013 11:36:43 -0800 (PST)
Received: from [10.0.1.13] (c-24-4-109-25.hsd1.ca.comcast.net [24.4.109.25]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: drc) by trantor.virtualized.org (Postfix) with ESMTPSA id D8E80170A7; Sat, 12 Jan 2013 19:36:41 +0000 (UTC)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Subject: Re: I-D Action: draft-moonesamy-rfc2050-historic-00.txt
From: David Conrad <drc@virtualized.org>
In-Reply-To: <50F12E80.8080007@gmail.com>
Date: Sat, 12 Jan 2013 11:36:40 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <6D2D2975-A47A-4A0B-A11F-D7C73FE22EDD@virtualized.org>
References: <20130112085109.7357.35960.idtracker@ietfa.amsl.com> <50F12E80.8080007@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-Mailer: Apple Mail (2.1499)
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 12 Jan 2013 19:36:44 -0000

Brian,

On Jan 12, 2013, at 1:36 AM, Brian E Carpenter =
<brian.e.carpenter@gmail.com> wrote:
> I object to making RFC 2050 historic without retaining at least the
> content of its Section 1 as an IETF BCP.

Which part of section 1 do you think has any relevance to the IETF as a =
BCP?

> While the IETF did formally hand over details of address
> allocation policy to IANA, we did so knowing that the RIRs
> themselves, and IANA, considered themselves bound by RFC 2050
> (see the list of authors of that document).

As one of those authors, I will state that I believe that RFC 2050 =
should be moved to historic (actually should have been moved quite some =
time ago).

- RFC 2050 was an attempt to document the _then current_ policies and =
processes of the RIRs. An RFC was chosen because there was no other =
viable publication mechanism that would reach the relevant communities. =
The Internet has changed a bit since 1996.  RFC 2050 documents the "Best =
Current Practice" of the then Internet registries for a very brief =
window -- RIR policies had already changed from what was documented in =
RFC 2050 by the time it had gotten through the IESG gauntlet.

- RFC 2050 explicitly discusses allocation policy of IPv4. IPv4 =
allocation is largely over. The vast majority of RFC 2050 is not =
particularly relevant to IPv6. Address allocation policies are and have =
been defined within the address consuming communities which have =
(reasonably) robust, open, and transparent mechanisms by which anyone =
can contribute. The IPv6 allocation framework has been defined in other =
RFCs.

- RFC 2050 discusses allocating IPv4 addresses to RIRs, ISPs, and end =
users for operational purposes and is unrelated to meeting the technical =
protocol standardization needs of the IETF.

> An update of RFC 2050, within the scope set by the IETF-IANA
> MoU, would be reasonable.

No, since addressing is _explicitly_ declared out of scope of that MoU, =
see section 4.3 of RFC 2860:

  "Two particular assigned spaces present policy issues in addition
   to the technical considerations specified by the IETF: the assignment
   of domain names, and the assignment of IP address blocks. These
   policy issues are outside the scope of this MOU."

I don't think it is particularly useful or helpful to try to assert that =
the IETF did "formally hand over" address allocation to IANA since, as =
you know, there are lots of folks who have, do, and will claim address =
allocation, as an operational matter, was never the IETF's to "hand =
over". What might be useful/helpful is to try to identify the portions =
of RFC 2050 that have any relevance to the IETF and verify that those =
portions are covered elsewhere.

Regards,
-drc


From stephen.farrell@cs.tcd.ie  Sat Jan 12 11:44:51 2013
Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9EDB321F871D for <ietf@ietfa.amsl.com>; Sat, 12 Jan 2013 11:44:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 gcK3uXV51Mw1 for <ietf@ietfa.amsl.com>; Sat, 12 Jan 2013 11:44:50 -0800 (PST)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) by ietfa.amsl.com (Postfix) with ESMTP id 4592121F8707 for <ietf@ietf.org>; Sat, 12 Jan 2013 11:44:49 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id D52CBBE3C; Sat, 12 Jan 2013 19:44:27 +0000 (GMT)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2jMlPgr6jAPc; Sat, 12 Jan 2013 19:44:26 +0000 (GMT)
Received: from [10.87.48.11] (unknown [86.42.19.92]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id A0DB2BE3B; Sat, 12 Jan 2013 19:44:26 +0000 (GMT)
Message-ID: <50F1BD1A.7050705@cs.tcd.ie>
Date: Sat, 12 Jan 2013 19:44:26 +0000
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130106 Thunderbird/17.0.2
MIME-Version: 1.0
To: SM <sm@resistor.net>
Subject: Re: Last Call: <draft-farrell-ft-03.txt> (A Fast-Track way to RFC with Running Code) to Experimental RFC
References: <20130111151453.22161.50884.idtracker@ietfa.amsl.com> <6.2.5.6.2.20130111094647.095f60e0@resistor.net> <50F077CC.7050206@cs.tcd.ie> <6.2.5.6.2.20130111125127.0a5828f8@resistor.net>
In-Reply-To: <6.2.5.6.2.20130111125127.0a5828f8@resistor.net>
X-Enigmail-Version: 1.5
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 12 Jan 2013 19:44:51 -0000

Hiya,

So I think the actions arising are:

- consider whether to have a "not before IETF meetings" restriction
  and make this an 18 month experiment
- maybe remove the text about -bis RFCs. (I slightly prefer it as-is
  fwiw, but let's see if we get more input)

Let me know if that's wrong.

Cheers,
S.

On 01/11/2013 09:34 PM, SM wrote:
> Hi Stephen,
> At 12:36 11-01-2013, Stephen Farrell wrote:
>> You mean rough consensus of the IETF I guess? Good question.
> 
> No, I mean consensus as that's also part what is gauged during a Last Call.
> 
>> First, WG rough consensus is formally unaffected. As is IESG
>> review. And if IETF LC comments are received that do meet the
>> IESG discuss criteria then those should be handled as now.
> 
> I am not concerned about the WG rough consensus angle (for the
> experiment) as it is a subset of a Last Call.
> 
>> So I guess we're left with cases where there's a lack of
>> rough consensus during IETF LC but where the meat of the
>> disagreement is something that doesn't qualify for an IESG
>> discuss ballot.
> 
> Hmm, you mentioned "rough consensus" on an IETF Last Call.  The IETF
> Last Call is about "consensus".  I may have misunderstood the experiment
> as I did not read it as "rough consensus and running code".  To say it
> differently, there isn't any change to the IETF Last Call; this is more
> about fast-tracking the WGLC and the IETF Last Call.
> 
>> I'd say that'd be quite likely to allow the responsible AD
>> to say that there had been so much debate during IETF LC that
>> this experiment ought not be used.
> 
> Ok.
> 
>> So, I don't think this experiment has any major effect
>> there really but maybe has a subtle one.
>>
>> I'll be interested in seeing if this happens if we do the
>> experiment.
> 
> Let's see how the experiment works out.
> 
>> I don't get what you mean. Can you explain? (I get that you don't want
>> to mention -bis cases, but I don't get why.)
> 
> What the experiment can do is make it easier to move from unpublished
> specification to RFC.  The "-bis" draft is from a previous RFC.  If you
> try to cover it the experiment can turn into a significant process
> change.  I prefer to leave that unspecified and see how the experiment
> works out instead of telling people to use it for "-bis" drafts.  In a
> "-bis" document is in good shape it should not be a significant problem
> to get it through the process.
> 
>> Not a bad idea. Something like "fast-track must be started at least
>> one month (longer?) before an IETF meeting starts" ?
> 
>   The fast-track process cannot be initiated within two weeks of an
>   IETF meeting.
> 
> You lose five weeks, two before, one for the meeting, and two after.
> 
>> I guess the only problem I'd have with that is that for an experiment
>> that'd run for one year, that takes out about 4 months (3 meetings
>> and the year-end holidays) which is a lot.
> 
> Ok, make it one week then (see my previous comment).
> 
>> If we extended the experiment to 18 months duration I'd have no
>> problem with something like that though. Or with leaving it as-is.
> 
> It can be left out as an implementation detail if it is easier to keep
> the experiment to 12 months.
> 
>> Can be. If a WG participant says "the decision you made on that
>> draft is broken: I appeal" then they first send that to the WG
>> chair.
> 
> Ok.
> 
>> I don't see any text change being suggested there. Correct me if
>> I'm wrong.
> 
> You're not wrong.
> 
> Regards,
> -sm
> 

From john-ietf@jck.com  Sat Jan 12 14:21:41 2013
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F059421F8917 for <ietf@ietfa.amsl.com>; Sat, 12 Jan 2013 14:21:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.134
X-Spam-Level: 
X-Spam-Status: No, score=-102.134 tagged_above=-999 required=5 tests=[AWL=0.465, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 YGgJk1Q3Yu+L for <ietf@ietfa.amsl.com>; Sat, 12 Jan 2013 14:21:40 -0800 (PST)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 4F7B121F8911 for <ietf@ietf.org>; Sat, 12 Jan 2013 14:21:40 -0800 (PST)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1Tu9SH-000AWy-HF; Sat, 12 Jan 2013 17:21:33 -0500
Date: Sat, 12 Jan 2013 17:21:28 -0500
From: John C Klensin <john-ietf@jck.com>
To: David Conrad <drc@virtualized.org>, Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: I-D Action: draft-moonesamy-rfc2050-historic-00.txt
Message-ID: <03E877D7862B38284128680C@JcK-HP8200.jck.com>
In-Reply-To: <6D2D2975-A47A-4A0B-A11F-D7C73FE22EDD@virtualized.org>
References: <20130112085109.7357.35960.idtracker@ietfa.amsl.com> <50F12E80.8080007@gmail.com> <6D2D2975-A47A-4A0B-A11F-D7C73FE22EDD@virtualized.org>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Cc: IETF discussion list <ietf@ietf.org>, Subramanian Moonesamy <sm+ietf@elandsys.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 12 Jan 2013 22:21:41 -0000

--On Saturday, January 12, 2013 11:36 -0800 David Conrad
<drc@virtualized.org> wrote:

>...
> No, since addressing is _explicitly_ declared out of scope of
> that MoU, see section 4.3 of RFC 2860:
> 
>   "Two particular assigned spaces present policy issues in
> addition    to the technical considerations specified by the
> IETF: the assignment    of domain names, and the assignment of
> IP address blocks. These    policy issues are outside the
> scope of this MOU."
> 
> I don't think it is particularly useful or helpful to try to
> assert that the IETF did "formally hand over" address
> allocation to IANA since, as you know, there are lots of folks
> who have, do, and will claim address allocation, as an
> operational matter, was never the IETF's to "hand over". What
> might be useful/helpful is to try to identify the portions of
> RFC 2050 that have any relevance to the IETF and verify that
> those portions are covered elsewhere.

David (and Brian and Subramanian), 

There are cans of poisonous, vicious vipers (only superficially
resembling cans of worms) that are, IMO, best not opened and
this is, IMO, one of them.  The reasons for that are probably as
obvious to you as they are to me and I certainly agree with most
of your last paragraph above.  However, I don't think the
section of 2860 that you cite helps very much because there is
another way to read it.  That alternate reading, which I believe
is actually the correct one, says that the addressing issues
(and the domain ones) consist of two parts "technical
considerations" which are specified by the IETF and "policy
issues" that are someone else's problem.  Indeed, it says
"policy issues in addition to...", which I think recognizes that
those "technical considerations" may have policy implications
and that it is within scope for the IETF to specify those too.
The exclusion is for policy issues that are _not_ part of the
technical considerations.

With the understanding that the boundary that posits is very
fuzzy, I don't think that basic principle has changed
significantly since the MOU and probably not much since RFC
2050.  The IETF still has responsibility for the technical
specification of addresses and the policies that narrowly
implies; other policy issues, including the models for
allocations of addresses to those who will use them, belong to
others.  

I think it unwise try to define the boundary more precisely than
that.  You may recall that an attempt was made to do so more or
less unilaterally at the time the NRO was formed; in my opinion,
that didn't work out especially well for the Internet (YMMD).
If Jon were participating in this conversation today, I'm quite
sure that he would be saying that it is much more important for
the RIRs and the IETF to work together to get the best result
for the Internet rather than putting energy into trying to
legislate or enforce a boundary (whether that effort started in
the IETF or in the RIRs).

best,
   john


From bernard_aboba@hotmail.com  Sat Jan 12 14:47:53 2013
Return-Path: <bernard_aboba@hotmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1E27021F8896; Sat, 12 Jan 2013 14:47:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.52
X-Spam-Level: 
X-Spam-Status: No, score=-102.52 tagged_above=-999 required=5 tests=[AWL=0.078, BAYES_00=-2.599, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100]
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 YOa8yYS7HKDh; Sat, 12 Jan 2013 14:47:52 -0800 (PST)
Received: from blu0-omc2-s8.blu0.hotmail.com (blu0-omc2-s8.blu0.hotmail.com [65.55.111.83]) by ietfa.amsl.com (Postfix) with ESMTP id ED8DD21F8868; Sat, 12 Jan 2013 14:47:51 -0800 (PST)
Received: from BLU002-W223 ([65.55.111.71]) by blu0-omc2-s8.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675);  Sat, 12 Jan 2013 14:47:51 -0800
X-EIP: [upC+gVIszH2n8zYAXJtHlskmiHwedsA3]
X-Originating-Email: [bernard_aboba@hotmail.com]
Message-ID: <BLU002-W2232C02D24F3D45F2E76B0A93280@phx.gbl>
Content-Type: multipart/alternative; boundary="_3e7ca20b-1d2a-475b-90d6-3e578f3fe97f_"
From: Bernard Aboba <bernard_aboba@hotmail.com>
To: "sm@resistor.net" <sm@resistor.net>
Subject: RE: Last Call: <draft-farrell-ft-03.txt> (A Fast-Track way to RFC with Running Code) to Experimental RFC
Date: Sat, 12 Jan 2013 14:47:51 -0800
Importance: Normal
In-Reply-To: <CADnDZ8-w4Nu0RCgE94yZuBT+y6s176V0_kQsk7d_oBwPtUPhNg@mail.gmail.com>
References: <20130111151453.22161.50884.idtracker@ietfa.amsl.com>, <CADnDZ8-w4Nu0RCgE94yZuBT+y6s176V0_kQsk7d_oBwPtUPhNg@mail.gmail.com>
MIME-Version: 1.0
X-OriginalArrivalTime: 12 Jan 2013 22:47:51.0224 (UTC) FILETIME=[D9FA3380:01CDF116]
Cc: "ietf@ietf.org" <ietf@ietf.org>, "iesg@ietf.org" <iesg@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 12 Jan 2013 22:47:53 -0000

--_3e7ca20b-1d2a-475b-90d6-3e578f3fe97f_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

+1

[IAB Chair hat off].

> Date: Fri=2C 11 Jan 2013 22:25:38 +0100
> Subject: Re: Last Call: <draft-farrell-ft-03.txt> (A Fast-Track way to RF=
C	with Running Code) to Experimental RFC
> From: abdussalambaryun@gmail.com
> To: sm@resistor.net
> CC: ietf@ietf.org=3B iesg@ietf.org
>=20
> Hi SM=2C
>=20
> I totally agree with your comments and suggestions=2C the draft SHOULD
> mention the important clarifications and the answers to SM's
> questions. This is an important draft and SHUOLD be clear about such
> important details in sections=2C why it ignores them without refering to
> informative procedure items to link things for understanding. How do
> authors write these drafts are they done with following procedure=2C
>=20
> AB
>=20
> ++++++++
> In Section 1:
>=20
>   "Additionally=2C the experiment will only require issues raised
>    during these three stages to be addressed if they meet the
>    IESG's Discuss criteria."
>=20
> Does this mean that a document does not have to represent consensus?
>=20
>   "In contrast=2C a "-bis" RFC that aims for Proposed Standard or
>    Experimental is likely to be a fine candidate."
>=20
>=20
> I read what the document proposes as lowering the barrier of entry for
> first publication. My preference is to say nothing about "-bis" RFCs
> (see quoted text). Some of the "-bis" drafts I have come across (note
> that this is not related to a draft being discussed currently) are not
> well-written even though there is running code. The running code might
> be due to author intervention instead of a blind test of the
> specification.
> In Section 2:
>=20
>   "Implementations developed during the production of an Internet-draft
>    can indicate that a working group has had the opportunity to get
>    early confirmation of its engineering choices."
>=20
> Agreed.
>=20
> In Section 3:
>=20
>   "Any Working Group Last Call (WGLC) or Area Director (AD) review
>   (which are routinely done=2C though not part of the formal [BCP9]
>   process) will run in parallel with the two-week IETF Last Call
>   (IETF-LC) period."
>=20
>=20
> I am not suggesting changing the two weeks. It can cause logistical
> problems. I'll take the risk of trying this experiment.
>   "Only comments that would be "DISCUSS-worthy" according to the
>    IESG Discuss Criteria [DCRIT] need be handled during last call.
>    Other comments can be handled or not=2C at the authors/editors
>    discretion."
>=20
> See my previous comment about this criteria.
>=20
> In Section 4:
>=20
>   "The fast-track process can be used for "bis" RFCs and might well
>    be quite suitable for those."
>=20
> I suggest removing this.
>=20
>   "If the timers (IETF LC or the two-weeks after IETF LC for fixing
>    things) co-incide with a major holiday period or IETF meeting
>    then the responsible AD can add a week or two as appropriate."
>=20
>=20
> I suggest not using the Fast-Track if it is less than two weeks before
> or after an IETF meeting. Some people only do IETF work during that
> period and that results in a spike. I don't think that it is a good
> idea for this experiment to encourage work during the meeting phase
> instead of the mailing list.
> In Section 5:
>=20
>   "An AD who wishes to do her review in parallel with Last Call is
>    always free to make that choice."
>=20
> "his" or a gender neutral term.
>=20
>   "This memo itself has no impact on appeal processes.  However=2C in
>    considering an appeal that relates to a document that has been
>    fast-track processed=2C the relevant judge (WG chair=2C AD=2C IESG or
>    IAB as appropriate) should consider the requirements posited here."
>=20
>=20
> The WG Chair is not a judge in such cases as it would be his/her
> decision being appealed.
>=20
> Some people are discouraged from bringing work into the IETF because
> of the long debates (which I likely contributed to). Big companies
> have an incentive to do work within the IETF. There is a perception in
> open source circles than there isn't much to gain in having a
> specification published as a RFC.
>=20
> The young=2C free and wild will not listen to the fogies. The better
> approach=2C in my opinion=2C is not to act as a gatekeeper or encourage a
> wall-garden attitude.
> Regards=2C
>=20
> -sm
 		 	   		  =

--_3e7ca20b-1d2a-475b-90d6-3e578f3fe97f_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<style><!--
.hmmessage P
{
margin:0px=3B
padding:0px
}
body.hmmessage
{
font-size: 12pt=3B
font-family:Calibri
}
--></style></head>
<body class=3D'hmmessage'><div dir=3D'ltr'>+1<br><br>[IAB Chair hat off].<b=
r><br><div><div id=3D"SkyDrivePlaceholder"></div>&gt=3B Date: Fri=2C 11 Jan=
 2013 22:25:38 +0100<br>&gt=3B Subject: Re: Last Call: &lt=3Bdraft-farrell-=
ft-03.txt&gt=3B (A Fast-Track way to RFC	with Running Code) to Experimental=
 RFC<br>&gt=3B From: abdussalambaryun@gmail.com<br>&gt=3B To: sm@resistor.n=
et<br>&gt=3B CC: ietf@ietf.org=3B iesg@ietf.org<br>&gt=3B <br>&gt=3B Hi SM=
=2C<br>&gt=3B <br>&gt=3B I totally agree with your comments and suggestions=
=2C the draft SHOULD<br>&gt=3B mention the important clarifications and the=
 answers to SM's<br>&gt=3B questions. This is an important draft and SHUOLD=
 be clear about such<br>&gt=3B important details in sections=2C why it igno=
res them without refering to<br>&gt=3B informative procedure items to link =
things for understanding. How do<br>&gt=3B authors write these drafts are t=
hey done with following procedure=2C<br>&gt=3B <br>&gt=3B AB<br>&gt=3B <br>=
&gt=3B ++++++++<br>&gt=3B In Section 1:<br>&gt=3B <br>&gt=3B   "Additionall=
y=2C the experiment will only require issues raised<br>&gt=3B    during the=
se three stages to be addressed if they meet the<br>&gt=3B    IESG's Discus=
s criteria."<br>&gt=3B <br>&gt=3B Does this mean that a document does not h=
ave to represent consensus?<br>&gt=3B <br>&gt=3B   "In contrast=2C a "-bis"=
 RFC that aims for Proposed Standard or<br>&gt=3B    Experimental is likely=
 to be a fine candidate."<br>&gt=3B <br>&gt=3B <br>&gt=3B I read what the d=
ocument proposes as lowering the barrier of entry for<br>&gt=3B first publi=
cation. My preference is to say nothing about "-bis" RFCs<br>&gt=3B (see qu=
oted text). Some of the "-bis" drafts I have come across (note<br>&gt=3B th=
at this is not related to a draft being discussed currently) are not<br>&gt=
=3B well-written even though there is running code. The running code might<=
br>&gt=3B be due to author intervention instead of a blind test of the<br>&=
gt=3B specification.<br>&gt=3B In Section 2:<br>&gt=3B <br>&gt=3B   "Implem=
entations developed during the production of an Internet-draft<br>&gt=3B   =
 can indicate that a working group has had the opportunity to get<br>&gt=3B=
    early confirmation of its engineering choices."<br>&gt=3B <br>&gt=3B Ag=
reed.<br>&gt=3B <br>&gt=3B In Section 3:<br>&gt=3B <br>&gt=3B   "Any Workin=
g Group Last Call (WGLC) or Area Director (AD) review<br>&gt=3B   (which ar=
e routinely done=2C though not part of the formal [BCP9]<br>&gt=3B   proces=
s) will run in parallel with the two-week IETF Last Call<br>&gt=3B   (IETF-=
LC) period."<br>&gt=3B <br>&gt=3B <br>&gt=3B I am not suggesting changing t=
he two weeks. It can cause logistical<br>&gt=3B problems. I'll take the ris=
k of trying this experiment.<br>&gt=3B   "Only comments that would be "DISC=
USS-worthy" according to the<br>&gt=3B    IESG Discuss Criteria [DCRIT] nee=
d be handled during last call.<br>&gt=3B    Other comments can be handled o=
r not=2C at the authors/editors<br>&gt=3B    discretion."<br>&gt=3B <br>&gt=
=3B See my previous comment about this criteria.<br>&gt=3B <br>&gt=3B In Se=
ction 4:<br>&gt=3B <br>&gt=3B   "The fast-track process can be used for "bi=
s" RFCs and might well<br>&gt=3B    be quite suitable for those."<br>&gt=3B=
 <br>&gt=3B I suggest removing this.<br>&gt=3B <br>&gt=3B   "If the timers =
(IETF LC or the two-weeks after IETF LC for fixing<br>&gt=3B    things) co-=
incide with a major holiday period or IETF meeting<br>&gt=3B    then the re=
sponsible AD can add a week or two as appropriate."<br>&gt=3B <br>&gt=3B <b=
r>&gt=3B I suggest not using the Fast-Track if it is less than two weeks be=
fore<br>&gt=3B or after an IETF meeting. Some people only do IETF work duri=
ng that<br>&gt=3B period and that results in a spike. I don't think that it=
 is a good<br>&gt=3B idea for this experiment to encourage work during the =
meeting phase<br>&gt=3B instead of the mailing list.<br>&gt=3B In Section 5=
:<br>&gt=3B <br>&gt=3B   "An AD who wishes to do her review in parallel wit=
h Last Call is<br>&gt=3B    always free to make that choice."<br>&gt=3B <br=
>&gt=3B "his" or a gender neutral term.<br>&gt=3B <br>&gt=3B   "This memo i=
tself has no impact on appeal processes.  However=2C in<br>&gt=3B    consid=
ering an appeal that relates to a document that has been<br>&gt=3B    fast-=
track processed=2C the relevant judge (WG chair=2C AD=2C IESG or<br>&gt=3B =
   IAB as appropriate) should consider the requirements posited here."<br>&=
gt=3B <br>&gt=3B <br>&gt=3B The WG Chair is not a judge in such cases as it=
 would be his/her<br>&gt=3B decision being appealed.<br>&gt=3B <br>&gt=3B S=
ome people are discouraged from bringing work into the IETF because<br>&gt=
=3B of the long debates (which I likely contributed to). Big companies<br>&=
gt=3B have an incentive to do work within the IETF. There is a perception i=
n<br>&gt=3B open source circles than there isn't much to gain in having a<b=
r>&gt=3B specification published as a RFC.<br>&gt=3B <br>&gt=3B The young=
=2C free and wild will not listen to the fogies. The better<br>&gt=3B appro=
ach=2C in my opinion=2C is not to act as a gatekeeper or encourage a<br>&gt=
=3B wall-garden attitude.<br>&gt=3B Regards=2C<br>&gt=3B <br>&gt=3B -sm<br>=
</div> 		 	   		  </div></body>
</html>=

--_3e7ca20b-1d2a-475b-90d6-3e578f3fe97f_--

From randy@psg.com  Sat Jan 12 15:49:19 2013
Return-Path: <randy@psg.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 33C7921F894E for <ietf@ietfa.amsl.com>; Sat, 12 Jan 2013 15:49:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.567
X-Spam-Level: 
X-Spam-Status: No, score=-2.567 tagged_above=-999 required=5 tests=[AWL=0.032,  BAYES_00=-2.599]
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 pre22wO0OWIp for <ietf@ietfa.amsl.com>; Sat, 12 Jan 2013 15:49:18 -0800 (PST)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by ietfa.amsl.com (Postfix) with ESMTP id B377F21F894D for <ietf@ietf.org>; Sat, 12 Jan 2013 15:49:18 -0800 (PST)
Received: from localhost ([127.0.0.1] helo=ryuu.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.80.1 (FreeBSD)) (envelope-from <randy@psg.com>) id 1TuApB-0007vh-3m; Sat, 12 Jan 2013 23:49:17 +0000
Date: Sat, 12 Jan 2013 13:49:16 -1000
Message-ID: <m24nimx8qr.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: John C Klensin <john-ietf@jck.com>
Subject: Re: I-D Action: draft-moonesamy-rfc2050-historic-00.txt
In-Reply-To: <03E877D7862B38284128680C@JcK-HP8200.jck.com>
References: <20130112085109.7357.35960.idtracker@ietfa.amsl.com> <50F12E80.8080007@gmail.com> <6D2D2975-A47A-4A0B-A11F-D7C73FE22EDD@virtualized.org> <03E877D7862B38284128680C@JcK-HP8200.jck.com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 12 Jan 2013 23:49:19 -0000

> If Jon were participating in this conversation today, I'm quite sure
> that he would be saying that it is much more important for the RIRs
> and the IETF to work together to get the best result for the Internet
> rather than putting energy into trying to legislate or enforce a
> boundary (whether that effort started in the IETF or in the RIRs).

can't speak for dr postel.  but this seems a responsible position.

randy

From drc@virtualized.org  Sat Jan 12 16:19:46 2013
Return-Path: <drc@virtualized.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5655521F899D for <ietf@ietfa.amsl.com>; Sat, 12 Jan 2013 16:19:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 SAHJIMHL4l+v for <ietf@ietfa.amsl.com>; Sat, 12 Jan 2013 16:19:45 -0800 (PST)
Received: from trantor.virtualized.org (trantor.virtualized.org [199.48.134.42]) by ietfa.amsl.com (Postfix) with ESMTP id 9804421F8941 for <ietf@ietf.org>; Sat, 12 Jan 2013 16:19:45 -0800 (PST)
Received: from [10.0.1.13] (c-24-4-109-25.hsd1.ca.comcast.net [24.4.109.25]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: drc) by trantor.virtualized.org (Postfix) with ESMTPSA id C3289170AD; Sun, 13 Jan 2013 00:19:44 +0000 (UTC)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Subject: Re: I-D Action: draft-moonesamy-rfc2050-historic-00.txt
From: David Conrad <drc@virtualized.org>
In-Reply-To: <03E877D7862B38284128680C@JcK-HP8200.jck.com>
Date: Sat, 12 Jan 2013 16:19:43 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <BBAC97B5-C633-4034-818D-5E9755012FF8@virtualized.org>
References: <20130112085109.7357.35960.idtracker@ietfa.amsl.com> <50F12E80.8080007@gmail.com> <6D2D2975-A47A-4A0B-A11F-D7C73FE22EDD@virtualized.org> <03E877D7862B38284128680C@JcK-HP8200.jck.com>
To: John C Klensin <john-ietf@jck.com>
X-Mailer: Apple Mail (2.1499)
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 13 Jan 2013 00:19:46 -0000

John,

On Jan 12, 2013, at 2:21 PM, John C Klensin <john-ietf@jck.com> wrote:
> However, I don't think the
> section of 2860 that you cite helps very much because there is
> another way to read it. =20

As you know, there are many in both high and low places who choose the =
interpretation of 2860 that best fits their particular interests, =
regardless of the intent of that document (or, from personal experience, =
efforts to try to explain history or reality).  As such, I'll repeat: I =
do not believe it useful or helpful to go down that particular rat hole.

The more relevant bit:

> The IETF still has responsibility for the technical
> specification of addresses and the policies that narrowly
> implies; other policy issues, including the models for
> allocations of addresses to those who will use them, belong to
> others. =20

I believe RFC 2050 does (and did) _not_ address "technical =
specifications of addresses", but rather documented (past tense) the =
then "best current practice" of policies associated with the operational =
deployment of those addresses for a short period around 1995 or so.

The Internet has moved on. The IETF still has the responsibility to =
define address technical specifications (e.g., an IPv6 address is 128 =
bits long), however I do not believe the IETF now has the responsibility =
to define operational deployment policy or processes (if it ever did).

As such, I think it perfectly appropriate to move RFC 2050 to "historic" =
since, in fact, it actually is.

> If Jon were participating in this conversation today, I'm quite
> sure that he would be saying that it is much more important for
> the RIRs and the IETF to work together to get the best result
> for the Internet rather than putting energy into trying to
> legislate or enforce a boundary

I doubt anyone rational would disagree with this, but I don't think =
that's the topic of discussion.  The issue, as I understand it, is that =
RFC 2050 is outdated and historic and its status should be made to =
reflect that truth.

Regards,
-drc


From dhc@dcrocker.net  Sat Jan 12 16:34:20 2013
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B818121F8941 for <ietf@ietfa.amsl.com>; Sat, 12 Jan 2013 16:34:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.449
X-Spam-Level: 
X-Spam-Status: No, score=-6.449 tagged_above=-999 required=5 tests=[AWL=0.150,  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 V+TpjmF2wPzw for <ietf@ietfa.amsl.com>; Sat, 12 Jan 2013 16:34:19 -0800 (PST)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 7B61621F8936 for <ietf@ietf.org>; Sat, 12 Jan 2013 16:34:19 -0800 (PST)
Received: from [192.168.1.66] (76-218-9-215.lightspeed.sntcca.sbcglobal.net [76.218.9.215]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id r0D0YIAR011353 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <ietf@ietf.org>; Sat, 12 Jan 2013 16:34:19 -0800
Message-ID: <50F20102.80800@dcrocker.net>
Date: Sat, 12 Jan 2013 16:34:10 -0800
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130107 Thunderbird/17.0.2
MIME-Version: 1.0
To: IETF discussion list <ietf@ietf.org>
Subject: Re: I-D Action: draft-moonesamy-rfc2050-historic-00.txt
References: <20130112085109.7357.35960.idtracker@ietfa.amsl.com> <50F12E80.8080007@gmail.com> <6D2D2975-A47A-4A0B-A11F-D7C73FE22EDD@virtualized.org> <03E877D7862B38284128680C@JcK-HP8200.jck.com> <BBAC97B5-C633-4034-818D-5E9755012FF8@virtualized.org>
In-Reply-To: <BBAC97B5-C633-4034-818D-5E9755012FF8@virtualized.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Sat, 12 Jan 2013 16:34:19 -0800 (PST)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 13 Jan 2013 00:34:20 -0000

On 1/12/2013 4:19 PM, David Conrad wrote:
> I believe RFC 2050 does (and did) _not_ address "technical
> specifications of addresses", but rather documented (past tense) the
> then "best current practice" of policies associated with the
> operational deployment of those addresses for a short period around
> 1995 or so.
>
> The Internet has moved on. The IETF still has the responsibility to
> define address technical specifications (e.g., an IPv6 address is 128
> bits long), however I do not believe the IETF now has the
> responsibility to define operational deployment policy or processes
> (if it ever did).
>
> As such, I think it perfectly appropriate to move RFC 2050 to
> "historic" since, in fact, it actually is.


The document's abstract declares the document's purposes to be:

    This document describes the registry system for the distribution of
    globally unique Internet address space and registry operations.
    ...
    This document describes the IP assignment policies currently used by
    the Regional Registries to implement the guidelines developed by the
    IANA. The guidelines and these policies are subject to revision at
    the direction of the IANA.


Unless I'm misunderstanding something, there's a simple issue here that 
should be resolved through a simple question:  Does the document still 
satisfy either of these purposes sufficiently and accurately.  My 
understanding from this thread (and elsewhere) is that the answer is no. 
  By definition, the document's role is therefore Historic and it only 
makes sense to make this official.

If there is content in the document that happens to still be useful, it 
should be extracted and published separately, so that no reader will 
suffer confusion and think that the remainder of the document remains 
applicable.

d/

ps.  A replacement document that /is/ sufficient to the current Internet 
would be a service to the community.

-- 
  Dave Crocker
  Brandenburg InternetWorking
  bbiw.net

From randy@psg.com  Sat Jan 12 19:14:45 2013
Return-Path: <randy@psg.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C694521F8A41 for <ietf@ietfa.amsl.com>; Sat, 12 Jan 2013 19:14:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.271
X-Spam-Level: 
X-Spam-Status: No, score=-2.271 tagged_above=-999 required=5 tests=[AWL=-0.272, BAYES_00=-2.599, J_CHICKENPOX_31=0.6]
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 MebNLr9h8rQA for <ietf@ietfa.amsl.com>; Sat, 12 Jan 2013 19:14:45 -0800 (PST)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by ietfa.amsl.com (Postfix) with ESMTP id 0D05021F8A3F for <ietf@ietf.org>; Sat, 12 Jan 2013 19:14:45 -0800 (PST)
Received: from localhost ([127.0.0.1] helo=ryuu.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.80.1 (FreeBSD)) (envelope-from <randy@psg.com>) id 1TuE1y-0008oA-GA; Sun, 13 Jan 2013 03:14:42 +0000
Date: Sat, 12 Jan 2013 17:14:39 -1000
Message-ID: <m21udpydsw.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: David Conrad <drc@virtualized.org>
Subject: Re: I-D Action: draft-moonesamy-rfc2050-historic-00.txt
In-Reply-To: <BBAC97B5-C633-4034-818D-5E9755012FF8@virtualized.org>
References: <20130112085109.7357.35960.idtracker@ietfa.amsl.com> <50F12E80.8080007@gmail.com> <6D2D2975-A47A-4A0B-A11F-D7C73FE22EDD@virtualized.org> <03E877D7862B38284128680C@JcK-HP8200.jck.com> <BBAC97B5-C633-4034-818D-5E9755012FF8@virtualized.org>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
Cc: IETF Disgust <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 13 Jan 2013 03:14:45 -0000

< vituperation >

> I believe RFC 2050 does (and did) _not_ address "technical
> specifications of addresses", but rather documented (past tense) the
> then "best current practice" of policies associated with the
> operational deployment of those addresses for a short period around
> 1995 or so.

from this ops pov, the danvers meeting was where the ops and the irs met
to agree on the critical issue of sean's ags+s falling over, agree that
we would not filter on shorter than a /19 outside of swamp, and that the
irs would allocate no longer than /19.  that the ir folk then took it
and made a massive layer nine out of it was on your own heads.  the
american idiom is that chickens come home to roost.

> RFC 2050 is outdated and historic and its status should be made to
> reflect that truth.

made your bed, sleep in it.  maybe learn not to do it again?  nope.  the
irs keep on making massive and complex policy.  there were and are
alternatives http://www.apnic.net/policy/proposals/prop-103

we need bookkeepers.  we get wannabe regulators.  now we have wannabe
regulators who want to write the regulations completely outside of
coordination with the rest of the community.  oh goodie.

randy

From drc@virtualized.org  Sat Jan 12 20:26:39 2013
Return-Path: <drc@virtualized.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7D32421F8A2F for <ietf@ietfa.amsl.com>; Sat, 12 Jan 2013 20:26:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 wPUT327B0V6Z for <ietf@ietfa.amsl.com>; Sat, 12 Jan 2013 20:26:39 -0800 (PST)
Received: from trantor.virtualized.org (trantor.virtualized.org [199.48.134.42]) by ietfa.amsl.com (Postfix) with ESMTP id EFDF521F8A1E for <ietf@ietf.org>; Sat, 12 Jan 2013 20:26:38 -0800 (PST)
Received: from [10.0.1.13] (c-24-4-109-25.hsd1.ca.comcast.net [24.4.109.25]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: drc) by trantor.virtualized.org (Postfix) with ESMTPSA id C90F6170A7; Sun, 13 Jan 2013 04:26:37 +0000 (UTC)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Subject: Re: I-D Action: draft-moonesamy-rfc2050-historic-00.txt
From: David Conrad <drc@virtualized.org>
In-Reply-To: <m21udpydsw.wl%randy@psg.com>
Date: Sat, 12 Jan 2013 20:26:36 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <A5A609EB-69B6-4B12-88A4-3024E2BF80C0@virtualized.org>
References: <20130112085109.7357.35960.idtracker@ietfa.amsl.com> <50F12E80.8080007@gmail.com> <6D2D2975-A47A-4A0B-A11F-D7C73FE22EDD@virtualized.org> <03E877D7862B38284128680C@JcK-HP8200.jck.com> <BBAC97B5-C633-4034-818D-5E9755012FF8@virtualized.org> <m21udpydsw.wl%randy@psg.com>
To: Randy Bush <randy@psg.com>
X-Mailer: Apple Mail (2.1499)
Cc: IETF Disgust <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 13 Jan 2013 04:26:39 -0000

On Jan 12, 2013, at 7:14 PM, Randy Bush <randy@psg.com> wrote:
>> RFC 2050 is outdated and historic and its status should be made to
>> reflect that truth.
> made your bed, sleep in it. =20

Mea culpa, but it's time to get out of bed.

> maybe learn not to do it again?  nope. =20

To be clear, I think RFC 2050 was helpful when it was published, however =
as I said, the Internet has moved on and I believe there are better =
venues in which operational policies for addresses can be developed. I =
figure it's called "best _current_ practice" for a reason.

> we need bookkeepers.  we get wannabe regulators. =20

+1

> now we have wannabe

> regulators who want to write the regulations completely outside of
> coordination with the rest of the community.  oh goodie.


I don't believe moving RFC 2050 to historic implies the operational =
community efforts to develop policy is "completely outside coordination =
with the rest of the community". I would, in fact, be quite supportive =
of (and would even contribute to (if it would be helpful)) IETF input to =
ICANN/IANA on a replacement for RFC 2050.=20

Regards,
-drc


From randy@psg.com  Sat Jan 12 21:01:27 2013
Return-Path: <randy@psg.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 63E9421F8A74 for <ietf@ietfa.amsl.com>; Sat, 12 Jan 2013 21:01:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.54
X-Spam-Level: 
X-Spam-Status: No, score=-2.54 tagged_above=-999 required=5 tests=[AWL=0.059,  BAYES_00=-2.599]
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 iZUuMspKgPfh for <ietf@ietfa.amsl.com>; Sat, 12 Jan 2013 21:01:26 -0800 (PST)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by ietfa.amsl.com (Postfix) with ESMTP id E17DD21F8A53 for <ietf@ietf.org>; Sat, 12 Jan 2013 21:01:26 -0800 (PST)
Received: from localhost ([127.0.0.1] helo=ryuu.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.80.1 (FreeBSD)) (envelope-from <randy@psg.com>) id 1TuFhD-00090f-RV; Sun, 13 Jan 2013 05:01:24 +0000
Date: Sat, 12 Jan 2013 19:01:23 -1000
Message-ID: <m2obgtwuak.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: David Conrad <drc@virtualized.org>
Subject: Re: I-D Action: draft-moonesamy-rfc2050-historic-00.txt
In-Reply-To: <A5A609EB-69B6-4B12-88A4-3024E2BF80C0@virtualized.org>
References: <20130112085109.7357.35960.idtracker@ietfa.amsl.com> <50F12E80.8080007@gmail.com> <6D2D2975-A47A-4A0B-A11F-D7C73FE22EDD@virtualized.org> <03E877D7862B38284128680C@JcK-HP8200.jck.com> <BBAC97B5-C633-4034-818D-5E9755012FF8@virtualized.org> <m21udpydsw.wl%randy@psg.com> <A5A609EB-69B6-4B12-88A4-3024E2BF80C0@virtualized.org>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
Cc: IETF Disgust <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 13 Jan 2013 05:01:27 -0000

< more vituperation >

>> we need bookkeepers.  we get wannabe regulators.  
> +1

and, as a friend pointed out, in sidr, we are arming them.  i try hard
to ameliorate this.  but that's another subject.

> I don't believe moving RFC 2050 to historic implies the operational
> community efforts to develop policy is "completely outside
> coordination with the rest of the community".

fwiw, i do not consider the irs to represent the operational community,
though they claim very loudly to do so.  they have coopted the space,
but, imiho, represent the interests of self-perpetuating organizational
fiefdoms far more than operators.  itu-t wannabes.

> I would, in fact, be quite supportive of (and would even contribute to
> (if it would be helpful)) IETF input to ICANN/IANA on a replacement
> for RFC 2050.

at russ's request (i did warn him of the poolpah), i tried to start a
2870 (dns root ops) bis with only one sentence added.

   2.7  Root servers SHOULD fully support queries and make corresponding
        responses with either IPv4 or IPv6.

the root ops private fiefdom rose up in objetion and non-cooperation
which has become their hallmark.

fighting fiefdoms is a waste of time.  the answer is to shut them the
hell down.

randy

From randy@psg.com  Sat Jan 12 22:55:58 2013
Return-Path: <randy@psg.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B72E221F8AE5 for <ietf@ietfa.amsl.com>; Sat, 12 Jan 2013 22:55:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.546
X-Spam-Level: 
X-Spam-Status: No, score=-2.546 tagged_above=-999 required=5 tests=[AWL=0.053,  BAYES_00=-2.599]
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 G51zlVFi7O4d for <ietf@ietfa.amsl.com>; Sat, 12 Jan 2013 22:55:58 -0800 (PST)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by ietfa.amsl.com (Postfix) with ESMTP id 1ECF021F8AE3 for <ietf@ietf.org>; Sat, 12 Jan 2013 22:55:58 -0800 (PST)
Received: from localhost ([127.0.0.1] helo=ryuu.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.80.1 (FreeBSD)) (envelope-from <randy@psg.com>) id 1TuHU4-0009Eg-PW for ietf@ietf.org; Sun, 13 Jan 2013 06:55:57 +0000
Date: Sat, 12 Jan 2013 20:55:56 -1000
Message-ID: <m24nilwozn.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: IETF Disgust <ietf@ietf.org>
Subject: digressive rant on internet fiefdoms
In-Reply-To: <m2obgtwuak.wl%randy@psg.com>
References: <20130112085109.7357.35960.idtracker@ietfa.amsl.com> <50F12E80.8080007@gmail.com> <6D2D2975-A47A-4A0B-A11F-D7C73FE22EDD@virtualized.org> <03E877D7862B38284128680C@JcK-HP8200.jck.com> <BBAC97B5-C633-4034-818D-5E9755012FF8@virtualized.org> <m21udpydsw.wl%randy@psg.com> <A5A609EB-69B6-4B12-88A4-3024E2BF80C0@virtualized.org> <m2obgtwuak.wl%randy@psg.com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 13 Jan 2013 06:55:58 -0000

> fighting fiefdoms is a waste of time.  the answer is to shut them the
> hell down.

a friend asked (to put it politely:-) me to clarify.

[ first, mea multi culpea, i helped start and/or served on the board (or
  equivalent) of a number of the organizations against which i rail.
  consider me the loyal opposition.  but i try, as we say, to work for
  the internet. ]

when people's livelihoods depend on an organization's existence, self-
interest is inevitable.  no blame, we're all just funny monkeys.  there
are no evil players here, just humans.  it's not their fault, it is ours
for creating and allowing it.

yes, we need the ir function fulfilled.  but i have become more and more
sceptical that we need six organizations doing it.  and organizations
with large staff.  we have built a privileged regulatory class.  when
you have a large building, half a dozen 'coffee ladies' on staff, or a
bunch of lawyers, then it's time for a revolution.

the ietf and nanog outsource out all services in arms' length contracts.
this has responsibility and accountability built in [0].  yes, all
organizations are self perpetuating, but i prefer the model where no one
is paid (directly [1]).

and i much prefer the ietf's nomcom model, which ameliorates the board
election game of the irs, nanog, etc, which are beauty contests and do
not serve the community well.  imiho, the beauty contests, the paid
fiefdoms, and the lawyers have led us from the bookkeeping model to the
regulatory.

randy

--

[0] - Accountability is something that is left when responsibility has
      been subtracted.  -- Pasi Sahlberg
[1] - http://archive.psg.com/051000.ccr-ivtf.pdf

From brian.e.carpenter@gmail.com  Sun Jan 13 00:18:18 2013
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4544D21F8AB8 for <ietf@ietfa.amsl.com>; Sun, 13 Jan 2013 00:18:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.422
X-Spam-Level: 
X-Spam-Status: No, score=-101.422 tagged_above=-999 required=5 tests=[AWL=0.268, BAYES_00=-2.599, RCVD_ILLEGAL_IP=1.908, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
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 ImrfA8wlNyEt for <ietf@ietfa.amsl.com>; Sun, 13 Jan 2013 00:18:17 -0800 (PST)
Received: from mail-wi0-f175.google.com (mail-wi0-f175.google.com [209.85.212.175]) by ietfa.amsl.com (Postfix) with ESMTP id 7925021F8AA8 for <ietf@ietf.org>; Sun, 13 Jan 2013 00:18:17 -0800 (PST)
Received: by mail-wi0-f175.google.com with SMTP id hm11so644233wib.14 for <ietf@ietf.org>; Sun, 13 Jan 2013 00:18:16 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:organization:user-agent :mime-version:to:cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=y4imlgkuhsWCcTCN3zEHqCkigOeUiRg4ocyi0cp13JM=; b=De6UNNpmfS5VnsFfAENgLx+bHReh3V5uHOIk1knVmjqrVFIBaqJOKyexLQ/PrioTGA UhZvY5W1DBsuzk0b2Oqb/aWPngjcYhOtVSLVZ/p1FE1OajMIylJuwyJHmvbKdS02GVUG i/+BgHRA7gYQVKJHd1xQ2qpOzU5noFvg1wAu06oAQOXKpA6M4HEOjvpTJEAh2XQLvqVk IbTGbrs04gw7g9lA6vduS2lZIhWJq6npBFKQUyapsB3rScGuVsOu4FdnUnn8D1otb4wk 1aQH6/2dCszxSnpTZPBPLkoqZcYCFNX3uyQ1f+Jm+49N030CLxZMIVq40oQhu8SZHRyr AF7Q==
X-Received: by 10.194.7.104 with SMTP id i8mr129099089wja.27.1358065096676; Sun, 13 Jan 2013 00:18:16 -0800 (PST)
Received: from [192.168.1.65] (host-2-102-219-76.as13285.net. [2.102.219.76]) by mx.google.com with ESMTPS id bd7sm7736009wib.8.2013.01.13.00.18.14 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 13 Jan 2013 00:18:15 -0800 (PST)
Message-ID: <50F26DC6.6000102@gmail.com>
Date: Sun, 13 Jan 2013 08:18:14 +0000
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: John C Klensin <john-ietf@jck.com>
Subject: Re: I-D Action: draft-moonesamy-rfc2050-historic-00.txt
References: <20130112085109.7357.35960.idtracker@ietfa.amsl.com> <50F12E80.8080007@gmail.com> <6D2D2975-A47A-4A0B-A11F-D7C73FE22EDD@virtualized.org> <03E877D7862B38284128680C@JcK-HP8200.jck.com>
In-Reply-To: <03E877D7862B38284128680C@JcK-HP8200.jck.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: Subramanian Moonesamy <sm+ietf@elandsys.com>, IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 13 Jan 2013 08:18:18 -0000

I of course agree with Dave Conrad that current practice has changed
since 1996. FWIW I also fully agree with John. I think it is quite
possible to write a quite short update of BCP 12 that keeps the
technical points that are still valid and omits the policy points
that have been delegated to IANA. Maybe we should have done this
in 2000.

Regards
   Brian


On 12/01/2013 22:21, John C Klensin wrote:
> 
> --On Saturday, January 12, 2013 11:36 -0800 David Conrad
> <drc@virtualized.org> wrote:
> 
>> ...
>> No, since addressing is _explicitly_ declared out of scope of
>> that MoU, see section 4.3 of RFC 2860:
>>
>>   "Two particular assigned spaces present policy issues in
>> addition    to the technical considerations specified by the
>> IETF: the assignment    of domain names, and the assignment of
>> IP address blocks. These    policy issues are outside the
>> scope of this MOU."
>>
>> I don't think it is particularly useful or helpful to try to
>> assert that the IETF did "formally hand over" address
>> allocation to IANA since, as you know, there are lots of folks
>> who have, do, and will claim address allocation, as an
>> operational matter, was never the IETF's to "hand over". What
>> might be useful/helpful is to try to identify the portions of
>> RFC 2050 that have any relevance to the IETF and verify that
>> those portions are covered elsewhere.
> 
> David (and Brian and Subramanian), 
> 
> There are cans of poisonous, vicious vipers (only superficially
> resembling cans of worms) that are, IMO, best not opened and
> this is, IMO, one of them.  The reasons for that are probably as
> obvious to you as they are to me and I certainly agree with most
> of your last paragraph above.  However, I don't think the
> section of 2860 that you cite helps very much because there is
> another way to read it.  That alternate reading, which I believe
> is actually the correct one, says that the addressing issues
> (and the domain ones) consist of two parts "technical
> considerations" which are specified by the IETF and "policy
> issues" that are someone else's problem.  Indeed, it says
> "policy issues in addition to...", which I think recognizes that
> those "technical considerations" may have policy implications
> and that it is within scope for the IETF to specify those too.
> The exclusion is for policy issues that are _not_ part of the
> technical considerations.
> 
> With the understanding that the boundary that posits is very
> fuzzy, I don't think that basic principle has changed
> significantly since the MOU and probably not much since RFC
> 2050.  The IETF still has responsibility for the technical
> specification of addresses and the policies that narrowly
> implies; other policy issues, including the models for
> allocations of addresses to those who will use them, belong to
> others.  
> 
> I think it unwise try to define the boundary more precisely than
> that.  You may recall that an attempt was made to do so more or
> less unilaterally at the time the NRO was formed; in my opinion,
> that didn't work out especially well for the Internet (YMMD).
> If Jon were participating in this conversation today, I'm quite
> sure that he would be saying that it is much more important for
> the RIRs and the IETF to work together to get the best result
> for the Internet rather than putting energy into trying to
> legislate or enforce a boundary (whether that effort started in
> the IETF or in the RIRs).
> 
> best,
>    john
> 
> 

From arturo.servin@gmail.com  Sun Jan 13 06:22:28 2013
Return-Path: <arturo.servin@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 24ED621F8431 for <ietf@ietfa.amsl.com>; Sun, 13 Jan 2013 06:22:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 SLS7XTfMDAoe for <ietf@ietfa.amsl.com>; Sun, 13 Jan 2013 06:22:27 -0800 (PST)
Received: from mail-gh0-f173.google.com (mail-gh0-f173.google.com [209.85.160.173]) by ietfa.amsl.com (Postfix) with ESMTP id 54E5521F8414 for <ietf@ietf.org>; Sun, 13 Jan 2013 06:22:27 -0800 (PST)
Received: by mail-gh0-f173.google.com with SMTP id 16so140866ghy.18 for <ietf@ietf.org>; Sun, 13 Jan 2013 06:22:26 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=jSyKRhlnE8jxxA5gyuRMsIqz9h3FiKfHGGYx0VA7wyY=; b=AlbCvPxNG9iUhicN81kcLBDDyGn50j6nITJVVD/hZbb6bk2noZtukRzz4p9l73K8XW 59Ajn/npAHt7EWOZSQ9NTtpL9YhC3ou86iv7iiT4bwL8j3TqeH0erOkGoML0zmJ/00T6 nbQhLbmjPksA/1rr/Ld9QfmkG3zfOtW6hyWAC1FEQu0JbeHkgaIf9GqmFRnjS+LN5LTA nNpxN3hjSjj6W+u2ZvOb0HZp8wCuV18DuiduHC9fpbSMvPFrGxdiJTGBKlQzxOLGSKyP ZnybgBdZmjJoizulJlUzP4+oWzd6ovdKeBSnWJb+optV81WPGTxTVead4Eu9PEa/VbIm fbrw==
X-Received: by 10.236.83.161 with SMTP id q21mr86618866yhe.91.1358086946748; Sun, 13 Jan 2013 06:22:26 -0800 (PST)
Received: from ?IPv6:2800:af:ba30:eca7:e8bc:a199:cf5:88fd? ([2800:af:ba30:eca7:e8bc:a199:cf5:88fd]) by mx.google.com with ESMTPS id t47sm10184724yhd.2.2013.01.13.06.22.24 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 13 Jan 2013 06:22:25 -0800 (PST)
Message-ID: <50F2C31D.1080403@gmail.com>
Date: Sun, 13 Jan 2013 12:22:21 -0200
From: Arturo Servin <arturo.servin@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: "ietf@ietf.org list" <ietf@ietf.org>, SM <sm@resistor.net>
Subject: Re: I-D Action: draft-moonesamy-rfc2050-historic-00.txt
References: <20130112085109.7357.35960.idtracker@ietfa.amsl.com> <50F12E80.8080007@gmail.com>
In-Reply-To: <50F12E80.8080007@gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 13 Jan 2013 14:22:28 -0000

	I agree that RFC2050 is not completely valid with the current state of
the Internet, but making it historic will not solve any problem IMHO.

	Before making 2050 historic, we should think what is and what is not
valid according with today's internet, what the technical community
needs to recommend to the RIR community and make a new document that
updates and obsoletes 2050.

Cheers,
as


	
On 12/01/2013 07:36, Brian E Carpenter wrote:
> I object to making RFC 2050 historic without retaining at least the
> content of its Section 1 as an IETF BCP.
> 
> While the IETF did formally hand over details of address
> allocation policy to IANA, we did so knowing that the RIRs
> themselves, and IANA, considered themselves bound by RFC 2050
> (see the list of authors of that document).
> 
> An update of RFC 2050, within the scope set by the IETF-IANA
> MoU, would be reasonable. Abrogation is not reasonable.
> 
> Regards
>    Brian Carpenter (speaking only for myself)
> 
> On 12/01/2013 08:51, internet-drafts@ietf.org wrote:
>> A New Internet-Draft is available from the on-line Internet-Drafts directories.
>>
>>
>> 	Title           : Reclassifying Internet Registry Allocation Guidelines to Historic
>> 	Author(s)       : S. Moonesamy
>> 	Filename        : draft-moonesamy-rfc2050-historic-00.txt
>> 	Pages           : 4
>> 	Date            : 2013-01-12
>>
>> Abstract:
>> RFC 2050 describes the registry system for the distribution of globally
>> unique Internet address space and registry operations.  It also
>> discusses about policy issues which are outside the scope of the IETF.
>> This document reclassifies RFC 2050 as Historic.  It also reclassifies
>> RFC 1366 and RFC 1466 as Historic.
>>
>>
>> The IETF datatracker status page for this draft is:
>> https://datatracker.ietf.org/doc/draft-moonesamy-rfc2050-historic
>>
>> There's also a htmlized version available at:
>> http://tools.ietf.org/html/draft-moonesamy-rfc2050-historic-00
>>
>>
>> Internet-Drafts are also available by anonymous FTP at:
>> ftp://ftp.ietf.org/internet-drafts/
>>
>> _______________________________________________
>> I-D-Announce mailing list
>> I-D-Announce@ietf.org
>> https://www.ietf.org/mailman/listinfo/i-d-announce
>> Internet-Draft directories: http://www.ietf.org/shadow.html
>> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
>>

From abdussalambaryun@gmail.com  Sun Jan 13 08:02:17 2013
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DEBC021F87A6 for <ietf@ietfa.amsl.com>; Sun, 13 Jan 2013 08:02:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.578
X-Spam-Level: 
X-Spam-Status: No, score=-3.578 tagged_above=-999 required=5 tests=[AWL=0.021,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 7liXCaAu4Erl for <ietf@ietfa.amsl.com>; Sun, 13 Jan 2013 08:02:17 -0800 (PST)
Received: from mail-vb0-f44.google.com (mail-vb0-f44.google.com [209.85.212.44]) by ietfa.amsl.com (Postfix) with ESMTP id 3492321F87A4 for <ietf@ietf.org>; Sun, 13 Jan 2013 08:02:17 -0800 (PST)
Received: by mail-vb0-f44.google.com with SMTP id fc26so2915737vbb.3 for <ietf@ietf.org>; Sun, 13 Jan 2013 08:02:12 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=Q7NxfqG7fsymNXqVqRtUWQikN6ufy9E4q0PSiFVPGis=; b=nqnsNJl9Fb4JO5uBr6WKskI0o5kK9edV0jMQqPNcfScSLATo9vkebE4OvgVT5t1lE0 UQklMIt6A1XBONVUtemFp0ZO5G1NEP07Tmyab0By9D2PLWsSYGh6Vl9dI6G4MOwiemL8 U2UbtvutfyXXhXOWjITRQ3Y+Eq9unpDOIflTKdlgUP/m9hYqLQJzxmg49AbZV9NqNV5u hOhYvyafJy7QoZzhbJWjRI31Yvs1NBSRRIhy4EIBNoonH78byONjqYgSK32uYn/hmJUQ 7Ba/hbU4vfJ+t+gJUbn3z4IRwkmdRSQQi0/NFBDkEn6sNBPS/rasJjNCf1O8uAeDb4hz EqsA==
MIME-Version: 1.0
Received: by 10.52.21.179 with SMTP id w19mr87698890vde.55.1358092932010; Sun, 13 Jan 2013 08:02:12 -0800 (PST)
Received: by 10.220.145.5 with HTTP; Sun, 13 Jan 2013 08:02:11 -0800 (PST)
In-Reply-To: <6.2.5.6.2.20130112064815.05ffc568@resistor.net>
References: <20130112085109.7357.35960.idtracker@ietfa.amsl.com> <50F12E80.8080007@gmail.com> <6.2.5.6.2.20130112064815.05ffc568@resistor.net>
Date: Sun, 13 Jan 2013 17:02:11 +0100
Message-ID: <CADnDZ88Jb6eV1CBmpztVzpw57=gnXhoEq=AqQTNGSjtug=hr_A@mail.gmail.com>
Subject: Re: I-D Action: draft-moonesamy-rfc2050-historic-00.txt
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: S Moonesamy <sm+ietf@elandsys.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: arturo.servin@gmail.com, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 13 Jan 2013 16:02:18 -0000

agree with Servin, to update 2050,

AB
+++

On Sun, 13 Jan 2013 12:22:21, Arturo Servin wrote:

I agree that RFC2050 is not completely valid with the current state of
the Internet, but making it historic will not solve any problem IMHO.

Before making 2050 historic, we should think what is and what is not
valid according with today's internet, what the technical community
needs to recommend to the RIR community and make a new document that
updates and obsoletes 2050.

Cheers,
as

From stewe@stewe.org  Sun Jan 13 23:50:59 2013
Return-Path: <stewe@stewe.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 68A1221F87BA for <ietf@ietfa.amsl.com>; Sun, 13 Jan 2013 23:50:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[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 RtWXBbfeRRSc for <ietf@ietfa.amsl.com>; Sun, 13 Jan 2013 23:50:58 -0800 (PST)
Received: from co9outboundpool.messaging.microsoft.com (co9ehsobe003.messaging.microsoft.com [207.46.163.26]) by ietfa.amsl.com (Postfix) with ESMTP id 116D021F8869 for <ietf@ietf.org>; Sun, 13 Jan 2013 23:50:57 -0800 (PST)
Received: from mail177-co9-R.bigfish.com (10.236.132.237) by CO9EHSOBE015.bigfish.com (10.236.130.78) with Microsoft SMTP Server id 14.1.225.23; Mon, 14 Jan 2013 07:50:47 +0000
Received: from mail177-co9 (localhost [127.0.0.1])	by mail177-co9-R.bigfish.com (Postfix) with ESMTP id 2017CBE00C4; Mon, 14 Jan 2013 07:50:47 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.236.133; KIP:(null); UIP:(null); IPV:NLI; H:BY2PRD0710HT005.namprd07.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: -23
X-BigFish: PS-23(z10d0kzbb2dI98dI9371I542I1432I41c5N4015Ic8kzz1ee6h1de0h1202h1e76h1d1ah1d2ah1082kzz1033IL17326ah8275dhz2fh2a8h668h839h944hd25hf0ah1220h1288h12a5h12a9h12bdh137ah13b6h1441h1504h1537h153bh15d0h162dh1631h1758h1155h)
Received-SPF: pass (mail177-co9: domain of stewe.org designates 157.56.236.133 as permitted sender) client-ip=157.56.236.133; envelope-from=stewe@stewe.org; helo=BY2PRD0710HT005.namprd07.prod.outlook.com ; .outlook.com ; 
Received: from mail177-co9 (localhost.localdomain [127.0.0.1]) by mail177-co9 (MessageSwitch) id 1358149843843079_9891; Mon, 14 Jan 2013 07:50:43 +0000 (UTC)
Received: from CO9EHSMHS009.bigfish.com (unknown [10.236.132.253])	by mail177-co9.bigfish.com (Postfix) with ESMTP id CA64B780019; Mon, 14 Jan 2013 07:50:43 +0000 (UTC)
Received: from BY2PRD0710HT005.namprd07.prod.outlook.com (157.56.236.133) by CO9EHSMHS009.bigfish.com (10.236.130.19) with Microsoft SMTP Server (TLS) id 14.1.225.23; Mon, 14 Jan 2013 07:50:38 +0000
Received: from BY2PRD0710MB354.namprd07.prod.outlook.com ([169.254.9.165]) by BY2PRD0710HT005.namprd07.prod.outlook.com ([10.255.86.40]) with mapi id 14.16.0257.004; Mon, 14 Jan 2013 07:50:38 +0000
From: Stephan Wenger <stewe@stewe.org>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Subject: Re: Last Call: <draft-farrell-ft-03.txt> (A Fast-Track way to RFC with Running Code) to Experimental RFC
Thread-Topic: Last Call: <draft-farrell-ft-03.txt> (A Fast-Track way to RFC with Running Code) to Experimental RFC
Thread-Index: AQHN8D7r3XY8HwCadU+f4XzrwHls7phGBgCAgAJ10YA=
Date: Mon, 14 Jan 2013 07:50:37 +0000
Message-ID: <FDBFA77C7400C74F87BC297393B53E3532B15771@BY2PRD0710MB354.namprd07.prod.outlook.com>
In-Reply-To: <50F1AC5B.3070608@cs.tcd.ie>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.255.86.4]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <3892A8F118A8A74DBF4EEEC5F1B80C8A@namprd07.prod.outlook.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: stewe.org
Cc: "adrian@olddog.co.uk" <adrian@olddog.co.uk>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Jan 2013 07:50:59 -0000

Hi,
Please see inline.
Stephan

On 1.12.2013 10:32 , "Stephen Farrell" <stephen.farrell@cs.tcd.ie> wrote:

>
>Hiya,
>
>On 01/11/2013 09:02 PM, Stephan Wenger wrote:
[...]
>
>>  Still, there is one reference that worries me, and that is the
>>reference
>> to GPLv3 code as an "extreme" in section 2.1.  Yes, the GPL (and similar
>> copyleft licenses) is an extreme, at least in terms of open source
>> licensing models.  However, it is not an extreme of openness or
>> accessibility of the source code for review by WG chair, AD, and
>> community.  I would hope that we are all aware that many (most?)
>> commercial software developers, by company policy or common sense, avoid
>> looking at GPL-ed code, out of fear of contamination of their own closed
>> source code. =20
>
><rant>
>
>I am aware that lawyers and others do encourage ignorance in such
>ways. Its an incredibly stupid way to behave IMO even if understandable
>in a horrendously short-sighted kind of way.

I understand that this is a rant.  And, I'm not ranting back, even if
tempted.  Well, maybe a little.  That said, I would like to understand the
"ignorance" part. =20

It is factually true that there is a risk of contamination, and a risk of
being required to publish formerly closed source code under a very onerous
license (patent rights, whatnot) when a developer exposes himself/herself
to GPLed code.  I'm not including citation showing this at this point
(call it time and space constraints, and off-topic--but it's easy enough
to do), but the logic is approximately: copyleft licenses require to grant
back derivative work in source code form, and inclusion of GPLed code
fragments into your source code can be viewed as derivative work.
Publishing source code can (and in most cases, is) not a strategy closed
source companies follow.

If a Free Software developer, probably with the help of folks like the
SFLC, sue your company over alleged creation of derivative work from GPLed
code without granting that source code back, you need to defend yourself,
or publish the code under the GPL with all its onerous conditions (again,
patent license and whatnot).  Whether fair use, de minimis, or similar
theories apply for a specific case depends on the amount of included GPLed
code, legislation, the quality of your lawyer and the one on the other
side, and so on.  In most cases of accidental contamination, it is IMO
likely that you get of the hook easily enough, and even more likely that
no one is suing you.  Still, even the smallest legal action is costly.

For this reason, in most closed source companies I'm aware off, GPLed code
is off-limits for developers and/or for all employees, perhaps minus those
folks in the IT department which are not involved in product development
but deal with production servers and such.  It's common business sense.

It's OK if you don't like that business model.  It's ok if you like "Free
Software" and its business model.  Form a religion about the so-called
"Free Software" model, for all I care.  (Oh wait, there is already one :-)
 However, I do not believe that your draft, and especially the section in
question, is the right place to do so.

[...]
>
></rant>
>
>> GPL-ed code  is, therefore, inaccessible for verification by
>> a large part of the IETF community, and does not serve as a good example
>> for "openness", which is how I interpret the spectrum laid out in
>>section
>> 2.1.  A better example would be source code that is almost universally
>> accessible.  The extreme here would be source code in the public domain.
>> Somewhat less convincing but perhaps a bit more realistically, source
>>code
>> under a BSD-style license like the one the IETF Trust is using.
>
>I'm not at all sure what concrete suggestion you're making, other
>than disparaging GPL. If your suggestion is s/GPLv3/BSD license/
>then that could be done but would make no difference at all to
>this draft, so I plan to leave this as-is.

Yes, I'm arguing in favor of replacing "GPL" with "BSD", or, even better,
with "public domain".  To rephrase the reason for it: ideally, in order to
verify "matching" between software and specification, the software would
need to be accessible to as many people (in practice: IETF participants)
as possible.  One extreme is correctly identified: closed source code is,
in almost all cases, accessible only to a very small group of people.  The
other extreme is "public domain" source code, where no reasonable lawyer
or business guy has a reason to tell their developers to not touch it.
BSD licensed code comes close, and is more common.

The GPLed code is not at one of the extremes, but middle ground.  I would
wager a guess that perhaps less than half of the IETF participants are
allowed to check GPLed code for something as business-uncritical as
fast-tracking a draft.  Therefore, GPLed code should not be an example for
universally accessible and verifiable code.

Clearer?  Please reconsider your position.

>
>> Second, the draft suggest that the existence of an implementation of the
>> specification should serve as a shortcut towards RFC, presumably because
>> such an implementation speak favorably to the implementability of the
>> specification.  That, however, is not universally true.
>
>Very few things in the IETF are universally true;-)
>
>> Specifically, if
>> implementer and spec writer are the same person (or part of the same
>> team), it is quite likely that the spec takes certain assumptions made
>>by
>> the implementers for granted, and does not document it.  That would be a
>> bad spec, accessible implementation or not.  The solution to this issue
>>is
>> IMO not, as the draft appears to be to suggest, to put burden on WG
>>chairs
>> and ADs to ensure that the spec and the implementation match.  Both WG
>> chairs and ADs have enough to do, and the incentive for rubber-stamping
>>is
>> quite high.  A more sensible solution may be to require that the
>> implementer is unaffiliated with the spec author; in other words, the
>> implementation is derived from the spec + IETF discussion context.
>
>That's a fair point but, a) we don't consider affiliations like that
>in the IETF, at least not in a written-rules kind of way,

"Affiliation" was not meant as "same employer". Clearly, same team in the
same company is a problem.  Co-developer in the same (small) open source
project is a problem.  US-based Office of CTO full-time standardizer (of
which the IETF has a fair share, we may like it or not) and code-grunts in
China are IMO not a problem, even if they work for the same mega-company.
There may be a better word than "affiliated" to describe this
relationship.  That word escapes me, though.  (Standard excuse: not an
English native speaker.)


>and b) there's
>nothing in principle wrong with the editor writing code.

For the purpose of short-cutting an approval mechanism (and only in this
context), I disagree, for the reasons already mentioned.  Outside of that
context, I'm fully with you, and I wish there would be more of those
multi-purpose types.

>While it
>is better if the code is written independent of the editor and even
>better if someone who hasn't been involved in the WG has done the
>coding, that'd be too high a burden to require IMO, especially given
>that this is an experiment.

Ack.

>
>I'd have no problem adding text that encouraged some form of
>independence though, if you'd like to provide some.

How about:

"If the source code has been developed independently of the authoring of
the draft (and ideally by non WG participants), it is likely that the
implementation and the draft match, and that pitfalls unaware developers
may find have been found and dealt with.  If, on the other hand, draft
author(s) and implementation developer(s) overlap, then it is sensible to
scrutinize the draft more closely, both with respect to its match with the
implementation and for assumptions that author/developer may have taken
for granted which warrant documentation in the draft."
=20
>
>> A third comment would be that, if you interpret the draft strictly, it
>>is
>> highly unlikely that the experiment would ever be exercised, as the
>> implementation needs to "match" the draft to be advanced, and that would
>> mean that the implementation has to follow in lockstep with the draft
>> development up until the final version.  With respect to the core
>>subject
>> matter of a draft, that may be fine.  However, many of the final edits
>>in
>> a draft come as input from IETF wide community review; things like
>> security, congestion control, and the like.  Those are often trivial to
>> write down, but can have a major implementation impact.  To cure this,
>>it
>> would IMO be acceptable if the implementation would be required to match
>> the latest or a reasonably young, i.e. a few months old version of the
>> draft.
>
>Another fair point but again one where its not really possible to
>describe a rule that'd be better and more precise than "match."
>I don't think a rule mentioning earlier or older drafts would be
>useful for this.
>
>I'll see if I can come up with something better than "match" but
>if you have text to suggest, that might help.

Trying:

"Match means that all, or substantially all, protocol mechanisms of the
draft are implemented, that no other code points are implemented that
would reasonably fall into the scope of the draft in question, that all
documented state machines are implemented and no other state machines, and
so forth.  The over-the-wire behavior of the implementation and of the
draft should substantially match, including more subtle points such as
timing relationship of messages, .  Minor divergences in details stemming
from unaligned development cycles of draft and implementation are
acceptable."

>
>Cheers,
>S.
>
>>=20
>> Please consider this.
>> Thanks,
>> Stephan
>>  =20
>>=20
>> On 1.11.2013 08:21 , "Adrian Farrel" <adrian@olddog.co.uk> wrote:
>>=20
>>> Hi Alexa,
>>>
>>> Please be aware of this document that has just entered a four-week IETF
>>> last
>>> call. The document describes a proposed IETF process experiment under
>>>the
>>> rules
>>> of RFC 3933.
>>>
>>> The proposed experiment calls on the IETF Secretariat to take specific
>>> actions
>>> under certain circumstances in corner cases of the experiment. Could
>>>you
>>> please
>>> have someone in the Secretariat look at the draft and comment on the
>>> practicalities of the actions. Note that, at this stage, no changes to
>>> the tools
>>> are proposed so any actions would require manual intervention (if the
>>> experiment
>>> were successful and resulted in permanent changes to IETF process we
>>> might make
>>> changes to the tools at some future time).
>>>
>>> Thanks,
>>> Adrian
>>>
>>>> -----Original Message-----
>>>> From: ietf-announce-bounces@ietf.org [mailto:ietf-announce-
>>>> bounces@ietf.org] On Behalf Of The IESG
>>>> Sent: 11 January 2013 15:15
>>>> To: IETF-Announce
>>>> Subject: Last Call: <draft-farrell-ft-03.txt> (A Fast-Track way to RFC
>>>> with
>>> Running
>>>> Code) to Experimental RFC
>>>>
>>>>
>>>> The IESG has received a request from an individual submitter to
>>>>consider
>>>> the following document:
>>>> - 'A Fast-Track way to RFC with Running Code'
>>>>   <draft-farrell-ft-03.txt> as Experimental RFC
>>>>
>>>> The IESG plans to make a decision in the next few weeks, and solicits
>>>> final comments on this action. Please send substantive comments to the
>>>> ietf@ietf.org mailing lists by 2013-02-08. Exceptionally, comments may
>>>> be
>>>> sent to iesg@ietf.org instead. In either case, please retain the
>>>> beginning of the Subject line to allow automated sorting.
>>>>
>>>> Abstract
>>>>
>>>>    This memo describes an optional, fast-track way to progress a
>>>>working
>>>>    group document to IESG review.  It is provided as a process
>>>>    experiment as defined in RFC 3933 for use when working group chairs
>>>>    believe that there is running code that implements a working group
>>>>    Internet-Draft.  The motivation is to have the IETF process
>>>>    explicitly consider running code, consistent with the IETF's
>>>>overall
>>>>    philosophy of running code and rough consensus.
>>>>
>>>>    In this process all of working group last call, IETF last call, and
>>>>    Area Director review are carried out in the same two week period.
>>>>    Only comments that meet IESG Discuss criteria need to be addressed
>>>>    during this stage, and authors are required to make any changes
>>>>    within two weeks.
>>>>
>>>>    This experiment will run for one year.
>>>>
>>>>
>>>> The file can be obtained via
>>>> http://datatracker.ietf.org/doc/draft-farrell-ft/
>>>>
>>>> IESG discussion can be tracked via
>>>> http://datatracker.ietf.org/doc/draft-farrell-ft/ballot/
>>>>
>>>> No IPR declarations have been submitted directly on this I-D.
>>>
>>>
>>=20
>>=20
>>=20
>



From petithug@acm.org  Mon Jan 14 01:08:19 2013
Return-Path: <petithug@acm.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BCDD511E8099 for <ietf@ietfa.amsl.com>; Mon, 14 Jan 2013 01:08:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.439
X-Spam-Level: 
X-Spam-Status: No, score=-102.439 tagged_above=-999 required=5 tests=[AWL=0.161, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
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 dbV-c-n0uhuR for <ietf@ietfa.amsl.com>; Mon, 14 Jan 2013 01:08:18 -0800 (PST)
Received: from implementers.org (implementers.org [IPv6:2604:3400:dc1:41:216:3eff:fe5b:8240]) by ietfa.amsl.com (Postfix) with ESMTP id 8EDCB21F8B90 for <ietf@ietf.org>; Mon, 14 Jan 2013 01:08:18 -0800 (PST)
Received: from [IPv6:2601:9:4b80:32:5415:9366:4865:dda8] (unknown [IPv6:2601:9:4b80:32:5415:9366:4865:dda8]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (Client CN "Marc Petit-Huguenin", Issuer "implementers.org" (verified OK)) by implementers.org (Postfix) with ESMTPS id 7E56D20373; Mon, 14 Jan 2013 09:08:16 +0000 (UTC)
Message-ID: <50F3CB0C.1040004@acm.org>
Date: Mon, 14 Jan 2013 01:08:28 -0800
From: Marc Petit-Huguenin <petithug@acm.org>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.11) Gecko/20121122 Icedove/10.0.11
MIME-Version: 1.0
To: Stephan Wenger <stewe@stewe.org>
Subject: Re: Last Call: <draft-farrell-ft-03.txt> (A Fast-Track way to RFC with Running Code) to Experimental RFC
References: <FDBFA77C7400C74F87BC297393B53E3532B13559@BY2PRD0710MB354.namprd07.prod.outlook.com>
In-Reply-To: <FDBFA77C7400C74F87BC297393B53E3532B13559@BY2PRD0710MB354.namprd07.prod.outlook.com>
X-Enigmail-Version: 1.4.1
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: "adrian@olddog.co.uk" <adrian@olddog.co.uk>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Jan 2013 09:08:20 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On 01/11/2013 01:02 PM, Stephan Wenger wrote:
> Hi,
> 
> Sorry for replying to this "advise to secretariat" thread and not to the 
> ietf-announce thread--I'm not subscribed to ietf-announce. I have three
> comments, and regret that I have not followed all of the discussions
> regarding this draft before, so please advise if those comments have
> already been raised and/or resolved.
> 
> 
> First, I'm glad that the direct preferences of open source implementations 
> over implementations compliant with other business models are mostly gone. 
> Still, there is one reference that worries me, and that is the reference to
> GPLv3 code as an "extreme" in section 2.1.  Yes, the GPL (and similar 
> copyleft licenses) is an extreme, at least in terms of open source 
> licensing models.  However, it is not an extreme of openness or 
> accessibility of the source code for review by WG chair, AD, and community.
> I would hope that we are all aware that many (most?) commercial software
> developers, by company policy or common sense, avoid looking at GPL-ed
> code, out of fear of contamination of their own closed source code.  GPL-ed
> code  is, therefore, inaccessible for verification by a large part of the
> IETF community,

Commercial software developers can do whatever they want, how idiotic it is
(see Oracle vs Google), that does not make them an example to follow.

I think that you underestimate the IETF community, who certainly know how to
see through all the FUD about the GPL.  Sure it may be a bad idea to literally
copy 300 lines of GPL code in your code, but that does not apply to what we
are talking about, which is reading code.

> and does not serve as a good example for "openness", which is how I
> interpret the spectrum laid out in section 2.1.  A better example would be
> source code that is almost universally accessible.  The extreme here would
> be source code in the public domain. Somewhat less convincing but perhaps a
> bit more realistically, source code under a BSD-style license like the one
> the IETF Trust is using.


- -- 
Marc Petit-Huguenin
Email: marc@petit-huguenin.org
Blog: http://blog.marc.petit-huguenin.org
Profile: http://www.linkedin.com/in/petithug
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iQIcBAEBCAAGBQJQ88sKAAoJECnERZXWan7ECfIP/RVps46nNG9HCpO96nq4JBIL
T1huBNLerYdB9Q1sYHH0B6TxRQMVxZOe11foOiqdm80qlqirwNKPCh4IBobDNYCr
3RIkd/N6CQNjrmTkobr7Vnfk2/E95i7mvkKUxco03tLBsDPqHhZsnrtRdcbDcXgz
w79C46auyL5ltAoVRS0T3/el5B9cEAvi0CqrzbiCUJrrG0pdpiyn/gFjrJL7ciKk
xZ2E5Mf1HhbpljDsk6Fh90zo+GT11lXo7C3mZyUHtraJfC8HLkt5epYA1zrcM88x
VJEW+OiOkDd49/+BtK8We9Lj8LGuBkiyCEBlJUOkAI5zbPxGPYMqzLcJJd76BgXo
9yhpSUwfr2Vtgwu98/oPUD7X30Suk5da7hN6pQGyHU4ZXlKcNDm30XqKcP7GldTv
CO/NiiBW0qPorcrfBpkxUanneVkk/E1xG3W7r6w22J2IXqIPAma0/U0hGppPo00C
mtY217g9OT+fGJBMxDAJNGEaH6Fak7xcBAMxAcqzj/P9BrSqh+gNgG1PhB6VvD4o
yAVtTpHNL/KsQsl9plcNVTkrnbtYoGAhYsV64w39wZCk/arQFmfZlNchVaDAdkuk
1Njt7IzkqH4YaGPyb9NU9bhwF2TNKvaI3RuoVvaLVxCJdRGukgp8n2wbtsPDpwd2
GzR+a9frCq6XxYvoZ8qN
=+5ox
-----END PGP SIGNATURE-----

From lars@netapp.com  Mon Jan 14 01:10:56 2013
Return-Path: <lars@netapp.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 02A0C21F88AE for <ietf@ietfa.amsl.com>; Mon, 14 Jan 2013 01:10:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.492
X-Spam-Level: 
X-Spam-Status: No, score=-10.492 tagged_above=-999 required=5 tests=[AWL=0.107, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 ttmGQwyVT0vy for <ietf@ietfa.amsl.com>; Mon, 14 Jan 2013 01:10:55 -0800 (PST)
Received: from mx12.netapp.com (mx12.netapp.com [216.240.18.77]) by ietfa.amsl.com (Postfix) with ESMTP id 1155F21F87C8 for <ietf@ietf.org>; Mon, 14 Jan 2013 01:10:55 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.84,466,1355126400";  d="scan'208";a="7539077"
Received: from smtp1.corp.netapp.com ([10.57.156.124]) by mx12-out.netapp.com with ESMTP; 14 Jan 2013 01:10:54 -0800
Received: from vmwexceht03-prd.hq.netapp.com (exchsmtp.hq.netapp.com [10.106.76.241]) by smtp1.corp.netapp.com (8.13.1/8.13.1/NTAP-1.6) with ESMTP id r0E9ArBx000631; Mon, 14 Jan 2013 01:10:54 -0800 (PST)
Received: from VMWEXCEHT06-PRD.hq.netapp.com (10.106.77.104) by vmwexceht03-prd.hq.netapp.com (10.106.76.241) with Microsoft SMTP Server (TLS) id 14.2.328.9; Mon, 14 Jan 2013 01:10:53 -0800
Received: from SACEXCMBX01-PRD.hq.netapp.com ([169.254.2.51]) by vmwexceht06-prd.hq.netapp.com ([10.106.77.104]) with mapi id 14.02.0328.009; Mon, 14 Jan 2013 01:10:53 -0800
From: "Eggert, Lars" <lars@netapp.com>
To: Marc Petit-Huguenin <petithug@acm.org>
Subject: Re: Last Call: <draft-farrell-ft-03.txt> (A Fast-Track way to RFC with Running Code) to Experimental RFC
Thread-Topic: Last Call: <draft-farrell-ft-03.txt> (A Fast-Track way to RFC with Running Code) to Experimental RFC
Thread-Index: Ac3wFdOP9tSRE1tiRE+NhIh/RtqHrgAbCXiAAH3y/AAAABV1AA==
Date: Mon, 14 Jan 2013 09:10:52 +0000
Message-ID: <D4D47BCFFE5A004F95D707546AC0D7E91F61B3C5@SACEXCMBX01-PRD.hq.netapp.com>
References: <FDBFA77C7400C74F87BC297393B53E3532B13559@BY2PRD0710MB354.namprd07.prod.outlook.com> <50F3CB0C.1040004@acm.org>
In-Reply-To: <50F3CB0C.1040004@acm.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.106.53.51]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <022B7976A759E34C8D28D51DF2CA78EC@tahoe.netapp.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "adrian@olddog.co.uk" <adrian@olddog.co.uk>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Jan 2013 09:10:56 -0000

Hi,

On Jan 14, 2013, at 10:08, Marc Petit-Huguenin <petithug@acm.org> wrote:
> I think that you underestimate the IETF community, who certainly know how=
 to
> see through all the FUD about the GPL.  Sure it may be a bad idea to lite=
rally
> copy 300 lines of GPL code in your code, but that does not apply to what =
we
> are talking about, which is reading code.

I have worked for employers before where reading GPL code was considered hi=
ghly problematic.

Lars=

From lars@netapp.com  Mon Jan 14 01:26:21 2013
Return-Path: <lars@netapp.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7D93121F8587 for <ietf@ietfa.amsl.com>; Mon, 14 Jan 2013 01:26:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.096
X-Spam-Level: 
X-Spam-Status: No, score=-10.096 tagged_above=-999 required=5 tests=[AWL=-0.296, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, SARE_SUB_RAND_LETTRS4=0.799]
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 k5Mor-bfJLJG for <ietf@ietfa.amsl.com>; Mon, 14 Jan 2013 01:26:20 -0800 (PST)
Received: from mx12.netapp.com (mx12.netapp.com [216.240.18.77]) by ietfa.amsl.com (Postfix) with ESMTP id C03F621F857C for <ietf@ietf.org>; Mon, 14 Jan 2013 01:26:20 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.84,466,1355126400";  d="scan'208";a="7542793"
Received: from smtp1.corp.netapp.com ([10.57.156.124]) by mx12-out.netapp.com with ESMTP; 14 Jan 2013 01:26:20 -0800
Received: from vmwexceht01-prd.hq.netapp.com (vmwexceht01-prd.hq.netapp.com [10.106.76.239]) by smtp1.corp.netapp.com (8.13.1/8.13.1/NTAP-1.6) with ESMTP id r0E9QKOM014507 for <ietf@ietf.org>; Mon, 14 Jan 2013 01:26:20 -0800 (PST)
Received: from SACEXCMBX01-PRD.hq.netapp.com ([169.254.2.51]) by vmwexceht01-prd.hq.netapp.com ([10.106.76.239]) with mapi id 14.02.0328.009; Mon, 14 Jan 2013 01:26:20 -0800
From: "Eggert, Lars" <lars@netapp.com>
To: "ietf@ietf.org list" <ietf@ietf.org>
Subject: Fwd: [irtf-discuss] New: Software-Defined Networking Research Group (SDNRG)
Thread-Topic: [irtf-discuss] New: Software-Defined Networking Research Group (SDNRG)
Thread-Index: AQHN8jk2XsJOTPQd3EOt8d44ZE5OJg==
Date: Mon, 14 Jan 2013 09:26:19 +0000
Message-ID: <D4D47BCFFE5A004F95D707546AC0D7E91F61C7DE@SACEXCMBX01-PRD.hq.netapp.com>
References: <D4D47BCFFE5A004F95D707546AC0D7E91F61B755@SACEXCMBX01-PRD.hq.netapp.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.106.53.51]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <0E6935DE68EB1F40A57654EE0D4D8265@tahoe.netapp.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Jan 2013 09:26:21 -0000

Begin forwarded message:

> From: "Eggert, Lars" <lars@netapp.com>
> Subject: [irtf-discuss] New: Software-Defined Networking Research Group (=
SDNRG)
> Date: January 14, 2013 10:24:57 GMT+01:00
> To: "<irtf-announce@irtf.org>" <irtf-announce@irtf.org>, "<irtf-discuss@i=
rtf.org>" <irtf-discuss@irtf.org>
> Cc: "sdn@irtf.org" <sdn@irtf.org>
> Reply-To: "irtf-discuss@irtf.org" <irtf-discuss@irtf.org>
>=20
> A new IRTF research group on Software-Defined Networking has been charter=
ed:
>=20
>  The Software-Defined Networking Research Group (SDNRG) investigates SDN
>  from various perspectives with the goal of identifying the approaches th=
at
>  can be defined, deployed and used in the near term as well identifying
>  future research challenges. In particular, key areas of interest include
>  solution scalability, abstractions, and programming languages and paradi=
gms
>  particularly useful in the context of SDN. In addition, it is an explici=
t
>  goal of the SDNRG to provide a forum for researchers to investigate key
>  and interesting problems in the Software-Defined Networking field.
>=20
> Charter and participation information can be found at http://irtf.org/sdn=
rg
>=20
> Lars Eggert
> IRTF Chair
>=20


From petithug@acm.org  Mon Jan 14 01:33:35 2013
Return-Path: <petithug@acm.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5196C21F8700 for <ietf@ietfa.amsl.com>; Mon, 14 Jan 2013 01:33:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.471
X-Spam-Level: 
X-Spam-Status: No, score=-102.471 tagged_above=-999 required=5 tests=[AWL=0.129, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
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 yDj3+YsFzn23 for <ietf@ietfa.amsl.com>; Mon, 14 Jan 2013 01:33:34 -0800 (PST)
Received: from implementers.org (implementers.org [IPv6:2604:3400:dc1:41:216:3eff:fe5b:8240]) by ietfa.amsl.com (Postfix) with ESMTP id 71DB921F876E for <ietf@ietf.org>; Mon, 14 Jan 2013 01:33:34 -0800 (PST)
Received: from [IPv6:2601:9:4b80:32:5415:9366:4865:dda8] (unknown [IPv6:2601:9:4b80:32:5415:9366:4865:dda8]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (Client CN "Marc Petit-Huguenin", Issuer "implementers.org" (verified OK)) by implementers.org (Postfix) with ESMTPS id 381B420373; Mon, 14 Jan 2013 09:33:33 +0000 (UTC)
Message-ID: <50F3D0F9.5030503@acm.org>
Date: Mon, 14 Jan 2013 01:33:45 -0800
From: Marc Petit-Huguenin <petithug@acm.org>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.11) Gecko/20121122 Icedove/10.0.11
MIME-Version: 1.0
To: "Eggert, Lars" <lars@netapp.com>
Subject: Re: Last Call: <draft-farrell-ft-03.txt> (A Fast-Track way to RFC with Running Code) to Experimental RFC
References: <FDBFA77C7400C74F87BC297393B53E3532B13559@BY2PRD0710MB354.namprd07.prod.outlook.com> <50F3CB0C.1040004@acm.org> <D4D47BCFFE5A004F95D707546AC0D7E91F61B3C5@SACEXCMBX01-PRD.hq.netapp.com>
In-Reply-To: <D4D47BCFFE5A004F95D707546AC0D7E91F61B3C5@SACEXCMBX01-PRD.hq.netapp.com>
X-Enigmail-Version: 1.4.1
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: "adrian@olddog.co.uk" <adrian@olddog.co.uk>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Jan 2013 09:33:35 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On 01/14/2013 01:10 AM, Eggert, Lars wrote:
> Hi,
> 
> On Jan 14, 2013, at 10:08, Marc Petit-Huguenin <petithug@acm.org> wrote:
>> I think that you underestimate the IETF community, who certainly know how
>> to see through all the FUD about the GPL.  Sure it may be a bad idea to
>> literally copy 300 lines of GPL code in your code, but that does not
>> apply to what we are talking about, which is reading code.
> 
> I have worked for employers before where reading GPL code was considered
> highly problematic.

Sure, if the IETF is part of your job, and your employer prevents you to read
GPL code (or read Spinoza, or sing under the shower), then do not do it for
the IETF.  Now if your employer does not regulate what you do on your own
time, then there is no problem here.

If someone said to writers to never read any book that is still copyrighted
because they might be contaminated and that may somehow induce them to
plagiarize without knowing it, how do you think they would react?  There is no
difference with software - excepted that there a lot more people that would
like us to think that software is different.

- -- 
Marc Petit-Huguenin
Email: marc@petit-huguenin.org
Blog: http://blog.marc.petit-huguenin.org
Profile: http://www.linkedin.com/in/petithug
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iQIcBAEBCAAGBQJQ89D3AAoJECnERZXWan7EticQAIXvbyfRD/LX9YT+/SiW21Wp
NBuVji+aAPyGaKvwpQ+G1pqrp74hUk2ylvmqOGi9JWc0/E3H/dhyBbksvEHrbyY8
1+4fGKtOAUkAW97IaBaWRQT9jbo7w9TytRVz8o3+Gh0b4qTmTHzBh76zXjS5v2RM
qRHFcCnSitXMUV4Y+PjtP8ZjpTd/J4Ahwsw9xa07WeNQIrfQ3PHYX8tC2xrrAuHm
1on3qI5FuumDjatWwNMhAb+/Sm0XLOiRJifjQxENOfOPW4JtkEcqi9Us3+7fNFMe
Z06qtrCC2oflODJw+7xZwguIJe8V+Eu8ea3wNnVaa3tqqBw+twZT/vhBSehrCgrU
hTSvj9zphutbRK/1xvEkMwggYhUPrwH7GTNKrANYYu8xb9O2MD2OB2OdrwtX4Aax
Z11lBsY7GC0Vum3X/aa+3UWu2cyiBDcDJym+pOvzOYPGJ7aNpEAdlRIYVdE7KV1t
1n7SrK960uX2WE9VgFdWptfm9QXGDjW417PDxlunNUzlY6Xb/C2uaQuuR6gZG7Vi
P3I+Yiz2LvioE3ZwTPDSboLPgbw29g3oEkCBjyfP14KjP2F8MTUfI3S5vTl0ZrAh
RaqkdT6sfREVxFFszyeAhDDAcXGkzvkZd1wgHwfw1HcKLlTUH6QNPVT5OGsA3DLQ
7CYGpSyyjONrEgZqxBXD
=/ZJe
-----END PGP SIGNATURE-----

From stewe@stewe.org  Mon Jan 14 01:44:30 2013
Return-Path: <stewe@stewe.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EA86421F8726 for <ietf@ietfa.amsl.com>; Mon, 14 Jan 2013 01:44:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[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 MHEVn6PqocsE for <ietf@ietfa.amsl.com>; Mon, 14 Jan 2013 01:44:30 -0800 (PST)
Received: from tx2outboundpool.messaging.microsoft.com (tx2ehsobe001.messaging.microsoft.com [65.55.88.11]) by ietfa.amsl.com (Postfix) with ESMTP id 17D0A21F870E for <ietf@ietf.org>; Mon, 14 Jan 2013 01:44:29 -0800 (PST)
Received: from mail166-tx2-R.bigfish.com (10.9.14.243) by TX2EHSOBE004.bigfish.com (10.9.40.24) with Microsoft SMTP Server id 14.1.225.23; Mon, 14 Jan 2013 09:44:29 +0000
Received: from mail166-tx2 (localhost [127.0.0.1])	by mail166-tx2-R.bigfish.com (Postfix) with ESMTP id 358C810015E; Mon, 14 Jan 2013 09:44:29 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.236.133; KIP:(null); UIP:(null); IPV:NLI; H:BY2PRD0710HT005.namprd07.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: -9
X-BigFish: PS-9(z10d0kzbb2dI98dI154cP9371I1432I1418I4015I62a3Izz1ee6h1de0h1202h1e76h1d1ah1d2ah1082kzz1954cbh17326ah8275bh8275dhz2fh2a8h668h839h946hd25hf0ah1288h12a5h12a9h12bdh137ah13b6h1441h1504h1537h153bh15d0h162dh1631h1758h1155h)
Received-SPF: pass (mail166-tx2: domain of stewe.org designates 157.56.236.133 as permitted sender) client-ip=157.56.236.133; envelope-from=stewe@stewe.org; helo=BY2PRD0710HT005.namprd07.prod.outlook.com ; .outlook.com ; 
Received: from mail166-tx2 (localhost.localdomain [127.0.0.1]) by mail166-tx2 (MessageSwitch) id 1358156667378741_8095; Mon, 14 Jan 2013 09:44:27 +0000 (UTC)
Received: from TX2EHSMHS011.bigfish.com (unknown [10.9.14.250])	by mail166-tx2.bigfish.com (Postfix) with ESMTP id 92A062C0057; Mon, 14 Jan 2013 09:44:23 +0000 (UTC)
Received: from BY2PRD0710HT005.namprd07.prod.outlook.com (157.56.236.133) by TX2EHSMHS011.bigfish.com (10.9.99.111) with Microsoft SMTP Server (TLS) id 14.1.225.23; Mon, 14 Jan 2013 09:43:39 +0000
Received: from BY2PRD0710MB354.namprd07.prod.outlook.com ([169.254.9.165]) by BY2PRD0710HT005.namprd07.prod.outlook.com ([10.255.86.40]) with mapi id 14.16.0257.004; Mon, 14 Jan 2013 09:43:29 +0000
From: Stephan Wenger <stewe@stewe.org>
To: Marc Petit-Huguenin <petithug@acm.org>, "Eggert, Lars" <lars@netapp.com>
Subject: Re: Last Call: <draft-farrell-ft-03.txt> (A Fast-Track way to RFC with Running Code) to Experimental RFC
Thread-Topic: Last Call: <draft-farrell-ft-03.txt> (A Fast-Track way to RFC with Running Code) to Experimental RFC
Thread-Index: AQHN8jpGfZSDQWG05E+8GQR351mbnphIo4AA
Date: Mon, 14 Jan 2013 09:43:28 +0000
Message-ID: <FDBFA77C7400C74F87BC297393B53E3532B1595B@BY2PRD0710MB354.namprd07.prod.outlook.com>
In-Reply-To: <50F3D0F9.5030503@acm.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.255.86.4]
Content-Type: text/plain; charset="Windows-1252"
Content-ID: <8A8117BFBE072D47A010B72834B73136@namprd07.prod.outlook.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: stewe.org
Cc: "adrian@olddog.co.uk" <adrian@olddog.co.uk>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Jan 2013 09:44:31 -0000

Inline.
S.


On 1.14.2013 10:33 , "Marc Petit-Huguenin" <petithug@acm.org> wrote:

>-----BEGIN PGP SIGNED MESSAGE-----
>Hash: SHA256
>
>On 01/14/2013 01:10 AM, Eggert, Lars wrote:
>> Hi,
>>=20
>> On Jan 14, 2013, at 10:08, Marc Petit-Huguenin <petithug@acm.org> wrote:
>>> I think that you underestimate the IETF community, who certainly know
>>>how
>>> to see through all the FUD about the GPL.  Sure it may be a bad idea to
>>> literally copy 300 lines of GPL code in your code, but that does not
>>> apply to what we are talking about, which is reading code.
>>=20
>> I have worked for employers before where reading GPL code was considered
>> highly problematic.
>
>Sure, if the IETF is part of your job, and your employer prevents you to
>read
>GPL code (or read Spinoza, or sing under the shower), then do not do it
>for
>the IETF.  Now if your employer does not regulate what you do on your own
>time, then there is no problem here.
>
>If someone said to writers to never read any book that is still
>copyrighted
>because they might be contaminated and that may somehow induce them to
>plagiarize without knowing it, how do you think they would react?

Many would laugh.  Some politicians in Germany, who were recently found
that they plagiarized in the PhD theses, would probably not=8A  Their risk
is low, though.

>There is no
>difference with software - excepted that there a lot more people that
>would
>like us to think that software is different.

This is incorrect.  If you are found to infringe on someone's copyright in
a book you put together, you have a copyright problem (only).  If you are
found to infringe on certain open source licenses (including the GPL
variants, but by no means limited to them), and the rightholder forces you
to take a license, you also have to provide a patent license under terms
you may not like.  Even if you don't take a license, it is quite possible
that you have (by copying GPLed code) provided in implied patent license.

Please don't oversimplify.

Thanks,
Stephan

>
>- --=20
>Marc Petit-Huguenin
>Email: marc@petit-huguenin.org
>Blog: http://blog.marc.petit-huguenin.org
>Profile: http://www.linkedin.com/in/petithug
>-----BEGIN PGP SIGNATURE-----
>Version: GnuPG v1.4.12 (GNU/Linux)
>
>iQIcBAEBCAAGBQJQ89D3AAoJECnERZXWan7EticQAIXvbyfRD/LX9YT+/SiW21Wp
>NBuVji+aAPyGaKvwpQ+G1pqrp74hUk2ylvmqOGi9JWc0/E3H/dhyBbksvEHrbyY8
>1+4fGKtOAUkAW97IaBaWRQT9jbo7w9TytRVz8o3+Gh0b4qTmTHzBh76zXjS5v2RM
>qRHFcCnSitXMUV4Y+PjtP8ZjpTd/J4Ahwsw9xa07WeNQIrfQ3PHYX8tC2xrrAuHm
>1on3qI5FuumDjatWwNMhAb+/Sm0XLOiRJifjQxENOfOPW4JtkEcqi9Us3+7fNFMe
>Z06qtrCC2oflODJw+7xZwguIJe8V+Eu8ea3wNnVaa3tqqBw+twZT/vhBSehrCgrU
>hTSvj9zphutbRK/1xvEkMwggYhUPrwH7GTNKrANYYu8xb9O2MD2OB2OdrwtX4Aax
>Z11lBsY7GC0Vum3X/aa+3UWu2cyiBDcDJym+pOvzOYPGJ7aNpEAdlRIYVdE7KV1t
>1n7SrK960uX2WE9VgFdWptfm9QXGDjW417PDxlunNUzlY6Xb/C2uaQuuR6gZG7Vi
>P3I+Yiz2LvioE3ZwTPDSboLPgbw29g3oEkCBjyfP14KjP2F8MTUfI3S5vTl0ZrAh
>RaqkdT6sfREVxFFszyeAhDDAcXGkzvkZd1wgHwfw1HcKLlTUH6QNPVT5OGsA3DLQ
>7CYGpSyyjONrEgZqxBXD
>=3D/ZJe
>-----END PGP SIGNATURE-----
>



From stephen.farrell@cs.tcd.ie  Mon Jan 14 01:47:11 2013
Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6448221F87A4 for <ietf@ietfa.amsl.com>; Mon, 14 Jan 2013 01:47:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.435
X-Spam-Level: 
X-Spam-Status: No, score=-102.435 tagged_above=-999 required=5 tests=[AWL=0.164, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 8DsUqSAO+bsL for <ietf@ietfa.amsl.com>; Mon, 14 Jan 2013 01:47:10 -0800 (PST)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) by ietfa.amsl.com (Postfix) with ESMTP id 9AD1A21F870E for <ietf@ietf.org>; Mon, 14 Jan 2013 01:47:09 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id B6A0FBE25; Mon, 14 Jan 2013 09:46:47 +0000 (GMT)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id b78PW3HXMtD3; Mon, 14 Jan 2013 09:46:41 +0000 (GMT)
Received: from [IPv6:2001:770:10:203:fc59:2c8:a489:8ef3] (unknown [IPv6:2001:770:10:203:fc59:2c8:a489:8ef3]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 9278ABE3B; Mon, 14 Jan 2013 09:46:41 +0000 (GMT)
Message-ID: <50F3D402.9060106@cs.tcd.ie>
Date: Mon, 14 Jan 2013 09:46:42 +0000
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130106 Thunderbird/17.0.2
MIME-Version: 1.0
To: Stephan Wenger <stewe@stewe.org>
Subject: Re: Last Call: <draft-farrell-ft-03.txt> (A Fast-Track way to RFC with Running Code) to Experimental RFC
References: <FDBFA77C7400C74F87BC297393B53E3532B15771@BY2PRD0710MB354.namprd07.prod.outlook.com>
In-Reply-To: <FDBFA77C7400C74F87BC297393B53E3532B15771@BY2PRD0710MB354.namprd07.prod.outlook.com>
X-Enigmail-Version: 1.5
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: "adrian@olddog.co.uk" <adrian@olddog.co.uk>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Jan 2013 09:47:11 -0000

Hiya,

On 01/14/2013 07:50 AM, Stephan Wenger wrote:
>> <rant>
...
> I understand that this is a rant.  And, I'm not ranting back, even if
> tempted.  
...

Yes, its tempting, but I'm going to resist since its irrelevant IMO.

...
>> </rant>

>> I'm not at all sure what concrete suggestion you're making, other
>> than disparaging GPL. If your suggestion is s/GPLv3/BSD license/
>> then that could be done but would make no difference at all to
>> this draft, so I plan to leave this as-is.
> 
> Yes, I'm arguing in favor of replacing "GPL" with "BSD", or, even better,
> with "public domain".  To rephrase the reason for it: ideally, in order to
> verify "matching" between software and specification, the software would
> need to be accessible to as many people (in practice: IETF participants)
> as possible.  One extreme is correctly identified: closed source code is,
> in almost all cases, accessible only to a very small group of people.  The
> other extreme is "public domain" source code, where no reasonable lawyer
> or business guy has a reason to tell their developers to not touch it.
> BSD licensed code comes close, and is more common.
> 
> The GPLed code is not at one of the extremes, but middle ground.  I would
> wager a guess that perhaps less than half of the IETF participants are
> allowed to check GPLed code for something as business-uncritical as
> fast-tracking a draft.  Therefore, GPLed code should not be an example for
> universally accessible and verifiable code.
> 
> Clearer?  Please reconsider your position.

Yes, that's clearer. We're talking about two different continuums
(or continua:-), so either would work, and neither is important to
this draft. I'll make the change if there's enough support for it,
but as I guess you can see, this is an area where we won't get folks
to entirely agree. In this case, we don't need to, since the text
in question is just explanatory and has no significant impact on
the experiment at all.

(BTW, I'll just note in passing that this kind of contentious
irrelevancy is exactly the kind of thing that an author/editor
running the experiment could freely ignore as not meeting the
discuss criteria. That'd be nice, but doesn't apply this time
unfortunately;-)

>>> Second, the draft suggest that the existence of an implementation of the
>>> specification should serve as a shortcut towards RFC, presumably because
>>> such an implementation speak favorably to the implementability of the
>>> specification.  That, however, is not universally true.
>>
>> Very few things in the IETF are universally true;-)
>>
>>> Specifically, if
>>> implementer and spec writer are the same person (or part of the same
>>> team), it is quite likely that the spec takes certain assumptions made
>>> by
>>> the implementers for granted, and does not document it.  That would be a
>>> bad spec, accessible implementation or not.  The solution to this issue
>>> is
>>> IMO not, as the draft appears to be to suggest, to put burden on WG
>>> chairs
>>> and ADs to ensure that the spec and the implementation match.  Both WG
>>> chairs and ADs have enough to do, and the incentive for rubber-stamping
>>> is
>>> quite high.  A more sensible solution may be to require that the
>>> implementer is unaffiliated with the spec author; in other words, the
>>> implementation is derived from the spec + IETF discussion context.
>>
>> That's a fair point but, a) we don't consider affiliations like that
>> in the IETF, at least not in a written-rules kind of way,
> 
> "Affiliation" was not meant as "same employer". Clearly, same team in the
> same company is a problem.  Co-developer in the same (small) open source
> project is a problem.  US-based Office of CTO full-time standardizer (of
> which the IETF has a fair share, we may like it or not) and code-grunts in
> China are IMO not a problem, even if they work for the same mega-company.
> There may be a better word than "affiliated" to describe this
> relationship.  That word escapes me, though.  (Standard excuse: not an
> English native speaker.)
> 
> 
>> and b) there's
>> nothing in principle wrong with the editor writing code.
> 
> For the purpose of short-cutting an approval mechanism (and only in this

s/short-cutting/speeding up/

> context), I disagree, for the reasons already mentioned.  Outside of that
> context, I'm fully with you, and I wish there would be more of those
> multi-purpose types.
> 
>> While it
>> is better if the code is written independent of the editor and even
>> better if someone who hasn't been involved in the WG has done the
>> coding, that'd be too high a burden to require IMO, especially given
>> that this is an experiment.
> 
> Ack.
> 
>>
>> I'd have no problem adding text that encouraged some form of
>> independence though, if you'd like to provide some.
> 
> How about:
> 
> "If the source code has been developed independently of the authoring of
> the draft (and ideally by non WG participants), it is likely that the
> implementation and the draft match, and that pitfalls unaware developers
> may find have been found and dealt with.  If, on the other hand, draft
> author(s) and implementation developer(s) overlap, then it is sensible to
> scrutinize the draft more closely, both with respect to its match with the
> implementation and for assumptions that author/developer may have taken
> for granted which warrant documentation in the draft."

That'd be no harm to add. I don't know that it improves the document
enough to bother though. I'll think about it, but let's see if anyone
else cares.

>>> A third comment would be that, if you interpret the draft strictly, it
>>> is
>>> highly unlikely that the experiment would ever be exercised, as the
>>> implementation needs to "match" the draft to be advanced, and that would
>>> mean that the implementation has to follow in lockstep with the draft
>>> development up until the final version.  With respect to the core
>>> subject
>>> matter of a draft, that may be fine.  However, many of the final edits
>>> in
>>> a draft come as input from IETF wide community review; things like
>>> security, congestion control, and the like.  Those are often trivial to
>>> write down, but can have a major implementation impact.  To cure this,
>>> it
>>> would IMO be acceptable if the implementation would be required to match
>>> the latest or a reasonably young, i.e. a few months old version of the
>>> draft.
>>
>> Another fair point but again one where its not really possible to
>> describe a rule that'd be better and more precise than "match."
>> I don't think a rule mentioning earlier or older drafts would be
>> useful for this.
>>
>> I'll see if I can come up with something better than "match" but
>> if you have text to suggest, that might help.
> 
> Trying:
> 
> "Match means that all, or substantially all, protocol mechanisms of the
> draft are implemented, that no other code points are implemented that
> would reasonably fall into the scope of the draft in question, that all
> documented state machines are implemented and no other state machines, and
> so forth.  The over-the-wire behavior of the implementation and of the
> draft should substantially match, including more subtle points such as
> timing relationship of messages, .  Minor divergences in details stemming
> from unaligned development cycles of draft and implementation are
> acceptable."

I like most of that, thanks. For now, I've added this to 2.1, let me
know if it works:

   We do not give a precise definition for "match" here but the intent
   is that all, or substantially all, protocol mechanisms of the draft
   are implemented, that the over-the-wire behavior of the
   implementation and of the draft should substantially match, including
   more subtle points such as timing relationship of messages, etc.
   Minor divergences in details stemming from unaligned development
   cycles of draft and implementation are acceptable.

Cheers,
S.

PS: There's a working draft at [1] in case that helps.

[1] http://down.dsg.cs.tcd.ie/misc/draft-farrell-ft-04.txt


> 
>>
>> Cheers,
>> S.
>>
>>>
>>> Please consider this.
>>> Thanks,
>>> Stephan
>>>   
>>>
>>> On 1.11.2013 08:21 , "Adrian Farrel" <adrian@olddog.co.uk> wrote:
>>>
>>>> Hi Alexa,
>>>>
>>>> Please be aware of this document that has just entered a four-week IETF
>>>> last
>>>> call. The document describes a proposed IETF process experiment under
>>>> the
>>>> rules
>>>> of RFC 3933.
>>>>
>>>> The proposed experiment calls on the IETF Secretariat to take specific
>>>> actions
>>>> under certain circumstances in corner cases of the experiment. Could
>>>> you
>>>> please
>>>> have someone in the Secretariat look at the draft and comment on the
>>>> practicalities of the actions. Note that, at this stage, no changes to
>>>> the tools
>>>> are proposed so any actions would require manual intervention (if the
>>>> experiment
>>>> were successful and resulted in permanent changes to IETF process we
>>>> might make
>>>> changes to the tools at some future time).
>>>>
>>>> Thanks,
>>>> Adrian
>>>>
>>>>> -----Original Message-----
>>>>> From: ietf-announce-bounces@ietf.org [mailto:ietf-announce-
>>>>> bounces@ietf.org] On Behalf Of The IESG
>>>>> Sent: 11 January 2013 15:15
>>>>> To: IETF-Announce
>>>>> Subject: Last Call: <draft-farrell-ft-03.txt> (A Fast-Track way to RFC
>>>>> with
>>>> Running
>>>>> Code) to Experimental RFC
>>>>>
>>>>>
>>>>> The IESG has received a request from an individual submitter to
>>>>> consider
>>>>> the following document:
>>>>> - 'A Fast-Track way to RFC with Running Code'
>>>>>   <draft-farrell-ft-03.txt> as Experimental RFC
>>>>>
>>>>> The IESG plans to make a decision in the next few weeks, and solicits
>>>>> final comments on this action. Please send substantive comments to the
>>>>> ietf@ietf.org mailing lists by 2013-02-08. Exceptionally, comments may
>>>>> be
>>>>> sent to iesg@ietf.org instead. In either case, please retain the
>>>>> beginning of the Subject line to allow automated sorting.
>>>>>
>>>>> Abstract
>>>>>
>>>>>    This memo describes an optional, fast-track way to progress a
>>>>> working
>>>>>    group document to IESG review.  It is provided as a process
>>>>>    experiment as defined in RFC 3933 for use when working group chairs
>>>>>    believe that there is running code that implements a working group
>>>>>    Internet-Draft.  The motivation is to have the IETF process
>>>>>    explicitly consider running code, consistent with the IETF's
>>>>> overall
>>>>>    philosophy of running code and rough consensus.
>>>>>
>>>>>    In this process all of working group last call, IETF last call, and
>>>>>    Area Director review are carried out in the same two week period.
>>>>>    Only comments that meet IESG Discuss criteria need to be addressed
>>>>>    during this stage, and authors are required to make any changes
>>>>>    within two weeks.
>>>>>
>>>>>    This experiment will run for one year.
>>>>>
>>>>>
>>>>> The file can be obtained via
>>>>> http://datatracker.ietf.org/doc/draft-farrell-ft/
>>>>>
>>>>> IESG discussion can be tracked via
>>>>> http://datatracker.ietf.org/doc/draft-farrell-ft/ballot/
>>>>>
>>>>> No IPR declarations have been submitted directly on this I-D.
>>>>
>>>>
>>>
>>>
>>>
>>
> 
> 
> 
> 

From stephen.farrell@cs.tcd.ie  Mon Jan 14 01:49:59 2013
Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D244F21F88BD; Mon, 14 Jan 2013 01:49:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.455
X-Spam-Level: 
X-Spam-Status: No, score=-102.455 tagged_above=-999 required=5 tests=[AWL=0.144, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 5B9NtE0PnGlP; Mon, 14 Jan 2013 01:49:58 -0800 (PST)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) by ietfa.amsl.com (Postfix) with ESMTP id 2AD3521F88BC; Mon, 14 Jan 2013 01:49:58 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id 6E3FBBE3F; Mon, 14 Jan 2013 09:49:36 +0000 (GMT)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vszvH57s7J9u; Mon, 14 Jan 2013 09:49:33 +0000 (GMT)
Received: from [IPv6:2001:770:10:203:fc59:2c8:a489:8ef3] (unknown [IPv6:2001:770:10:203:fc59:2c8:a489:8ef3]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 7724ABE3B; Mon, 14 Jan 2013 09:49:33 +0000 (GMT)
Message-ID: <50F3D4AD.8080108@cs.tcd.ie>
Date: Mon, 14 Jan 2013 09:49:33 +0000
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130106 Thunderbird/17.0.2
MIME-Version: 1.0
To: Bernard Aboba <bernard_aboba@hotmail.com>
Subject: Re: Last Call: <draft-farrell-ft-03.txt> (A Fast-Track way to RFC with Running Code) to Experimental RFC
References: <20130111151453.22161.50884.idtracker@ietfa.amsl.com>, <CADnDZ8-w4Nu0RCgE94yZuBT+y6s176V0_kQsk7d_oBwPtUPhNg@mail.gmail.com> <BLU002-W2232C02D24F3D45F2E76B0A93280@phx.gbl>
In-Reply-To: <BLU002-W2232C02D24F3D45F2E76B0A93280@phx.gbl>
X-Enigmail-Version: 1.5
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: "sm@resistor.net" <sm@resistor.net>, "ietf@ietf.org" <ietf@ietf.org>, "iesg@ietf.org" <iesg@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Jan 2013 09:49:59 -0000

Hi Bernard,

I'm sorry, I have no idea what it is that you agree with.
Can you elaborate?

Thanks,
S.

On 01/12/2013 10:47 PM, Bernard Aboba wrote:
> +1
> 
> [IAB Chair hat off].
> 
>> Date: Fri, 11 Jan 2013 22:25:38 +0100
>> Subject: Re: Last Call: <draft-farrell-ft-03.txt> (A Fast-Track way to RFC	with Running Code) to Experimental RFC
>> From: abdussalambaryun@gmail.com
>> To: sm@resistor.net
>> CC: ietf@ietf.org; iesg@ietf.org
>>
>> Hi SM,
>>
>> I totally agree with your comments and suggestions, the draft SHOULD
>> mention the important clarifications and the answers to SM's
>> questions. This is an important draft and SHUOLD be clear about such
>> important details in sections, why it ignores them without refering to
>> informative procedure items to link things for understanding. How do
>> authors write these drafts are they done with following procedure,
>>
>> AB
>>
>> ++++++++
>> In Section 1:
>>
>>   "Additionally, the experiment will only require issues raised
>>    during these three stages to be addressed if they meet the
>>    IESG's Discuss criteria."
>>
>> Does this mean that a document does not have to represent consensus?
>>
>>   "In contrast, a "-bis" RFC that aims for Proposed Standard or
>>    Experimental is likely to be a fine candidate."
>>
>>
>> I read what the document proposes as lowering the barrier of entry for
>> first publication. My preference is to say nothing about "-bis" RFCs
>> (see quoted text). Some of the "-bis" drafts I have come across (note
>> that this is not related to a draft being discussed currently) are not
>> well-written even though there is running code. The running code might
>> be due to author intervention instead of a blind test of the
>> specification.
>> In Section 2:
>>
>>   "Implementations developed during the production of an Internet-draft
>>    can indicate that a working group has had the opportunity to get
>>    early confirmation of its engineering choices."
>>
>> Agreed.
>>
>> In Section 3:
>>
>>   "Any Working Group Last Call (WGLC) or Area Director (AD) review
>>   (which are routinely done, though not part of the formal [BCP9]
>>   process) will run in parallel with the two-week IETF Last Call
>>   (IETF-LC) period."
>>
>>
>> I am not suggesting changing the two weeks. It can cause logistical
>> problems. I'll take the risk of trying this experiment.
>>   "Only comments that would be "DISCUSS-worthy" according to the
>>    IESG Discuss Criteria [DCRIT] need be handled during last call.
>>    Other comments can be handled or not, at the authors/editors
>>    discretion."
>>
>> See my previous comment about this criteria.
>>
>> In Section 4:
>>
>>   "The fast-track process can be used for "bis" RFCs and might well
>>    be quite suitable for those."
>>
>> I suggest removing this.
>>
>>   "If the timers (IETF LC or the two-weeks after IETF LC for fixing
>>    things) co-incide with a major holiday period or IETF meeting
>>    then the responsible AD can add a week or two as appropriate."
>>
>>
>> I suggest not using the Fast-Track if it is less than two weeks before
>> or after an IETF meeting. Some people only do IETF work during that
>> period and that results in a spike. I don't think that it is a good
>> idea for this experiment to encourage work during the meeting phase
>> instead of the mailing list.
>> In Section 5:
>>
>>   "An AD who wishes to do her review in parallel with Last Call is
>>    always free to make that choice."
>>
>> "his" or a gender neutral term.
>>
>>   "This memo itself has no impact on appeal processes.  However, in
>>    considering an appeal that relates to a document that has been
>>    fast-track processed, the relevant judge (WG chair, AD, IESG or
>>    IAB as appropriate) should consider the requirements posited here."
>>
>>
>> The WG Chair is not a judge in such cases as it would be his/her
>> decision being appealed.
>>
>> Some people are discouraged from bringing work into the IETF because
>> of the long debates (which I likely contributed to). Big companies
>> have an incentive to do work within the IETF. There is a perception in
>> open source circles than there isn't much to gain in having a
>> specification published as a RFC.
>>
>> The young, free and wild will not listen to the fogies. The better
>> approach, in my opinion, is not to act as a gatekeeper or encourage a
>> wall-garden attitude.
>> Regards,
>>
>> -sm
>  		 	   		  
> 

From stewe@stewe.org  Mon Jan 14 02:03:15 2013
Return-Path: <stewe@stewe.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8183F21F86DC for <ietf@ietfa.amsl.com>; Mon, 14 Jan 2013 02:03:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.099
X-Spam-Level: 
X-Spam-Status: No, score=-5.099 tagged_above=-999 required=5 tests=[AWL=-1.500, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 V-F+fz9vhaUn for <ietf@ietfa.amsl.com>; Mon, 14 Jan 2013 02:03:11 -0800 (PST)
Received: from ch1outboundpool.messaging.microsoft.com (ch1ehsobe004.messaging.microsoft.com [216.32.181.184]) by ietfa.amsl.com (Postfix) with ESMTP id B970F21F86BB for <ietf@ietf.org>; Mon, 14 Jan 2013 02:03:10 -0800 (PST)
Received: from mail179-ch1-R.bigfish.com (10.43.68.225) by CH1EHSOBE001.bigfish.com (10.43.70.51) with Microsoft SMTP Server id 14.1.225.23; Mon, 14 Jan 2013 10:03:09 +0000
Received: from mail179-ch1 (localhost [127.0.0.1])	by mail179-ch1-R.bigfish.com (Postfix) with ESMTP id B8A2118012B; Mon, 14 Jan 2013 10:03:09 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.236.133; KIP:(null); UIP:(null); IPV:NLI; H:BY2PRD0710HT005.namprd07.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: -18
X-BigFish: PS-18(z10d0kz98dI542I1432I4015Izz1ee6h1de0h1202h1e76h1d1ah1d2ah1082kzz1033IL17326ah8275dhz2fh2a8h668h839h946hd25hf0ah1288h12a5h12a9h12bdh137ah13b6h1441h1504h1537h153bh15d0h162dh1631h1758h1155h)
Received-SPF: pass (mail179-ch1: domain of stewe.org designates 157.56.236.133 as permitted sender) client-ip=157.56.236.133; envelope-from=stewe@stewe.org; helo=BY2PRD0710HT005.namprd07.prod.outlook.com ; .outlook.com ; 
Received: from mail179-ch1 (localhost.localdomain [127.0.0.1]) by mail179-ch1 (MessageSwitch) id 1358157787894182_323; Mon, 14 Jan 2013 10:03:07 +0000 (UTC)
Received: from CH1EHSMHS007.bigfish.com (snatpool1.int.messaging.microsoft.com [10.43.68.241])	by mail179-ch1.bigfish.com (Postfix) with ESMTP id D79CEC0076;	Mon, 14 Jan 2013 10:03:07 +0000 (UTC)
Received: from BY2PRD0710HT005.namprd07.prod.outlook.com (157.56.236.133) by CH1EHSMHS007.bigfish.com (10.43.70.7) with Microsoft SMTP Server (TLS) id 14.1.225.23; Mon, 14 Jan 2013 10:03:07 +0000
Received: from BY2PRD0710MB354.namprd07.prod.outlook.com ([169.254.9.165]) by BY2PRD0710HT005.namprd07.prod.outlook.com ([10.255.86.40]) with mapi id 14.16.0257.004; Mon, 14 Jan 2013 10:03:07 +0000
From: Stephan Wenger <stewe@stewe.org>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Subject: Re: Last Call: <draft-farrell-ft-03.txt> (A Fast-Track way to RFC with Running Code) to Experimental RFC
Thread-Topic: Last Call: <draft-farrell-ft-03.txt> (A Fast-Track way to RFC with Running Code) to Experimental RFC
Thread-Index: AQHN8D7r3XY8HwCadU+f4XzrwHls7phGBgCAgAJ10YCAABvOAIAAFVWA
Date: Mon, 14 Jan 2013 10:03:07 +0000
Message-ID: <FDBFA77C7400C74F87BC297393B53E3532B159FB@BY2PRD0710MB354.namprd07.prod.outlook.com>
In-Reply-To: <50F3D402.9060106@cs.tcd.ie>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.255.86.4]
Content-Type: text/plain; charset="Windows-1252"
Content-ID: <33BCE069F1426A4692BFB534A1715486@namprd07.prod.outlook.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: stewe.org
Cc: "adrian@olddog.co.uk" <adrian@olddog.co.uk>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Jan 2013 10:03:15 -0000

Perhaps my final comment on this.  Also cutting the thread down to
something readable.  Inline.
S.


On 1.14.2013 10:46 , "Stephen Farrell" <stephen.farrell@cs.tcd.ie> wrote:

[...]
>
>
>Yes, that's clearer. We're talking about two different continuums
>(or continua:-), so either would work, and neither is important to
>this draft. I'll make the change if there's enough support for it,
>but as I guess you can see, this is an area where we won't get folks
>to entirely agree. In this case, we don't need to, since the text
>in question is just explanatory and has no significant impact on
>the experiment at all.

Definitely my final comment on this topic:  I agree that the change has no
impact on the operation of the iETF under the draft.  IMO it simply fixes
a flaw of logic. =20

[...]


>>>[=8A]
>>> I'd have no problem adding text that encouraged some form of
>>> independence though, if you'd like to provide some.
>>=20
>> How about:
>>=20
>> "If the source code has been developed independently of the authoring of
>> the draft (and ideally by non WG participants), it is likely that the
>> implementation and the draft match, and that pitfalls unaware developers
>> may find have been found and dealt with.  If, on the other hand, draft
>> author(s) and implementation developer(s) overlap, then it is sensible
>>to
>> scrutinize the draft more closely, both with respect to its match with
>>the
>> implementation and for assumptions that author/developer may have taken
>> for granted which warrant documentation in the draft."
>
>That'd be no harm to add. I don't know that it improves the document
>enough to bother though. I'll think about it, but let's see if anyone
>else cares.

Thanks.

[...]
>
>>>
>>> I'll see if I can come up with something better than "match" but
>>> if you have text to suggest, that might help.
>>=20
>> Trying:
>>=20
>> "Match means that all, or substantially all, protocol mechanisms of the
>> draft are implemented, that no other code points are implemented that
>> would reasonably fall into the scope of the draft in question, that all
>> documented state machines are implemented and no other state machines,
>>and
>> so forth.  The over-the-wire behavior of the implementation and of the
>> draft should substantially match, including more subtle points such as
>> timing relationship of messages, .  Minor divergences in details
>>stemming
>> from unaligned development cycles of draft and implementation are
>> acceptable."
>
>I like most of that, thanks. For now, I've added this to 2.1, let me
>know if it works:
>
>   We do not give a precise definition for "match" here but the intent
>   is that all, or substantially all, protocol mechanisms of the draft
>   are implemented, that the over-the-wire behavior of the
>   implementation and of the draft should substantially match, including
>   more subtle points such as timing relationship of messages, etc.
>   Minor divergences in details stemming from unaligned development
>   cycles of draft and implementation are acceptable.

Works for me.

>
>Cheers,
>S.
>
>PS: There's a working draft at [1] in case that helps.
>
>[1] http://down.dsg.cs.tcd.ie/misc/draft-farrell-ft-04.txt
>
>
>>=20
>>>
>>> Cheers,
>>> S.
>>>
>>>>
>>>> Please consider this.
>>>> Thanks,
>>>> Stephan
>>>>  =20
>>>>
>>>> On 1.11.2013 08:21 , "Adrian Farrel" <adrian@olddog.co.uk> wrote:
>>>>
>>>>> Hi Alexa,
>>>>>
>>>>> Please be aware of this document that has just entered a four-week
>>>>>IETF
>>>>> last
>>>>> call. The document describes a proposed IETF process experiment under
>>>>> the
>>>>> rules
>>>>> of RFC 3933.
>>>>>
>>>>> The proposed experiment calls on the IETF Secretariat to take
>>>>>specific
>>>>> actions
>>>>> under certain circumstances in corner cases of the experiment. Could
>>>>> you
>>>>> please
>>>>> have someone in the Secretariat look at the draft and comment on the
>>>>> practicalities of the actions. Note that, at this stage, no changes
>>>>>to
>>>>> the tools
>>>>> are proposed so any actions would require manual intervention (if the
>>>>> experiment
>>>>> were successful and resulted in permanent changes to IETF process we
>>>>> might make
>>>>> changes to the tools at some future time).
>>>>>
>>>>> Thanks,
>>>>> Adrian
>>>>>
>>>>>> -----Original Message-----
>>>>>> From: ietf-announce-bounces@ietf.org [mailto:ietf-announce-
>>>>>> bounces@ietf.org] On Behalf Of The IESG
>>>>>> Sent: 11 January 2013 15:15
>>>>>> To: IETF-Announce
>>>>>> Subject: Last Call: <draft-farrell-ft-03.txt> (A Fast-Track way to
>>>>>>RFC
>>>>>> with
>>>>> Running
>>>>>> Code) to Experimental RFC
>>>>>>
>>>>>>
>>>>>> The IESG has received a request from an individual submitter to
>>>>>> consider
>>>>>> the following document:
>>>>>> - 'A Fast-Track way to RFC with Running Code'
>>>>>>   <draft-farrell-ft-03.txt> as Experimental RFC
>>>>>>
>>>>>> The IESG plans to make a decision in the next few weeks, and
>>>>>>solicits
>>>>>> final comments on this action. Please send substantive comments to
>>>>>>the
>>>>>> ietf@ietf.org mailing lists by 2013-02-08. Exceptionally, comments
>>>>>>may
>>>>>> be
>>>>>> sent to iesg@ietf.org instead. In either case, please retain the
>>>>>> beginning of the Subject line to allow automated sorting.
>>>>>>
>>>>>> Abstract
>>>>>>
>>>>>>    This memo describes an optional, fast-track way to progress a
>>>>>> working
>>>>>>    group document to IESG review.  It is provided as a process
>>>>>>    experiment as defined in RFC 3933 for use when working group
>>>>>>chairs
>>>>>>    believe that there is running code that implements a working
>>>>>>group
>>>>>>    Internet-Draft.  The motivation is to have the IETF process
>>>>>>    explicitly consider running code, consistent with the IETF's
>>>>>> overall
>>>>>>    philosophy of running code and rough consensus.
>>>>>>
>>>>>>    In this process all of working group last call, IETF last call,
>>>>>>and
>>>>>>    Area Director review are carried out in the same two week period.
>>>>>>    Only comments that meet IESG Discuss criteria need to be
>>>>>>addressed
>>>>>>    during this stage, and authors are required to make any changes
>>>>>>    within two weeks.
>>>>>>
>>>>>>    This experiment will run for one year.
>>>>>>
>>>>>>
>>>>>> The file can be obtained via
>>>>>> http://datatracker.ietf.org/doc/draft-farrell-ft/
>>>>>>
>>>>>> IESG discussion can be tracked via
>>>>>> http://datatracker.ietf.org/doc/draft-farrell-ft/ballot/
>>>>>>
>>>>>> No IPR declarations have been submitted directly on this I-D.
>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>
>>=20
>>=20
>>=20
>>=20
>



From petithug@acm.org  Mon Jan 14 02:31:31 2013
Return-Path: <petithug@acm.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 62C3C21F8918 for <ietf@ietfa.amsl.com>; Mon, 14 Jan 2013 02:31:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.492
X-Spam-Level: 
X-Spam-Status: No, score=-102.492 tagged_above=-999 required=5 tests=[AWL=0.108, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
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 vrhZm43jLRpw for <ietf@ietfa.amsl.com>; Mon, 14 Jan 2013 02:31:30 -0800 (PST)
Received: from implementers.org (implementers.org [IPv6:2604:3400:dc1:41:216:3eff:fe5b:8240]) by ietfa.amsl.com (Postfix) with ESMTP id 50C6F21F8906 for <ietf@ietf.org>; Mon, 14 Jan 2013 02:31:30 -0800 (PST)
Received: from [IPv6:2601:9:4b80:32:5415:9366:4865:dda8] (unknown [IPv6:2601:9:4b80:32:5415:9366:4865:dda8]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (Client CN "Marc Petit-Huguenin", Issuer "implementers.org" (verified OK)) by implementers.org (Postfix) with ESMTPS id C24E820373; Mon, 14 Jan 2013 10:31:28 +0000 (UTC)
Message-ID: <50F3DE8C.3080302@acm.org>
Date: Mon, 14 Jan 2013 02:31:40 -0800
From: Marc Petit-Huguenin <petithug@acm.org>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.11) Gecko/20121122 Icedove/10.0.11
MIME-Version: 1.0
To: Stephan Wenger <stewe@stewe.org>
Subject: Re: Last Call: <draft-farrell-ft-03.txt> (A Fast-Track way to RFC with Running Code) to Experimental RFC
References: <FDBFA77C7400C74F87BC297393B53E3532B1595B@BY2PRD0710MB354.namprd07.prod.outlook.com>
In-Reply-To: <FDBFA77C7400C74F87BC297393B53E3532B1595B@BY2PRD0710MB354.namprd07.prod.outlook.com>
X-Enigmail-Version: 1.4.1
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Cc: "adrian@olddog.co.uk" <adrian@olddog.co.uk>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Jan 2013 10:31:31 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On 01/14/2013 01:43 AM, Stephan Wenger wrote:
> Inline. S.
> 
> 
> On 1.14.2013 10:33 , "Marc Petit-Huguenin" <petithug@acm.org> wrote:
> 
> On 01/14/2013 01:10 AM, Eggert, Lars wrote:
>>>> Hi,
>>>> 
>>>> On Jan 14, 2013, at 10:08, Marc Petit-Huguenin <petithug@acm.org>
>>>> wrote:
>>>>> I think that you underestimate the IETF community, who certainly
>>>>> know how to see through all the FUD about the GPL.  Sure it may be
>>>>> a bad idea to literally copy 300 lines of GPL code in your code,
>>>>> but that does not apply to what we are talking about, which is
>>>>> reading code.
>>>> 
>>>> I have worked for employers before where reading GPL code was
>>>> considered highly problematic.
> 
> Sure, if the IETF is part of your job, and your employer prevents you to 
> read GPL code (or read Spinoza, or sing under the shower), then do not do
> it for the IETF.  Now if your employer does not regulate what you do on
> your own time, then there is no problem here.
> 
> If someone said to writers to never read any book that is still 
> copyrighted because they might be contaminated and that may somehow induce
> them to plagiarize without knowing it, how do you think they would react?
> 
>> Many would laugh.  Some politicians in Germany, who were recently found 
>> that they plagiarized in the PhD theses, would probably notÅ   Their risk 
>> is low, though.

And?  Plagiarizing is extremely wrong.  But preventing people to read book is
not how any sane person would try to solve the plagiarism problem.

And yet that is what is tried - with some success as I discover - with software.

> 
> There is no difference with software - excepted that there a lot more
> people that would like us to think that software is different.
> 
>> This is incorrect.  If you are found to infringe on someone's copyright
>> in a book you put together, you have a copyright problem (only).  If you
>> are found to infringe on certain open source licenses (including the GPL 
>> variants, but by no means limited to them), and the rightholder forces
>> you to take a license, you also have to provide a patent license under
>> terms you may not like.  Even if you don't take a license, it is quite
>> possible that you have (by copying GPLed code) provided in implied patent
>> license.

Do you have a case to share where that happened with a GPL license?

- -- 
Marc Petit-Huguenin
Email: marc@petit-huguenin.org
Blog: http://blog.marc.petit-huguenin.org
Profile: http://www.linkedin.com/in/petithug
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iQIcBAEBCAAGBQJQ896LAAoJECnERZXWan7EKHoQALpP81quorS9MiMD0D5bFfkS
4B3sJS8VCCZJxasMNuZY1b0foJl1u/n1fQTuyle3/TD0Ld2yz3BXWk8fav/dlaBz
5ZaGKRG3QzoDJG3afDmDPmP1bQ6u0riJ6U1V2QuzfiuIjp9h2Vzf/3dYSiqTGITB
vBCImbpUkgKP7U7/SsfsPEIeBEdJLuaZ+DmPa0pQ8wLPjKEGJbvfNnMuNcBYIHkf
b2uyEn1kcJbrkAsnWJkVWCGJukiHzbSDSRB7s9TWbLl4GXykBHZ9PvzNCARTrJD3
WZ2n9/2roewaAgKP9I8xaGuTTepFnkciUgwGCFSKUNqb+j/oPtFnl0ng2OIFAIX2
WBKQQMTYzu/tY6Rudwdnu6qBMN6Wag/wUG1QxDIIR/daA4ikmdZxJibZEeZ2FQ4f
uf4QAgMfHBSPjQIQ6Zgm0ch36LxifewPyOlU/LXui0MTXB6QClKYFdqLNc9Mzpdf
pB3K7KJtBEBTQshZ6Ad97f4S0PXupXcv8yJCrCJHYnh7BKL0GXcf3lnqmLh1TwFR
18rtMHiKdcwcHzQSGOt0/ny4tJcsaNp3rtWN1XZVfrLPnh3THM6vXNCO0WkTwTXL
w6uplJLhny/47RXRBEIPRHB+XDxKiDZ+JbVsWVfpfhlLCe2dMHMZpE7ELzEK9WuG
nzBiUyNwdJge+C0nzedQ
=Wkhd
-----END PGP SIGNATURE-----

From stewe@stewe.org  Mon Jan 14 03:45:41 2013
Return-Path: <stewe@stewe.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1A24121F8635 for <ietf@ietfa.amsl.com>; Mon, 14 Jan 2013 03:45:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.424
X-Spam-Level: 
X-Spam-Status: No, score=-4.424 tagged_above=-999 required=5 tests=[AWL=-1.425, BAYES_00=-2.599, J_CHICKENPOX_33=0.6, RCVD_IN_DNSWL_LOW=-1]
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 OILH-AsPFGTz for <ietf@ietfa.amsl.com>; Mon, 14 Jan 2013 03:45:40 -0800 (PST)
Received: from ch1outboundpool.messaging.microsoft.com (ch1ehsobe003.messaging.microsoft.com [216.32.181.183]) by ietfa.amsl.com (Postfix) with ESMTP id D8A5321F861A for <ietf@ietf.org>; Mon, 14 Jan 2013 03:45:39 -0800 (PST)
Received: from mail116-ch1-R.bigfish.com (10.43.68.236) by CH1EHSOBE002.bigfish.com (10.43.70.52) with Microsoft SMTP Server id 14.1.225.23; Mon, 14 Jan 2013 11:45:38 +0000
Received: from mail116-ch1 (localhost [127.0.0.1])	by mail116-ch1-R.bigfish.com (Postfix) with ESMTP id 045CA4202EF; Mon, 14 Jan 2013 11:45:39 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.236.133; KIP:(null); UIP:(null); IPV:NLI; H:BY2PRD0710HT001.namprd07.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: -8
X-BigFish: PS-8(z10d0kzbb2dI98dI154cP9371I1432I1418I62a3Izz1ee6h1de0h1202h1e76h1d1ah1d2ah1082kzz1954cbh17326ah8275bh8275dhz2fh2a8h668h839hd25hf0ah1288h12a5h12a9h12bdh137ah13b6h1441h1504h1537h153bh15d0h162dh1631h1758h1155h)
Received-SPF: pass (mail116-ch1: domain of stewe.org designates 157.56.236.133 as permitted sender) client-ip=157.56.236.133; envelope-from=stewe@stewe.org; helo=BY2PRD0710HT001.namprd07.prod.outlook.com ; .outlook.com ; 
Received: from mail116-ch1 (localhost.localdomain [127.0.0.1]) by mail116-ch1 (MessageSwitch) id 1358163937119506_22679; Mon, 14 Jan 2013 11:45:37 +0000 (UTC)
Received: from CH1EHSMHS035.bigfish.com (snatpool2.int.messaging.microsoft.com [10.43.68.233])	by mail116-ch1.bigfish.com (Postfix) with ESMTP id 188782A005A;	Mon, 14 Jan 2013 11:45:37 +0000 (UTC)
Received: from BY2PRD0710HT001.namprd07.prod.outlook.com (157.56.236.133) by CH1EHSMHS035.bigfish.com (10.43.70.35) with Microsoft SMTP Server (TLS) id 14.1.225.23; Mon, 14 Jan 2013 11:45:36 +0000
Received: from BY2PRD0710MB354.namprd07.prod.outlook.com ([169.254.9.165]) by BY2PRD0710HT001.namprd07.prod.outlook.com ([10.255.86.36]) with mapi id 14.16.0257.004; Mon, 14 Jan 2013 11:45:36 +0000
From: Stephan Wenger <stewe@stewe.org>
To: Marc Petit-Huguenin <petithug@acm.org>
Subject: Re: Last Call: <draft-farrell-ft-03.txt> (A Fast-Track way to RFC with Running Code) to Experimental RFC
Thread-Topic: Last Call: <draft-farrell-ft-03.txt> (A Fast-Track way to RFC with Running Code) to Experimental RFC
Thread-Index: AQHN8jpGfZSDQWG05E+8GQR351mbnphIo4AA///8uACAACVnAA==
Date: Mon, 14 Jan 2013 11:45:35 +0000
Message-ID: <FDBFA77C7400C74F87BC297393B53E3532B15B50@BY2PRD0710MB354.namprd07.prod.outlook.com>
In-Reply-To: <50F3DE8C.3080302@acm.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.255.86.4]
Content-Type: text/plain; charset="iso-8859-2"
Content-ID: <0C61693DB7A8064095D0D3C3A5361ECA@namprd07.prod.outlook.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: stewe.org
Cc: "adrian@olddog.co.uk" <adrian@olddog.co.uk>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Jan 2013 11:45:41 -0000

Hi,
Please see inline.
Stephan

On 1.14.2013 11:31 , "Marc Petit-Huguenin" <petithug@acm.org> wrote:

>-----BEGIN PGP SIGNED MESSAGE-----
>Hash: SHA256
>
>On 01/14/2013 01:43 AM, Stephan Wenger wrote:
>> Inline. S.
>>=20
>>=20
>> On 1.14.2013 10:33 , "Marc Petit-Huguenin" <petithug@acm.org> wrote:
>>=20
>> On 01/14/2013 01:10 AM, Eggert, Lars wrote:
>>>>> Hi,
>>>>>=20
>>>>> On Jan 14, 2013, at 10:08, Marc Petit-Huguenin <petithug@acm.org>
>>>>> wrote:
>>>>>> I think that you underestimate the IETF community, who certainly
>>>>>> know how to see through all the FUD about the GPL.  Sure it may be
>>>>>> a bad idea to literally copy 300 lines of GPL code in your code,
>>>>>> but that does not apply to what we are talking about, which is
>>>>>> reading code.
>>>>>=20
>>>>> I have worked for employers before where reading GPL code was
>>>>> considered highly problematic.
>>=20
>> Sure, if the IETF is part of your job, and your employer prevents you
>>to=20
>> read GPL code (or read Spinoza, or sing under the shower), then do not
>>do
>> it for the IETF.  Now if your employer does not regulate what you do on
>> your own time, then there is no problem here.
>>=20
>> If someone said to writers to never read any book that is still
>> copyrighted because they might be contaminated and that may somehow
>>induce
>> them to plagiarize without knowing it, how do you think they would
>>react?
>>=20
>>> Many would laugh.  Some politicians in Germany, who were recently
>>>found=20
>>> that they plagiarized in the PhD theses, would probably not=A9  Their
>>>risk=20
>>> is low, though.
>
>And?  Plagiarizing is extremely wrong.  But preventing people to read
>book is
>not how any sane person would try to solve the plagiarism problem.

I agree. =20

>
>And yet that is what is tried - with some success as I discover - with
>software.
>
>>=20
>> There is no difference with software - excepted that there a lot more
>> people that would like us to think that software is different.
>>=20
>>> This is incorrect.  If you are found to infringe on someone's copyright
>>> in a book you put together, you have a copyright problem (only).  If
>>>you
>>> are found to infringe on certain open source licenses (including the
>>>GPL=20
>>> variants, but by no means limited to them), and the rightholder forces
>>> you to take a license, you also have to provide a patent license under
>>> terms you may not like.  Even if you don't take a license, it is quite
>>> possible that you have (by copying GPLed code) provided in implied
>>>patent
>>> license.
>
>Do you have a case to share where that happened with a GPL license?

It has been pointed out to me that the formulation "take a license" above
was misleading, and I agree.  What I meant is that the rightholder forces
you to re-license your code under GPL (what is sometimes called the
"viral" effect of the GPL).

As for your question, I vaguely recall an opinion which upheld the
requirement to grant a patent license for GPLv2(?) code (GPLv2 is not
pointing out the requirement to license patents as clearly as GPLv3 does).
 But I would have to dig,and have limited motivation to do so right now.
As for the implied patent license, I'm not aware of case law.

Stephan

>
>- --=20
>Marc Petit-Huguenin
>Email: marc@petit-huguenin.org
>Blog: http://blog.marc.petit-huguenin.org
>Profile: http://www.linkedin.com/in/petithug
>-----BEGIN PGP SIGNATURE-----
>Version: GnuPG v1.4.12 (GNU/Linux)
>
>iQIcBAEBCAAGBQJQ896LAAoJECnERZXWan7EKHoQALpP81quorS9MiMD0D5bFfkS
>4B3sJS8VCCZJxasMNuZY1b0foJl1u/n1fQTuyle3/TD0Ld2yz3BXWk8fav/dlaBz
>5ZaGKRG3QzoDJG3afDmDPmP1bQ6u0riJ6U1V2QuzfiuIjp9h2Vzf/3dYSiqTGITB
>vBCImbpUkgKP7U7/SsfsPEIeBEdJLuaZ+DmPa0pQ8wLPjKEGJbvfNnMuNcBYIHkf
>b2uyEn1kcJbrkAsnWJkVWCGJukiHzbSDSRB7s9TWbLl4GXykBHZ9PvzNCARTrJD3
>WZ2n9/2roewaAgKP9I8xaGuTTepFnkciUgwGCFSKUNqb+j/oPtFnl0ng2OIFAIX2
>WBKQQMTYzu/tY6Rudwdnu6qBMN6Wag/wUG1QxDIIR/daA4ikmdZxJibZEeZ2FQ4f
>uf4QAgMfHBSPjQIQ6Zgm0ch36LxifewPyOlU/LXui0MTXB6QClKYFdqLNc9Mzpdf
>pB3K7KJtBEBTQshZ6Ad97f4S0PXupXcv8yJCrCJHYnh7BKL0GXcf3lnqmLh1TwFR
>18rtMHiKdcwcHzQSGOt0/ny4tJcsaNp3rtWN1XZVfrLPnh3THM6vXNCO0WkTwTXL
>w6uplJLhny/47RXRBEIPRHB+XDxKiDZ+JbVsWVfpfhlLCe2dMHMZpE7ELzEK9WuG
>nzBiUyNwdJge+C0nzedQ
>=3DWkhd
>-----END PGP SIGNATURE-----
>



From john@jlc.net  Mon Jan 14 05:05:47 2013
Return-Path: <john@jlc.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0820821F86D2 for <ietf@ietfa.amsl.com>; Mon, 14 Jan 2013 05:05:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.036
X-Spam-Level: 
X-Spam-Status: No, score=-106.036 tagged_above=-999 required=5 tests=[AWL=0.563, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 rG6i1c-xwuGq for <ietf@ietfa.amsl.com>; Mon, 14 Jan 2013 05:05:46 -0800 (PST)
Received: from mailhost.jlc.net (mailhost.jlc.net [199.201.159.4]) by ietfa.amsl.com (Postfix) with ESMTP id BA21321F86CC for <ietf@ietf.org>; Mon, 14 Jan 2013 05:05:45 -0800 (PST)
Received: by mailhost.jlc.net (Postfix, from userid 104) id 51FD433C4C; Mon, 14 Jan 2013 08:05:41 -0500 (EST)
Date: Mon, 14 Jan 2013 08:05:41 -0500
From: John Leslie <john@jlc.net>
To: ietf@ietf.org
Subject: Re: Last Call: <draft-farrell-ft-03.txt> (A Fast-Track way to RFC with Running Code) to Experimental RFC
Message-ID: <20130114130541.GK62444@verdi>
References: <20130111151453.22161.50884.idtracker@ietfa.amsl.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20130111151453.22161.50884.idtracker@ietfa.amsl.com>
User-Agent: Mutt/1.4.1i
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Jan 2013 13:05:47 -0000

The IESG <iesg-secretary@ietf.org> wrote:
> 
> The IESG has received a request from an individual submitter to consider
> the following document:
> - 'A Fast-Track way to RFC with Running Code'
>   <draft-farrell-ft-03.txt> as Experimental RFC
> 
> The IESG plans to make a decision in the next few weeks, and solicits
> final comments on this action.

   I'm pretty darn uncomfortable _ever_ picking a fight with any
sitting AD, But I feel obligated to say this seems like a terrible
idea to me.

   As a background, I'm a long-time believer in "rough consensus" for
Proposed Standard and "running code" for advancement along the
standards track. I do not believe the two mix well.

   A standard needs to be as simple as possible (but no simpler);
running code needs to be complex.

   Stephen Farrell wants to "speed up" our process by adding an
incentive for "having" running code. Specifically:
] 
] This memo describes a way to fast-track some final stage reviews for
] a working group draft when the working group management and area
] directors believe that the existence of one or more implementations
] serve as a practical review of the engineering choices made by the
] working group.

   Actually, now that I read that carefully, it doesn't even need to be
"running" code. :^(

] This experiment needs an implementation that matches the specification
] contained in the draft.

   (Verifying that has proven to be surprisingly hard. One guesses
that the "match" may not be rigidly enforced...)

   Understand, IMHO there is much to be gained by testing the
interoperability of independent implementations of a specification;
but that is a long-winded process, hardly anything which could be
done during the "fast-track" Stephen is proposing.

] It is up to the WG chairs and responsible AD to satisfy themselves
] on this point within the normal bounds of trust

   "Normal bounds of trust" isn't particularly compatible with our
paradigm of transparency of process...

   I don't even think it means the same thing to the rather limited
set of people named here.

] and without any implication about the licensing related to an
] open- or closed-source implementation.

   Any mention of licensing seems out of place here.

] Note that the existence of an implementation is not sufficient to
] ensure that the draft will automatically pass working group or IETF
] last call, nor that it will receive IESG approval.

   Nor should it be, of course...

   Getting to the devil-in-the-details:
] 
] 1. Any Working Group Last Call (WGLC) or Area Director (AD) review
]    ... will run in parallel with the two-week IETF Last Call

] 2. The IETF last call announcement message must say that the draft
]    in question is following the fast-track process...

] 3. The draft itself should note (e.g. in the introduction) that it
]    has been fast-track processed and reference this RFC.

] 4. Only comments that would be "DISCUSS-worthy" according to the
]    IESG Discuss Criteria [DCRIT] need be handled during last call.
]    Other comments can be handled or not, at the authors/editors
]    discretion.

   This is actually normal for IETF-wide LastCall (though it leads
to raised tempers when seemingly valid comments are ignored).

   It is not normal for WG LastCall; nor is it even compatible with
"rough consensus" -- by which we mean that any new questions raised
have been considered to the satisfaction of a substantial majority
of the participants.

] 5. The responsible AD for the WG concerned makes the decision as to
]    whether changes are required as a result of review comments, and
]    determines whether or not those have been completed.  If
]    significant change or extended discussion is required, or if
]    changes are not complete within two weeks after the end of fast-
]    track last call, then the draft is returned to the WG by the
]    responsible AD and the document is withdrawn from the experiment.

   This is not an easy read. :^(

   First, it centralizes the decision in one person (whereas normal
WGLC process has two or more WG Chairs judging consensus of the group).

   Second, it centralizes the decision in one person whether changes
in the document properly address any WG or IETF-wide comments. This
kind-of matches current practice in the IESG for Area Director
comments; but does not match the theory -- and we could on very short
notice regress from the level of trust which allows this to happen
now.

   Third, the two-week drop-dead time limit is unworkable. Not just
IMHO; in practice it hardly ever happens that everything resolves
itself that quickly. AD DISCUSS comments tend to bunch up in the
hours before the telechat, and frequently need to be clarified
_after_ the telechat.

   Fourth, it's not really clear what happens after "the document is
withdrawn from the experiment." It would appear at first blush that
it must now start a separate WGLC, followed by a new IETF LastCall.
I would never consent to this process for a document _I_ cared about.

] 6. As soon as the responsible AD has confirmed that the authors/
]    editors have made any changes required as a result of fast-track
]    last-call, then the document should enter IESG review and be
]    placed on the next IESG telechat agenda that is more than one
]    week in the future.

   Oh... Stephen wasn't talking about the IESG process at all!

   I'm even more confused now.

   I guess this means that one person (the responsible AD) takes a
look at any and all comments during the "combined" LastCall and
responsible-AD-review and makes a unilateral decision of what
changes the authors/editors should make (on short notice); then
things open for IESG-member DISCUSS comments.

   This would seem to preclude the current practice of putting
drafts on the IESG agenda _before_ the end of IETF LastCall. I'm
only getting more confused as to how this speeds up our process.

] 7. Given the reduced time associated with fast-track processing, the
]    responsible AD may not have time to carry out sufficient review
]    prior to IESG evaluation to be confident in balloting "Yes" for
]    the document.  Draft progression during and after IESG review is
]    otherwise unaffected, so a "Yes" ballot is needed from some AD.

   I _do_ understand that part, thought it's a bit obscure to those
who haven't been IESG members: no document gets approved by the
IESG without at least one "Yes" ballot-position; and Stephen wants
to be able to decline to ballot "Yes" on a document he (as
responsible-AD) has almost unilaterally re-written. (This would
be a really-bad idea, IMHO.)

] 8. If at any point in the fast-track process the responsbile AD does
]    not act in a timely fashion then the IESG Secretary should ensure
]    that the draft enters IESG evaluation and is scheduled for the
]    the soonest IESG telechat that is more than one week after the
]    end of the two-week post-IETF LC period.  That is, if the
]    responsible AD does not act, then the default action applies
]    which is that the draft enters IESG evaluation and is placed on
]    the earliest IESG telechat.

   (This is too complicated for me to try to explain in this email.)

====

   There's a lot more I could review, but I won't in this post.

   Were I an AD responsible to ballot on this, I'd ballot "abstain".
"Abstain" means "There's no point trying to satisfy me," and is
the way an IESG member essentially votes "No."

   I don't believe "running code" is even particularly helpful in
run-of-the-mill Proposed Standards. I've seen it _seriously_ harm
the documents in cases where the "running code" has shipped and
there is reticence to change it: no matter how many weaknesses are
pointed out, you can't get WG consensus to change the spec.

   In cases where "running code" has proven helpful, it's my
honest opinion that the spec has become way too complicated (and
thus the "running code" has proven which parts are unworkable).

   I don't believe it's possible to "fast-track" "runnng code";
nor do I believe it would be desirable were it possible. Code
needs to deal with complex cases that, for the most part, don't
need to be standardized in the first place. But code which
doesn't deal with these is useless in the marketplace.

   IMHO, we designed a separate "Proposed Standard" step to get
a specification published quickly without delving into the many
questions that arise when writing actual code. There are plenty
of Standards-Development Organizations that start from "code".
We don't need to become one of them.

--
John Leslie <john@jlc.net>

From stephen.farrell@cs.tcd.ie  Mon Jan 14 05:24:53 2013
Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6884B21F86C4 for <ietf@ietfa.amsl.com>; Mon, 14 Jan 2013 05:24:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.67
X-Spam-Level: 
X-Spam-Status: No, score=-102.67 tagged_above=-999 required=5 tests=[AWL=-0.071, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 QnAGMOEO8Y-j for <ietf@ietfa.amsl.com>; Mon, 14 Jan 2013 05:24:52 -0800 (PST)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) by ietfa.amsl.com (Postfix) with ESMTP id 10A7521F8726 for <ietf@ietf.org>; Mon, 14 Jan 2013 05:24:52 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id 254ECBE3C; Mon, 14 Jan 2013 13:24:21 +0000 (GMT)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4O-HQEiTE+20; Mon, 14 Jan 2013 13:24:18 +0000 (GMT)
Received: from [IPv6:2001:770:10:203:fc59:2c8:a489:8ef3] (unknown [IPv6:2001:770:10:203:fc59:2c8:a489:8ef3]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id D04FEBDC7; Mon, 14 Jan 2013 13:24:18 +0000 (GMT)
Message-ID: <50F40703.50300@cs.tcd.ie>
Date: Mon, 14 Jan 2013 13:24:19 +0000
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130106 Thunderbird/17.0.2
MIME-Version: 1.0
To: John Leslie <john@jlc.net>
Subject: Re: Last Call: <draft-farrell-ft-03.txt> (A Fast-Track way to RFC with Running Code) to Experimental RFC
References: <20130111151453.22161.50884.idtracker@ietfa.amsl.com> <20130114130541.GK62444@verdi>
In-Reply-To: <20130114130541.GK62444@verdi>
X-Enigmail-Version: 1.5
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Jan 2013 13:24:53 -0000

Hi John,

On 01/14/2013 01:05 PM, John Leslie wrote:
> The IESG <iesg-secretary@ietf.org> wrote:
>>
>> The IESG has received a request from an individual submitter to consider
>> the following document:
>> - 'A Fast-Track way to RFC with Running Code'
>>   <draft-farrell-ft-03.txt> as Experimental RFC
>>
>> The IESG plans to make a decision in the next few weeks, and solicits
>> final comments on this action.
> 
>    I'm pretty darn uncomfortable _ever_ picking a fight with any
> sitting AD, But I feel obligated to say this seems like a terrible
> idea to me.

Just a quick response to say that there's no fight required.
Its just fine that you think its a terrible idea. And you may
be right, or maybe not, I guess we might find out if the
experiment is done. Or if enough others hate it well enough,
we won't find out because the experiment won't start. That's
all ok.

And given that its a process-thing, I started it fully expecting
to see more or less all flavours of agreement and disagreement:-)

So I'm not at all put out to see someone just hates this.

I'll respond in detail later on when I get a chance.

Cheers,
S.

> 
>    As a background, I'm a long-time believer in "rough consensus" for
> Proposed Standard and "running code" for advancement along the
> standards track. I do not believe the two mix well.
> 
>    A standard needs to be as simple as possible (but no simpler);
> running code needs to be complex.
> 
>    Stephen Farrell wants to "speed up" our process by adding an
> incentive for "having" running code. Specifically:
> ] 
> ] This memo describes a way to fast-track some final stage reviews for
> ] a working group draft when the working group management and area
> ] directors believe that the existence of one or more implementations
> ] serve as a practical review of the engineering choices made by the
> ] working group.
> 
>    Actually, now that I read that carefully, it doesn't even need to be
> "running" code. :^(
> 
> ] This experiment needs an implementation that matches the specification
> ] contained in the draft.
> 
>    (Verifying that has proven to be surprisingly hard. One guesses
> that the "match" may not be rigidly enforced...)
> 
>    Understand, IMHO there is much to be gained by testing the
> interoperability of independent implementations of a specification;
> but that is a long-winded process, hardly anything which could be
> done during the "fast-track" Stephen is proposing.
> 
> ] It is up to the WG chairs and responsible AD to satisfy themselves
> ] on this point within the normal bounds of trust
> 
>    "Normal bounds of trust" isn't particularly compatible with our
> paradigm of transparency of process...
> 
>    I don't even think it means the same thing to the rather limited
> set of people named here.
> 
> ] and without any implication about the licensing related to an
> ] open- or closed-source implementation.
> 
>    Any mention of licensing seems out of place here.
> 
> ] Note that the existence of an implementation is not sufficient to
> ] ensure that the draft will automatically pass working group or IETF
> ] last call, nor that it will receive IESG approval.
> 
>    Nor should it be, of course...
> 
>    Getting to the devil-in-the-details:
> ] 
> ] 1. Any Working Group Last Call (WGLC) or Area Director (AD) review
> ]    ... will run in parallel with the two-week IETF Last Call
> 
> ] 2. The IETF last call announcement message must say that the draft
> ]    in question is following the fast-track process...
> 
> ] 3. The draft itself should note (e.g. in the introduction) that it
> ]    has been fast-track processed and reference this RFC.
> 
> ] 4. Only comments that would be "DISCUSS-worthy" according to the
> ]    IESG Discuss Criteria [DCRIT] need be handled during last call.
> ]    Other comments can be handled or not, at the authors/editors
> ]    discretion.
> 
>    This is actually normal for IETF-wide LastCall (though it leads
> to raised tempers when seemingly valid comments are ignored).
> 
>    It is not normal for WG LastCall; nor is it even compatible with
> "rough consensus" -- by which we mean that any new questions raised
> have been considered to the satisfaction of a substantial majority
> of the participants.
> 
> ] 5. The responsible AD for the WG concerned makes the decision as to
> ]    whether changes are required as a result of review comments, and
> ]    determines whether or not those have been completed.  If
> ]    significant change or extended discussion is required, or if
> ]    changes are not complete within two weeks after the end of fast-
> ]    track last call, then the draft is returned to the WG by the
> ]    responsible AD and the document is withdrawn from the experiment.
> 
>    This is not an easy read. :^(
> 
>    First, it centralizes the decision in one person (whereas normal
> WGLC process has two or more WG Chairs judging consensus of the group).
> 
>    Second, it centralizes the decision in one person whether changes
> in the document properly address any WG or IETF-wide comments. This
> kind-of matches current practice in the IESG for Area Director
> comments; but does not match the theory -- and we could on very short
> notice regress from the level of trust which allows this to happen
> now.
> 
>    Third, the two-week drop-dead time limit is unworkable. Not just
> IMHO; in practice it hardly ever happens that everything resolves
> itself that quickly. AD DISCUSS comments tend to bunch up in the
> hours before the telechat, and frequently need to be clarified
> _after_ the telechat.
> 
>    Fourth, it's not really clear what happens after "the document is
> withdrawn from the experiment." It would appear at first blush that
> it must now start a separate WGLC, followed by a new IETF LastCall.
> I would never consent to this process for a document _I_ cared about.
> 
> ] 6. As soon as the responsible AD has confirmed that the authors/
> ]    editors have made any changes required as a result of fast-track
> ]    last-call, then the document should enter IESG review and be
> ]    placed on the next IESG telechat agenda that is more than one
> ]    week in the future.
> 
>    Oh... Stephen wasn't talking about the IESG process at all!
> 
>    I'm even more confused now.
> 
>    I guess this means that one person (the responsible AD) takes a
> look at any and all comments during the "combined" LastCall and
> responsible-AD-review and makes a unilateral decision of what
> changes the authors/editors should make (on short notice); then
> things open for IESG-member DISCUSS comments.
> 
>    This would seem to preclude the current practice of putting
> drafts on the IESG agenda _before_ the end of IETF LastCall. I'm
> only getting more confused as to how this speeds up our process.
> 
> ] 7. Given the reduced time associated with fast-track processing, the
> ]    responsible AD may not have time to carry out sufficient review
> ]    prior to IESG evaluation to be confident in balloting "Yes" for
> ]    the document.  Draft progression during and after IESG review is
> ]    otherwise unaffected, so a "Yes" ballot is needed from some AD.
> 
>    I _do_ understand that part, thought it's a bit obscure to those
> who haven't been IESG members: no document gets approved by the
> IESG without at least one "Yes" ballot-position; and Stephen wants
> to be able to decline to ballot "Yes" on a document he (as
> responsible-AD) has almost unilaterally re-written. (This would
> be a really-bad idea, IMHO.)
> 
> ] 8. If at any point in the fast-track process the responsbile AD does
> ]    not act in a timely fashion then the IESG Secretary should ensure
> ]    that the draft enters IESG evaluation and is scheduled for the
> ]    the soonest IESG telechat that is more than one week after the
> ]    end of the two-week post-IETF LC period.  That is, if the
> ]    responsible AD does not act, then the default action applies
> ]    which is that the draft enters IESG evaluation and is placed on
> ]    the earliest IESG telechat.
> 
>    (This is too complicated for me to try to explain in this email.)
> 
> ====
> 
>    There's a lot more I could review, but I won't in this post.
> 
>    Were I an AD responsible to ballot on this, I'd ballot "abstain".
> "Abstain" means "There's no point trying to satisfy me," and is
> the way an IESG member essentially votes "No."
> 
>    I don't believe "running code" is even particularly helpful in
> run-of-the-mill Proposed Standards. I've seen it _seriously_ harm
> the documents in cases where the "running code" has shipped and
> there is reticence to change it: no matter how many weaknesses are
> pointed out, you can't get WG consensus to change the spec.
> 
>    In cases where "running code" has proven helpful, it's my
> honest opinion that the spec has become way too complicated (and
> thus the "running code" has proven which parts are unworkable).
> 
>    I don't believe it's possible to "fast-track" "runnng code";
> nor do I believe it would be desirable were it possible. Code
> needs to deal with complex cases that, for the most part, don't
> need to be standardized in the first place. But code which
> doesn't deal with these is useless in the marketplace.
> 
>    IMHO, we designed a separate "Proposed Standard" step to get
> a specification published quickly without delving into the many
> questions that arise when writing actual code. There are plenty
> of Standards-Development Organizations that start from "code".
> We don't need to become one of them.
> 
> --
> John Leslie <john@jlc.net>
> 
> 

From nabil.n.bitar@verizon.com  Mon Jan 14 06:35:26 2013
Return-Path: <nabil.n.bitar@verizon.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8431B21F8976; Mon, 14 Jan 2013 06:35:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.249
X-Spam-Level: 
X-Spam-Status: No, score=-3.249 tagged_above=-999 required=5 tests=[AWL=0.350,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 nQtlFo3t3UfM; Mon, 14 Jan 2013 06:35:25 -0800 (PST)
Received: from fldsmtpe03.verizon.com (fldsmtpe03.verizon.com [140.108.26.142]) by ietfa.amsl.com (Postfix) with ESMTP id 23EFB21F8995; Mon, 14 Jan 2013 06:35:25 -0800 (PST)
X-IronPort-Anti-Spam-Filtered: false
Received: from unknown (HELO fldsmtpi03.verizon.com) ([166.68.71.145]) by fldsmtpe03.verizon.com with ESMTP; 14 Jan 2013 14:35:22 +0000
From: "Bitar, Nabil N" <nabil.n.bitar@verizon.com>
X-IronPort-AV: E=Sophos;i="4.84,468,1355097600"; d="scan'208";a="396005174"
Received: from fldp1lumxc7hb05.verizon.com (HELO FLDP1LUMXC7HB05.us.one.verizon.com) ([166.68.75.87]) by fldsmtpi03.verizon.com with ESMTP; 14 Jan 2013 14:35:21 +0000
Received: from fldp1lumxc7v63.us.one.verizon.com ([166.68.45.45]) by FLDP1LUMXC7HB05.us.one.verizon.com ([166.68.75.87]) with mapi; Mon, 14 Jan 2013 09:35:21 -0500
To: Loa Andersson <loa@pi.nu>, Greg Mirsky <gregimirsky@gmail.com>
Date: Mon, 14 Jan 2013 09:35:00 -0500
Subject: Re: [PWE3] Gen-ART review of draft-ietf-pwe3-mpls-eth-oam-iwk-06
Thread-Topic: [PWE3] Gen-ART review of draft-ietf-pwe3-mpls-eth-oam-iwk-06
Thread-Index: Ac3yZGEabESV70e/Q8OzvI3GDIcDng==
Message-ID: <CD117626.73FD3%nabil.n.bitar@verizon.com>
In-Reply-To: <50EBFCA0.3060307@pi.nu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.2.3.120616
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "Bitar, Nabil N" <nabil.n.bitar@verizon.com>, "ietf@ietf.org" <ietf@ietf.org>, "gen-art@ietf.org" <gen-art@ietf.org>, "dinmohan@hotmail.com" <dinmohan@hotmail.com>, "sajassi@cisco.com" <sajassi@cisco.com>, "pwe3@ietf.org" <pwe3@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Jan 2013 14:35:26 -0000

Hi,
I will folloup on the other emails. Just catching up in reverse order. RDI
(Reverse defect indication) is what is used in RFC 6310 to indicate
failure in the rverse direction from the failure, and this document is
aligned with that. At the same time, RDI as Remote defect indication is
what is used for Ethernet CFM, so the attemot here is to call out
the acronyms used and in this case it is the same acronym that correspond
to two different terminologies, each with its own context identified.

Thanks,
Nabil

On 1/8/13 6:01 AM, "Loa Andersson" <loa@pi.nu> wrote:

>Greg,
>
>RFC 6428 expands RDI as:
>
>    RDI: Remote Defect Indication
>
>/Loa
>
>On 2013-01-07 21:51, Greg Mirsky wrote:
>> Dear Nabil,
>> can we avoid different interpretation of the same abbreviation (RDI):
>>
>>     RDI   Remote Defect Indication for Continuity Check Message
>>
>>     RDI   Reverse Defect Indication
>>
>> AFAIK, the latter form is the interpretation used by both IEEE 802.1ag
>> and Y.1731. How useful is the first form?
>>
>> Regards,
>>
>> Greg
>>
>>
>>
>> On Fri, Jan 4, 2013 at 8:17 AM, Bitar, Nabil N
>> <nabil.n.bitar@verizon.com <mailto:nabil.n.bitar@verizon.com>> wrote:
>>
>>     Hi Dave,
>>     Related to abbreviations comment below and to be clearer, I renamed
>>     the original terminology section to "Abbreviations and Terminology".
>>     I also created a subsection called "Abbreviations" ,and
>>     "Terminology" became the second subsection.  Here iis how the edits
>>look
>>
>>
>>       3. Abbreviations and Terminology____
>>
>>
>>         3.1. Abbreviations____
>>
>>     AISAlarm Indication Signal____
>>
>>     ACAttachment Circuit____
>>
>>     BFDBidirectional Forwarding Detection____
>>
>>     CCContinuity Check____
>>
>>     CCMContinuity Check Message____
>>
>>     CECustomer Equipment____
>>
>>     CVConnectivity Verification____
>>
>>     E-LMI Ethernet Local Management Interface____
>>
>>     EVCEthernet Virtual Circuit____
>>
>>     LDPLabel Distribution Protocol____
>>
>>     LoSLoss of Signal____
>>
>>     MAMaintenance Association____
>>
>>     MDMaintenance Domain____
>>
>>     MEMaintenance Entity____
>>
>>     MEGMaintenance Entity Group____
>>
>>     MEPMaintenance End Point____
>>
>>     MIPMaintenance End Point____
>>
>>     MPLSMultiprotocol Label Switching____
>>
>>     MS-PW Multi-Segment Pseudowire____
>>
>>     NSNative Service____
>>
>>     OAMOperations, Administration, and Maintenance____
>>
>>     PEProvider Edge____
>>
>>     PSNPacket Switched Network____
>>
>>     PWPseudowire____
>>
>>     RDIRemote Defect Indication for Continuity Check Message____
>>
>>         RDI   Reverse Defect Indication
>>
>>     S-PESwitching Provider Edge____
>>
>>     TLVType Length Value____
>>
>>     T-PETerminating Provider Edge____
>>
>>     __ __
>>
>>
>>         3.2. Terminology____
>>
>>     This document uses the following terms with corresponding
>>     definitions: ____
>>
>>     - MD Level:Maintenance Domain (MD) Level which identifies a value in
>>     the range of 0-7 associated with Ethernet OAM frame. MD Level
>>     identifies the span of the Ethernet OAM frame.____
>>
>>     - MEP:Maintenance End Point is responsible for origination and
>>     termination of OAM frames for a given MEG.____
>>
>>     - MIP: Maintenance Intermediate Point is located between peer MEPs
>>     and can process OAM frames but does not initiate or terminate
>>them.____
>>
>>     Further, this document also uses the terminology and conventions
>>     used in [RFC6310].____
>>
>>
>>
>>     Thanks,
>>
>>     Nabil
>>
>>
>>     From: <Bitar>, Nabil N <nabil.n.bitar@one.verizon.com
>>     <mailto:nabil.n.bitar@one.verizon.com>>
>>     Date: Wednesday, January 2, 2013 11:28 AM
>>     To: "Black, David" <david.black@emc.com
>>     <mailto:david.black@emc.com>>, "dinmohan@hotmail.com
>>     <mailto:dinmohan@hotmail.com>" <dinmohan@hotmail.com
>>     <mailto:dinmohan@hotmail.com>>, "Bitar, Nabil N"
>>     <nabil.n.bitar@one.verizon.com
>>     <mailto:nabil.n.bitar@one.verizon.com>>, Sagessi <sajassi@cisco.com
>>     <mailto:sajassi@cisco.com>>, "gen-art@ietf.org
>>     <mailto:gen-art@ietf.org>" <gen-art@ietf.org
>><mailto:gen-art@ietf.org>>
>>     Cc: "pwe3@ietf.org <mailto:pwe3@ietf.org>" <pwe3@ietf.org
>>     <mailto:pwe3@ietf.org>>, "ietf@ietf.org <mailto:ietf@ietf.org>"
>>     <ietf@ietf.org <mailto:ietf@ietf.org>>
>>     Subject: Re: Gen-ART review of draft-ietf-pwe3-mpls-eth-oam-iwk-06
>>
>>     Hi Dave,
>>     Sorry for a late reply addressing your comments. Please, see inline.
>>
>>     Thanks,
>>     Nabil
>>
>>     From: "Black, David" <david.black@emc.com
>><mailto:david.black@emc.com>>
>>     Date: Monday, August 20, 2012 8:57 PM
>>     To: "dinmohan@hotmail.com <mailto:dinmohan@hotmail.com>"
>>     <dinmohan@hotmail.com <mailto:dinmohan@hotmail.com>>, "Bitar, Nabil
>>     N" <nabil.n.bitar@one.verizon.com
>>     <mailto:nabil.n.bitar@one.verizon.com>>, Sagessi <sajassi@cisco.com
>>     <mailto:sajassi@cisco.com>>, "gen-art@ietf.org
>>     <mailto:gen-art@ietf.org>" <gen-art@ietf.org
>><mailto:gen-art@ietf.org>>
>>     Cc: "Black, David" <david.black@emc.com
>>     <mailto:david.black@emc.com>>, "pwe3@ietf.org
>>     <mailto:pwe3@ietf.org>" <pwe3@ietf.org <mailto:pwe3@ietf.org>>,
>>     "ietf@ietf.org <mailto:ietf@ietf.org>" <ietf@ietf.org
>>     <mailto:ietf@ietf.org>>
>>     Subject: Gen-ART review of draft-ietf-pwe3-mpls-eth-oam-iwk-06
>>
>>     I am the assigned Gen-ART reviewer for this draft. For background on
>>     Gen-ART, please
>>     see the FAQ at
>>     <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>>
>>     Please resolve these comments along with any other Last Call
>>     comments you may receive.
>>
>>     Document: draft-ietf-pwe3-mpls-eth-oam-iwk-06
>>     Reviewer: David L. Black
>>     Review Date: August 20, 2012
>>     IETF LC End Date: August 20, 2012
>>
>>     Summary:
>>     This draft is basically ready for publication, but has nits that
>>     should be fixed before publication.
>>
>>     <NB> Thanks.
>>
>>     This draft covers defect behavior for Ethernet pseudowires,
>>
>>     including defect state mapping and PE defect reporting behavior.
>>
>>     The draft is generally in good shape.  I found a few minor nits.
>>
>>     1) The draft uses a lot of acronyms - while each acronym appears to
>>
>>     be expanded on first use, an additional section near the start of
>>the
>>
>>     draft listing all of them would be helpful.
>>
>>
>>     <NB> Done.
>>
>>     2) There's a typo in the first paragraph of section 2:
>>
>>           covers the following Ethernet OAM (Opertaions, Administration
>>and
>>
>>     Opertaions -> Operations.
>>
>>
>>     <NB> Thanks. Done.
>>
>>     3) The following normative reference is incomplete - please add
>>     additional
>>
>>     information that will enable a reader to locate the referenced
>>document:
>>
>>           [MEF16] "Ethernet Local Management Interface", MEF16, January
>>     2006.
>>
>>
>>     [MEF16] "Ethernet Local Management Interface", Metro Ethernet Forum
>>     Technical Specification MEF16, January 2006.
>>
>>     <NB> changed it to :
>>
>>     4) idnits2.12.13 did not like the pagination:
>>
>>        =3D=3D The page length should not exceed 58 lines per page, but t=
here
>>     was 22
>>           longer pages, the longest (page 1) being 61 lines
>>
>>     <NB> That will be fixed.
>>     Thanks,
>>     --David
>>     ----------------------------------------------------
>>     David L. Black, Distinguished Engineer
>>     EMC Corporation, 176 South St., Hopkinton, MA  01748
>>     +1 (508) 293-7953 <tel:%2B1%20%28508%29%20293-7953>             FAX:
>>     +1 (508) 293-7786 <tel:%2B1%20%28508%29%20293-7786>
>>     david.black@emc.com <mailto:david.black@emc.com>        Mobile: +1
>>     (978) 394-7754 <tel:%2B1%20%28978%29%20394-7754>
>>     ----------------------------------------------------
>>
>>     _______________________________________________
>>     pwe3 mailing list
>>     pwe3@ietf.org <mailto:pwe3@ietf.org>
>>     https://www.ietf.org/mailman/listinfo/pwe3
>>
>>
>>
>>
>> _______________________________________________
>> pwe3 mailing list
>> pwe3@ietf.org
>> https://www.ietf.org/mailman/listinfo/pwe3
>>
>
>--=20
>
>
>Loa Andersson                         email: loa.andersson@ericsson.com
>Sr Strategy and Standards Manager            loa@pi.nu
>Ericsson Inc                          phone: +46 10 717 52 13
>                                              +46 767 72 92 13


From nabil.n.bitar@verizon.com  Mon Jan 14 06:37:03 2013
Return-Path: <nabil.n.bitar@verizon.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5532321F89C0; Mon, 14 Jan 2013 06:37:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.307
X-Spam-Level: 
X-Spam-Status: No, score=-3.307 tagged_above=-999 required=5 tests=[AWL=0.291,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
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 vay+zRgU44Dl; Mon, 14 Jan 2013 06:37:00 -0800 (PST)
Received: from fldsmtpe03.verizon.com (fldsmtpe03.verizon.com [140.108.26.142]) by ietfa.amsl.com (Postfix) with ESMTP id 925AC21F89E5; Mon, 14 Jan 2013 06:36:59 -0800 (PST)
X-IronPort-Anti-Spam-Filtered: false
Received: from unknown (HELO fldsmtpi03.verizon.com) ([166.68.71.145]) by fldsmtpe03.verizon.com with ESMTP; 14 Jan 2013 14:36:49 +0000
From: "Bitar, Nabil N" <nabil.n.bitar@verizon.com>
X-IronPort-AV: E=Sophos;i="4.84,468,1355097600";  d="scan'208,217";a="396006186"
Received: from fldp1lumxc7hb03.verizon.com (HELO FLDP1LUMXC7HB03.us.one.verizon.com) ([166.68.75.86]) by fldsmtpi03.verizon.com with ESMTP; 14 Jan 2013 14:36:49 +0000
Received: from fldp1lumxc7v63.us.one.verizon.com ([166.68.45.45]) by FLDP1LUMXC7HB03.us.one.verizon.com ([166.68.75.86]) with mapi; Mon, 14 Jan 2013 09:36:48 -0500
To: Gregory Mirsky <gregory.mirsky@ericsson.com>, Loa Andersson <loa@pi.nu>
Date: Mon, 14 Jan 2013 09:36:39 -0500
Subject: Re: [PWE3] Gen-ART review of draft-ietf-pwe3-mpls-eth-oam-iwk-06
Thread-Topic: [PWE3] Gen-ART review of draft-ietf-pwe3-mpls-eth-oam-iwk-06
Thread-Index: Ac3yZJWLxxQPvVmTQwGqIpTqn3FWIg==
Message-ID: <CD198217.75765%nabil.n.bitar@verizon.com>
In-Reply-To: <7347100B5761DC41A166AC17F22DF112039212@eusaamb103.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.2.3.120616
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_CD19821775765nabilnbitarverizoncom_"
MIME-Version: 1.0
Cc: "sajassi@cisco.com" <sajassi@cisco.com>, "gen-art@ietf.org" <gen-art@ietf.org>, "dinmohan@hotmail.com" <dinmohan@hotmail.com>, "pwe3@ietf.org" <pwe3@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Jan 2013 14:37:03 -0000

--_000_CD19821775765nabilnbitarverizoncom_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi Greg,
Please, see my other email I just sent.

Thanks,
Nabil

From: Gregory Mirsky <gregory.mirsky@ericsson.com<mailto:gregory.mirsky@eri=
csson.com>>
Date: Tuesday, January 8, 2013 11:45 AM
To: Loa Andersson <loa@pi.nu<mailto:loa@pi.nu>>
Cc: "pwe3@ietf.org<mailto:pwe3@ietf.org>" <pwe3@ietf.org<mailto:pwe3@ietf.o=
rg>>, "gen-art@ietf.org<mailto:gen-art@ietf.org>" <gen-art@ietf.org<mailto:=
gen-art@ietf.org>>, "dinmohan@hotmail.com<mailto:dinmohan@hotmail.com>" <di=
nmohan@hotmail.com<mailto:dinmohan@hotmail.com>>, Sagessi <sajassi@cisco.co=
m<mailto:sajassi@cisco.com>>, "ietf@ietf.org<mailto:ietf@ietf.org>" <ietf@i=
etf.org<mailto:ietf@ietf.org>>
Subject: Re: [PWE3] Gen-ART review of draft-ietf-pwe3-mpls-eth-oam-iwk-06

Dear Huub and Loa,
my brain did s/Reverese/Remote/ by itself. Indeed, 802.1ag and Y.1731 use R=
DI for Remote Defect Indication, and nothing in Reverse. And that how draft=
-ietf-pwe3-mpls-eth-oam-iwk-06 should expand RDI as well.

        Regards,
                Greg

-----Original Message-----
From: pwe3-bounces@ietf.org<mailto:pwe3-bounces@ietf.org> [mailto:pwe3-boun=
ces@ietf.org] On Behalf Of Loa Andersson
Sent: Tuesday, January 08, 2013 3:02 AM
To: Greg Mirsky
Cc: ietf@ietf.org<mailto:ietf@ietf.org>; gen-art@ietf.org<mailto:gen-art@ie=
tf.org>; dinmohan@hotmail.com<mailto:dinmohan@hotmail.com>; sajassi@cisco.c=
om<mailto:sajassi@cisco.com>; pwe3@ietf.org<mailto:pwe3@ietf.org>
Subject: Re: [PWE3] Gen-ART review of draft-ietf-pwe3-mpls-eth-oam-iwk-06

Greg,

RFC 6428 expands RDI as:

    RDI: Remote Defect Indication

/Loa

On 2013-01-07 21:51, Greg Mirsky wrote:
> Dear Nabil,
> can we avoid different interpretation of the same abbreviation (RDI):
>
>     RDI   Remote Defect Indication for Continuity Check Message
>
>     RDI   Reverse Defect Indication
>
> AFAIK, the latter form is the interpretation used by both IEEE 802.1ag
> and Y.1731. How useful is the first form?
>
> Regards,
>
> Greg
>
>
>
> On Fri, Jan 4, 2013 at 8:17 AM, Bitar, Nabil N
> <nabil.n.bitar@verizon.com<mailto:nabil.n.bitar@verizon.com> <mailto:nabi=
l.n.bitar@verizon.com>> wrote:
>
>     Hi Dave,
>     Related to abbreviations comment below and to be clearer, I renamed
>     the original terminology section to "Abbreviations and Terminology".
>     I also created a subsection called "Abbreviations" ,and
>     "Terminology" became the second subsection.  Here iis how the
> edits look
>
>
>       3. Abbreviations and Terminology____
>
>
>         3.1. Abbreviations____
>
>     AISAlarm Indication Signal____
>
>     ACAttachment Circuit____
>
>     BFDBidirectional Forwarding Detection____
>
>     CCContinuity Check____
>
>     CCMContinuity Check Message____
>
>     CECustomer Equipment____
>
>     CVConnectivity Verification____
>
>     E-LMI Ethernet Local Management Interface____
>
>     EVCEthernet Virtual Circuit____
>
>     LDPLabel Distribution Protocol____
>
>     LoSLoss of Signal____
>
>     MAMaintenance Association____
>
>     MDMaintenance Domain____
>
>     MEMaintenance Entity____
>
>     MEGMaintenance Entity Group____
>
>     MEPMaintenance End Point____
>
>     MIPMaintenance End Point____
>
>     MPLSMultiprotocol Label Switching____
>
>     MS-PW Multi-Segment Pseudowire____
>
>     NSNative Service____
>
>     OAMOperations, Administration, and Maintenance____
>
>     PEProvider Edge____
>
>     PSNPacket Switched Network____
>
>     PWPseudowire____
>
>     RDIRemote Defect Indication for Continuity Check Message____
>
>         RDI   Reverse Defect Indication
>
>     S-PESwitching Provider Edge____
>
>     TLVType Length Value____
>
>     T-PETerminating Provider Edge____
>
>     __ __
>
>
>         3.2. Terminology____
>
>     This document uses the following terms with corresponding
>     definitions: ____
>
>     - MD Level:Maintenance Domain (MD) Level which identifies a value in
>     the range of 0-7 associated with Ethernet OAM frame. MD Level
>     identifies the span of the Ethernet OAM frame.____
>
>     - MEP:Maintenance End Point is responsible for origination and
>     termination of OAM frames for a given MEG.____
>
>     - MIP: Maintenance Intermediate Point is located between peer MEPs
>     and can process OAM frames but does not initiate or terminate
> them.____
>
>     Further, this document also uses the terminology and conventions
>     used in [RFC6310].____
>
>
>
>     Thanks,
>
>     Nabil
>
>
>     From: <Bitar>, Nabil N <nabil.n.bitar@one.verizon.com<mailto:nabil.n.=
bitar@one.verizon.com>
>     <mailto:nabil.n.bitar@one.verizon.com>>
>     Date: Wednesday, January 2, 2013 11:28 AM
>     To: "Black, David" <david.black@emc.com<mailto:david.black@emc.com>
>     <mailto:david.black@emc.com>>, "dinmohan@hotmail.com<mailto:dinmohan@=
hotmail.com>
>     <mailto:dinmohan@hotmail.com>" <dinmohan@hotmail.com<mailto:dinmohan@=
hotmail.com>
>     <mailto:dinmohan@hotmail.com>>, "Bitar, Nabil N"
>     <nabil.n.bitar@one.verizon.com<mailto:nabil.n.bitar@one.verizon.com>
>     <mailto:nabil.n.bitar@one.verizon.com>>, Sagessi <sajassi@cisco.com<m=
ailto:sajassi@cisco.com>
>     <mailto:sajassi@cisco.com>>, "gen-art@ietf.org<mailto:gen-art@ietf.or=
g>
>     <mailto:gen-art@ietf.org>" <gen-art@ietf.org<mailto:gen-art@ietf.org>=
 <mailto:gen-art@ietf.org>>
>     Cc: "pwe3@ietf.org<mailto:pwe3@ietf.org> <mailto:pwe3@ietf.org>" <pwe=
3@ietf.org<mailto:pwe3@ietf.org>
>     <mailto:pwe3@ietf.org>>, "ietf@ietf.org<mailto:ietf@ietf.org> <mailto=
:ietf@ietf.org>"
>     <ietf@ietf.org<mailto:ietf@ietf.org> <mailto:ietf@ietf.org>>
>     Subject: Re: Gen-ART review of draft-ietf-pwe3-mpls-eth-oam-iwk-06
>
>     Hi Dave,
>     Sorry for a late reply addressing your comments. Please, see inline.
>
>     Thanks,
>     Nabil
>
>     From: "Black, David" <david.black@emc.com<mailto:david.black@emc.com>=
 <mailto:david.black@emc.com>>
>     Date: Monday, August 20, 2012 8:57 PM
>     To: "dinmohan@hotmail.com<mailto:dinmohan@hotmail.com> <mailto:dinmoh=
an@hotmail.com>"
>     <dinmohan@hotmail.com<mailto:dinmohan@hotmail.com> <mailto:dinmohan@h=
otmail.com>>, "Bitar, Nabil
>     N" <nabil.n.bitar@one.verizon.com<mailto:nabil.n.bitar@one.verizon.co=
m>
>     <mailto:nabil.n.bitar@one.verizon.com>>, Sagessi <sajassi@cisco.com<m=
ailto:sajassi@cisco.com>
>     <mailto:sajassi@cisco.com>>, "gen-art@ietf.org<mailto:gen-art@ietf.or=
g>
>     <mailto:gen-art@ietf.org>" <gen-art@ietf.org<mailto:gen-art@ietf.org>=
 <mailto:gen-art@ietf.org>>
>     Cc: "Black, David" <david.black@emc.com<mailto:david.black@emc.com>
>     <mailto:david.black@emc.com>>, "pwe3@ietf.org<mailto:pwe3@ietf.org>
>     <mailto:pwe3@ietf.org>" <pwe3@ietf.org<mailto:pwe3@ietf.org> <mailto:=
pwe3@ietf.org>>,
>     "ietf@ietf.org<mailto:ietf@ietf.org> <mailto:ietf@ietf.org>" <ietf@ie=
tf.org<mailto:ietf@ietf.org>
>     <mailto:ietf@ietf.org>>
>     Subject: Gen-ART review of draft-ietf-pwe3-mpls-eth-oam-iwk-06
>
>     I am the assigned Gen-ART reviewer for this draft. For background on
>     Gen-ART, please
>     see the FAQ at
>     <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>
>     Please resolve these comments along with any other Last Call
>     comments you may receive.
>
>     Document: draft-ietf-pwe3-mpls-eth-oam-iwk-06
>     Reviewer: David L. Black
>     Review Date: August 20, 2012
>     IETF LC End Date: August 20, 2012
>
>     Summary:
>     This draft is basically ready for publication, but has nits that
>     should be fixed before publication.
>
>     <NB> Thanks.
>
>     This draft covers defect behavior for Ethernet pseudowires,
>
>     including defect state mapping and PE defect reporting behavior.
>
>     The draft is generally in good shape.  I found a few minor nits.
>
>     1) The draft uses a lot of acronyms - while each acronym appears
> to
>
>     be expanded on first use, an additional section near the start of
> the
>
>     draft listing all of them would be helpful.
>
>
>     <NB> Done.
>
>     2) There's a typo in the first paragraph of section 2:
>
>           covers the following Ethernet OAM (Opertaions,
> Administration and
>
>     Opertaions -> Operations.
>
>
>     <NB> Thanks. Done.
>
>     3) The following normative reference is incomplete - please add
>     additional
>
>     information that will enable a reader to locate the referenced docume=
nt:
>
>           [MEF16] "Ethernet Local Management Interface", MEF16, January
>     2006.
>
>
>     [MEF16] "Ethernet Local Management Interface", Metro Ethernet Forum
>     Technical Specification MEF16, January 2006.
>
>     <NB> changed it to :
>
>     4) idnits2.12.13 did not like the pagination:
>
>        =3D=3D The page length should not exceed 58 lines per page, but th=
ere
>     was 22
>           longer pages, the longest (page 1) being 61 lines
>
>     <NB> That will be fixed.
>     Thanks,
>     --David
>     ----------------------------------------------------
>     David L. Black, Distinguished Engineer
>     EMC Corporation, 176 South St., Hopkinton, MA  01748
>     +1 (508) 293-7953 <tel:%2B1%20%28508%29%20293-7953>             FAX:
>     +1 (508) 293-7786 <tel:%2B1%20%28508%29%20293-7786>
>     david.black@emc.com<mailto:david.black@emc.com> <mailto:david.black@e=
mc.com>        Mobile: +1
>     (978) 394-7754 <tel:%2B1%20%28978%29%20394-7754>
>     ----------------------------------------------------
>
>     _______________________________________________
>     pwe3 mailing list
>     pwe3@ietf.org<mailto:pwe3@ietf.org> <mailto:pwe3@ietf.org>
>     https://www.ietf.org/mailman/listinfo/pwe3
>
>
>
>
> _______________________________________________
> pwe3 mailing list
> pwe3@ietf.org<mailto:pwe3@ietf.org>
> https://www.ietf.org/mailman/listinfo/pwe3
>

--


Loa Andersson                         email: loa.andersson@ericsson.com<mai=
lto:loa.andersson@ericsson.com>
Sr Strategy and Standards Manager            loa@pi.nu<mailto:loa@pi.nu>
Ericsson Inc                          phone: +46 10 717 52 13
                                              +46 767 72 92 13 ____________=
___________________________________
pwe3 mailing list
pwe3@ietf.org<mailto:pwe3@ietf.org>
https://www.ietf.org/mailman/listinfo/pwe3


--_000_CD19821775765nabilnbitarverizoncom_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html><head></head><body style=3D"word-wrap: break-word; -webkit-nbsp-mode:=
 space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-si=
ze: 14px; font-family: Calibri, sans-serif; "><div>Hi Greg,</div><div>Pleas=
e, see my other email I just sent.</div><div><br></div><div>Thanks,</div><d=
iv>Nabil</div><div><br></div><span id=3D"OLK_SRC_BODY_SECTION"><div style=
=3D"font-family:Calibri; font-size:11pt; text-align:left; color:black; BORD=
ER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; PADD=
ING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; BORDER-RI=
GHT: medium none; PADDING-TOP: 3pt"><span style=3D"font-weight:bold">From: =
</span> Gregory Mirsky &lt;<a href=3D"mailto:gregory.mirsky@ericsson.com">g=
regory.mirsky@ericsson.com</a>&gt;<br><span style=3D"font-weight:bold">Date=
: </span> Tuesday, January 8, 2013 11:45 AM<br><span style=3D"font-weight:b=
old">To: </span> Loa Andersson &lt;<a href=3D"mailto:loa@pi.nu">loa@pi.nu</=
a>&gt;<br><span style=3D"font-weight:bold">Cc: </span> "<a href=3D"mailto:p=
we3@ietf.org">pwe3@ietf.org</a>" &lt;<a href=3D"mailto:pwe3@ietf.org">pwe3@=
ietf.org</a>&gt;, "<a href=3D"mailto:gen-art@ietf.org">gen-art@ietf.org</a>=
" &lt;<a href=3D"mailto:gen-art@ietf.org">gen-art@ietf.org</a>&gt;, "<a hre=
f=3D"mailto:dinmohan@hotmail.com">dinmohan@hotmail.com</a>" &lt;<a href=3D"=
mailto:dinmohan@hotmail.com">dinmohan@hotmail.com</a>&gt;, Sagessi &lt;<a h=
ref=3D"mailto:sajassi@cisco.com">sajassi@cisco.com</a>&gt;, "<a href=3D"mai=
lto:ietf@ietf.org">ietf@ietf.org</a>" &lt;<a href=3D"mailto:ietf@ietf.org">=
ietf@ietf.org</a>&gt;<br><span style=3D"font-weight:bold">Subject: </span> =
Re: [PWE3] Gen-ART review of draft-ietf-pwe3-mpls-eth-oam-iwk-06<br></div><=
div><br></div><div><meta http-equiv=3D"Content-Type" content=3D"text/html; =
charset=3Dutf-8"><meta name=3D"Generator" content=3D"Microsoft Exchange Ser=
ver"><!-- converted from rtf --><style><!-- .EmailQuote { margin-left: 1pt;=
 padding-left: 4pt; border-left: #800000 2px solid; } --></style><div><font=
 face=3D"Arial" size=3D"2"><span style=3D"font-size:10pt;"><div>Dear Huub a=
nd Loa,</div><div>my brain did s/Reverese/Remote/ by itself. Indeed, 802.1a=
g and Y.1731 use RDI for Remote Defect Indication, and nothing in Reverse. =
And that how draft-ietf-pwe3-mpls-eth-oam-iwk-06 should expand RDI as well.=
</div><div>&nbsp;</div><div>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Rega=
rds,</div><div>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Greg</div><div>&nbsp;</div><div>-----Origina=
l Message-----</div><div>From: <a href=3D"mailto:pwe3-bounces@ietf.org">pwe=
3-bounces@ietf.org</a> [<a href=3D"mailto:pwe3-bounces@ietf.org"><font colo=
r=3D"blue"><u>mailto:pwe3-bounces@ietf.org</u></font></a>] On Behalf Of Loa=
 Andersson</div><div>Sent: Tuesday, January 08, 2013 3:02 AM</div><div>To: =
Greg Mirsky</div><div>Cc: <a href=3D"mailto:ietf@ietf.org">ietf@ietf.org</a=
>; <a href=3D"mailto:gen-art@ietf.org">gen-art@ietf.org</a>; <a href=3D"mai=
lto:dinmohan@hotmail.com">dinmohan@hotmail.com</a>; <a href=3D"mailto:sajas=
si@cisco.com">sajassi@cisco.com</a>; <a href=3D"mailto:pwe3@ietf.org">pwe3@=
ietf.org</a></div><div>Subject: Re: [PWE3] Gen-ART review of draft-ietf-pwe=
3-mpls-eth-oam-iwk-06</div><div>&nbsp;</div><div>Greg,</div><div>&nbsp;</di=
v><div>RFC 6428 expands RDI as:</div><div>&nbsp;</div><div>&nbsp;&nbsp;&nbs=
p; RDI: Remote Defect Indication</div><div>&nbsp;</div><div>/Loa</div><div>=
&nbsp;</div><div>On 2013-01-07 21:51, Greg Mirsky wrote:</div><div>&gt; Dea=
r Nabil,</div><div>&gt; can we avoid different interpretation of the same a=
bbreviation (RDI):</div><div>&gt;</div><div>&gt;&nbsp;&nbsp;&nbsp;&nbsp; RD=
I&nbsp;&nbsp; Remote Defect Indication for Continuity Check Message</div><d=
iv>&gt;</div><div>&gt;&nbsp;&nbsp;&nbsp;&nbsp; RDI&nbsp;&nbsp; Reverse Defe=
ct Indication</div><div>&gt;</div><div>&gt; AFAIK, the latter form is the i=
nterpretation used by both IEEE 802.1ag </div><div>&gt; and Y.1731. How use=
ful is the first form?</div><div>&gt;</div><div>&gt; Regards,</div><div>&gt=
;</div><div>&gt; Greg</div><div>&gt;</div><div>&gt;</div><div>&gt;</div><di=
v>&gt; On Fri, Jan 4, 2013 at 8:17 AM, Bitar, Nabil N </div><div>&gt; &lt;<=
a href=3D"mailto:nabil.n.bitar@verizon.com">nabil.n.bitar@verizon.com</a> &=
lt;<a href=3D"mailto:nabil.n.bitar@verizon.com"><font color=3D"blue"><u>mai=
lto:nabil.n.bitar@verizon.com</u></font></a>&gt;&gt; wrote:</div><div>&gt;<=
/div><div>&gt;&nbsp;&nbsp;&nbsp;&nbsp; Hi Dave,</div><div>&gt;&nbsp;&nbsp;&=
nbsp;&nbsp; Related to abbreviations comment below and to be clearer, I ren=
amed</div><div>&gt;&nbsp;&nbsp;&nbsp;&nbsp; the original terminology sectio=
n to "Abbreviations and Terminology".</div><div>&gt;&nbsp;&nbsp;&nbsp;&nbsp=
; I also created a subsection called "Abbreviations" ,and</div><div>&gt;&nb=
sp;&nbsp;&nbsp;&nbsp; "Terminology" became the second subsection.&nbsp; Her=
e iis how the </div><div>&gt; edits look</div><div>&gt;</div><div>&gt;</div=
><div>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 3. Abbreviations and Termino=
logy____</div><div>&gt;</div><div>&gt;</div><div>&gt;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp; 3.1. Abbreviations____</div><div>&gt;</div><div>=
&gt;&nbsp;&nbsp;&nbsp;&nbsp; AISAlarm Indication Signal____</div><div>&gt;<=
/div><div>&gt;&nbsp;&nbsp;&nbsp;&nbsp; ACAttachment Circuit____</div><div>&=
gt;</div><div>&gt;&nbsp;&nbsp;&nbsp;&nbsp; BFDBidirectional Forwarding Dete=
ction____</div><div>&gt;</div><div>&gt;&nbsp;&nbsp;&nbsp;&nbsp; CCContinuit=
y Check____</div><div>&gt;</div><div>&gt;&nbsp;&nbsp;&nbsp;&nbsp; CCMContin=
uity Check Message____</div><div>&gt;</div><div>&gt;&nbsp;&nbsp;&nbsp;&nbsp=
; CECustomer Equipment____</div><div>&gt;</div><div>&gt;&nbsp;&nbsp;&nbsp;&=
nbsp; CVConnectivity Verification____</div><div>&gt;</div><div>&gt;&nbsp;&n=
bsp;&nbsp;&nbsp; E-LMI Ethernet Local Management Interface____</div><div>&g=
t;</div><div>&gt;&nbsp;&nbsp;&nbsp;&nbsp; EVCEthernet Virtual Circuit____</=
div><div>&gt;</div><div>&gt;&nbsp;&nbsp;&nbsp;&nbsp; LDPLabel Distribution =
Protocol____</div><div>&gt;</div><div>&gt;&nbsp;&nbsp;&nbsp;&nbsp; LoSLoss =
of Signal____</div><div>&gt;</div><div>&gt;&nbsp;&nbsp;&nbsp;&nbsp; MAMaint=
enance Association____</div><div>&gt;</div><div>&gt;&nbsp;&nbsp;&nbsp;&nbsp=
; MDMaintenance Domain____</div><div>&gt;</div><div>&gt;&nbsp;&nbsp;&nbsp;&=
nbsp; MEMaintenance Entity____</div><div>&gt;</div><div>&gt;&nbsp;&nbsp;&nb=
sp;&nbsp; MEGMaintenance Entity Group____</div><div>&gt;</div><div>&gt;&nbs=
p;&nbsp;&nbsp;&nbsp; MEPMaintenance End Point____</div><div>&gt;</div><div>=
&gt;&nbsp;&nbsp;&nbsp;&nbsp; MIPMaintenance End Point____</div><div>&gt;</d=
iv><div>&gt;&nbsp;&nbsp;&nbsp;&nbsp; MPLSMultiprotocol Label Switching____<=
/div><div>&gt;</div><div>&gt;&nbsp;&nbsp;&nbsp;&nbsp; MS-PW Multi-Segment P=
seudowire____</div><div>&gt;</div><div>&gt;&nbsp;&nbsp;&nbsp;&nbsp; NSNativ=
e Service____</div><div>&gt;</div><div>&gt;&nbsp;&nbsp;&nbsp;&nbsp; OAMOper=
ations, Administration, and Maintenance____</div><div>&gt;</div><div>&gt;&n=
bsp;&nbsp;&nbsp;&nbsp; PEProvider Edge____</div><div>&gt;</div><div>&gt;&nb=
sp;&nbsp;&nbsp;&nbsp; PSNPacket Switched Network____</div><div>&gt;</div><d=
iv>&gt;&nbsp;&nbsp;&nbsp;&nbsp; PWPseudowire____</div><div>&gt;</div><div>&=
gt;&nbsp;&nbsp;&nbsp;&nbsp; RDIRemote Defect Indication for Continuity Chec=
k Message____</div><div>&gt;</div><div>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp; RDI&nbsp;&nbsp; Reverse Defect Indication</div><div>&gt;</=
div><div>&gt;&nbsp;&nbsp;&nbsp;&nbsp; S-PESwitching Provider Edge____</div>=
<div>&gt;</div><div>&gt;&nbsp;&nbsp;&nbsp;&nbsp; TLVType Length Value____</=
div><div>&gt;</div><div>&gt;&nbsp;&nbsp;&nbsp;&nbsp; T-PETerminating Provid=
er Edge____</div><div>&gt;</div><div>&gt;&nbsp;&nbsp;&nbsp;&nbsp; __ __</di=
v><div>&gt;</div><div>&gt;</div><div>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp; 3.2. Terminology____</div><div>&gt;</div><div>&gt;&nbsp;&nbs=
p;&nbsp;&nbsp; This document uses the following terms with corresponding</d=
iv><div>&gt;&nbsp;&nbsp;&nbsp;&nbsp; definitions: ____</div><div>&gt;</div>=
<div>&gt;&nbsp;&nbsp;&nbsp;&nbsp; - MD Level:Maintenance Domain (MD) Level =
which identifies a value in</div><div>&gt;&nbsp;&nbsp;&nbsp;&nbsp; the rang=
e of 0-7 associated with Ethernet OAM frame. MD Level</div><div>&gt;&nbsp;&=
nbsp;&nbsp;&nbsp; identifies the span of the Ethernet OAM frame.____</div><=
div>&gt;</div><div>&gt;&nbsp;&nbsp;&nbsp;&nbsp; - MEP:Maintenance End Point=
 is responsible for origination and</div><div>&gt;&nbsp;&nbsp;&nbsp;&nbsp; =
termination of OAM frames for a given MEG.____</div><div>&gt;</div><div>&gt=
;&nbsp;&nbsp;&nbsp;&nbsp; - MIP: Maintenance Intermediate Point is located =
between peer MEPs</div><div>&gt;&nbsp;&nbsp;&nbsp;&nbsp; and can process OA=
M frames but does not initiate or terminate </div><div>&gt; them.____</div>=
<div>&gt;</div><div>&gt;&nbsp;&nbsp;&nbsp;&nbsp; Further, this document als=
o uses the terminology and conventions</div><div>&gt;&nbsp;&nbsp;&nbsp;&nbs=
p; used in [RFC6310].____</div><div>&gt;</div><div>&gt;</div><div>&gt;</div=
><div>&gt;&nbsp;&nbsp;&nbsp;&nbsp; Thanks,</div><div>&gt;</div><div>&gt;&nb=
sp;&nbsp;&nbsp;&nbsp; Nabil</div><div>&gt;</div><div>&gt;</div><div>&gt;&nb=
sp;&nbsp;&nbsp;&nbsp; From: &lt;Bitar&gt;, Nabil N &lt;<a href=3D"mailto:na=
bil.n.bitar@one.verizon.com">nabil.n.bitar@one.verizon.com</a></div><div>&g=
t;&nbsp;&nbsp;&nbsp;&nbsp; &lt;<a href=3D"mailto:nabil.n.bitar@one.verizon.=
com"><font color=3D"blue"><u>mailto:nabil.n.bitar@one.verizon.com</u></font=
></a>&gt;&gt;</div><div>&gt;&nbsp;&nbsp;&nbsp;&nbsp; Date: Wednesday, Janua=
ry 2, 2013 11:28 AM</div><div>&gt;&nbsp;&nbsp;&nbsp;&nbsp; To: "Black, Davi=
d" &lt;<a href=3D"mailto:david.black@emc.com">david.black@emc.com</a></div>=
<div>&gt;&nbsp;&nbsp;&nbsp;&nbsp; &lt;<a href=3D"mailto:david.black@emc.com=
"><font color=3D"blue"><u>mailto:david.black@emc.com</u></font></a>&gt;&gt;=
, "<a href=3D"mailto:dinmohan@hotmail.com">dinmohan@hotmail.com</a></div><d=
iv>&gt;&nbsp;&nbsp;&nbsp;&nbsp; &lt;<a href=3D"mailto:dinmohan@hotmail.com"=
><font color=3D"blue"><u>mailto:dinmohan@hotmail.com</u></font></a>&gt;" &l=
t;<a href=3D"mailto:dinmohan@hotmail.com">dinmohan@hotmail.com</a></div><di=
v>&gt;&nbsp;&nbsp;&nbsp;&nbsp; &lt;<a href=3D"mailto:dinmohan@hotmail.com">=
<font color=3D"blue"><u>mailto:dinmohan@hotmail.com</u></font></a>&gt;&gt;,=
 "Bitar, Nabil N"</div><div>&gt;&nbsp;&nbsp;&nbsp;&nbsp; &lt;<a href=3D"mai=
lto:nabil.n.bitar@one.verizon.com">nabil.n.bitar@one.verizon.com</a></div><=
div>&gt;&nbsp;&nbsp;&nbsp;&nbsp; &lt;<a href=3D"mailto:nabil.n.bitar@one.ve=
rizon.com"><font color=3D"blue"><u>mailto:nabil.n.bitar@one.verizon.com</u>=
</font></a>&gt;&gt;, Sagessi &lt;<a href=3D"mailto:sajassi@cisco.com">sajas=
si@cisco.com</a></div><div>&gt;&nbsp;&nbsp;&nbsp;&nbsp; &lt;<a href=3D"mail=
to:sajassi@cisco.com"><font color=3D"blue"><u>mailto:sajassi@cisco.com</u><=
/font></a>&gt;&gt;, "<a href=3D"mailto:gen-art@ietf.org">gen-art@ietf.org</=
a></div><div>&gt;&nbsp;&nbsp;&nbsp;&nbsp; &lt;<a href=3D"mailto:gen-art@iet=
f.org"><font color=3D"blue"><u>mailto:gen-art@ietf.org</u></font></a>&gt;" =
&lt;<a href=3D"mailto:gen-art@ietf.org">gen-art@ietf.org</a> &lt;<a href=3D=
"mailto:gen-art@ietf.org"><font color=3D"blue"><u>mailto:gen-art@ietf.org</=
u></font></a>&gt;&gt;</div><div>&gt;&nbsp;&nbsp;&nbsp;&nbsp; Cc: "<a href=
=3D"mailto:pwe3@ietf.org">pwe3@ietf.org</a> &lt;<a href=3D"mailto:pwe3@ietf=
.org"><font color=3D"blue"><u>mailto:pwe3@ietf.org</u></font></a>&gt;" &lt;=
<a href=3D"mailto:pwe3@ietf.org">pwe3@ietf.org</a></div><div>&gt;&nbsp;&nbs=
p;&nbsp;&nbsp; &lt;<a href=3D"mailto:pwe3@ietf.org"><font color=3D"blue"><u=
>mailto:pwe3@ietf.org</u></font></a>&gt;&gt;, "<a href=3D"mailto:ietf@ietf.=
org">ietf@ietf.org</a> &lt;<a href=3D"mailto:ietf@ietf.org"><font color=3D"=
blue"><u>mailto:ietf@ietf.org</u></font></a>&gt;"</div><div>&gt;&nbsp;&nbsp=
;&nbsp;&nbsp; &lt;<a href=3D"mailto:ietf@ietf.org">ietf@ietf.org</a> &lt;<a=
 href=3D"mailto:ietf@ietf.org"><font color=3D"blue"><u>mailto:ietf@ietf.org=
</u></font></a>&gt;&gt;</div><div>&gt;&nbsp;&nbsp;&nbsp;&nbsp; Subject: Re:=
 Gen-ART review of draft-ietf-pwe3-mpls-eth-oam-iwk-06</div><div>&gt;</div>=
<div>&gt;&nbsp;&nbsp;&nbsp;&nbsp; Hi Dave,</div><div>&gt;&nbsp;&nbsp;&nbsp;=
&nbsp; Sorry for a late reply addressing your comments. Please, see inline.=
</div><div>&gt;</div><div>&gt;&nbsp;&nbsp;&nbsp;&nbsp; Thanks,</div><div>&g=
t;&nbsp;&nbsp;&nbsp;&nbsp; Nabil</div><div>&gt;</div><div>&gt;&nbsp;&nbsp;&=
nbsp;&nbsp; From: "Black, David" &lt;<a href=3D"mailto:david.black@emc.com"=
>david.black@emc.com</a> &lt;<a href=3D"mailto:david.black@emc.com"><font c=
olor=3D"blue"><u>mailto:david.black@emc.com</u></font></a>&gt;&gt;</div><di=
v>&gt;&nbsp;&nbsp;&nbsp;&nbsp; Date: Monday, August 20, 2012 8:57 PM</div><=
div>&gt;&nbsp;&nbsp;&nbsp;&nbsp; To: "<a href=3D"mailto:dinmohan@hotmail.co=
m">dinmohan@hotmail.com</a> &lt;<a href=3D"mailto:dinmohan@hotmail.com"><fo=
nt color=3D"blue"><u>mailto:dinmohan@hotmail.com</u></font></a>&gt;"</div><=
div>&gt;&nbsp;&nbsp;&nbsp;&nbsp; &lt;<a href=3D"mailto:dinmohan@hotmail.com=
">dinmohan@hotmail.com</a> &lt;<a href=3D"mailto:dinmohan@hotmail.com"><fon=
t color=3D"blue"><u>mailto:dinmohan@hotmail.com</u></font></a>&gt;&gt;, "Bi=
tar, Nabil</div><div>&gt;&nbsp;&nbsp;&nbsp;&nbsp; N" &lt;<a href=3D"mailto:=
nabil.n.bitar@one.verizon.com">nabil.n.bitar@one.verizon.com</a></div><div>=
&gt;&nbsp;&nbsp;&nbsp;&nbsp; &lt;<a href=3D"mailto:nabil.n.bitar@one.verizo=
n.com"><font color=3D"blue"><u>mailto:nabil.n.bitar@one.verizon.com</u></fo=
nt></a>&gt;&gt;, Sagessi &lt;<a href=3D"mailto:sajassi@cisco.com">sajassi@c=
isco.com</a></div><div>&gt;&nbsp;&nbsp;&nbsp;&nbsp; &lt;<a href=3D"mailto:s=
ajassi@cisco.com"><font color=3D"blue"><u>mailto:sajassi@cisco.com</u></fon=
t></a>&gt;&gt;, "<a href=3D"mailto:gen-art@ietf.org">gen-art@ietf.org</a></=
div><div>&gt;&nbsp;&nbsp;&nbsp;&nbsp; &lt;<a href=3D"mailto:gen-art@ietf.or=
g"><font color=3D"blue"><u>mailto:gen-art@ietf.org</u></font></a>&gt;" &lt;=
<a href=3D"mailto:gen-art@ietf.org">gen-art@ietf.org</a> &lt;<a href=3D"mai=
lto:gen-art@ietf.org"><font color=3D"blue"><u>mailto:gen-art@ietf.org</u></=
font></a>&gt;&gt;</div><div>&gt;&nbsp;&nbsp;&nbsp;&nbsp; Cc: "Black, David"=
 &lt;<a href=3D"mailto:david.black@emc.com">david.black@emc.com</a></div><d=
iv>&gt;&nbsp;&nbsp;&nbsp;&nbsp; &lt;<a href=3D"mailto:david.black@emc.com">=
<font color=3D"blue"><u>mailto:david.black@emc.com</u></font></a>&gt;&gt;, =
"<a href=3D"mailto:pwe3@ietf.org">pwe3@ietf.org</a></div><div>&gt;&nbsp;&nb=
sp;&nbsp;&nbsp; &lt;<a href=3D"mailto:pwe3@ietf.org"><font color=3D"blue"><=
u>mailto:pwe3@ietf.org</u></font></a>&gt;" &lt;<a href=3D"mailto:pwe3@ietf.=
org">pwe3@ietf.org</a> &lt;<a href=3D"mailto:pwe3@ietf.org"><font color=3D"=
blue"><u>mailto:pwe3@ietf.org</u></font></a>&gt;&gt;,</div><div>&gt;&nbsp;&=
nbsp;&nbsp;&nbsp; "<a href=3D"mailto:ietf@ietf.org">ietf@ietf.org</a> &lt;<=
a href=3D"mailto:ietf@ietf.org"><font color=3D"blue"><u>mailto:ietf@ietf.or=
g</u></font></a>&gt;" &lt;<a href=3D"mailto:ietf@ietf.org">ietf@ietf.org</a=
></div><div>&gt;&nbsp;&nbsp;&nbsp;&nbsp; &lt;<a href=3D"mailto:ietf@ietf.or=
g"><font color=3D"blue"><u>mailto:ietf@ietf.org</u></font></a>&gt;&gt;</div=
><div>&gt;&nbsp;&nbsp;&nbsp;&nbsp; Subject: Gen-ART review of draft-ietf-pw=
e3-mpls-eth-oam-iwk-06</div><div>&gt;</div><div>&gt;&nbsp;&nbsp;&nbsp;&nbsp=
; I am the assigned Gen-ART reviewer for this draft. For background on</div=
><div>&gt;&nbsp;&nbsp;&nbsp;&nbsp; Gen-ART, please</div><div>&gt;&nbsp;&nbs=
p;&nbsp;&nbsp; see the FAQ at</div><div>&gt;&nbsp;&nbsp;&nbsp;&nbsp; &lt;<a=
 href=3D"http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq"><font col=
or=3D"blue"><u>http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq</u><=
/font></a>&gt;.</div><div>&gt;</div><div>&gt;&nbsp;&nbsp;&nbsp;&nbsp; Pleas=
e resolve these comments along with any other Last Call</div><div>&gt;&nbsp=
;&nbsp;&nbsp;&nbsp; comments you may receive.</div><div>&gt;</div><div>&gt;=
&nbsp;&nbsp;&nbsp;&nbsp; Document: draft-ietf-pwe3-mpls-eth-oam-iwk-06</div=
><div>&gt;&nbsp;&nbsp;&nbsp;&nbsp; Reviewer: David L. Black</div><div>&gt;&=
nbsp;&nbsp;&nbsp;&nbsp; Review Date: August 20, 2012</div><div>&gt;&nbsp;&n=
bsp;&nbsp;&nbsp; IETF LC End Date: August 20, 2012</div><div>&gt;</div><div=
>&gt;&nbsp;&nbsp;&nbsp;&nbsp; Summary:</div><div>&gt;&nbsp;&nbsp;&nbsp;&nbs=
p; This draft is basically ready for publication, but has nits that</div><d=
iv>&gt;&nbsp;&nbsp;&nbsp;&nbsp; should be fixed before publication.</div><d=
iv>&gt;</div><div>&gt;&nbsp;&nbsp;&nbsp;&nbsp; &lt;NB&gt; Thanks.</div><div=
>&gt;</div><div>&gt;&nbsp;&nbsp;&nbsp;&nbsp; This draft covers defect behav=
ior for Ethernet pseudowires,</div><div>&gt;</div><div>&gt;&nbsp;&nbsp;&nbs=
p;&nbsp; including defect state mapping and PE defect reporting behavior.</=
div><div>&gt;</div><div>&gt;&nbsp;&nbsp;&nbsp;&nbsp; The draft is generally=
 in good shape.&nbsp; I found a few minor nits.</div><div>&gt;</div><div>&g=
t;&nbsp;&nbsp;&nbsp;&nbsp; 1) The draft uses a lot of acronyms - while each=
 acronym appears </div><div>&gt; to</div><div>&gt;</div><div>&gt;&nbsp;&nbs=
p;&nbsp;&nbsp; be expanded on first use, an additional section near the sta=
rt of </div><div>&gt; the</div><div>&gt;</div><div>&gt;&nbsp;&nbsp;&nbsp;&n=
bsp; draft listing all of them would be helpful.</div><div>&gt;</div><div>&=
gt;</div><div>&gt;&nbsp;&nbsp;&nbsp;&nbsp; &lt;NB&gt; Done.</div><div>&gt;<=
/div><div>&gt;&nbsp;&nbsp;&nbsp;&nbsp; 2) There's a typo in the first parag=
raph of section 2:</div><div>&gt;</div><div>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; covers the following Ethernet OAM (Operta=
ions, </div><div>&gt; Administration and</div><div>&gt;</div><div>&gt;&nbsp=
;&nbsp;&nbsp;&nbsp; Opertaions -&gt; Operations.</div><div>&gt;</div><div>&=
gt;</div><div>&gt;&nbsp;&nbsp;&nbsp;&nbsp; &lt;NB&gt; Thanks. Done.</div><d=
iv>&gt;</div><div>&gt;&nbsp;&nbsp;&nbsp;&nbsp; 3) The following normative r=
eference is incomplete - please add</div><div>&gt;&nbsp;&nbsp;&nbsp;&nbsp; =
additional</div><div>&gt;</div><div>&gt;&nbsp;&nbsp;&nbsp;&nbsp; informatio=
n that will enable a reader to locate the referenced document:</div><div>&g=
t;</div><div>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p; [MEF16] "Ethernet Local Management Interface", MEF16, January</div><div>=
&gt;&nbsp;&nbsp;&nbsp;&nbsp; 2006.</div><div>&gt;</div><div>&gt;</div><div>=
&gt;&nbsp;&nbsp;&nbsp;&nbsp; [MEF16] "Ethernet Local Management Interface",=
 Metro Ethernet Forum</div><div>&gt;&nbsp;&nbsp;&nbsp;&nbsp; Technical Spec=
ification MEF16, January 2006.</div><div>&gt;</div><div>&gt;&nbsp;&nbsp;&nb=
sp;&nbsp; &lt;NB&gt; changed it to :</div><div>&gt;</div><div>&gt;&nbsp;&nb=
sp;&nbsp;&nbsp; 4) idnits2.12.13 did not like the pagination:</div><div>&gt=
;</div><div>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =3D=3D The page =
length should not exceed 58 lines per page, but there</div><div>&gt;&nbsp;&=
nbsp;&nbsp;&nbsp; was 22</div><div>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp; longer pages, the longest (page 1) being 61 lines<=
/div><div>&gt;</div><div>&gt;&nbsp;&nbsp;&nbsp;&nbsp; &lt;NB&gt; That will =
be fixed.</div><div>&gt;&nbsp;&nbsp;&nbsp;&nbsp; Thanks,</div><div>&gt;&nbs=
p;&nbsp;&nbsp;&nbsp; --David</div><div>&gt;&nbsp;&nbsp;&nbsp;&nbsp; -------=
---------------------------------------------</div><div>&gt;&nbsp;&nbsp;&nb=
sp;&nbsp; David L. Black, Distinguished Engineer</div><div>&gt;&nbsp;&nbsp;=
&nbsp;&nbsp; EMC Corporation, 176 South St., Hopkinton, MA&nbsp; 01748</div=
><div>&gt;&nbsp;&nbsp;&nbsp;&nbsp; +1 (508) 293-7953 &lt;tel:%2B1%20%28508%=
29%20293-7953&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp; FAX:</div><div>&gt;&nbsp;&nbsp;&nbsp;&nbsp; +1 (508) 293-778=
6 &lt;tel:%2B1%20%28508%29%20293-7786&gt;</div><div>&gt;&nbsp;&nbsp;&nbsp;&=
nbsp; <a href=3D"mailto:david.black@emc.com">david.black@emc.com</a> &lt;<a=
 href=3D"mailto:david.black@emc.com"><font color=3D"blue"><u>mailto:david.b=
lack@emc.com</u></font></a>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; M=
obile: +1</div><div>&gt;&nbsp;&nbsp;&nbsp;&nbsp; (978) 394-7754 &lt;tel:%2B=
1%20%28978%29%20394-7754&gt;</div><div>&gt;&nbsp;&nbsp;&nbsp;&nbsp; -------=
---------------------------------------------</div><div>&gt;</div><div>&gt;=
&nbsp;&nbsp;&nbsp;&nbsp; _______________________________________________</d=
iv><div>&gt;&nbsp;&nbsp;&nbsp;&nbsp; pwe3 mailing list</div><div>&gt;&nbsp;=
&nbsp;&nbsp;&nbsp; <a href=3D"mailto:pwe3@ietf.org">pwe3@ietf.org</a> &lt;<=
a href=3D"mailto:pwe3@ietf.org"><font color=3D"blue"><u>mailto:pwe3@ietf.or=
g</u></font></a>&gt;</div><div>&gt;&nbsp;&nbsp;&nbsp;&nbsp; <a href=3D"http=
s://www.ietf.org/mailman/listinfo/pwe3"><font color=3D"blue"><u>https://www=
.ietf.org/mailman/listinfo/pwe3</u></font></a></div><div>&gt;</div><div>&gt=
;</div><div>&gt;</div><div>&gt;</div><div>&gt; ____________________________=
___________________</div><div>&gt; pwe3 mailing list</div><div>&gt; <a href=
=3D"mailto:pwe3@ietf.org">pwe3@ietf.org</a></div><div>&gt; <a href=3D"https=
://www.ietf.org/mailman/listinfo/pwe3"><font color=3D"blue"><u>https://www.=
ietf.org/mailman/listinfo/pwe3</u></font></a></div><div>&gt;</div><div>&nbs=
p;</div><div>-- </div><div>&nbsp;</div><div>&nbsp;</div><div>Loa Andersson&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; email:=
 <a href=3D"mailto:loa.andersson@ericsson.com">loa.andersson@ericsson.com</=
a></div><div>Sr Strategy and Standards Manager&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <a href=3D"mailto:loa@pi.nu">loa@pi.n=
u</a></div><div>Ericsson Inc&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp; phone: +46 10 717 52 13</div><div>&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; +46 767 72 92 13 ________________________=
_______________________</div><div>pwe3 mailing list</div><div><a href=3D"ma=
ilto:pwe3@ietf.org">pwe3@ietf.org</a></div><div><a href=3D"https://www.ietf=
.org/mailman/listinfo/pwe3"><font color=3D"blue"><u>https://www.ietf.org/ma=
ilman/listinfo/pwe3</u></font></a></div><div>&nbsp;</div></span></font></di=
v></div></span></body></html>

--_000_CD19821775765nabilnbitarverizoncom_--

From benl@google.com  Mon Jan 14 06:38:20 2013
Return-Path: <benl@google.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1501021F858A for <ietf@ietfa.amsl.com>; Mon, 14 Jan 2013 06:38:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.902
X-Spam-Level: 
X-Spam-Status: No, score=-102.902 tagged_above=-999 required=5 tests=[AWL=0.075, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
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 v-O1L-aASi4s for <ietf@ietfa.amsl.com>; Mon, 14 Jan 2013 06:38:19 -0800 (PST)
Received: from mail-wi0-f182.google.com (mail-wi0-f182.google.com [209.85.212.182]) by ietfa.amsl.com (Postfix) with ESMTP id 0045921F865D for <ietf@ietf.org>; Mon, 14 Jan 2013 06:38:18 -0800 (PST)
Received: by mail-wi0-f182.google.com with SMTP id hn14so1287415wib.15 for <ietf@ietf.org>; Mon, 14 Jan 2013 06:38:18 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=YlwDiyN3XCYFkKreTjtU0GUr5gHzPBFdSzfZ96NxeNo=; b=ouN1X9mUV9XA5zsfu+jbXH0/fWzhfq0oEU1YGv/cJOMOFWFVoLXTIel15x7O8fc830 Ld4hcENzKpPcMIRD0cjUHPx1CQ4s7fAYD+wUrzTGP9KEin6v7L7FUhbSlH0vBNAU93wJ zHAUHKaGPcsn63HhJBxXugsAsRKtpNOAXdgGtWqJLmMoQTVJVKvBv2cs/wuYP0vFiQ1v oyepmsEmAI+IAB24WvWtASknPfeSQQe0LwhxOn8gt3Sy4gb5kr7OUG8AUed2qAauiWWB oaM6SipN2FkcSm8yJubnfZxGXWb9tYXKftL+6EzFOVX7rIzqfuXuAxAo4VG8CUaoRjaU v5GA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:x-gm-message-state; bh=YlwDiyN3XCYFkKreTjtU0GUr5gHzPBFdSzfZ96NxeNo=; b=SI6cBAduJjHshrsQwLwG0zfx+WciXpc0zXGbiAgY01YpZkIJUS6PhAt7SXfPnIAtef QYsAkz2wX7sBbZLxE766LsayBhOsfoE6u/OjWeMIpyWBvfdmwXhQq5QXHA+Z7UvoElck M6AeVpriQgf80k8XnmdX33xm7tKXga3fwKibfC4qeKsE2RkwjsE+s4CozARGGi4LlWVV 08kMaQ1tuL5AJnwz25BtWLhXGtqjuLVwdfgXRWucppzoHv0rIkzOrswyVsFg3EtPvyjB S/sn+9athr8UHrH/S2q2JSXODRlMjz9Ewhdnu7wzyX9OTbtg/+hQ3hgrhmIz8xSIXsz6 JB/A==
MIME-Version: 1.0
Received: by 10.180.97.68 with SMTP id dy4mr12889651wib.7.1358174297945; Mon, 14 Jan 2013 06:38:17 -0800 (PST)
Received: by 10.194.29.195 with HTTP; Mon, 14 Jan 2013 06:38:17 -0800 (PST)
In-Reply-To: <50F3EC5C.3070109@cs.tcd.ie>
References: <6.2.5.6.2.20130110065213.0ad01a90@resistor.net> <50F3EC5C.3070109@cs.tcd.ie>
Date: Mon, 14 Jan 2013 14:38:17 +0000
Message-ID: <CABrd9SToe0LvzSa+po6UeX92fBz=8mrk1k7Z5i_nph_2oSDKsQ@mail.gmail.com>
Subject: Re: [therightkey] Fwd: Re: Last Call: <draft-laurie-pki-sunlight-05.txt> (Certificate Transparency) to Experimental RFC
From: Ben Laurie <benl@google.com>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>, IETF Discussion List <ietf@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1
X-Gm-Message-State: ALoCoQnomVPDoD1llIbKfv5wIKcU3+8gVQX+igmRZPkAKWs2+3X4mBSFpZ+yK3EHllHZREw25fqvR6MvBrTBl0DYnBR0W+aXAJAgqc/KQlMYFRVUYd/m1JsXpYPyeI5QiXDJR0xyblH4LLPBjYJKq5fvDobDdRbjovnBADwew1gNvG+3u3NxJi4lM6cHOhalc+gBhMsWlsWd
Cc: SM <sm@resistor.net>, "therightkey@ietf.org" <therightkey@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Jan 2013 14:38:20 -0000

On 14 January 2013 11:30, Stephen Farrell <stephen.farrell@cs.tcd.ie> wrote:
>
> FYI. Some comments sent just to the IETF list. Please
> respond there.
>
> Thanks,
> S.
>
>
> -------- Original Message --------
> Subject: Re: Last Call: <draft-laurie-pki-sunlight-05.txt> (Certificate
> Transparency) to Experimental RFC
> Date: Thu, 10 Jan 2013 09:10:32 -0800
> From: SM <sm@resistor.net>
> To: ietf@ietf.org
>
> At 11:33 20-12-2012, The IESG wrote:
>>The IESG has received a request from an individual submitter to consider
>>the following document:
>>- 'Certificate Transparency'
>>   <draft-laurie-pki-sunlight-05.txt> as Experimental RFC
>>
>>The IESG plans to make a decision in the next few weeks, and solicits
>>final comments on this action. Please send substantive comments to the
>>ietf@ietf.org mailing lists by 2013-01-24. Exceptionally, comments may be
>
> In Section 1:
>
>   "Certificate Transparency aims to mitigate the problem of misissued
>    certificates by providing publicly auditable, append-only, untrusted
>    logs of all issued certificates."
>
> It seems that CAs are having trust issues.  ETSI TS 102 042 audits
> looks like paperwork instead of assessing what could go wrong
> [1].  Isn't Certificate Transparency trying to mitigate the problem
> of CAs issuing fake certificates instead of "misissued" certificates?

Is there a difference, when you get down to it?

>
> In Section 3:
>
>   "Logs MUST NOT impose any conditions on copying data retrieved from
>    the log."
>
> I am reading the above as meaning that the data retrieved is in the
> public domain.  Is that correct?

Yes. This is necessary for auditing/monitoring.

>  The wording could be improved as
> logs do not have any consciousness.

I have changed it to "Log operators..."

>
> In Section 3.1:
>
>  "In order to enable attribution of each logged certificate to its
>   issuer, the log SHALL publish a list of acceptable root certificates
>   (this list might usefully be the union of root certificates trusted
>   by major browser vendors)."
>
> Why is this a "SHALL" instead of a "MUST"?

MUST and SHALL are equivalent.

>  I suggest a better
> wording for "log" in the above as "log" is defined as "a single,
> ever-growing, append-only Merkle Tree of such certificates".  There
> are other occurrences of "log" in the draft that should be reviewed.

What wording do you suggest that would be better?

> In Section 4:
>
>   "Messages are sent as HTTPS GET or POST requests.  Parameters for
>    POSTs and all responses are encoded as JSON objects.
>
> I suggest adding a reference for JSON objects.

There will be in the next version.

>   "It must map one-to-one to a known public key (how this
>    mapping is distributed is out of scope for this document)."
>
> This looks like a requirement.

If it were a requirement it would say MUST - but in any case, it is
gone in the next version.

>   "A compliant v1 implementation MUST NOT expect this to
>    be 0 (i.e. v1)."
>
> What happens if the v1 implementation gets a zero?

I don't understand the question.

> In Section 7.3:
>
>   "Violation of the append-only property is detected by global gossiping,
>    i.e., everyone auditing logs comparing their versions of the latest
>    signed tree heads."
>
> In my humble opinion that's a practical approach.
>
> Section 7 is about security and privacy considerations.  I didn't see
> any privacy considerations in Section 7.

Good point, I have renamed it.

>  I don't think that it is
> really needed as the document is about publicly auditable logs.  If
> there is any concern about information disclosure it could be
> mentioned that Certificate Transparency is for public end-entities.
>
> Regards,
> -sm
>
> 1. Confirm that there are automatic blocks in place for high-profile
> domain names (including those targeted in the DigiNotar and Comodo
> attacks in 2011)
>
>
>
>
>
> _______________________________________________
> therightkey mailing list
> therightkey@ietf.org
> https://www.ietf.org/mailman/listinfo/therightkey

From john-ietf@jck.com  Mon Jan 14 07:19:28 2013
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 08DA321F8994 for <ietf@ietfa.amsl.com>; Mon, 14 Jan 2013 07:19:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.289
X-Spam-Level: 
X-Spam-Status: No, score=-102.289 tagged_above=-999 required=5 tests=[AWL=0.310, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 OjfmL5C4pgSW for <ietf@ietfa.amsl.com>; Mon, 14 Jan 2013 07:19:27 -0800 (PST)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 71C1D21F8901 for <ietf@ietf.org>; Mon, 14 Jan 2013 07:19:27 -0800 (PST)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1Tulor-000EKA-5X; Mon, 14 Jan 2013 10:19:25 -0500
Date: Mon, 14 Jan 2013 10:19:20 -0500
From: John C Klensin <john-ietf@jck.com>
To: David Conrad <drc@virtualized.org>
Subject: Re: I-D Action: draft-moonesamy-rfc2050-historic-00.txt
Message-ID: <A4FC42DF71F5F7E5A36C9D4C@JcK-HP8200.jck.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Jan 2013 15:19:28 -0000

--On Saturday, January 12, 2013 16:19 -0800 David Conrad
<drc@virtualized.org> wrote:

> John,
> 
> On Jan 12, 2013, at 2:21 PM, John C Klensin
> <john-ietf@jck.com> wrote:
>> However, I don't think the
>> section of 2860 that you cite helps very much because there is
>> another way to read it.  
> 
> As you know, there are many in both high and low places who
> choose the interpretation of 2860 that best fits their
> particular interests, regardless of the intent of that
> document (or, from personal experience, efforts to try to
> explain history or reality).  As such, I'll repeat: I do not
> believe it useful or helpful to go down that particular rat
> hole.

On those general subjects -- that trying to open the question of
2050 is a rat hole and that we should not go down it, we
completely agree.  I suggest that, despite stumbling into it,
trying to do biblical-quality exegesis on the specific text and
wording of most RFCs is also a rat hole (or perhaps just a
different edge of the same one).  That seems especially true for
RFCs from an era when the intent was to document agreement among
parties who were working together rather than trying to
establish boundaries among parties who were inclined to play
power games.

Beyond that, I find myself in almost complete agreement with
Randy and will not repeat what he has written.

   john



From barryleiba.mailing.lists@gmail.com  Mon Jan 14 07:54:51 2013
Return-Path: <barryleiba.mailing.lists@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D50FE21F88C8 for <ietf@ietfa.amsl.com>; Mon, 14 Jan 2013 07:54:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.138
X-Spam-Level: 
X-Spam-Status: No, score=-103.138 tagged_above=-999 required=5 tests=[AWL=-0.161, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
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 CR2hx-514CpO for <ietf@ietfa.amsl.com>; Mon, 14 Jan 2013 07:54:51 -0800 (PST)
Received: from mail-vc0-f180.google.com (mail-vc0-f180.google.com [209.85.220.180]) by ietfa.amsl.com (Postfix) with ESMTP id CF0D221F8566 for <ietf@ietf.org>; Mon, 14 Jan 2013 07:54:50 -0800 (PST)
Received: by mail-vc0-f180.google.com with SMTP id p16so3686061vcq.11 for <ietf@ietf.org>; Mon, 14 Jan 2013 07:54:50 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type; bh=ZDj9ja1mLUAinM/2QYYo+PFtSgDupSO6tuAj+ssC5HU=; b=Av5aRaO51oyBXa0SUIHGaiGngcDcwtNHVBjtCQKpm/KMFr0hvyoditRG1/dW0LH2Vl /o7FN464UdMmQFCZ7//Uah8xPog7SzF7Iw23/063TjM9m43joNYEFxtJPz18CPIPJ+yf Wi6/G4XaIxqBv8AP2l+0yDOGznYOKPKq4TCDbIS01AfEU5to/cpoE/DW/2SXkqvsLiKH K5q9zOOHTZV5xyjaOIfFCLlCe+F10IMsoKr4vx8PaI5v6L5PeTfaZWeGP76UNf0m90Vu 7ngwxzsoPlOAVMacTTF71Z4bQN7M1F8+7M8/wLPxnldlRB1BU20BTDDqS0inkS/og6mp tfoQ==
MIME-Version: 1.0
Received: by 10.220.238.146 with SMTP id ks18mr13456542vcb.58.1358178889980; Mon, 14 Jan 2013 07:54:49 -0800 (PST)
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.59.3.41 with HTTP; Mon, 14 Jan 2013 07:54:49 -0800 (PST)
In-Reply-To: <6.2.5.6.2.20130111094647.095f60e0@resistor.net>
References: <20130111151453.22161.50884.idtracker@ietfa.amsl.com> <6.2.5.6.2.20130111094647.095f60e0@resistor.net>
Date: Mon, 14 Jan 2013 10:54:49 -0500
X-Google-Sender-Auth: cnkVhD4pcHW6USroisgRE3bYUZI
Message-ID: <CAC4RtVA3i2DGWPwrYQj4qe2=Ri0zMa6=BPm1JYK-U1qb2-Uw4Q@mail.gmail.com>
Subject: Re: Last Call: <draft-farrell-ft-03.txt> (A Fast-Track way to RFC with Running Code) to Experimental RFC
From: Barry Leiba <barryleiba@computer.org>
To: IETF discussion list <ietf@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Jan 2013 15:54:51 -0000

I want to address one point that SM made:

>   "Additionally, the experiment will only require issues raised
>    during these three stages to be addressed if they meet the
>    IESG's Discuss criteria."
>
> Does this mean that a document does not have to represent consensus?

This bothered me too: by limiting what last call comments we address,
aren't we limiting the consensus process?  Last call (which includes
directorate and review team reviews) often results in many comments
that will make the document better, but that wouldn't be likely
candidates for DISCUSS positons in IESG Evaluation.  Isn't it a bad
idea to say, outright, "Oh, well, you don't have to pay attention to
those."?  GenART reviews, in particular, are designed to be very
detailed and to call out not just substantive issues, but editorial
ones.  Aren't we showing disrespect to reviewers who spend a lot of
time on a document if we then say, "Yeah, thanks, but we're going to
ignore those."?

But here's the thing: Judgment.

I noted in another conversation recently that we aren't just automata
who mechanically handle process.  And what we're talking about here
isn't a situation where the responsible AD will look at each comment
as if putting it on a scale, and will say, "Doesn't meet DISCUSS
criteria; toss it."

What we have is a case where working group chairs have brought the
document forward ans said, "The working group has consensus on this
document.  Maybe the last of the 't's are not crossed and there's
still an 'i' or two un-dotted, but there's broad consensus in the WG
and running code that shows it's solid, and we're ready for a
fast-track last call."  After that, the community and the IESG get to
comment.  ADs can only block progress on a document (essentially going
against WG consensus) with DISCUSS positions, and those positions need
to meet the DISCUSS criteria.  This is, the document is saying, the
case also with last call comments: in order to go against the WG's
consensus, there needs to be some strength to the argument.

In fact, this document isn't saying anything different to what can
already happen: if the document's authors, shepherd, and responsible
AD all say, "That batch of last call comments don't really matter,"
they can leave those comments un-addressed.  And if another AD
disagrees with that assessment, she can put a DISCUSS position on,
saying that important last call comments were not addressed, the
document does not appear to have rough consensus, etc.

Also, in fact, most document authors are pleased to get comments that
improve the document, and will *not* ignore comments just to save a
few days in the process.  ADs regularly put many non-blocking comments
on documents, ones that do not meet DISCUSS criteria, and document
authors are usually happy to consider them, to discuss them, and to
make changes to the document to address them when that's the right
thing to do.

I'll also note that the quote above from the document doesn't say or
imply that non-DISCUSS-worthy last call comments will never be
addressed -- only that they are not required to be addressed before
the document goes to the IESG.  If the goal is to run things in
parallel, it would be entirely reasonable for people to say, "This
batch of comments are things we can work on while the IESG is
evaluating the document."  Again, judgment.

I'm really not worried about that aspect of this proposal.  Whatever
faults I think this has, I do not think it will result in Proposed
Standard documents with any less consensus than we have now.

Barry

From nabil.n.bitar@verizon.com  Mon Jan 14 08:06:54 2013
Return-Path: <nabil.n.bitar@verizon.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B2F2721F87C8; Mon, 14 Jan 2013 08:06:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.349
X-Spam-Level: 
X-Spam-Status: No, score=-3.349 tagged_above=-999 required=5 tests=[AWL=0.250,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 MorTbH8CPV7Z; Mon, 14 Jan 2013 08:06:54 -0800 (PST)
Received: from fldsmtpe03.verizon.com (fldsmtpe03.verizon.com [140.108.26.142]) by ietfa.amsl.com (Postfix) with ESMTP id C085821F87BA; Mon, 14 Jan 2013 08:06:51 -0800 (PST)
X-IronPort-Anti-Spam-Filtered: false
Received: from unknown (HELO fldsmtpi01.verizon.com) ([166.68.71.143]) by fldsmtpe03.verizon.com with ESMTP; 14 Jan 2013 16:06:51 +0000
From: "Bitar, Nabil N" <nabil.n.bitar@verizon.com>
X-IronPort-AV: E=Sophos;i="4.84,468,1355097600"; d="scan'208";a="400863067"
Received: from fldp1lumxc7hb03.verizon.com (HELO FLDP1LUMXC7HB03.us.one.verizon.com) ([166.68.75.86]) by fldsmtpi01.verizon.com with ESMTP; 14 Jan 2013 16:06:51 +0000
Received: from fldp1lumxc7v63.us.one.verizon.com ([166.68.45.45]) by FLDP1LUMXC7HB03.us.one.verizon.com ([166.68.75.86]) with mapi; Mon, 14 Jan 2013 11:06:50 -0500
To: "huubatwork@gmail.com" <huubatwork@gmail.com>, Greg Mirsky <gregimirsky@gmail.com>
Date: Mon, 14 Jan 2013 11:06:36 -0500
Subject: Re: [PWE3] Gen-ART review of draft-ietf-pwe3-mpls-eth-oam-iwk-06
Thread-Topic: [PWE3] Gen-ART review of draft-ietf-pwe3-mpls-eth-oam-iwk-06
Thread-Index: Ac3ycSlEEGtuEo7BSHS7loLqQ9sTwQ==
Message-ID: <CD198238.75766%nabil.n.bitar@verizon.com>
In-Reply-To: <50EBF245.1020602@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.2.3.120616
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "Bitar, Nabil N" <nabil.n.bitar@verizon.com>, "ietf@ietf.org" <ietf@ietf.org>, "gen-art@ietf.org" <gen-art@ietf.org>, "dinmohan@hotmail.com" <dinmohan@hotmail.com>, "sajassi@cisco.com" <sajassi@cisco.com>, "pwe3@ietf.org" <pwe3@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Jan 2013 16:06:54 -0000

Hi,
In agreement with below definitions in 802.1ag and Y.1731  and their
mappings.Will align the terminology definition in the draft with that of
802.1ag. Y.1731 has the terminology mapping to 802.1ag's as well.

Thanks,
Nabil


On 1/8/13 5:17 AM, "Huub van Helvoort" <huubatwork@gmail.com> wrote:

>Dear Greg,
>
>You responded:
>
> > IEEE 802.1ag interprets MEP and MIP as:
> >
> >   * Maintenance association End Point
> >   * Maintenance domain Intermediate Point
>
>Indeed, and MA =3D=3D MEG, MD =3D=3D ME.
>
> > Y.1731 interprets them as:
> >
> >   * Maintenance entity group (MEG) End Point
> >   * MEG Intermediate Point
>
>Correct.
>
> > The reference to MD Level implies reference to IEEE 802.1ag, at least
>as
> > use of terminology, since Y.1731 doesn't have Maintenance Domain
> > construct and refers to the same value as MEG Level. I'd suggest to
> > follow one model, IEEE 802.1ag or Y.1731, terminology throughout the
> > document so that there's no need for re-mapping. I think that it is
> > easier to follow Y.1731.
>
>I agree that this is the best.
>These are the abbreviations used for MPLS-TP too.
>
>Best regards, Huub.
>
>
> > On Fri, Jan 4, 2013 at 8:30 AM, Huub van Helvoort <huubatwork@gmail.com
> > <mailto:huubatwork@gmail.com>> wrote:
> >
> >     All,
> >
> >     Some nits that need to be fixed:
> >
> >
> >
> >         ME  Maintenance Entity
> >
> >         MEG  Maintenance Entity Group
> >
> >         MEP Maintenance End Point
> >
> >
> >     MEP  "ME End Point" or "Maintenance Entity End Point"
> >
> >
> >         MIP  Maintenance End Point
> >
> >
> >     MIP  "ME Intermediate Point" or "Maintenance Entity Intermediate
>Point"
> >
> >
> >
> >              3.2. Terminology
> >
> >
> >         - MEP:  Maintenance End Point is responsible for origination
>and
> >         termination of OAM frames for a given MEG.
> >
> >
> >     - MEP:  Maintenance Entity End Point is responsible for origination
> >
> >
> >         - MIP: Maintenance Intermediate Point is located between peer
> >         MEPs and
> >         can process OAM frames but does not initiate or terminate them.
> >
> >
> >     - MIP: Maintenance Entity Intermediate Point is located between
> >
> >
> >     Regards, Huub.


From ogud@ogud.com  Mon Jan 14 08:39:31 2013
Return-Path: <ogud@ogud.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1B1B421F8775 for <ietf@ietfa.amsl.com>; Mon, 14 Jan 2013 08:39:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.599
X-Spam-Level: 
X-Spam-Status: No, score=-103.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
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 u4lJtZORRTeP for <ietf@ietfa.amsl.com>; Mon, 14 Jan 2013 08:39:30 -0800 (PST)
Received: from smtp167.iad.emailsrvr.com (smtp167.iad.emailsrvr.com [207.97.245.167]) by ietfa.amsl.com (Postfix) with ESMTP id 8479521F86D2 for <ietf@ietf.org>; Mon, 14 Jan 2013 08:39:24 -0800 (PST)
Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp56.relay.iad1a.emailsrvr.com (SMTP Server) with ESMTP id E1C3A3D8751; Mon, 14 Jan 2013 11:39:23 -0500 (EST)
X-Virus-Scanned: OK
Received: by smtp56.relay.iad1a.emailsrvr.com (Authenticated sender: ogud-AT-ogud.com) with ESMTPSA id 84C0C3D8740;  Mon, 14 Jan 2013 11:39:23 -0500 (EST)
Message-ID: <50F434BA.6000108@ogud.com>
Date: Mon, 14 Jan 2013 11:39:22 -0500
From: Olafur Gudmundsson <ogud@ogud.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130107 Thunderbird/17.0.2
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Last Call: <draft-farrell-ft-03.txt> (A Fast-Track way to RFC with Running Code) to Experimental RFC
References: <20130111151453.22161.50884.idtracker@ietfa.amsl.com>
In-Reply-To: <20130111151453.22161.50884.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: The IESG <iesg-secretary@ietf.org>, ogud@ogud.com, IETF-Announce <ietf-announce@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Jan 2013 16:39:31 -0000

On 11/01/2013 10:14, The IESG wrote:
>
> The IESG has received a request from an individual submitter to
> consider the following document: - 'A Fast-Track way to RFC with
> Running Code' <draft-farrell-ft-03.txt> as Experimental RFC
>
> The IESG plans to make a decision in the next few weeks, and solicits
> final comments on this action. Please send substantive comments to
> the ietf@ietf.org mailing lists by 2013-02-08. Exceptionally,
> comments may be sent to iesg@ietf.org instead. In either case, please
> retain the beginning of the Subject line to allow automated sorting.
>

I have experience in process like this, as my WG DNSEXT has required
multiple implementations and inter-op testing before advancing before
advancing documents that make significant changes to the DNS protocol.
Having done this I'm confident that the resulting specifications and
code was much better.

I support this experiment but offer the following comments.

Comment #1: The important part of running code is to assess
clarity of the specification, thus implementation by editors of the
document should not count as one-of-two required implementations
Implementations by editors co-workers are ok IFF the the editors keep
track of communications that lead to changes in code or draft.

Comment #2: It is important that participants all realize that point of
the exercise is not to point figurers at bugs. Rather the goal is to
improve the specifications and make ALL the implementations as compliant
and bug free as possible.

Comment #3 (Section 4 point #6)
Test cases used for interoperability are critical. These test
cases MUST be public. Evaluations of test cases generated by the
implementors and/or other working group participants are critical as
that is a great indicator of the quality and thoroughness of the tests.
IMHO public test cases render the point of open vs. closed source
irrelevant.

Comment #4: The IETF-LC and WGLC statements SHOULD contain references to
the testing performed and the implementations that participated.

	Olafur

From hsantos@isdg.net  Mon Jan 14 09:03:51 2013
Return-Path: <hsantos@isdg.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2555021F8844 for <ietf@ietfa.amsl.com>; Mon, 14 Jan 2013 09:03:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.09
X-Spam-Level: 
X-Spam-Status: No, score=-102.09 tagged_above=-999 required=5 tests=[AWL=-0.355, BAYES_00=-2.599, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311, USER_IN_WHITELIST=-100]
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 kOLI33whi6l8 for <ietf@ietfa.amsl.com>; Mon, 14 Jan 2013 09:03:50 -0800 (PST)
Received: from ntbbs.winserver.com (catinthebox.net [208.247.131.9]) by ietfa.amsl.com (Postfix) with ESMTP id E776321F88BE for <ietf@ietf.org>; Mon, 14 Jan 2013 09:03:49 -0800 (PST)
DKIM-Signature: v=1; d=isdg.net; s=tms1; a=rsa-sha1; c=simple/relaxed; l=4846; t=1358183017; h=Received:Received: Received:Received:Message-ID:Date:From:Organization:To:Subject: List-ID; bh=vP80w3Cqv/BVny3Yb+B2V811/wo=; b=nwsGH1arHddacbD1LbEE TGo/4v2PXc1Usxqyu9sbH9Z5cVup7NX6Nha8BE4rzv5AT1/WVSvU2e69D/iFzBd7 kCNSMcxYzOc4e4JSFl1QVBHzuXgbZL7H8KIwUsSvUToIIMHuGflZhOQEgDmSatWB 9h4UpdcBr8qIUyUS01KlkAY=
Received: by winserver.com (Wildcat! SMTP Router v7.0.454.4) for ietf@ietf.org; Mon, 14 Jan 2013 12:03:37 -0500
Authentication-Results: dkim.winserver.com; dkim=pass header.d=beta.winserver.com header.s=tms1 header.i=beta.winserver.com;  adsp=pass policy=all author.d=isdg.net asl.d=beta.winserver.com;
Received: from opensite.winserver.com ([208.247.131.23]) by winserver.com (Wildcat! SMTP v7.0.454.4) with ESMTP id 1319771171.5317.3044; Mon, 14 Jan 2013 12:03:37 -0500
DKIM-Signature: v=1; d=beta.winserver.com; s=tms1; a=rsa-sha256; c=simple/relaxed; l=4846; t=1358182952; h=Received:Received: Message-ID:Date:From:Organization:To:Subject:List-ID; bh=tjMOA6b EQz8gCxZXEC1V0BszbBwK1LEZHQ4tDY65Jac=; b=Kt6JCx9tw+lxOv9f8E4bYfj fx3HGe7fV8qPELpCpBu9asVwyodlOYBIGCxSRY6bm5aRG166a37EiuJUAKj68J/t R98FfZfqmSfBg/RXHlZstX0/sbiVxdJYPPf30ff5N0eTi7FfZKJ4VEWj8W8vpdLG Uon7fJpktVmrPiaFHAIU=
Received: by beta.winserver.com (Wildcat! SMTP Router v7.0.454.4) for ietf@ietf.org; Mon, 14 Jan 2013 12:02:32 -0500
Received: from [192.168.1.101] ([99.3.147.93]) by beta.winserver.com (Wildcat! SMTP v7.0.454.4) with ESMTP id 1918467742.10.7484; Mon, 14 Jan 2013 12:02:31 -0500
Message-ID: <50F43AC9.8060305@isdg.net>
Date: Mon, 14 Jan 2013 12:05:13 -0500
From: Hector Santos <hsantos@isdg.net>
Organization: Santronics Software, Inc.
User-Agent: Thunderbird 2.0.0.24 (Windows/20100228)
MIME-Version: 1.0
To: adrian@olddog.co.uk
Subject: Re: FW: Last Call: <draft-farrell-ft-03.txt> (A Fast-Track way to RFC	with Running Code) to Experimental RFC
References: <017001cdf017$c394df00$4abe9d00$@olddog.co.uk>
In-Reply-To: <017001cdf017$c394df00$4abe9d00$@olddog.co.uk>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Jan 2013 17:03:51 -0000

I have two concerns and comments:

- How will success or failure be measured?  Number of appeal increases 
or lesser amount?  I have a concern that once this door is open, there 
will be increase appeals and also apathy of outcomes.  There should be 
a statement of what sort of problems or issues are possible and 
envisioned and the plans to deal with them or not.

- The drafts indicates that fast tracking probably applies better 
towards BIS work. I cited concerns that this ideas should only be used 
for new work, not BIS work where there is already established 
implementators and working code.  I prefer to work in "No Surprises" 
environment where it doesn't require me to pay attention to all 
protocol change work to make sure nothing fell thru the crack or some 
group of vendors with their questionable "code" implementation 
different from the norm being mandated in new BIS work.

I only see this RFC being used to negate voiced concerns in the name 
of fast tracking, not win people over if they already have a problem 
with the work, especially if its BIS WORK.  But then again, maybe that 
is the intent.

I believe the experiment should only be applied first to new protocol 
work, not BIS work and if so, iff there are absolutely no question of 
possible conflict of interest, rush to judgment and no new code change 
impacts.  Existing protocol implementers should not be put into a 
position, and worst within a shorter time period, to argue or just 
review what BIS changes made entail and force them into appeal actions.

Perhaps the experiment can be done in two phases. I believe there is 
good in fast tracking new ideas and methods, especially if simple and 
one that most people seem to agree with with little concerns. Many 
vendors have much to contribute in this area.  So the first phase can 
explore only with fast tracking new concepts. If this works out well 
using some measuring tool, then BIS work can be better explored for 
fast tracking by gaining some insights from the first phase.

--
HLS

Adrian Farrel wrote:
> Hi Alexa,
> 
> Please be aware of this document that has just entered a four-week IETF last
> call. The document describes a proposed IETF process experiment under the rules
> of RFC 3933.
> 
> The proposed experiment calls on the IETF Secretariat to take specific actions
> under certain circumstances in corner cases of the experiment. Could you please
> have someone in the Secretariat look at the draft and comment on the
> practicalities of the actions. Note that, at this stage, no changes to the tools
> are proposed so any actions would require manual intervention (if the experiment
> were successful and resulted in permanent changes to IETF process we might make
> changes to the tools at some future time).
> 
> Thanks,
> Adrian
> 
>> -----Original Message-----
>> From: ietf-announce-bounces@ietf.org [mailto:ietf-announce-
>> bounces@ietf.org] On Behalf Of The IESG
>> Sent: 11 January 2013 15:15
>> To: IETF-Announce
>> Subject: Last Call: <draft-farrell-ft-03.txt> (A Fast-Track way to RFC with
> Running
>> Code) to Experimental RFC
>>
>>
>> The IESG has received a request from an individual submitter to consider
>> the following document:
>> - 'A Fast-Track way to RFC with Running Code'
>>   <draft-farrell-ft-03.txt> as Experimental RFC
>>
>> The IESG plans to make a decision in the next few weeks, and solicits
>> final comments on this action. Please send substantive comments to the
>> ietf@ietf.org mailing lists by 2013-02-08. Exceptionally, comments may be
>> sent to iesg@ietf.org instead. In either case, please retain the
>> beginning of the Subject line to allow automated sorting.
>>
>> Abstract
>>
>>    This memo describes an optional, fast-track way to progress a working
>>    group document to IESG review.  It is provided as a process
>>    experiment as defined in RFC 3933 for use when working group chairs
>>    believe that there is running code that implements a working group
>>    Internet-Draft.  The motivation is to have the IETF process
>>    explicitly consider running code, consistent with the IETF's overall
>>    philosophy of running code and rough consensus.
>>
>>    In this process all of working group last call, IETF last call, and
>>    Area Director review are carried out in the same two week period.
>>    Only comments that meet IESG Discuss criteria need to be addressed
>>    during this stage, and authors are required to make any changes
>>    within two weeks.
>>
>>    This experiment will run for one year.
>>
>>
>> The file can be obtained via
>> http://datatracker.ietf.org/doc/draft-farrell-ft/
>>
>> IESG discussion can be tracked via
>> http://datatracker.ietf.org/doc/draft-farrell-ft/ballot/
>>
>> No IPR declarations have been submitted directly on this I-D.
> 
> 
> 

-- 
HLS



From bclaise@cisco.com  Mon Jan 14 09:07:41 2013
Return-Path: <bclaise@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 871A521F848B; Mon, 14 Jan 2013 09:07:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.568
X-Spam-Level: 
X-Spam-Status: No, score=-10.568 tagged_above=-999 required=5 tests=[AWL=0.030, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8]
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 n7hYUqq-Yb5z; Mon, 14 Jan 2013 09:07:37 -0800 (PST)
Received: from av-tac-bru.cisco.com (weird-brew.cisco.com [144.254.15.118]) by ietfa.amsl.com (Postfix) with ESMTP id 7847C21F89B9; Mon, 14 Jan 2013 09:07:31 -0800 (PST)
X-TACSUNS: Virus Scanned
Received: from strange-brew.cisco.com (localhost.cisco.com [127.0.0.1]) by av-tac-bru.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id r0EGqaXa022363; Mon, 14 Jan 2013 17:52:36 +0100 (CET)
Received: from [10.60.67.89] (ams-bclaise-8918.cisco.com [10.60.67.89]) by strange-brew.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id r0EGqFJ6005038; Mon, 14 Jan 2013 17:52:26 +0100 (CET)
Message-ID: <50F437BF.8040005@cisco.com>
Date: Mon, 14 Jan 2013 17:52:15 +0100
From: Benoit Claise <bclaise@cisco.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: "draft-ietf-opsawg-oam-overview@tools.ietf.org" <draft-ietf-opsawg-oam-overview@tools.ietf.org>
Subject: Re: Last Call: <draft-ietf-opsawg-oam-overview-08.txt> (An Overview of Operations, Administration, and Maintenance (OAM) Mechanisms) to Informational RFC
References: <20130111193616.19158.16205.idtracker@ietfa.amsl.com>
In-Reply-To: <20130111193616.19158.16205.idtracker@ietfa.amsl.com>
Content-Type: multipart/alternative; boundary="------------090402040208020001020605"
Cc: opsawg@ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Jan 2013 17:07:41 -0000

This is a multi-part message in MIME format.
--------------090402040208020001020605
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

draft-ietf-opsawg-oam-overview authors,

Here is my feedback on this document.

1.
Is this document in line with 
http://tools.ietf.org/html/draft-ietf-trill-oam-req-04?
* For example, the following definitions could be reused.

    Fault: The term Fault refers to an inability to perform a required
    action, e.g., an unsuccessful attempt to deliver a packet.

    Defect: The term Defect refers to an interruption in the normal
    operation, such that over a period of time no packets are delivered
    successfully.

    Failure: The term Failure refers to the termination of the required
    function over a longer period of time. Persistence of a defect for a
    period of time is interpreted as a failure.

* For example, on the basic abstract
Abstract

    Operations, Administration, and Maintenance (OAM) is a general term
    that refers to a toolset that can be used for fault detection and
    isolation, and for performance measurement. OAM mechanisms have been
    defined for various layers in the protocol stack, and are used with a
    variety of protocols.

Abstract (draft-ietf-trill-oam-req-04)

    OAM (Operations, Administration and Maintenance) is a general term
    used to identify functions and toolsets to troubleshoot and monitor
    networks. This document presents, OAM Requirements applicable to
    TRILL.

So, as an example: does OAM include function?
I advice to review draft-ietf-trill-oam-req-04

2.
draft-ietf-trill-oam is not mentioned, while the abstract mentions:
    This document presents an overview of the OAM mechanisms that have
    been defined and are currently being defined by the IETF.
Search for OAM in the current draft names (https://datatracker.ietf.org/), and you will find many references.
Ok, I see later on:	
    This document focuses on IETF
    documents that have been published as RFCs, while other ongoing OAM-
    related work is outside the scope.
Ok, fine then: we don't need a reference to all the drafts.
However, draft-ietf-trill-oam is closed to be a RFC, and should be mentioned.


3.
Section 1
    The term OAM in this document refers to Operations, Administration
    and Maintenance [OAM-Def  <http://tools.ietf.org/html/draft-ietf-opsawg-oam-overview-08#ref-OAM-Def>], focusing on the forwarding plane of OAM.
What does it mean "focusing on the forwarding plane of OAM"?
Do you take a subset of the definition for this document?
Btw, I don't see a definition in the terminology section.
In section 2.2.3
    A Maintenance Point (MP) is a functional entity that is defined at a
    node in the network, and either initiates or reacts to OAM messages.
Which plane is MP?

4.
Section 1, Introduction
"Hence, management aspects are outside the scope of this document."
I don't understand which management aspects we speak about here.

5.
Clarifying question regarding 1.2
If speak about OWAMP or TWAMP 'synthetic traffic), is that data plane, 
control plane, or management plane?
Note that I found later on in the draft:

    OWAMP and TWAMP use two separate protocols: a Control plane protocol,
    and a Test plane protocol.

Interestingly enough, after reading the document, I reviewed 
http://datatracker.ietf.org/doc/draft-ietf-opsawg-oam-overview/ballot/, 
and saw the same feedback from Stewart Bryant:

    Provide a clear view of OAM functionality and its relationship
    to various "planes" of networking (data plane, control plane,
    management plane). In particular, the importance of
    fate-sharing of OAM and user traffic flows in packet networks
    should be explained.

6.

I see a multiplication of "plane" terms in the IETF document, and in this document in particular.
I could find: forwarding plane, management plane, control plane, data plane, user plane, and test plane.
Way too many.
Please be consistent

7.

    Table 1 summarizes the IETF OAM related RFCs discussed in this
    document.

    Table 2 summarizes the OAM standards mentioned in this document.

You need to change the Table 2 description. Do you want to say something along the lines of:
    Table 2 summarizes the OAM standards specified by other Standard Development Organization
    (SDO) than the IETF, along with IETF references where applicable.


8.
Section 2.2.1
    For a formal definition of each term, refer to the references at the end of
    this document.
Without a reference to a specific RFC, this is the type of statement which is not useful: you have 5 pages of references.
You position this document as "An Overview of  Operations, Administration, and Maintenance (OAM) Mechanisms", but you tell the reader: "if you want to know about the terms,
just read first all references!"

9.
You specify some terms and some OAM categories,
    2.2.2  <http://tools.ietf.org/html/draft-ietf-opsawg-oam-overview-08#section-2.2.2>. OAM Maintenance Entities ..........................13  <http://tools.ietf.org/html/draft-ietf-opsawg-oam-overview-08#page-13>
          2.2.3  <http://tools.ietf.org/html/draft-ietf-opsawg-oam-overview-08#section-2.2.3>. OAM Maintenance Points ............................14  <http://tools.ietf.org/html/draft-ietf-opsawg-oam-overview-08#page-14>
          2.2.4  <http://tools.ietf.org/html/draft-ietf-opsawg-oam-overview-08#section-2.2.4>. Proactive and On-demand activation ................15  <http://tools.ietf.org/html/draft-ietf-opsawg-oam-overview-08#page-15>
          2.2.5  <http://tools.ietf.org/html/draft-ietf-opsawg-oam-overview-08#section-2.2.5>. Connectivity Verification and Continuity Checks ...15  <http://tools.ietf.org/html/draft-ietf-opsawg-oam-overview-08#page-15>
          2.2.6  <http://tools.ietf.org/html/draft-ietf-opsawg-oam-overview-08#section-2.2.6>. Failures ..........................................15  <http://tools.ietf.org/html/draft-ietf-opsawg-oam-overview-08#page-15>
... but you don't use them in the section 3

Just_one_example with section 3.2.2
-
    o Demand mode: in this mode, BFD control packets are sent on-demand.
       Upon need, a system initiates a series of BFD control packets to
       verify the liveness of the session
Instead of liveness, you have defined Connectivity Verification and Continuity Checks  in section 2.2.5
- OLD:
    Each of the end-points of the monitored path maintains its own
    session identification
NEW:
    Each of the MEP maintains its own session identification
OR NEW (actually I don't know)
    Each of the MP maintains its own session identification
- OLD
	A BFD echo packet is sent to a peer system
Peer system = MEP, MP, or something else?
- etc...

10.
This document is composed of a list of OAM content and references, but I'm really missing the document "scope and target audience".
When we did RFC 6632, which is the companion document, we hadhttp://tools.ietf.org/html/rfc6632#section-1.1
  
    The target audience of the document is, on the one hand, IETF working
    groups, which aim to select appropriate standard management protocols
    and data models to address their needs concerning network management.
    On the other hand, the document can be used as an overview and
    guideline by non-IETF Standards Development Organizations (SDOs)
    planning to use IETF management technologies and data models for the
    realization of management applications.  The document can also be
    used to initiate a discussion between the bodies with the goal to
    gather new requirements and to detect possible gaps.  Finally, this
    document is directed to all interested parties that seek to get an
    overview of the current set of the IETF network management protocols
    such as network administrators or newcomers to the IETF.

You should have something similar.


11.
Section 3.6.1, put the paragraph 2 at the end of the section. The "alternative" in the following sentence would then make sense
    Alternative protocols for performance measurement are defined, for
    example, in MPLS-TP OAM ([MPLS-LM-DM  <http://tools.ietf.org/html/draft-ietf-opsawg-oam-overview-08#ref-MPLS-LM-DM>], [TP-LM-DM  <http://tools.ietf.org/html/draft-ietf-opsawg-oam-overview-08#ref-TP-LM-DM>]), and in Ethernet
    OAM [ITU-T-Y1731  <http://tools.ietf.org/html/draft-ietf-opsawg-oam-overview-08#ref-ITU-T-Y1731>].


My conclusions: this document still needs some work

Regards, Benoit
  

> The IESG has received a request from the Operations and Management Area
> Working Group WG (opsawg) to consider the following document:
> - 'An Overview of Operations, Administration, and Maintenance (OAM)
>     Mechanisms'
>    <draft-ietf-opsawg-oam-overview-08.txt> as Informational RFC
>
> The IESG plans to make a decision in the next few weeks, and solicits
> final comments on this action. Please send substantive comments to the
> ietf@ietf.org mailing lists by 2013-01-25. Exceptionally, comments may be
> sent to iesg@ietf.org instead. In either case, please retain the
> beginning of the Subject line to allow automated sorting.
>
> Abstract
>
>
>     Operations, Administration, and Maintenance (OAM) is a general term
>     that refers to a toolset that can be used for fault detection and
>     isolation, and for performance measurement. OAM mechanisms have been
>     defined for various layers in the protocol stack, and are used with a
>     variety of protocols.
>
>     This document presents an overview of the OAM mechanisms that have
>     been defined and are currently being defined by the IETF.
>
>
>
>
> The file can be obtained via
> http://datatracker.ietf.org/doc/draft-ietf-opsawg-oam-overview/
>
> IESG discussion can be tracked via
> http://datatracker.ietf.org/doc/draft-ietf-opsawg-oam-overview/ballot/
>
>
> No IPR declarations have been submitted directly on this I-D.
>
>
>


--------------090402040208020001020605
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <div class="moz-cite-prefix">draft-ietf-opsawg-oam-overview authors,<br>
      <br>
      Here is my feedback on this document.<br>
      <br>
      1.<br>
      Is this document in line with <a moz-do-not-send="true"
        class="moz-txt-link-freetext"
        href="http://tools.ietf.org/html/draft-ietf-trill-oam-req-04">http://tools.ietf.org/html/draft-ietf-trill-oam-req-04</a>?
      <br>
      * For example, the following definitions could be reused.<br>
      <pre class="newpage">   Fault: The term Fault refers to an inability to perform a required
   action, e.g., an unsuccessful attempt to deliver a packet.

   Defect: The term Defect refers to an interruption in the normal
   operation, such that over a period of time no packets are delivered
   successfully.

   Failure: The term Failure refers to the termination of the required
   function over a longer period of time. Persistence of a defect for a
   period of time is interpreted as a failure.

* For example, on the basic abstract 
Abstract

   Operations, Administration, and Maintenance (OAM) is a general term
   that refers to a toolset that can be used for fault detection and
   isolation, and for performance measurement. OAM mechanisms have been
   defined for various layers in the protocol stack, and are used with a
   variety of protocols.

Abstract (draft-ietf-trill-oam-req-04)

   OAM (Operations, Administration and Maintenance) is a general term
   used to identify functions and toolsets to troubleshoot and monitor
   networks. This document presents, OAM Requirements applicable to
   TRILL. 

So, as an example: does OAM include function? 
I advice to review draft-ietf-trill-oam-req-04

2. 
draft-ietf-trill-oam is not mentioned, while the abstract mentions:
   This document presents an overview of the OAM mechanisms that have
   been defined and are currently being defined by the IETF.
Search for OAM in the current draft names (<a moz-do-not-send="true" class="moz-txt-link-freetext" href="https://datatracker.ietf.org/">https://datatracker.ietf.org/</a>), and you will find many references.
Ok, I see later on:	
   This document focuses on IETF
   documents that have been published as RFCs, while other ongoing OAM-
   related work is outside the scope.
Ok, fine then: we don't need a reference to all the drafts. 
However, draft-ietf-trill-oam is closed to be a RFC, and should be mentioned.


3.
Section 1
   The term OAM in this document refers to Operations, Administration
   and Maintenance [<a moz-do-not-send="true" href="http://tools.ietf.org/html/draft-ietf-opsawg-oam-overview-08#ref-OAM-Def" title="&quot;Guidelines for the use of the OAM acronym in the IETF &quot;">OAM-Def</a>], focusing on the forwarding plane of OAM.
What does it mean "focusing on the forwarding plane of OAM"?
Do you take a subset of the definition for this document?
Btw, I don't see a definition in the terminology section.
In section 2.2.3
   A Maintenance Point (MP) is a functional entity that is defined at a
   node in the network, and either initiates or reacts to OAM messages.
Which plane is MP?

4.
Section 1, Introduction
"Hence, management aspects are outside the scope of this document."
I don't understand which management aspects we speak about here.
</pre>
      5.<br>
      Clarifying question regarding 1.2<br>
      If speak about OWAMP or TWAMP 'synthetic traffic), is that data
      plane, control plane, or management plane?<br>
      Note that I found later on in the draft:<br>
      <pre class="newpage">   OWAMP and TWAMP use two separate protocols: a Control plane protocol,
   and a Test plane protocol.</pre>
      Interestingly enough, after reading the document, I reviewed <a
        moz-do-not-send="true" class="moz-txt-link-freetext"
href="http://datatracker.ietf.org/doc/draft-ietf-opsawg-oam-overview/ballot/">http://datatracker.ietf.org/doc/draft-ietf-opsawg-oam-overview/ballot/</a>,
      and saw the same feedback from Stewart Bryant:<br>
      <blockquote>
        <pre>Provide a clear view of OAM functionality and its relationship
to various &#8220;planes&#8221; of networking (data plane, control plane,
management plane). In particular, the importance of
fate-sharing of OAM and user traffic flows in packet networks
should be explained.</pre>
      </blockquote>
      6.<br>
      <pre class="newpage">I see a multiplication of "plane" terms in the IETF document, and in this document in particular.
I could find: forwarding plane, management plane, control plane, data plane, user plane, and test plane.
Way too many.
Please be consistent
</pre>
      7.<br>
      <pre class="newpage">   Table 1 summarizes the IETF OAM related RFCs discussed in this
   document.

   Table 2 summarizes the OAM standards mentioned in this document. 

You need to change the Table 2 description. Do you want to say something along the lines of:
   Table 2 summarizes the OAM standards specified by other Standard Development Organization 
   (SDO) than the IETF, along with IETF references where applicable.


8.
Section 2.2.1
   For a formal definition of each term, refer to the references at the end of
   this document.
Without a reference to a specific RFC, this is the type of statement which is not useful: you have 5 pages of references.
You position this document as "An Overview of<span class="h1"></span> Operations, Administration, and Maintenance (OAM) Mechanisms<span class="h1"></span>", but you tell the reader: "if you want to know about the terms,
just read first all references!"

9.
You specify some terms and some OAM categories, 
   <a moz-do-not-send="true" href="http://tools.ietf.org/html/draft-ietf-opsawg-oam-overview-08#section-2.2.2">2.2.2</a>. OAM Maintenance Entities .......................... <a moz-do-not-send="true" href="http://tools.ietf.org/html/draft-ietf-opsawg-oam-overview-08#page-13">13</a>
         <a moz-do-not-send="true" href="http://tools.ietf.org/html/draft-ietf-opsawg-oam-overview-08#section-2.2.3">2.2.3</a>. OAM Maintenance Points ............................ <a moz-do-not-send="true" href="http://tools.ietf.org/html/draft-ietf-opsawg-oam-overview-08#page-14">14</a>
         <a moz-do-not-send="true" href="http://tools.ietf.org/html/draft-ietf-opsawg-oam-overview-08#section-2.2.4">2.2.4</a>. Proactive and On-demand activation ................ <a moz-do-not-send="true" href="http://tools.ietf.org/html/draft-ietf-opsawg-oam-overview-08#page-15">15</a>
         <a moz-do-not-send="true" href="http://tools.ietf.org/html/draft-ietf-opsawg-oam-overview-08#section-2.2.5">2.2.5</a>. Connectivity Verification and Continuity Checks ... <a moz-do-not-send="true" href="http://tools.ietf.org/html/draft-ietf-opsawg-oam-overview-08#page-15">15</a>
         <a moz-do-not-send="true" href="http://tools.ietf.org/html/draft-ietf-opsawg-oam-overview-08#section-2.2.6">2.2.6</a>. Failures .......................................... <a moz-do-not-send="true" href="http://tools.ietf.org/html/draft-ietf-opsawg-oam-overview-08#page-15">15</a>
... but you don't use them in the section 3

Just <u>one </u>example with section 3.2.2
-
   o Demand mode: in this mode, BFD control packets are sent on-demand.
      Upon need, a system initiates a series of BFD control packets to
      verify the liveness of the session
Instead of liveness, you have defined Connectivity Verification and Continuity Checks<span class="h4"></span> in section 2.2.5
- OLD:
   Each of the end-points of the monitored path maintains its own
   session identification
NEW:
   Each of the MEP maintains its own session identification
OR NEW (actually I don't know)
   Each of the MP maintains its own session identification
- OLD
	A BFD echo packet is sent to a peer system
Peer system = MEP, MP, or something else?
- etc... 

10. 
This document is composed of a list of OAM content and references, but I'm really missing the document "scope and target audience".
When we did RFC 6632, which is the companion document, we had <a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://tools.ietf.org/html/rfc6632#section-1.1">http://tools.ietf.org/html/rfc6632#section-1.1</a>
&nbsp;
   The target audience of the document is, on the one hand, IETF working
   groups, which aim to select appropriate standard management protocols
   and data models to address their needs concerning network management.
   On the other hand, the document can be used as an overview and
   guideline by non-IETF Standards Development Organizations (SDOs)
   planning to use IETF management technologies and data models for the
   realization of management applications.  The document can also be
   used to initiate a discussion between the bodies with the goal to
   gather new requirements and to detect possible gaps.  Finally, this
   document is directed to all interested parties that seek to get an
   overview of the current set of the IETF network management protocols
   such as network administrators or newcomers to the IETF.

You should have something similar.


11.
Section 3.6.1, put the paragraph 2 at the end of the section. The "alternative" in the following sentence would then make sense
   Alternative protocols for performance measurement are defined, for
   example, in MPLS-TP OAM ([<a moz-do-not-send="true" href="http://tools.ietf.org/html/draft-ietf-opsawg-oam-overview-08#ref-MPLS-LM-DM" title="&quot;Packet Loss and Delay Measurement for MPLS Networks&quot;">MPLS-LM-DM</a>], [<a moz-do-not-send="true" href="http://tools.ietf.org/html/draft-ietf-opsawg-oam-overview-08#ref-TP-LM-DM" title="&quot;A Packet Loss and Delay Measurement Profile for MPLS-Based Transport Networks&quot;">TP-LM-DM</a>]), and in Ethernet
   OAM [<a moz-do-not-send="true" href="http://tools.ietf.org/html/draft-ietf-opsawg-oam-overview-08#ref-ITU-T-Y1731" title="&quot;OAM Functions and Mechanisms for Ethernet-based Networks&quot;">ITU-T-Y1731</a>].


My conclusions: this document still needs some work

Regards, Benoit
&nbsp;
</pre>
    </div>
    <blockquote
      cite="mid:20130111193616.19158.16205.idtracker@ietfa.amsl.com"
      type="cite">
      <pre wrap="">
The IESG has received a request from the Operations and Management Area
Working Group WG (opsawg) to consider the following document:
- 'An Overview of Operations, Administration, and Maintenance (OAM)
   Mechanisms'
  &lt;draft-ietf-opsawg-oam-overview-08.txt&gt; as Informational RFC

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action. Please send substantive comments to the
<a class="moz-txt-link-abbreviated" href="mailto:ietf@ietf.org">ietf@ietf.org</a> mailing lists by 2013-01-25. Exceptionally, comments may be
sent to <a class="moz-txt-link-abbreviated" href="mailto:iesg@ietf.org">iesg@ietf.org</a> instead. In either case, please retain the
beginning of the Subject line to allow automated sorting.

Abstract


   Operations, Administration, and Maintenance (OAM) is a general term
   that refers to a toolset that can be used for fault detection and
   isolation, and for performance measurement. OAM mechanisms have been
   defined for various layers in the protocol stack, and are used with a
   variety of protocols.

   This document presents an overview of the OAM mechanisms that have
   been defined and are currently being defined by the IETF.




The file can be obtained via
<a class="moz-txt-link-freetext" href="http://datatracker.ietf.org/doc/draft-ietf-opsawg-oam-overview/">http://datatracker.ietf.org/doc/draft-ietf-opsawg-oam-overview/</a>

IESG discussion can be tracked via
<a class="moz-txt-link-freetext" href="http://datatracker.ietf.org/doc/draft-ietf-opsawg-oam-overview/ballot/">http://datatracker.ietf.org/doc/draft-ietf-opsawg-oam-overview/ballot/</a>


No IPR declarations have been submitted directly on this I-D.



</pre>
    </blockquote>
    <br>
  </body>
</html>

--------------090402040208020001020605--

From stephen.farrell@cs.tcd.ie  Mon Jan 14 09:40:07 2013
Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 723E721F87D2 for <ietf@ietfa.amsl.com>; Mon, 14 Jan 2013 09:40:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.777
X-Spam-Level: 
X-Spam-Status: No, score=-102.777 tagged_above=-999 required=5 tests=[AWL=-0.178, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 7Eqg8v7yEJfV for <ietf@ietfa.amsl.com>; Mon, 14 Jan 2013 09:40:06 -0800 (PST)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) by ietfa.amsl.com (Postfix) with ESMTP id ABB3E21F87CB for <ietf@ietf.org>; Mon, 14 Jan 2013 09:40:05 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id A42A3BE47; Mon, 14 Jan 2013 17:39:42 +0000 (GMT)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pLzAkZ6NYstn; Mon, 14 Jan 2013 17:39:37 +0000 (GMT)
Received: from [IPv6:2001:770:10:203:fc59:2c8:a489:8ef3] (unknown [IPv6:2001:770:10:203:fc59:2c8:a489:8ef3]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 2DE37BE35; Mon, 14 Jan 2013 17:39:37 +0000 (GMT)
Message-ID: <50F442D9.7080702@cs.tcd.ie>
Date: Mon, 14 Jan 2013 17:39:37 +0000
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130106 Thunderbird/17.0.2
MIME-Version: 1.0
To: John Leslie <john@jlc.net>
Subject: Re: Last Call: <draft-farrell-ft-03.txt> (A Fast-Track way to RFC with Running Code) to Experimental RFC
References: <20130111151453.22161.50884.idtracker@ietfa.amsl.com> <20130114130541.GK62444@verdi>
In-Reply-To: <20130114130541.GK62444@verdi>
X-Enigmail-Version: 1.5
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Jan 2013 17:40:07 -0000

Hi again John,

Substantive response this time...

On 01/14/2013 01:05 PM, John Leslie wrote:
> The IESG <iesg-secretary@ietf.org> wrote:
>>
>> The IESG has received a request from an individual submitter to consider
>> the following document:
>> - 'A Fast-Track way to RFC with Running Code'
>>   <draft-farrell-ft-03.txt> as Experimental RFC
>>
>> The IESG plans to make a decision in the next few weeks, and solicits
>> final comments on this action.
> 
>    I'm pretty darn uncomfortable _ever_ picking a fight with any
> sitting AD, But I feel obligated to say this seems like a terrible
> idea to me.
> 
>    As a background, I'm a long-time believer in "rough consensus" for
> Proposed Standard and "running code" for advancement along the
> standards track. I do not believe the two mix well.

I don't get why they don't mix well to be honest. And I don't
get it from your mail (so far). But I think you're maybe
interpreting the draft differently from how its intended so
let's see if we can figure it out.

I'd also point out that this experiment is optional. And
the intent is that if the experiment were a success that
the fast track process would always be optional - to be
used or not as WG chairs choose, with the co-operation of
authors/editors and ADs, pretty much any of whom could
basically force the draft to be processed in the normal
manner.

Some of your concerns read as if the goal were that all PS
RFCs would be processed this way. That's not the goal and
that's stated in the draft.

>    A standard needs to be as simple as possible (but no simpler);
> running code needs to be complex.
> 
>    Stephen Farrell wants to "speed up" our process by adding an
> incentive for "having" running code. Specifically:
> ] 
> ] This memo describes a way to fast-track some final stage reviews for
> ] a working group draft when the working group management and area
> ] directors believe that the existence of one or more implementations
> ] serve as a practical review of the engineering choices made by the
> ] working group.
> 
>    Actually, now that I read that carefully, it doesn't even need to be
> "running" code. :^(

Well I reckon its pretty clear when you read the whole thing,
but text tweaks are welcome.

> ] This experiment needs an implementation that matches the specification
> ] contained in the draft.
> 
>    (Verifying that has proven to be surprisingly hard. One guesses
> that the "match" may not be rigidly enforced...)
> 
>    Understand, IMHO there is much to be gained by testing the
> interoperability of independent implementations of a specification;
> but that is a long-winded process, hardly anything which could be
> done during the "fast-track" Stephen is proposing.

It may be a long process. I think that'll depend on the
subject matter. Could well be that this isn't suitable for
things where sensibly checking the implementation matches
the draft is too complex. And maybe that's a good thing
(if it encourages us to write simpler specifications for
example).

> ] It is up to the WG chairs and responsible AD to satisfy themselves
> ] on this point within the normal bounds of trust
> 
>    "Normal bounds of trust" isn't particularly compatible with our
> paradigm of transparency of process...
> 
>    I don't even think it means the same thing to the rather limited
> set of people named here.

Yeah you may be right. Can't recall who suggested that phrase
(maybe it was me, but it doesn't sound like me:-) but it could
be improved on I guess.

We do also trust WG chairs and ADs for lots of stuff already, so
would it be better if it said, e.g.:

   This experiment needs an implementation that matches the
   specification contained in the draft.  It is up to the WG chairs and
   responsible AD to satisfy themselves on this point.

   There is no implication here as to the licensing of the
   implementation whether open- or closed-source.  ...

> ] and without any implication about the licensing related to an
> ] open- or closed-source implementation.
> 
>    Any mention of licensing seems out of place here.

But it only says that licensing can be anything. I do think
that's worth saying but maybe could be better split out as
above.

> 
> ] Note that the existence of an implementation is not sufficient to
> ] ensure that the draft will automatically pass working group or IETF
> ] last call, nor that it will receive IESG approval.
> 
>    Nor should it be, of course...
> 
>    Getting to the devil-in-the-details:
> ] 
> ] 1. Any Working Group Last Call (WGLC) or Area Director (AD) review
> ]    ... will run in parallel with the two-week IETF Last Call
> 
> ] 2. The IETF last call announcement message must say that the draft
> ]    in question is following the fast-track process...
> 
> ] 3. The draft itself should note (e.g. in the introduction) that it
> ]    has been fast-track processed and reference this RFC.
> 
> ] 4. Only comments that would be "DISCUSS-worthy" according to the
> ]    IESG Discuss Criteria [DCRIT] need be handled during last call.
> ]    Other comments can be handled or not, at the authors/editors
> ]    discretion.
> 
>    This is actually normal for IETF-wide LastCall (though it leads
> to raised tempers when seemingly valid comments are ignored).
> 
>    It is not normal for WG LastCall; nor is it even compatible with
> "rough consensus" -- by which we mean that any new questions raised
> have been considered to the satisfaction of a substantial majority
> of the participants.

Well WGLC isn't part of 2026, and others have argued that that means
that there's no need for this to even be a process-experiment. That
seems to be at odds with your position.

My take on this is that yes, this is a proposal for an experiment
that changes what we do now with WGLC, and its one I think we ought
try. I think we just disagree on whether that's a good thing to
try or not.

> 
> ] 5. The responsible AD for the WG concerned makes the decision as to
> ]    whether changes are required as a result of review comments, and
> ]    determines whether or not those have been completed.  If
> ]    significant change or extended discussion is required, or if
> ]    changes are not complete within two weeks after the end of fast-
> ]    track last call, then the draft is returned to the WG by the
> ]    responsible AD and the document is withdrawn from the experiment.
> 
>    This is not an easy read. :^(
> 
>    First, it centralizes the decision in one person (whereas normal
> WGLC process has two or more WG Chairs judging consensus of the group).

I disagree. All the WG chairs must already want to use the fast-track
experiment so they presumably are already ok with the draft at the
start of IETF LC. So the only thing the responsible AD is judging is
whether the IETF LC comments are such that going ahead to IESG review
is ok, which what happens now.

>    Second, it centralizes the decision in one person whether changes
> in the document properly address any WG or IETF-wide comments. This
> kind-of matches current practice in the IESG for Area Director
> comments; but does not match the theory -- and we could on very short
> notice regress from the level of trust which allows this to happen
> now.

I don't get what you mean there about the theory.

>    Third, the two-week drop-dead time limit is unworkable. Not just
> IMHO; in practice it hardly ever happens that everything resolves
> itself that quickly. 

You might be right. But I think if some WG chairs and authors/editors
ask for fast-track then they also need to be willing to work quickly
to handle IETF LC comments, and they ought only do this where they
expect it to work and are willing to try make it happen. So I'd
argue to keep this timer. (The duration of the timer I agree might
be wrong.)

> AD DISCUSS comments tend to bunch up in the
> hours before the telechat, and frequently need to be clarified
> _after_ the telechat.

I don't know what you mean about AD DISCUSSes - IESG review isn't
changed in that respect and the draft does not require authors to
handle those any differently from today.

>    Fourth, it's not really clear what happens after "the document is
> withdrawn from the experiment." It would appear at first blush that
> it must now start a separate WGLC, followed by a new IETF LastCall.
> I would never consent to this process for a document _I_ cared about.

You are correct, the intent is that the draft goes back to the WG
and is then processed as normal.

> ] 6. As soon as the responsible AD has confirmed that the authors/
> ]    editors have made any changes required as a result of fast-track
> ]    last-call, then the document should enter IESG review and be
> ]    placed on the next IESG telechat agenda that is more than one
> ]    week in the future.
> 
>    Oh... Stephen wasn't talking about the IESG process at all!
> 
>    I'm even more confused now.

I'm confused that you're confused!

>    I guess this means that one person (the responsible AD) takes a
> look at any and all comments during the "combined" LastCall and
> responsible-AD-review and makes a unilateral decision of what
> changes the authors/editors should make (on short notice); then
> things open for IESG-member DISCUSS comments.

Right. That's the idea. But note the WG chairs kick off the
process.

>    This would seem to preclude the current practice of putting
> drafts on the IESG agenda _before_ the end of IETF LastCall. I'm
> only getting more confused as to how this speeds up our process.

It may be that the set of drafts for which this is useful and the
set that are reasonable to put on a telechat agenda before the end
of IETF LC are disjoint. But its an interesting, though I'd say
minor, point that might come up during the experiment if we try it.

> ] 7. Given the reduced time associated with fast-track processing, the
> ]    responsible AD may not have time to carry out sufficient review
> ]    prior to IESG evaluation to be confident in balloting "Yes" for
> ]    the document.  Draft progression during and after IESG review is
> ]    otherwise unaffected, so a "Yes" ballot is needed from some AD.
> 
>    I _do_ understand that part, thought it's a bit obscure to those
> who haven't been IESG members: no document gets approved by the
> IESG without at least one "Yes" ballot-position; and Stephen wants
> to be able to decline to ballot "Yes" on a document he (as
> responsible-AD) has almost unilaterally re-written. (This would
> be a really-bad idea, IMHO.)

No, that's not the intent, nor I think would it be what'd happen;
"almost unilaterally re-written" would not be appropriate I entirely
agree, but I don't see any AD doing that after IETF LC now, and I
can't see it happening with this experiment.

Today, the convention is that the responsible AD ballots yes to
kick off the process of IESG review. This is just saying that
that AD might start IESG review with a different position (I
would guess a no-objection, though there are exceptions to
everything;-) because that AD hasn't had time to fully evaluate
the draft. That AD might e.g. have asked someone else to check
the implementation (allowed by this draft) but might want to
do a fuller review during IESG evaluation before presumably
balloting yes. Requiring the yes ballot up front is just a bit
too demanding with the fast track timers.

> ] 8. If at any point in the fast-track process the responsbile AD does
> ]    not act in a timely fashion then the IESG Secretary should ensure
> ]    that the draft enters IESG evaluation and is scheduled for the
> ]    the soonest IESG telechat that is more than one week after the
> ]    end of the two-week post-IETF LC period.  That is, if the
> ]    responsible AD does not act, then the default action applies
> ]    which is that the draft enters IESG evaluation and is placed on
> ]    the earliest IESG telechat.
> 
>    (This is too complicated for me to try to explain in this email.)

Maybe you'll come back to it?

> ====
> 
>    There's a lot more I could review, but I won't in this post.
> 
>    Were I an AD responsible to ballot on this, I'd ballot "abstain".
> "Abstain" means "There's no point trying to satisfy me," and is
> the way an IESG member essentially votes "No."
> 
>    I don't believe "running code" is even particularly helpful in
> run-of-the-mill Proposed Standards. 

Right. I guess that's where we disagree.

> I've seen it _seriously_ harm
> the documents in cases where the "running code" has shipped and
> there is reticence to change it: no matter how many weaknesses are
> pointed out, you can't get WG consensus to change the spec.

I agree that happens. I don't think this'll change how often.
But if it made that happen more often then yes, we should probably
declare the experiment over and not make this part of the
formal process. I could argue that this might reduce that
problem, on the basis that the draft and code are more likely
to be the same, but I've no empirical basis on which to base
that argument. (Same as you wouldn't if you argued that this
experiment will make it happen more often.)

>    In cases where "running code" has proven helpful, it's my
> honest opinion that the spec has become way too complicated (and
> thus the "running code" has proven which parts are unworkable).

Hmm. I've had somewhat the opposite experience, so I guess
YMMV. I've not gone to dig up examples though but in DKIM I
think we ended up with a simpler spec. due to some folks
doing good work with running code before and during the WG's
processing of the drafts.

>    I don't believe it's possible to "fast-track" "runnng code";
> nor do I believe it would be desirable were it possible. Code
> needs to deal with complex cases that, for the most part, don't
> need to be standardized in the first place. But code which
> doesn't deal with these is useless in the marketplace.

That may be right, but we're not talking about fast-tracking the
code.

>    IMHO, we designed a separate "Proposed Standard" step to get
> a specification published quickly without delving into the many
> questions that arise when writing actual code. 

That's fair. I think this experiment partly reflects one way
in which the standards process theory and IETF practice have
diverged over the years. The bar for PS is mostly now much
higher than was the original intent. I think that in some
cases, this experiment might lower that bar a little.

> There are plenty
> of Standards-Development Organizations that start from "code".
> We don't need to become one of them.

We also have issues with RFCs for which there is no code and
never will be;-)

But more to the point, I think that in a lot of cases where
the IETF has done a good job, there has been running code
before the WG even started, so I disagree that starting from
code is bad. Rubber stamping stuff whether based on code
or not would be bad, but isn't part of this experiment.

Cheers,
S.

> 
> --
> John Leslie <john@jlc.net>
> 
> 

From stephen.farrell@cs.tcd.ie  Mon Jan 14 10:02:52 2013
Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CBE8E21F847F; Mon, 14 Jan 2013 10:02:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.757
X-Spam-Level: 
X-Spam-Status: No, score=-102.757 tagged_above=-999 required=5 tests=[AWL=-0.158, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 OjbHUruaEhZB; Mon, 14 Jan 2013 10:02:51 -0800 (PST)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) by ietfa.amsl.com (Postfix) with ESMTP id 82A2B21F8479; Mon, 14 Jan 2013 10:02:44 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id 49C83BE56; Mon, 14 Jan 2013 18:02:19 +0000 (GMT)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8X89YWud16-G; Mon, 14 Jan 2013 18:02:08 +0000 (GMT)
Received: from [IPv6:2001:770:10:203:fc59:2c8:a489:8ef3] (unknown [IPv6:2001:770:10:203:fc59:2c8:a489:8ef3]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id AEE55BE3F; Mon, 14 Jan 2013 18:02:08 +0000 (GMT)
Message-ID: <50F44821.3030802@cs.tcd.ie>
Date: Mon, 14 Jan 2013 18:02:09 +0000
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130106 Thunderbird/17.0.2
MIME-Version: 1.0
To: Olafur Gudmundsson <ogud@ogud.com>
Subject: Re: Last Call: <draft-farrell-ft-03.txt> (A Fast-Track way to RFC with Running Code) to Experimental RFC
References: <20130111151453.22161.50884.idtracker@ietfa.amsl.com> <50F434BA.6000108@ogud.com>
In-Reply-To: <50F434BA.6000108@ogud.com>
X-Enigmail-Version: 1.5
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: The IESG <iesg-secretary@ietf.org>, ietf@ietf.org, IETF-Announce <ietf-announce@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Jan 2013 18:02:53 -0000

Hi Olafur,

On 01/14/2013 04:39 PM, Olafur Gudmundsson wrote:
> On 11/01/2013 10:14, The IESG wrote:
>>
>> The IESG has received a request from an individual submitter to
>> consider the following document: - 'A Fast-Track way to RFC with
>> Running Code' <draft-farrell-ft-03.txt> as Experimental RFC
>>
>> The IESG plans to make a decision in the next few weeks, and solicits
>> final comments on this action. Please send substantive comments to
>> the ietf@ietf.org mailing lists by 2013-02-08. Exceptionally,
>> comments may be sent to iesg@ietf.org instead. In either case, please
>> retain the beginning of the Subject line to allow automated sorting.
>>
> 
> I have experience in process like this, as my WG DNSEXT has required
> multiple implementations and inter-op testing before advancing before
> advancing documents that make significant changes to the DNS protocol.
> Having done this I'm confident that the resulting specifications and
> code was much better.
> 
> I support this experiment but offer the following comments.

Phew, so I'm not entirely crazy, good to know:-)

> Comment #1: The important part of running code is to assess
> clarity of the specification, thus implementation by editors of the
> document should not count as one-of-two required implementations
> Implementations by editors co-workers are ok IFF the the editors keep
> track of communications that lead to changes in code or draft.

First this draft only requires one implementation and not two as
your WG did. Second, I don't know what you mean by "keep track
of communications" - can you explain? (Or send a pointer to
one you used in the WG?)

That's also sort of like the point Stefan W. raised. And he
suggested:

         "If the source code has been developed
         independently of the authoring of the draft (and ideally by non
         WG participants), it is likely that the implementation and the
         draft match, and that pitfalls unaware developers may find have
         been found and dealt with.  If, on the other hand, draft
         author(s) and implementation developer(s) overlap, then it is
         sensible to scrutinize the draft more closely, both with
         respect to its match with the implementation and for
         assumptions that author/developer may have taken for granted
         which warrant documentation in the draft."

Are you saying something like that would help?

Personally, I think there are thousands of nuggets of advice
that we could possibly add, but I'm not convinced that we
should - I think we'd be better off trying to keep this draft
shorter and simpler and then if the experiment succeeds we can
incorporate those things that experience has shown are worth
including.

> Comment #2: It is important that participants all realize that point of
> the exercise is not to point figurers at bugs. Rather the goal is to
> improve the specifications and make ALL the implementations as compliant
> and bug free as possible.

Agreed. Not sure what text would change though.

Same comment about "nuggets" as above:-)

> Comment #3 (Section 4 point #6)
> Test cases used for interoperability are critical. These test
> cases MUST be public. Evaluations of test cases generated by the
> implementors and/or other working group participants are critical as
> that is a great indicator of the quality and thoroughness of the tests.
> IMHO public test cases render the point of open vs. closed source
> irrelevant.

I think that's arguable, but a reasonable argument. Again though,
I don't think we're at the point where a MUST ought go into this
draft and that'd be better done when the experiment's done.

Or do you have a suggestion for text? (I'm not at all sure how
I'd write that up now.)

> Comment #4: The IETF-LC and WGLC statements SHOULD contain references to
> the testing performed and the implementations that participated.

I could buy that as a SHOULD or "ought." I've noted that
in the working version as a change to maybe make. [1]

Cheers,
S.

> 
>     Olafur
> 
> 

From stephen.farrell@cs.tcd.ie  Mon Jan 14 10:13:15 2013
Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 25B5221F8893 for <ietf@ietfa.amsl.com>; Mon, 14 Jan 2013 10:13:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.749
X-Spam-Level: 
X-Spam-Status: No, score=-102.749 tagged_above=-999 required=5 tests=[AWL=-0.150, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 f3e0EX96kiPc for <ietf@ietfa.amsl.com>; Mon, 14 Jan 2013 10:13:14 -0800 (PST)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) by ietfa.amsl.com (Postfix) with ESMTP id E76D821F888C for <ietf@ietf.org>; Mon, 14 Jan 2013 10:13:13 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id 48EE1BE3F; Mon, 14 Jan 2013 18:12:52 +0000 (GMT)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VLAl0KzpN8Vs; Mon, 14 Jan 2013 18:12:46 +0000 (GMT)
Received: from [IPv6:2001:770:10:203:fc59:2c8:a489:8ef3] (unknown [IPv6:2001:770:10:203:fc59:2c8:a489:8ef3]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 8A61EBE35; Mon, 14 Jan 2013 18:12:46 +0000 (GMT)
Message-ID: <50F44A9F.2030007@cs.tcd.ie>
Date: Mon, 14 Jan 2013 18:12:47 +0000
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130106 Thunderbird/17.0.2
MIME-Version: 1.0
To: Hector Santos <hsantos@isdg.net>
Subject: Re: FW: Last Call: <draft-farrell-ft-03.txt> (A Fast-Track way to RFC	with Running Code) to Experimental RFC
References: <017001cdf017$c394df00$4abe9d00$@olddog.co.uk> <50F43AC9.8060305@isdg.net>
In-Reply-To: <50F43AC9.8060305@isdg.net>
X-Enigmail-Version: 1.5
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: adrian@olddog.co.uk, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Jan 2013 18:13:15 -0000

Hi Hector,

On 01/14/2013 05:05 PM, Hector Santos wrote:
> I have two concerns and comments:
> 
> - How will success or failure be measured?  Number of appeal increases
> or lesser amount?  I have a concern that once this door is open, there
> will be increase appeals and also apathy of outcomes.  There should be a
> statement of what sort of problems or issues are possible and envisioned
> and the plans to deal with them or not.

RFC 3933 describes that I guess. Basically, if the IESG consider
it a success then they could make the RFC into a BCP or more likely
find a victim to write an I-D for that. That'd go through the
usual process.

I don't think this'll have any impact on appeals (hope not anyway),
and for me the main metric of success will be whether or not it
gets used, and if used, if the people involved in those drafts
think its worth making permanent or not.

> 
> - The drafts indicates that fast tracking probably applies better
> towards BIS work. 

Not really. Its says that -bis RFCs might be suitable.

> I cited concerns that this ideas should only be used
> for new work, not BIS work where there is already established
> implementators and working code.  I prefer to work in "No Surprises"
> environment where it doesn't require me to pay attention to all protocol
> change work to make sure nothing fell thru the crack or some group of
> vendors with their questionable "code" implementation different from the
> norm being mandated in new BIS work.

I don't get the concern.

> I only see this RFC being used to negate voiced concerns in the name of
> fast tracking, not win people over if they already have a problem with
> the work, especially if its BIS WORK.  But then again, maybe that is the
> intent.
> 
> I believe the experiment should only be applied first to new protocol
> work, not BIS work and if so, iff there are absolutely no question of
> possible conflict of interest, rush to judgment and no new code change
> impacts.  Existing protocol implementers should not be put into a
> position, and worst within a shorter time period, to argue or just
> review what BIS changes made entail and force them into appeal actions.
> 
> Perhaps the experiment can be done in two phases. I believe there is
> good in fast tracking new ideas and methods, especially if simple and
> one that most people seem to agree with with little concerns. Many
> vendors have much to contribute in this area.  So the first phase can
> explore only with fast tracking new concepts. If this works out well
> using some measuring tool, then BIS work can be better explored for fast
> tracking by gaining some insights from the first phase.

Ah, you're worried some WG will shoot out a -bis draft this way
and that existing implementers will miss that because of the
shorter timescale and no longer be "compliant" with the latest RFC?
Is that it?

To be honest, I can't really see that this'll have any impact
there. If the existing coder who'd be caught out isn't aware that
a WG is doing stuff then this will make no difference. If they
are aware that the WG is doing a -bis, then they can comment as
always before and during IETF LC. I really can't see this
experiment causing any real surprise in cases like that.

S.

> 
> -- 
> HLS
> 
> Adrian Farrel wrote:
>> Hi Alexa,
>>
>> Please be aware of this document that has just entered a four-week
>> IETF last
>> call. The document describes a proposed IETF process experiment under
>> the rules
>> of RFC 3933.
>>
>> The proposed experiment calls on the IETF Secretariat to take specific
>> actions
>> under certain circumstances in corner cases of the experiment. Could
>> you please
>> have someone in the Secretariat look at the draft and comment on the
>> practicalities of the actions. Note that, at this stage, no changes to
>> the tools
>> are proposed so any actions would require manual intervention (if the
>> experiment
>> were successful and resulted in permanent changes to IETF process we
>> might make
>> changes to the tools at some future time).
>>
>> Thanks,
>> Adrian
>>
>>> -----Original Message-----
>>> From: ietf-announce-bounces@ietf.org [mailto:ietf-announce-
>>> bounces@ietf.org] On Behalf Of The IESG
>>> Sent: 11 January 2013 15:15
>>> To: IETF-Announce
>>> Subject: Last Call: <draft-farrell-ft-03.txt> (A Fast-Track way to
>>> RFC with
>> Running
>>> Code) to Experimental RFC
>>>
>>>
>>> The IESG has received a request from an individual submitter to consider
>>> the following document:
>>> - 'A Fast-Track way to RFC with Running Code'
>>>   <draft-farrell-ft-03.txt> as Experimental RFC
>>>
>>> The IESG plans to make a decision in the next few weeks, and solicits
>>> final comments on this action. Please send substantive comments to the
>>> ietf@ietf.org mailing lists by 2013-02-08. Exceptionally, comments
>>> may be
>>> sent to iesg@ietf.org instead. In either case, please retain the
>>> beginning of the Subject line to allow automated sorting.
>>>
>>> Abstract
>>>
>>>    This memo describes an optional, fast-track way to progress a working
>>>    group document to IESG review.  It is provided as a process
>>>    experiment as defined in RFC 3933 for use when working group chairs
>>>    believe that there is running code that implements a working group
>>>    Internet-Draft.  The motivation is to have the IETF process
>>>    explicitly consider running code, consistent with the IETF's overall
>>>    philosophy of running code and rough consensus.
>>>
>>>    In this process all of working group last call, IETF last call, and
>>>    Area Director review are carried out in the same two week period.
>>>    Only comments that meet IESG Discuss criteria need to be addressed
>>>    during this stage, and authors are required to make any changes
>>>    within two weeks.
>>>
>>>    This experiment will run for one year.
>>>
>>>
>>> The file can be obtained via
>>> http://datatracker.ietf.org/doc/draft-farrell-ft/
>>>
>>> IESG discussion can be tracked via
>>> http://datatracker.ietf.org/doc/draft-farrell-ft/ballot/
>>>
>>> No IPR declarations have been submitted directly on this I-D.
>>
>>
>>
> 

From drc@virtualized.org  Mon Jan 14 10:18:45 2013
Return-Path: <drc@virtualized.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5613A21F892C for <ietf@ietfa.amsl.com>; Mon, 14 Jan 2013 10:18:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599]
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 SohgpK4jlCAB for <ietf@ietfa.amsl.com>; Mon, 14 Jan 2013 10:18:41 -0800 (PST)
Received: from trantor.virtualized.org (trantor.virtualized.org [199.48.134.42]) by ietfa.amsl.com (Postfix) with ESMTP id 67A6E21F8893 for <ietf@ietf.org>; Mon, 14 Jan 2013 10:18:41 -0800 (PST)
Received: from [10.0.1.13] (c-24-4-109-25.hsd1.ca.comcast.net [24.4.109.25]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: drc) by trantor.virtualized.org (Postfix) with ESMTPSA id 95CB4170A7; Mon, 14 Jan 2013 18:18:38 +0000 (UTC)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Subject: Re: I-D Action: draft-moonesamy-rfc2050-historic-00.txt
From: David Conrad <drc@virtualized.org>
In-Reply-To: <A4FC42DF71F5F7E5A36C9D4C@JcK-HP8200.jck.com>
Date: Mon, 14 Jan 2013 10:18:36 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <C316A5E8-209D-4A9A-9430-D96F15CBE02C@virtualized.org>
References: <A4FC42DF71F5F7E5A36C9D4C@JcK-HP8200.jck.com>
To: John C Klensin <john-ietf@jck.com>
X-Mailer: Apple Mail (2.1499)
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Jan 2013 18:18:45 -0000

John,

Just to be clear:

On Jan 14, 2013, at 7:19 AM, John C Klensin <john-ietf@jck.com> wrote:
> On those general subjects -- that trying to open the question of
> 2050 is a rat hole and that we should not go down it, we
> completely agree. =20

If the choice is leaving 2050 as is or reopening it to update it to =
reflect modern reality, I'd favor the latter.  I actually think the good =
parts of 2050 are probably covered in other documents and as such it's =
safe to unceremoniously bury 2050 in the back yard, but haven't bothered =
to actually verify this.

> I suggest that, despite stumbling into it,
> trying to do biblical-quality exegesis on the specific text and
> wording of most RFCs is also a rat hole (or perhaps just a
> different edge of the same one). =20

This is what I view as the pointless and exceedingly painful rathole and =
I'd recommend not going down it.

Regards,
-drc


From john@jlc.net  Mon Jan 14 10:52:41 2013
Return-Path: <john@jlc.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9521021F8450 for <ietf@ietfa.amsl.com>; Mon, 14 Jan 2013 10:52:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.073
X-Spam-Level: 
X-Spam-Status: No, score=-106.073 tagged_above=-999 required=5 tests=[AWL=0.526, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 2eb3HhtsImCR for <ietf@ietfa.amsl.com>; Mon, 14 Jan 2013 10:52:40 -0800 (PST)
Received: from mailhost.jlc.net (mailhost.jlc.net [199.201.159.4]) by ietfa.amsl.com (Postfix) with ESMTP id DCD6121F848B for <ietf@ietf.org>; Mon, 14 Jan 2013 10:52:39 -0800 (PST)
Received: by mailhost.jlc.net (Postfix, from userid 104) id 0659233DB8; Mon, 14 Jan 2013 13:52:40 -0500 (EST)
Date: Mon, 14 Jan 2013 13:52:39 -0500
From: John Leslie <john@jlc.net>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Subject: Re: Last Call: <draft-farrell-ft-03.txt> (A Fast-Track way to RFC with Running Code) to Experimental RFC
Message-ID: <20130114185239.GA41685@verdi>
References: <20130111151453.22161.50884.idtracker@ietfa.amsl.com> <20130114130541.GK62444@verdi> <50F442D9.7080702@cs.tcd.ie>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <50F442D9.7080702@cs.tcd.ie>
User-Agent: Mutt/1.4.1i
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Jan 2013 18:52:41 -0000

   Stephen did well to respond quickly!

   I will respond to most of his comments in private email, rather than
increase the noise-level on the <ietf> list. But a couple of points
deserve a better community understanding...

Stephen Farrell <stephen.farrell@cs.tcd.ie> wrote:
>...
> Well WGLC isn't part of 2026, and others have argued that that means
> that there's no need for this to even be a process-experiment...

   I think the Narrative Minutes show the IESG members questioned why
Stephen didn't simply bring things to IETF LastCall without a WG
LastCall. I invite readers to peruse the Narrative Minutes yourself
and see if it helps your understanding of what Stephen wanted beyond
that.

   But clearly the IESG has (not-yet-declared) consensus that Stephen
could do that without needing an experiment.

> My take on this is that yes, this is a proposal for an experiment
> that changes what we do now with WGLC, and its one I think we ought
> try.

   Clearly our process documents leave a lot of room for something
other than a formal WG LastCall -- but whatever is done is under the
management of the normal WG Chairs. I don't really understand how
Stephen wants to change that; but the his draft reads as if he
wants to take over responsibility for any last WG comments from the
WG Chairs. (It's _hard_ to believe that's what he wants -- the AD
job seems quite large enough without taking on such responsibilities.)

>... 
> Today, the convention is that the responsible AD ballots yes to
> kick off the process of IESG review. This is just saying that
> that AD might start IESG review with a different position (I
> would guess a no-objection, though there are exceptions to
> everything;-) because that AD hasn't had time to fully evaluate
> the draft. That AD might e.g. have asked someone else to check
> the implementation (allowed by this draft) but might want to
> do a fuller review during IESG evaluation before presumably
> balloting yes. Requiring the yes ballot up front is just a bit
> too demanding with the fast track timers.

   This text would better explain what Stephen was trying to say
in item 7. I'm not convinced it needs to be said at all -- this
is about internal IESG process; and most IETF participants neither
understand internal IESG process nor have any desire to learn it.

>> I don't believe "running code" is even particularly helpful in
>> run-of-the-mill Proposed Standards. 
> 
> Right. I guess that's where we disagree.
> 
>> I've seen it _seriously_ harm
>> the documents in cases where the "running code" has shipped and
>> there is reticence to change it: no matter how many weaknesses are
>> pointed out, you can't get WG consensus to change the spec.
> 
> I agree that happens. I don't think this'll change how often.

   At first blush, I would expect WG Chairs to try this experiment
when they happen to already have implementations (and not try for
it when they don't). The reticence to change shipping code is
both very human and good generic-management: I don't expect this
reticence to go away.

   I _do_ think this experiment would make the problem worse. Any
change to shipping code involves some level of management decision;
and squeezing such management decision into two weeks ensures it
won't happen absent _customer_ complaints.

   Am I being unfair to talk about squeezing that decision into
two weeks? Possibly I am... But this whole experiment _is_ about
squeezing the timeframe; and in my experience squeezing timeframes
tends to crowd out careful consideration. YMMV...

>> In cases where "running code" has proven helpful, it's my
>> honest opinion that the spec has become way too complicated (and
>> thus the "running code" has proven which parts are unworkable).
> 
> Hmm. I've had somewhat the opposite experience, so I guess
> YMMV. I've not gone to dig up examples though but in DKIM I
> think we ended up with a simpler spec. due to some folks
> doing good work with running code before and during the WG's
> processing of the drafts.

   Yes: DKIM clearly had become too complicated. Stephen and I
agree there!

>> IMHO, we designed a separate "Proposed Standard" step to get
>> a specification published quickly without delving into the many
>> questions that arise when writing actual code. 
> 
> That's fair. I think this experiment partly reflects one way
> in which the standards process theory and IETF practice have
> diverged over the years. The bar for PS is mostly now much
> higher than was the original intent. I think that in some
> cases, this experiment might lower that bar a little.

   I'm always fascinated at the things folks think will "lower
the bar" for Proposed Standard. ;^)

>... 
> But more to the point, I think that in a lot of cases where
> the IETF has done a good job, there has been running code
> before the WG even started...

   This perhaps explains where Stephen is coming from. Such
cases do exist; and it is arguable that the process Stephen has
describe in this draft are well-suited to such cases (though I
would still have to quibble about some details).

   I remain unconvinced, however, that fast-tracking the cases
that start from running code is a good use of WG efforts. Such
cases seem better suited to Independent Submissions from a
design team (which would _greatly_ speed the process). When
a WG is formed, IMHO, they should be encouraged to look at the
problem from some quite different angles, in search of a way
to "Simplify!".

--
John Leslie <john@jlc.net>

From Lee@asgard.org  Mon Jan 14 11:13:37 2013
Return-Path: <Lee@asgard.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9F33021F8B35 for <ietf@ietfa.amsl.com>; Mon, 14 Jan 2013 11:13:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 hDAfKKDFOL3X for <ietf@ietfa.amsl.com>; Mon, 14 Jan 2013 11:13:36 -0800 (PST)
Received: from atl4mhob14.myregisteredsite.com (atl4mhob14.myregisteredsite.com [209.17.115.52]) by ietfa.amsl.com (Postfix) with ESMTP id 813B321F8B33 for <ietf@ietf.org>; Mon, 14 Jan 2013 11:13:36 -0800 (PST)
Received: from mailpod.hostingplatform.com (mail.networksolutionsemail.com [205.178.146.50]) by atl4mhob14.myregisteredsite.com (8.14.4/8.14.4) with ESMTP id r0EJDZBh004933 for <ietf@ietf.org>; Mon, 14 Jan 2013 14:13:35 -0500
Received: (qmail 11398 invoked by uid 0); 14 Jan 2013 19:13:34 -0000
Received: from unknown (HELO ?10.71.36.69?) (lee@asgard.org@204.235.115.165) by 0 with ESMTPA; 14 Jan 2013 19:13:34 -0000
User-Agent: Microsoft-MacOutlook/14.2.5.121010
Date: Mon, 14 Jan 2013 14:13:30 -0500
Subject: Re: I-D Action: draft-moonesamy-rfc2050-historic-00.txt
From: Lee Howard <Lee@asgard.org>
To: David Conrad <drc@virtualized.org>, John C Klensin <john-ietf@jck.com>
Message-ID: <CD19C02E.7F3B%Lee@asgard.org>
Thread-Topic: I-D Action: draft-moonesamy-rfc2050-historic-00.txt
In-Reply-To: <C316A5E8-209D-4A9A-9430-D96F15CBE02C@virtualized.org>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Jan 2013 19:13:37 -0000

On 1/14/13 1:18 PM, "David Conrad" <drc@virtualized.org> wrote:

>John,
>
>Just to be clear:
>
>On Jan 14, 2013, at 7:19 AM, John C Klensin <john-ietf@jck.com> wrote:
>> On those general subjects -- that trying to open the question of
>> 2050 is a rat hole and that we should not go down it, we
>> completely agree.
>
>If the choice is leaving 2050 as is or reopening it to update it to
>reflect modern reality, I'd favor the latter.  I actually think the good
>parts of 2050 are probably covered in other documents and as such it's
>safe to unceremoniously bury 2050 in the back yard, but haven't bothered
>to actually verify this.

I would not support moving rfc2050 to Historic on the basis of your
"probably."  Absent a document that updates/obsoletes 2050, I can't think
of any good that would come of moving it to Historic.

This draft also moves rfc1366 and rfc1466 to Historic, though I note that
rfc2050 obsoleted 1466, which replaced 1366.
For rfc2050, I would want discussions of the points made in the original
document, and notice of where the current status is documented.  Much of
it is still true, and is still BCP.

Lee



From abdussalambaryun@gmail.com  Mon Jan 14 11:23:13 2013
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 77B3121F8ACE for <ietf@ietfa.amsl.com>; Mon, 14 Jan 2013 11:23:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.581
X-Spam-Level: 
X-Spam-Status: No, score=-3.581 tagged_above=-999 required=5 tests=[AWL=0.018,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 iD4IcYEMRzpj for <ietf@ietfa.amsl.com>; Mon, 14 Jan 2013 11:23:11 -0800 (PST)
Received: from mail-vb0-f51.google.com (mail-vb0-f51.google.com [209.85.212.51]) by ietfa.amsl.com (Postfix) with ESMTP id 5B6D321F8AC3 for <ietf@ietf.org>; Mon, 14 Jan 2013 11:23:11 -0800 (PST)
Received: by mail-vb0-f51.google.com with SMTP id fq11so3817883vbb.24 for <ietf@ietf.org>; Mon, 14 Jan 2013 11:23:10 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:cc:content-type; bh=rVOLvDVM6lK7N9T9CU3R4cQ55o7/W37GC/4VQzyfXIY=; b=vBy8a9grZ2jY/P1t339cnrdtBznQjoB500qrJ17k4rVn/RSITEoMshMq6PBNDk+RG8 1NglcRIJAVSlP8jQZ/FgnBPNDaMEYLiY+ESi5L4FADmbFUfV1vnj/yk2YOF4TeBFA2Dj /FfcOfYxheax8HDb0K/RfBTFAhiPF5h2DSHcJS6NVs6G3gj8Oxij+cVnl1LaeY64o9Xh VnX4NZjRuV2Ynd1iL1NrSNDSgMjyWuvCtwvIrpl10T9ytJNnDvKa6jpU170Xi1RNF3TD vutBykfvN4RfA1TH9+94js1pgRWQj4Vnpx+RhI+Isz6zPnE7/X1SX08kMHdj5YWuLCxN guMw==
MIME-Version: 1.0
Received: by 10.220.107.5 with SMTP id z5mr103425195vco.22.1358191390858; Mon, 14 Jan 2013 11:23:10 -0800 (PST)
Received: by 10.220.145.5 with HTTP; Mon, 14 Jan 2013 11:23:10 -0800 (PST)
Date: Mon, 14 Jan 2013 20:23:10 +0100
Message-ID: <CADnDZ8854LRh-wjfLT-9Xg-njwPBW5PhUUFgJinRTr5hc9VWOg@mail.gmail.com>
Subject: Re: I-D Action: draft-moonesamy-rfc2050-historic-00.txt
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: john-ietf@jck.com
Content-Type: text/plain; charset=ISO-8859-1
Cc: ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Jan 2013 19:23:13 -0000

Hi John,

> I suggest that, despite stumbling into it,
> trying to do biblical-quality exegesis on the specific text and
> wording of most RFCs is also a rat hole (or perhaps just a
> different edge of the same one).

We have to be reasonable in IETF. I don't understand your reason, do
you mean 2050 is not needing update or do you mean it is a rat hole.
There is no doubt that we need to close any rat hole, and to open to
produce new drafts,

I agree with Conrad and Moonesamy input,

AB

From ncamwing@cisco.com  Mon Jan 14 12:29:53 2013
Return-Path: <ncamwing@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7C35B21F8B25; Mon, 14 Jan 2013 12:29:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 pFqiXnyGZqT2; Mon, 14 Jan 2013 12:29:52 -0800 (PST)
Received: from rcdn-iport-6.cisco.com (rcdn-iport-6.cisco.com [173.37.86.77]) by ietfa.amsl.com (Postfix) with ESMTP id A6AC721F8AE3; Mon, 14 Jan 2013 12:29:52 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2440; q=dns/txt; s=iport; t=1358195392; x=1359404992; h=from:to:cc:subject:date:message-id:in-reply-to: content-id:content-transfer-encoding:mime-version; bh=11LZnwKUd//44mubDxCSZptScAc9JcFyUfSSkf3QNhs=; b=O38Xc4E72J1cZfp5wetWDE8HLQpysCYwSPWXagGIHpqRGyTF0MH6wGW0 jcVOSfNKcLOdk2Fo4710+pIcMr8ISbeYXuOZY8+N/jDlIoJQzlm8laBvQ HTr+IPkD9nCJCTyQ6WnbMulWRQLAPBoewzwECU2D0K5qfDB07taRSrYJJ I=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ag0FAMRp9FCtJXG9/2dsb2JhbAA7CbpEgzYWc4IeAQEBBDo0CxIBCBIGChQFPRQDDgIEAQ0FCIgRtUWMfYNQYQOmVIJ1giQ
X-IronPort-AV: E=Sophos;i="4.84,468,1355097600"; d="scan'208";a="162296379"
Received: from rcdn-core2-2.cisco.com ([173.37.113.189]) by rcdn-iport-6.cisco.com with ESMTP; 14 Jan 2013 20:29:52 +0000
Received: from xhc-aln-x02.cisco.com (xhc-aln-x02.cisco.com [173.36.12.76]) by rcdn-core2-2.cisco.com (8.14.5/8.14.5) with ESMTP id r0EKTqM9007998 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 14 Jan 2013 20:29:52 GMT
Received: from xmb-aln-x02.cisco.com ([169.254.5.197]) by xhc-aln-x02.cisco.com ([173.36.12.76]) with mapi id 14.02.0318.004; Mon, 14 Jan 2013 14:29:51 -0600
From: "Nancy Cam-Winget (ncamwing)" <ncamwing@cisco.com>
To: SM <sm@resistor.net>, "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: Last Call: <draft-ietf-nea-pt-eap-06.txt> (PT-EAP: Posture Transport (PT) Protocol For EAP Tunnel Methods) to Proposed Standard
Thread-Topic: Last Call: <draft-ietf-nea-pt-eap-06.txt> (PT-EAP: Posture Transport (PT) Protocol For EAP Tunnel Methods) to Proposed Standard
Thread-Index: AQHN8pXnKHR1ECWe3UGYdb6j/BleQw==
Date: Mon, 14 Jan 2013 20:29:51 +0000
Message-ID: <B80278DF1B7C814184086F4A6ECB3115225B9B21@xmb-aln-x02.cisco.com>
In-Reply-To: <6.2.5.6.2.20130108225436.0b31f008@resistor.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.2.1.120420
x-originating-ip: [10.154.12.73]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <74F017BB889D714E8604217F4D7665FA@cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "nea@ietf.org" <nea@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Jan 2013 20:29:53 -0000

Hi SM,

Thanks for the thorough review of the draft.  Please see comments below:

On 1/8/13 11:25 PM, "SM" <sm@resistor.net> wrote:

>At 06:43 02-01-2013, The IESG wrote:
>>The IESG has received a request from the Network Endpoint Assessment WG
>>(nea) to consider the following document:
>>- 'PT-EAP: Posture Transport (PT) Protocol For EAP Tunnel Methods'
>>   <draft-ietf-nea-pt-eap-06.txt> as Proposed Standard
>>
>>The IESG plans to make a decision in the next few weeks, and solicits
>>final comments on this action. Please send substantive comments to the
>>ietf@ietf.org mailing lists by 2013-01-16. Exceptionally, comments may be
>
>This is a quick comment.
>
>In Section 1:
>
>   "The PT-EAP protocol MUST be protected by an outer
>    TLS-based EAP tunnel method to ensure the exchanged messages are
>    protected from a variety of threats from hostile intermediaries."
>
>The RFC 2119 boilerplate is after that "MUST".
[NCW] I can change it to a lower case "must", ok?

>
>In Section 1.1:
>
>   "This document does not define an architecture or reference model.
>    Instead, it defines a protocol that works within the reference model
>    described in the NEA Requirements specification [RFC5209]."
>
>The reference is informative.
[NCW] We can move the reference to be normative.

>
>In Section 6:
>
>   "PT-EAP does not directly utilize or require direct knowledge of
>    any personally identifiable information (PII).  PT-EAP will
>    typically be used in conjunction with other EAP methods
>    that provide for the user authentication (if bi-directional
>    authentication is used), so the user's credentials are not
>    directly seen by the PT-EAP inner method."
>
>Section 9 RFC 5209 mentions that:
>
>   "However, in situations where the endpoint is owned by the user
>    or where local laws protect the rights of the user even when
>    using endpoints owned by another party, it is critical that the NEA
>    implementation enable the user to control what endpoint information
>    is shared with the network."
>
>I didn't find any information in the draft to assess the privacy
>implications.  Are there any such implications?
[NCW] I don't think there are specifically for PT-EAP.  The sections you
reference
Were to (in section 6) addressing the general EAP identity as PT-EAP is
really not
An "authentication" method.
>
>Regards,
>-sm=20
>


From mrex@sap.com  Mon Jan 14 12:32:56 2013
Return-Path: <mrex@sap.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2A8C821F87D5 for <ietf@ietfa.amsl.com>; Mon, 14 Jan 2013 12:32:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.172
X-Spam-Level: 
X-Spam-Status: No, score=-10.172 tagged_above=-999 required=5 tests=[AWL=0.077, BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_HI=-8]
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 CtFX+3D5oYUU for <ietf@ietfa.amsl.com>; Mon, 14 Jan 2013 12:32:55 -0800 (PST)
Received: from smtpde02.sap-ag.de (smtpde02.sap-ag.de [155.56.68.140]) by ietfa.amsl.com (Postfix) with ESMTP id 263A921F87CB for <ietf@ietf.org>; Mon, 14 Jan 2013 12:32:54 -0800 (PST)
Received: from mail05.wdf.sap.corp by smtpde02.sap-ag.de (26) with ESMTP id r0EKWqOt018125 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 14 Jan 2013 21:32:53 +0100 (MET)
Subject: Re: Last Call: <draft-farrell-ft-03.txt> (A Fast-Track way to RFC with Running Code) to Experimental RFC
In-Reply-To: <20130114130541.GK62444@verdi>
To: John Leslie <john@jlc.net>
Date: Mon, 14 Jan 2013 21:32:52 +0100 (CET)
X-Mailer: ELM [version 2.4ME+ PL125 (25)]
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="US-ASCII"
Message-Id: <20130114203252.E331A1A455@ld9781.wdf.sap.corp>
From: mrex@sap.com (Martin Rex)
X-SAP: out
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: mrex@sap.com
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Jan 2013 20:32:56 -0000

John Leslie wrote:
> 
>    I'm pretty darn uncomfortable _ever_ picking a fight with any
> sitting AD, But I feel obligated to say this seems like a terrible
> idea to me.
> 
>    As a background, I'm a long-time believer in "rough consensus" for
> Proposed Standard and "running code" for advancement along the
> standards track. I do not believe the two mix well.

I don't have the resource to participate the discussion, but
these statements capture my opinion pretty well.

I also believe that the existence of "running code" would be a terrible
excuse for not resolving technical objections. 

While implementing a spec can help finding inconsitencies and ambiguities
in a spec, infering the reverse when the implementation is *NOT*
created as a by-product of a formal correctness proofing tool for the
spec does not hold.

Weird implementations that are incompliant with a spec, or that ignore
rather than recognize and report defects in a spec are extremely common.

And if the sequence of events is, that an implementation is created first,
and then producing a spec describing the alleged implementation behaviour,
is going to result in lots of surprises about the frequent lack of
correctness of both, the spec and the implementation it is based upon.


-Martin

From mrex@sap.com  Mon Jan 14 13:24:25 2013
Return-Path: <mrex@sap.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B7EF021F8AD4 for <ietf@ietfa.amsl.com>; Mon, 14 Jan 2013 13:24:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.176
X-Spam-Level: 
X-Spam-Status: No, score=-10.176 tagged_above=-999 required=5 tests=[AWL=0.073, BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_HI=-8]
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 78JWEeXjSMtj for <ietf@ietfa.amsl.com>; Mon, 14 Jan 2013 13:24:24 -0800 (PST)
Received: from smtpde02.sap-ag.de (smtpde02.sap-ag.de [155.56.68.140]) by ietfa.amsl.com (Postfix) with ESMTP id 8B0D221F8AC0 for <ietf@ietf.org>; Mon, 14 Jan 2013 13:24:24 -0800 (PST)
Received: from mail05.wdf.sap.corp by smtpde02.sap-ag.de (26) with ESMTP id r0ELOMqB029774 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 14 Jan 2013 22:24:22 +0100 (MET)
Subject: Re: Last Call: <draft-laurie-pki-sunlight-05.txt> (Certificate Transparency) to Experimental RFC
In-Reply-To: <6.2.5.6.2.20130110065213.0ad01a90@resistor.net>
To: SM <sm@resistor.net>
Date: Mon, 14 Jan 2013 22:24:22 +0100 (CET)
X-Mailer: ELM [version 2.4ME+ PL125 (25)]
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="US-ASCII"
Message-Id: <20130114212422.AEA431A455@ld9781.wdf.sap.corp>
From: mrex@sap.com (Martin Rex)
X-SAP: out
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: mrex@sap.com
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Jan 2013 21:24:25 -0000

SM wrote:
>
> The IESG wrote:
>>
>>The IESG has received a request from an individual submitter to consider
>>the following document:
>>- 'Certificate Transparency'
>>   <draft-laurie-pki-sunlight-05.txt> as Experimental RFC
>>
>>The IESG plans to make a decision in the next few weeks, and solicits
>>final comments on this action. Please send substantive comments to the
>>ietf@ietf.org mailing lists by 2013-01-24. Exceptionally, comments may be
> 
> In Section 1:
> 
>    "Certificate Transparency aims to mitigate the problem of misissued
>     certificates by providing publicly auditable, append-only, untrusted
>     logs of all issued certificates."
> 
> It seems that CAs are having trust issues.  ETSI TS 102 042 audits 
> looks like paperwork instead of assessing what could go wrong 
> [1].  Isn't Certificate Transparency trying to mitigate the problem 
> of CAs issuing fake certificates instead of "misissued" certificates?


More appropriately, RPs are having trust issues with public CAs,
and domain owners have found themselves more than once faced with
the unexpected fraudulent issuance of certs allegedly authorized
for their domains.

Certificate Transparency (CT), the ways I understand it, is basically
a public certificate issuance log for public CAs (those you find in
the CABrowser forum, who have their their (Root)CA certs distributed
as pre-trusted in common Web Browsers).

Such a public cert issuance log can be used by domain owners to detect
cert issuance for their domains that they didn't actually authorize
or ask for (so which are likely fraudulent) *much* earlier after cert
issuance.  So far, this would often only become apparent if the CA
detected the fraudulent issuance itself, or when an attacked RP
would realize that it is being attacked with a perfectly valid(!!)
server certificate.  The latter typically happens only with RPs
that perform cert pinning and where the user that is alerted about
an unexpected server cert change is sufficiently knowledgable to
distinguish a likely misissued server cert from a mere roll-over
server cert change.


X.509/PKIX has a serious design/birth defect in certificate revocation,
by lacking the means to convey the information whether a certificate
was properly issued and is properly visible to CA audits and
desaster recovery procedures.  For CRLs that design flaw can not be
fixed within the protocol itself, because CRLs are a pure blacklisting
mechanism that blindly assumes that the absence of a revocation
implies that a certificate has been properly issued.  An assumption
that has been proven to be a flawed in the real world several times by now.

When complementing CRL checking with CT, this X.509 CRL design flaw
can be mitigated.


There currently are proposals for fixing a slightly different (but
related) problem for OCSP in PKIX, but there are some X.509 fanciers
that appear enfuriated by the idea of admitting that X.509 CRLs and
rfc2560-OCSP contain a shortcoming that needs fixing, so progress
in PKIX is slow.

The scope of CT is different than whatever PKIX might deliver
(even when rough consensus can be obtained within PKIX to improve OCSP),
because CT allows domain owners to monitor/determine issuance of certs
for their domain from public records.

-Martin

From stephen.farrell@cs.tcd.ie  Mon Jan 14 13:35:05 2013
Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 24F6721F8AD4 for <ietf@ietfa.amsl.com>; Mon, 14 Jan 2013 13:35:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 pCqlydH26qT7 for <ietf@ietfa.amsl.com>; Mon, 14 Jan 2013 13:35:04 -0800 (PST)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) by ietfa.amsl.com (Postfix) with ESMTP id F190721F8AB0 for <ietf@ietf.org>; Mon, 14 Jan 2013 13:35:03 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id B5CD0BE20; Mon, 14 Jan 2013 21:34:41 +0000 (GMT)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ia5cpHBbiP3F; Mon, 14 Jan 2013 21:34:40 +0000 (GMT)
Received: from [10.87.48.11] (unknown [86.41.50.151]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id E9E59BE1E; Mon, 14 Jan 2013 21:34:39 +0000 (GMT)
Message-ID: <50F479EF.8000402@cs.tcd.ie>
Date: Mon, 14 Jan 2013 21:34:39 +0000
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130106 Thunderbird/17.0.2
MIME-Version: 1.0
To: John Leslie <john@jlc.net>
Subject: Re: Last Call: <draft-farrell-ft-03.txt> (A Fast-Track way to RFC with Running Code) to Experimental RFC
References: <20130111151453.22161.50884.idtracker@ietfa.amsl.com> <20130114130541.GK62444@verdi> <50F442D9.7080702@cs.tcd.ie> <20130114185239.GA41685@verdi>
In-Reply-To: <20130114185239.GA41685@verdi>
X-Enigmail-Version: 1.5
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Jan 2013 21:35:05 -0000

Hiya,

On 01/14/2013 06:52 PM, John Leslie wrote:
>    Stephen did well to respond quickly!

Responsive with dodgy ideas - sounds like me:-)

>    I will respond to most of his comments in private email, rather than
> increase the noise-level on the <ietf> list. But a couple of points
> deserve a better community understanding...
> 
> Stephen Farrell <stephen.farrell@cs.tcd.ie> wrote:
>> ...
>> Well WGLC isn't part of 2026, and others have argued that that means
>> that there's no need for this to even be a process-experiment...
> 
>    I think the Narrative Minutes show the IESG members questioned why
> Stephen didn't simply bring things to IETF LastCall without a WG
> LastCall. I invite readers to peruse the Narrative Minutes yourself
> and see if it helps your understanding of what Stephen wanted beyond
> that.
> 
>    But clearly the IESG has (not-yet-declared) consensus that Stephen
> could do that without needing an experiment.

Sorry John, I'm lost. There was no WG here and hence no WGLC.
The IESG hasn't as far as I know reached any consensus for
or against this approach, whether declared or not.

The IESG chatted about this on an informal telechat just after it
was previously discussed on this list, and some ADs had concerns
about the experiment. Others seemed less concerned. Some changes
to the draft resulted from that discussion, but my guess is that
the existing concerns are not fully resolved.

On last week's telechat Adrian as sponsoring AD asked if anyone
felt this was implausible enough that an IETF LC ought not be issued
(as RFC 3933 says) and there was no objection to that. So we're
now at IETF LC for this draft. Again, there's no implication that
the IESG like or will approve this experiment.

>> My take on this is that yes, this is a proposal for an experiment
>> that changes what we do now with WGLC, and its one I think we ought
>> try.
> 
>    Clearly our process documents leave a lot of room for something
> other than a formal WG LastCall -- but whatever is done is under the
> management of the normal WG Chairs. 

As would be the case during this experiment. Its the WG chairs
that initiate the fast-track process and that's very clear in
the draft.

> I don't really understand how
> Stephen wants to change that; but the his draft reads as if he
> wants to take over responsibility for any last WG comments from the
> WG Chairs. (It's _hard_ to believe that's what he wants -- the AD
> job seems quite large enough without taking on such responsibilities.)

Indeed that'd be hard to believe. Again, the WG chairs initiate
this, so I'm confused how you think I could think that. I think
the experiment would put some additional time-pressure on ADs
but doesn't really add to the absolute amount of text review work
for each draft except in terms of dealing with/checking the
implementation, which is new.

>> ... 
>> Today, the convention is that the responsible AD ballots yes to
>> kick off the process of IESG review. This is just saying that
>> that AD might start IESG review with a different position (I
>> would guess a no-objection, though there are exceptions to
>> everything;-) because that AD hasn't had time to fully evaluate
>> the draft. That AD might e.g. have asked someone else to check
>> the implementation (allowed by this draft) but might want to
>> do a fuller review during IESG evaluation before presumably
>> balloting yes. Requiring the yes ballot up front is just a bit
>> too demanding with the fast track timers.
> 
>    This text would better explain what Stephen was trying to say
> in item 7. I'm not convinced it needs to be said at all -- this
> is about internal IESG process; and most IETF participants neither
> understand internal IESG process nor have any desire to learn it.

Fair point. OTOH, I think its a real aspect of the experiment so
ought be mentioned even if that's not very useful for most readers.

>>> I don't believe "running code" is even particularly helpful in
>>> run-of-the-mill Proposed Standards. 
>>
>> Right. I guess that's where we disagree.
>>
>>> I've seen it _seriously_ harm
>>> the documents in cases where the "running code" has shipped and
>>> there is reticence to change it: no matter how many weaknesses are
>>> pointed out, you can't get WG consensus to change the spec.
>>
>> I agree that happens. I don't think this'll change how often.
> 
>    At first blush, I would expect WG Chairs to try this experiment
> when they happen to already have implementations (and not try for
> it when they don't). The reticence to change shipping code is
> both very human and good generic-management: I don't expect this
> reticence to go away.

And that'd be fine. This experiment is not intended for all drafts.

>    I _do_ think this experiment would make the problem worse. Any
> change to shipping code involves some level of management decision;
> and squeezing such management decision into two weeks ensures it
> won't happen absent _customer_ complaints.

Reasonable point. But you've conflated shipping code and running
code and also code changes with product release cycles. All of
those can be independent things so I don't think your conclusion
holds.

>    Am I being unfair to talk about squeezing that decision into
> two weeks? Possibly I am... But this whole experiment _is_ about
> squeezing the timeframe; and in my experience squeezing timeframes
> tends to crowd out careful consideration. YMMV...

Not unfair, no. Just incorrect:-)

>>> In cases where "running code" has proven helpful, it's my
>>> honest opinion that the spec has become way too complicated (and
>>> thus the "running code" has proven which parts are unworkable).
>>
>> Hmm. I've had somewhat the opposite experience, so I guess
>> YMMV. I've not gone to dig up examples though but in DKIM I
>> think we ended up with a simpler spec. due to some folks
>> doing good work with running code before and during the WG's
>> processing of the drafts.
> 
>    Yes: DKIM clearly had become too complicated. Stephen and I
> agree there!

Heh. I think DKIM is pretty simple in itself actually. Mail
of course isn't, nor is spam.

> 
>>> IMHO, we designed a separate "Proposed Standard" step to get
>>> a specification published quickly without delving into the many
>>> questions that arise when writing actual code. 
>>
>> That's fair. I think this experiment partly reflects one way
>> in which the standards process theory and IETF practice have
>> diverged over the years. The bar for PS is mostly now much
>> higher than was the original intent. I think that in some
>> cases, this experiment might lower that bar a little.
> 
>    I'm always fascinated at the things folks think will "lower
> the bar" for Proposed Standard. ;^)

Yep. Its a process-proposal, and thus involves tilting and
windmills:-)

>> But more to the point, I think that in a lot of cases where
>> the IETF has done a good job, there has been running code
>> before the WG even started...
> 
>    This perhaps explains where Stephen is coming from. Such
> cases do exist; and it is arguable that the process Stephen has
> describe in this draft are well-suited to such cases (though I
> would still have to quibble about some details).

Right.

>    I remain unconvinced, however, that fast-tracking the cases
> that start from running code is a good use of WG efforts. Such
> cases seem better suited to Independent Submissions from a
> design team (which would _greatly_ speed the process). When
> a WG is formed, IMHO, they should be encouraged to look at the
> problem from some quite different angles, in search of a way
> to "Simplify!".

Maybe. But that's a different proposal, perhaps a better one,
but a different one, and this is the one on the table right
now. (I make no claim that this experiment is the best
possible or anything like that.)

Cheers,
S.



> 
> --
> John Leslie <john@jlc.net>
> 
> 

From sm@resistor.net  Mon Jan 14 13:42:09 2013
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BB34321F88C4; Mon, 14 Jan 2013 13:42:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.583
X-Spam-Level: 
X-Spam-Status: No, score=-102.583 tagged_above=-999 required=5 tests=[AWL=0.016, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 d6eAt+uc28D9; Mon, 14 Jan 2013 13:42:06 -0800 (PST)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 33C5621F888C; Mon, 14 Jan 2013 13:42:06 -0800 (PST)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r0ELfwQk015885; Mon, 14 Jan 2013 13:42:01 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1358199724; bh=4tFNIUI0YQa3tG2dr+E8nheKffWwn8ncoviWILR2i9o=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=rd2rvXJ0vL0p5RWgX9wb2g0RbVdi2tMZA6EbKHDFdz1jSIp94ULp9SrGThMMUUCON 3i+qlyw5Hln6FSP8JUdUH65gkPMPZZw/gzhDngAh9hphdqYOcxCzKxDiBf3IaqpMmK w48IhyzeLqF8XWJ/L9hEjAqxVOq2I0f/Kva0DsW8=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1358199724; i=@resistor.net; bh=4tFNIUI0YQa3tG2dr+E8nheKffWwn8ncoviWILR2i9o=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=RffMZ2pKrof4JRPTJFqvENZNUFqYs0Qh/Cf6t0tm6fsKXPeZxloSvjTZVW8MqrSVU G0X1OgOh/aVBL3sPlcGTHWydQZB4ZJ0Gwt6IStpr2CChZyxKAu8XhCqrW2PzBgSCty LAMJApQ6XsUktEBhI7ryfpYUHlgt4exSPyjacE4E=
Message-Id: <6.2.5.6.2.20130114123552.0a8fb9e8@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Mon, 14 Jan 2013 13:34:09 -0800
To: "Nancy Cam-Winget (ncamwing)" <ncamwing@cisco.com>
From: SM <sm@resistor.net>
Subject: Re: Last Call: <draft-ietf-nea-pt-eap-06.txt> (PT-EAP: Posture Transport (PT) Protocol For EAP Tunnel Methods) to Proposed Standard
In-Reply-To: <B80278DF1B7C814184086F4A6ECB3115225B9B21@xmb-aln-x02.cisco .com>
References: <6.2.5.6.2.20130108225436.0b31f008@resistor.net> <B80278DF1B7C814184086F4A6ECB3115225B9B21@xmb-aln-x02.cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: ietf-privacy@ietf.org, nea@ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Jan 2013 21:42:09 -0000

Hi Nancy,
At 12:29 14-01-2013, Nancy Cam-Winget (ncamwing) wrote:
>[NCW] I can change it to a lower case "must", ok?

That's ok.

>[NCW] We can move the reference to be normative.

Ok.

>[NCW] I don't think there are specifically for PT-EAP.  The sections you
>reference
>Were to (in section 6) addressing the general EAP identity as PT-EAP is
>really not
>An "authentication" method.

If I understood the above correctly PT-EAP does not transport any 
information which could be used to identify an individual.  That's 
different from PT-EAP not being an "authenticated" method. Therefore, 
there isn't much to say in terms of privacy considerations.

I suggest not including the following then:

   "As a transport protocol, PT-EAP does not directly utilize or
    require direct knowledge of any personally identifiable
    information (PII)."

The draft can leverage the second paragraph of Section 6 as "privacy 
considerations" instead of making a statement about PII.  I'll copy 
this message to ietf-privacy@ to get a better opinion.

In Section 6:

   "Therefore, it is important for deployers to leverage these
    protections in order to prevent disclosure of PII potentially
    contained within PA-TNC or PB-TNC within the PT-EAP payload."

I suggest "information about an individual" instead of PII [1].

Regards,
-sm

1. I used the wording from draft-iab-privacy-considerations-06  


From sm@resistor.net  Mon Jan 14 14:09:35 2013
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D2A0821F8859 for <ietf@ietfa.amsl.com>; Mon, 14 Jan 2013 14:09:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.584
X-Spam-Level: 
X-Spam-Status: No, score=-102.584 tagged_above=-999 required=5 tests=[AWL=0.015, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 k8f0x4XBPzG4 for <ietf@ietfa.amsl.com>; Mon, 14 Jan 2013 14:09:34 -0800 (PST)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id CC1CE21F883B for <ietf@ietf.org>; Mon, 14 Jan 2013 14:09:34 -0800 (PST)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r0EM9Pi8023321; Mon, 14 Jan 2013 14:09:28 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1358201371; bh=1wdRvKCTv2pzoe/4CxzTj4AuaHz+uL5K4CyHyRLQTnU=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=ZstCdK0Tngl/ENrICHjGn5RLmJi9CSx9jfsbdYq/kJD0KgoiYMzzGKcRkTZeqoeSX XLEqqNDPfHgM3/WZi8B40U2sEc1HEjkPKE94100J3Xwh6s6UH6CLnNPEWqtnh4w6PR bAQ7iaf191PThAaT/j/sA3OAW062uhfP828lTJpQ=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1358201371; i=@resistor.net; bh=1wdRvKCTv2pzoe/4CxzTj4AuaHz+uL5K4CyHyRLQTnU=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=UEYH3eq5ZrpXH48dsXigtgk9IFaBTZ8s+fvSDXph5qYIN4QbXZXg55wSAJgvEiL5b 93AvgA5lbCxIzjkkF/UvFvq7V1BXrkEJXwShXAIbpQY+m/Qr4m1A6kyNvlvsXmOfjl ETP2UyOsJ7nhWZ2TYw4GsXdwlIkCsxZphP4Eyf4A=
Message-Id: <6.2.5.6.2.20130114134400.09386f80@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Mon, 14 Jan 2013 14:04:55 -0800
To: Ben Laurie <benl@google.com>
From: SM <sm@resistor.net>
Subject: Re: Last Call: <draft-laurie-pki-sunlight-05.txt> (Certificate Transparency) to Experimental RFC
In-Reply-To: <CABrd9SToe0LvzSa+po6UeX92fBz=8mrk1k7Z5i_nph_2oSDKsQ@mail.g mail.com>
References: <6.2.5.6.2.20130110065213.0ad01a90@resistor.net> <50F3EC5C.3070109@cs.tcd.ie> <CABrd9SToe0LvzSa+po6UeX92fBz=8mrk1k7Z5i_nph_2oSDKsQ@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Jan 2013 22:09:36 -0000

Hi Ben,

As a FYI, Eliot Lear posted a review at 
http://www.ietf.org/mail-archive/web/apps-discuss/current/msg08649.html

At 06:38 14-01-2013, Ben Laurie wrote:
>Is there a difference, when you get down to it?

If I am talking to a non-English speaker it might be clearer when I 
say "fake Gucci handbag" instead of "misissued Gucci handbag".

I don't have a strong opinion about this.

>Yes. This is necessary for auditing/monitoring.

Ok.

>I have changed it to "Log operators..."

Ok.

>MUST and SHALL are equivalent.

Yes.

>What wording do you suggest that would be better?

I'll take this off-list.

>I don't understand the question.

If I guarantee that I won't use a zero the code doesn't expect 
it.  If the code gets a zero it might not handle it gracefully.  It's 
safer to tell the receiver to ignore a zero than to tell the sender 
not to send a zero.

Regards,
-sm 


From stephen.farrell@cs.tcd.ie  Mon Jan 14 14:15:15 2013
Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 414DE21F8B65 for <ietf@ietfa.amsl.com>; Mon, 14 Jan 2013 14:15:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 eZ3DCTDjC8cy for <ietf@ietfa.amsl.com>; Mon, 14 Jan 2013 14:15:14 -0800 (PST)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) by ietfa.amsl.com (Postfix) with ESMTP id A206821F8B54 for <ietf@ietf.org>; Mon, 14 Jan 2013 14:15:07 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id AD332BE49; Mon, 14 Jan 2013 22:14:44 +0000 (GMT)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aIbharMKDIgQ; Mon, 14 Jan 2013 22:14:43 +0000 (GMT)
Received: from [10.87.48.11] (unknown [86.41.50.151]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id BF401BE3B; Mon, 14 Jan 2013 22:14:43 +0000 (GMT)
Message-ID: <50F48353.4010105@cs.tcd.ie>
Date: Mon, 14 Jan 2013 22:14:43 +0000
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130106 Thunderbird/17.0.2
MIME-Version: 1.0
To: mrex@sap.com
Subject: Re: Last Call: <draft-farrell-ft-03.txt> (A Fast-Track way to RFC with Running Code) to Experimental RFC
References: <20130114203252.E331A1A455@ld9781.wdf.sap.corp>
In-Reply-To: <20130114203252.E331A1A455@ld9781.wdf.sap.corp>
X-Enigmail-Version: 1.5
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: John Leslie <john@jlc.net>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Jan 2013 22:15:15 -0000

Hi Martin,

On 01/14/2013 08:32 PM, Martin Rex wrote:
> John Leslie wrote:
>>
>>    I'm pretty darn uncomfortable _ever_ picking a fight with any
>> sitting AD, But I feel obligated to say this seems like a terrible
>> idea to me.
>>
>>    As a background, I'm a long-time believer in "rough consensus" for
>> Proposed Standard and "running code" for advancement along the
>> standards track. I do not believe the two mix well.
> 
> I don't have the resource to participate the discussion, but
> these statements capture my opinion pretty well.
> 
> I also believe that the existence of "running code" would be a terrible
> excuse for not resolving technical objections. 

I agree.

> While implementing a spec can help finding inconsitencies and ambiguities
> in a spec, 

Still agree.

> infering the reverse when the implementation is *NOT*
> created as a by-product of a formal correctness proofing tool for the
> spec does not hold.

Formal correctness proofs aren't really an IETF thing, so I'm lost.
(I.e. I've no idea what you mean that's relevant to this draft.)

> Weird implementations that are incompliant with a spec, or that ignore
> rather than recognize and report defects in a spec are extremely common.

Still lost.

> And if the sequence of events is, that an implementation is created first,
> and then producing a spec describing the alleged implementation behaviour,
> is going to result in lots of surprises about the frequent lack of
> correctness of both, the spec and the implementation it is based upon.

You're saying that this experiment will lead to RFCs that are
actually reverse engineered code being produced by IETF WGs?

Really? It seems to me you're forgetting the entire process of
chartering a WG and doing all the other work that precedes IETF
LC.

S.

> 
> 
> -Martin
> 

From shanna@juniper.net  Mon Jan 14 14:19:00 2013
Return-Path: <shanna@juniper.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 490B921F8B47; Mon, 14 Jan 2013 14:19:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.467
X-Spam-Level: 
X-Spam-Status: No, score=-103.467 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, UNRESOLVED_TEMPLATE=3.132, USER_IN_WHITELIST=-100]
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 1lv2jHYUTg6q; Mon, 14 Jan 2013 14:18:59 -0800 (PST)
Received: from exprod7og126.obsmtp.com (exprod7og126.obsmtp.com [64.18.2.206]) by ietfa.amsl.com (Postfix) with ESMTP id B8F2721F84BC; Mon, 14 Jan 2013 14:18:57 -0800 (PST)
Received: from P-EMHUB02-HQ.jnpr.net ([66.129.224.36]) (using TLSv1) by exprod7ob126.postini.com ([64.18.6.12]) with SMTP ID DSNKUPSETDx/Xh4zV2B62sLV74McbkbAQXho@postini.com; Mon, 14 Jan 2013 14:18:57 PST
Received: from P-CLDFE01-HQ.jnpr.net (172.24.192.59) by P-EMHUB02-HQ.jnpr.net (172.24.192.36) with Microsoft SMTP Server (TLS) id 8.3.213.0; Mon, 14 Jan 2013 14:18:05 -0800
Received: from o365mail.juniper.net (207.17.137.224) by o365mail.juniper.net (172.24.192.59) with Microsoft SMTP Server id 14.1.355.2; Mon, 14 Jan 2013 14:18:05 -0800
Received: from db3outboundpool.messaging.microsoft.com (213.199.154.144) by o365mail.juniper.net (207.17.137.224) with Microsoft SMTP Server (TLS) id 14.1.355.2; Mon, 14 Jan 2013 14:26:12 -0800
Received: from mail111-db3-R.bigfish.com (10.3.81.229) by DB3EHSOBE002.bigfish.com (10.3.84.22) with Microsoft SMTP Server id 14.1.225.23; Mon, 14 Jan 2013 22:18:00 +0000
Received: from mail111-db3 (localhost [127.0.0.1])	by mail111-db3-R.bigfish.com (Postfix) with ESMTP id 3CB9540092; Mon, 14 Jan 2013 22:18:00 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.234.117; KIP:(null); UIP:(null); (null); H:SN2PRD0510HT004.namprd05.prod.outlook.com; R:internal; EFV:INT
X-SpamScore: -26
X-BigFish: PS-26(zz98dI9371I936eI542I1432I4015Izz1ee6h1de0h1202h1e76h1d1ah1d2ahzz1033IL8275dhz2dh2a8h668h839h944hd25hf0ah1220h1288h12a5h12a9h12bdh137ah13b6h1441h1504h1537h153bh15d0h162dh1631h1758h1155h)
Received: from mail111-db3 (localhost.localdomain [127.0.0.1]) by mail111-db3 (MessageSwitch) id 135820187838073_26643; Mon, 14 Jan 2013 22:17:58 +0000 (UTC)
Received: from DB3EHSMHS013.bigfish.com (unknown [10.3.81.248])	by mail111-db3.bigfish.com (Postfix) with ESMTP id 0626318087C; Mon, 14 Jan 2013 22:17:58 +0000 (UTC)
Received: from SN2PRD0510HT004.namprd05.prod.outlook.com (157.56.234.117) by DB3EHSMHS013.bigfish.com (10.3.87.113) with Microsoft SMTP Server (TLS) id 14.1.225.23; Mon, 14 Jan 2013 22:17:57 +0000
Received: from SN2PRD0510MB372.namprd05.prod.outlook.com ([169.254.9.200]) by SN2PRD0510HT004.namprd05.prod.outlook.com ([10.255.116.39]) with mapi id 14.16.0257.004; Mon, 14 Jan 2013 22:17:57 +0000
From: Stephen Hanna <shanna@juniper.net>
To: SM <sm@resistor.net>, "Nancy Cam-Winget (ncamwing)" <ncamwing@cisco.com>
Subject: RE: Last Call: <draft-ietf-nea-pt-eap-06.txt> (PT-EAP: Posture Transport (PT) Protocol For EAP Tunnel Methods) to Proposed Standard
Thread-Topic: Last Call: <draft-ietf-nea-pt-eap-06.txt> (PT-EAP: Posture Transport (PT) Protocol For EAP Tunnel Methods) to Proposed Standard
Thread-Index: AQHN8qFy2guu4upU5k6s0KIIdnd2+phJYd4g
Date: Mon, 14 Jan 2013 22:17:57 +0000
Message-ID: <F1DFC16DCAA7D3468651A5A776D5796E069A3D59@SN2PRD0510MB372.namprd05.prod.outlook.com>
References: <6.2.5.6.2.20130108225436.0b31f008@resistor.net> <B80278DF1B7C814184086F4A6ECB3115225B9B21@xmb-aln-x02.cisco.com> <6.2.5.6.2.20130114123552.0a8fb9e8@resistor.net>
In-Reply-To: <6.2.5.6.2.20130114123552.0a8fb9e8@resistor.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [66.129.232.2]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-FOPE-CONNECTOR: Id%0$Dn%*$RO%0$TLS%0$FQDN%$TlsDn%
X-FOPE-CONNECTOR: Id%12219$Dn%RESISTOR.NET$RO%2$TLS%5$FQDN%onpremiseedge-1018244.customer.frontbridge.com$TlsDn%o365mail.juniper.net
X-FOPE-CONNECTOR: Id%12219$Dn%CISCO.COM$RO%2$TLS%5$FQDN%onpremiseedge-1018244.customer.frontbridge.com$TlsDn%o365mail.juniper.net
X-FOPE-CONNECTOR: Id%12219$Dn%IETF.ORG$RO%2$TLS%5$FQDN%onpremiseedge-1018244.customer.frontbridge.com$TlsDn%o365mail.juniper.net
Cc: "ietf-privacy@ietf.org" <ietf-privacy@ietf.org>, "nea@ietf.org" <nea@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Jan 2013 22:19:00 -0000

Changing our reference to RFC 5209 to be normative may cause
more problems than it solves. As RFC 3967 (BCP 97) says,

> IETF procedures generally require that a standards track RFC
> may not have a normative reference to another standards track
> document at a lower maturity level or to a non standards track
> specification (other than specifications from other standards
> bodies). For example, a standards track document may not have
> a normative reference to an informational RFC.

Generally, documents that contain use cases or architectures are
Informational. References to such documents in a standards track
document are informative because referring to the use cases is
not required in order to implement the standard.

RFC 5209 lists use cases for NEA, describes a reference model
for NEA, and includes requirements that the NEA protocols must
meet. None of the requirements in RFC 5209 are requirements on
implementations of the NEA protocols. Therefore, the PT-EAP spec
should not include a normative reference to RFC 5209. And that's
good, because RFC 5209 is an Informational RFC.

If I've missed something (e.g. a reason why the reference should
be normative), please explain it more clearly.

Thanks,

Steve

> -----Original Message-----
> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of
> SM
> Sent: Monday, January 14, 2013 4:34 PM
> To: Nancy Cam-Winget (ncamwing)
> Cc: ietf-privacy@ietf.org; nea@ietf.org; ietf@ietf.org
> Subject: Re: Last Call: <draft-ietf-nea-pt-eap-06.txt> (PT-EAP: Posture
> Transport (PT) Protocol For EAP Tunnel Methods) to Proposed Standard
>=20
> Hi Nancy,
> At 12:29 14-01-2013, Nancy Cam-Winget (ncamwing) wrote:
> >[NCW] I can change it to a lower case "must", ok?
>=20
> That's ok.
>=20
> >[NCW] We can move the reference to be normative.
>=20
> Ok.
>=20
> >[NCW] I don't think there are specifically for PT-EAP.  The sections
> you
> >reference
> >Were to (in section 6) addressing the general EAP identity as PT-EAP
> is
> >really not
> >An "authentication" method.
>=20
> If I understood the above correctly PT-EAP does not transport any
> information which could be used to identify an individual.  That's
> different from PT-EAP not being an "authenticated" method. Therefore,
> there isn't much to say in terms of privacy considerations.
>=20
> I suggest not including the following then:
>=20
>    "As a transport protocol, PT-EAP does not directly utilize or
>     require direct knowledge of any personally identifiable
>     information (PII)."
>=20
> The draft can leverage the second paragraph of Section 6 as "privacy
> considerations" instead of making a statement about PII.  I'll copy
> this message to ietf-privacy@ to get a better opinion.
>=20
> In Section 6:
>=20
>    "Therefore, it is important for deployers to leverage these
>     protections in order to prevent disclosure of PII potentially
>     contained within PA-TNC or PB-TNC within the PT-EAP payload."
>=20
> I suggest "information about an individual" instead of PII [1].
>=20
> Regards,
> -sm
>=20
> 1. I used the wording from draft-iab-privacy-considerations-06
>=20



From ogud@ogud.com  Mon Jan 14 14:29:12 2013
Return-Path: <ogud@ogud.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9FB5021F8A08 for <ietf@ietfa.amsl.com>; Mon, 14 Jan 2013 14:29:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.599
X-Spam-Level: 
X-Spam-Status: No, score=-103.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
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 OmlMi27idE+g for <ietf@ietfa.amsl.com>; Mon, 14 Jan 2013 14:29:12 -0800 (PST)
Received: from smtp197.iad.emailsrvr.com (smtp197.iad.emailsrvr.com [207.97.245.197]) by ietfa.amsl.com (Postfix) with ESMTP id F0BBE21F8AA6 for <ietf@ietf.org>; Mon, 14 Jan 2013 14:29:11 -0800 (PST)
Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp39.relay.iad1a.emailsrvr.com (SMTP Server) with ESMTP id 36AE7982BE; Mon, 14 Jan 2013 17:29:11 -0500 (EST)
X-Virus-Scanned: OK
Received: by smtp39.relay.iad1a.emailsrvr.com (Authenticated sender: ogud-AT-ogud.com) with ESMTPSA id 09CE4981C9;  Mon, 14 Jan 2013 17:29:09 -0500 (EST)
Message-ID: <50F486B4.6090407@ogud.com>
Date: Mon, 14 Jan 2013 17:29:08 -0500
From: Olafur Gudmundsson <ogud@ogud.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130107 Thunderbird/17.0.2
MIME-Version: 1.0
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Subject: Re: Last Call: <draft-farrell-ft-03.txt> (A Fast-Track way to RFC with Running Code) to Experimental RFC
References: <20130111151453.22161.50884.idtracker@ietfa.amsl.com> <50F434BA.6000108@ogud.com> <50F44821.3030802@cs.tcd.ie>
In-Reply-To: <50F44821.3030802@cs.tcd.ie>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org, The IESG <iesg@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Jan 2013 22:29:12 -0000

Hi Stephen,

On 14/01/2013 13:02, Stephen Farrell wrote:
> Hi Olafur,
>
> On 01/14/2013 04:39 PM, Olafur Gudmundsson wrote:
>>
>> I have experience in process like this, as my WG DNSEXT has required
>> multiple implementations and inter-op testing before advancing before
>> advancing documents that make significant changes to the DNS protocol.
>> Having done this I'm confident that the resulting specifications and
>> code was much better.
>>
>> I support this experiment but offer the following comments.
> Phew, so I'm not entirely crazy, good to know:-)

>> Comment #1: The important part of running code is to assess
>> clarity of the specification, thus implementation by editors of the
>> document should not count as one-of-two required implementations
>> Implementations by editors co-workers are ok IFF the the editors keep
>> track of communications that lead to changes in code or draft.
> First this draft only requires one implementation and not two as
> your WG did. Second, I don't know what you mean by "keep track
> of communications" - can you explain? (Or send a pointer to
> one you used in the WG?)

If you only require one then it OUGHT to be by someone other than the 
editors to count, otherwise it is just a proof of concept and we have 
limited confidence  that spec and code match up.

Well this can be done in number of ways,
- Issues tracker
- Postings to WG mailing list
- Notes in Appendix,

In our case we used the second one.

> That's also sort of like the point Stefan W. raised. And he
> suggested:
>
>           "If the source code has been developed
>           independently of the authoring of the draft (and ideally by non
>           WG participants), it is likely that the implementation and the
>           draft match, and that pitfalls unaware developers may find have
>           been found and dealt with.  If, on the other hand, draft
>           author(s) and implementation developer(s) overlap, then it is
>           sensible to scrutinize the draft more closely, both with
>           respect to its match with the implementation and for
>           assumptions that author/developer may have taken for granted
>           which warrant documentation in the draft."
>
> Are you saying something like that would help?
I agree with Stefan W.  but would make it stronger that implementation by
editors does not count except for interoperability testing.

> Personally, I think there are thousands of nuggets of advice
> that we could possibly add, but I'm not convinced that we
> should - I think we'd be better off trying to keep this draft
> shorter and simpler and then if the experiment succeeds we can
> incorporate those things that experience has shown are worth
> including.
I agree, thus I suppressed lots of comments/suggestions

>> Comment #2: It is important that participants all realize that point of
>> the exercise is not to point figurers at bugs. Rather the goal is to
>> improve the specifications and make ALL the implementations as compliant
>> and bug free as possible.
> Agreed. Not sure what text would change though.
>
> Same comment about "nuggets" as above:-)
I was hoping we could work this into paragraph #3 of introduction section.
I will think about text changes and send you off-line.

>> Comment #3 (Section 4 point #6)
>> Test cases used for interoperability are critical. These test
>> cases MUST be public. Evaluations of test cases generated by the
>> implementors and/or other working group participants are critical as
>> that is a great indicator of the quality and thoroughness of the tests.
>> IMHO public test cases render the point of open vs. closed source
>> irrelevant.
> I think that's arguable, but a reasonable argument. Again though,
> I don't think we're at the point where a MUST ought go into this
> draft and that'd be better done when the experiment's done.
>
> Or do you have a suggestion for text? (I'm not at all sure how
> I'd write that up now.)
I will take a stab at re-write second paragraph of section 2.1 to 
reflect this but that might take a day or two.

>> Comment #4: The IETF-LC and WGLC statements SHOULD contain references to
>> the testing performed and the implementations that participated.
> I could buy that as a SHOULD or "ought." I've noted that
> in the working version as a change to maybe make. [1]

good.

     Olafur


From stephen.farrell@cs.tcd.ie  Mon Jan 14 14:38:49 2013
Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ECD3A21F8A06; Mon, 14 Jan 2013 14:38:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 jB27u0CMTPrL; Mon, 14 Jan 2013 14:38:49 -0800 (PST)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) by ietfa.amsl.com (Postfix) with ESMTP id 5CB4621F89E5; Mon, 14 Jan 2013 14:38:49 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id 7CF0CBE4C; Mon, 14 Jan 2013 22:38:27 +0000 (GMT)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id N9wqdrBj7fFP; Mon, 14 Jan 2013 22:38:26 +0000 (GMT)
Received: from [10.87.48.11] (unknown [86.41.50.151]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 86F23BE47; Mon, 14 Jan 2013 22:38:26 +0000 (GMT)
Message-ID: <50F488E2.9080505@cs.tcd.ie>
Date: Mon, 14 Jan 2013 22:38:26 +0000
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130106 Thunderbird/17.0.2
MIME-Version: 1.0
To: Olafur Gudmundsson <ogud@ogud.com>
Subject: Re: Last Call: <draft-farrell-ft-03.txt> (A Fast-Track way to RFC with Running Code) to Experimental RFC
References: <20130111151453.22161.50884.idtracker@ietfa.amsl.com> <50F434BA.6000108@ogud.com> <50F44821.3030802@cs.tcd.ie> <50F486B4.6090407@ogud.com>
In-Reply-To: <50F486B4.6090407@ogud.com>
X-Enigmail-Version: 1.5
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org, The IESG <iesg@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Jan 2013 22:38:50 -0000

Hi Olafur,

Thanks for the offer of text. Looking forward to getting that.
Just on this one though...

On 01/14/2013 10:29 PM, Olafur Gudmundsson wrote:
>> That's also sort of like the point Stefan W. raised. And he
>> suggested:
>>
>>           "If the source code has been developed
>>           independently of the authoring of the draft (and ideally by non
>>           WG participants), it is likely that the implementation and the
>>           draft match, and that pitfalls unaware developers may find have
>>           been found and dealt with.  If, on the other hand, draft
>>           author(s) and implementation developer(s) overlap, then it is
>>           sensible to scrutinize the draft more closely, both with
>>           respect to its match with the implementation and for
>>           assumptions that author/developer may have taken for granted
>>           which warrant documentation in the draft."
>>
>> Are you saying something like that would help?
> I agree with Stefan W.  but would make it stronger that implementation by
> editors does not count except for interoperability testing.

Stephan W. also suggested that at first.

My concern is that this is too onerous during a 12 month experiment.
If we constrain it too much, then nobody will try it.

It could be that such constraints may be reasonable after a successful
experiment but I'm really wary of killing this before it starts
with too many pieces of well-meant advice or too many reasonable
sounding rules.

I'd have no problem adding an appendix with such ideas or putting
'em on the wiki page for the experiment though if that'd work.

Cheers,
S.



From mrex@sap.com  Mon Jan 14 18:10:40 2013
Return-Path: <mrex@sap.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 04ECB11E809B for <ietf@ietfa.amsl.com>; Mon, 14 Jan 2013 18:10:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.187
X-Spam-Level: 
X-Spam-Status: No, score=-10.187 tagged_above=-999 required=5 tests=[AWL=0.062, BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_HI=-8]
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 5KqnIMcyBAJq for <ietf@ietfa.amsl.com>; Mon, 14 Jan 2013 18:10:39 -0800 (PST)
Received: from smtpde02.sap-ag.de (smtpde02.sap-ag.de [155.56.68.140]) by ietfa.amsl.com (Postfix) with ESMTP id 4778711E809A for <ietf@ietf.org>; Mon, 14 Jan 2013 18:10:39 -0800 (PST)
Received: from mail05.wdf.sap.corp by smtpde02.sap-ag.de (26) with ESMTP id r0F2AWe6011672 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 15 Jan 2013 03:10:32 +0100 (MET)
Subject: Re: Last Call: <draft-farrell-ft-03.txt> (A Fast-Track way to RFC with Running Code) to Experimental RFC
In-Reply-To: <20130114185239.GA41685@verdi>
To: John Leslie <john@jlc.net>
Date: Tue, 15 Jan 2013 03:10:31 +0100 (CET)
X-Mailer: ELM [version 2.4ME+ PL125 (25)]
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="US-ASCII"
Message-Id: <20130115021032.00A0D1A454@ld9781.wdf.sap.corp>
From: mrex@sap.com (Martin Rex)
X-SAP: out
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: mrex@sap.com
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Jan 2013 02:10:40 -0000

John Leslie wrote:
> 
> >... 
> > But more to the point, I think that in a lot of cases where
> > the IETF has done a good job, there has been running code
> > before the WG even started...
> 
>    This perhaps explains where Stephen is coming from. Such
> cases do exist; and it is arguable that the process Stephen has
> describe in this draft are well-suited to such cases (though I
> would still have to quibble about some details).
> 
>    I remain unconvinced, however, that fast-tracking the cases
> that start from running code is a good use of WG efforts. Such
> cases seem better suited to Independent Submissions from a
> design team (which would _greatly_ speed the process). When
> a WG is formed, IMHO, they should be encouraged to look at the
> problem from some quite different angles, in search of a way
> to "Simplify!".

I also believe that being more honest about something that is
more a design team effort than the result of more traditional
WG work should probably carry through that notion of an
Independent Submission, and, when being fast-tracked, that it
is essentially a request for rubber-stamping.


-Martin

From dean.willis@softarmor.com  Mon Jan 14 22:16:19 2013
Return-Path: <dean.willis@softarmor.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EA63321F8B67 for <ietf@ietfa.amsl.com>; Mon, 14 Jan 2013 22:16:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.599
X-Spam-Level: 
X-Spam-Status: No, score=-103.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
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 8E4MUmsXzllw for <ietf@ietfa.amsl.com>; Mon, 14 Jan 2013 22:16:19 -0800 (PST)
Received: from mail-ob0-f170.google.com (mail-ob0-f170.google.com [209.85.214.170]) by ietfa.amsl.com (Postfix) with ESMTP id 22ABC21F8717 for <ietf@ietf.org>; Mon, 14 Jan 2013 22:16:18 -0800 (PST)
Received: by mail-ob0-f170.google.com with SMTP id wp18so4742117obc.15 for <ietf@ietf.org>; Mon, 14 Jan 2013 22:16:15 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=softarmor.com; s=google; h=x-received:content-type:mime-version:subject:from:in-reply-to:date :cc:content-transfer-encoding:message-id:references:to:x-mailer; bh=WLK2oar8ucwUUSkXCRHjm0752ixQerYwUBEzkjVaQug=; b=W8xw5uaP7IDSdoq5ItRS6JxEruy2jxTtPFxpXtckBfofh5BR/A6qYHo9K5TSfJl0j7 +CCdHaALexZIBjcG3Oj/FaEUVIbMZMwG+mz7Sr9ZPgPth5yNr1OYsITG7W6jEsfIiO57 mwuwCT5YGByuxw02c27MVjgmSr7gYfg45IhFw=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:content-type:mime-version:subject:from:in-reply-to:date :cc:content-transfer-encoding:message-id:references:to:x-mailer :x-gm-message-state; bh=WLK2oar8ucwUUSkXCRHjm0752ixQerYwUBEzkjVaQug=; b=Hx1gQc5/BkTGXYm6NBEjGfHA0hDE3KFCzM3DnKDuvD4eUn9iEKlMit3pYMXmt2lf4V rkDPTCaI8abAjviXwffy+G4+7usdZvAJG1Y2Jdg7dlv2ldogduya7MPz7mXDl1wHDbH+ 11tX3Ol/J476I8W48bbBmc8tbhWySk6dNm2PbR9Gm1Ys9Kum3C0DhLuVFKg9BDIYA//B JPvnK9p550xvqFaW/PNqWx/TpVPoGMdnjEymM+zPHjTXM/IO2uySz71+uCrZOvKlp3ss h8cFh4kKHv7u8gAFnj5/7TB+Yog1HAFJynyFPSNJaw6n7mNCGu0Qz3PsbptsUJKkKwp2 IyIQ==
X-Received: by 10.60.32.199 with SMTP id l7mr52077334oei.76.1358230575788; Mon, 14 Jan 2013 22:16:15 -0800 (PST)
Received: from [192.168.2.115] (cpe-72-181-157-19.tx.res.rr.com. [72.181.157.19]) by mx.google.com with ESMTPS id zn9sm12461780obb.23.2013.01.14.22.16.14 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 14 Jan 2013 22:16:15 -0800 (PST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Subject: Re: Making RFC2119 key language easier to Protocol Readers
From: Dean Willis <dean.willis@softarmor.com>
In-Reply-To: <alpine.DEB.2.00.1301051010080.26235@uplift.swm.pp.se>
Date: Tue, 15 Jan 2013 00:16:14 -0600
Content-Transfer-Encoding: quoted-printable
Message-Id: <119BCE53-84DD-41F7-813C-B0644B4C82F9@softarmor.com>
References: <CADnDZ8-yCxUbrD9oFyQKkJuTgDZbamnV8K4GU+sAN5SekpyHAA@mail.gmail.com> <CADnDZ88XgyNXiu1fdK3WB7jrZTmfuvAc5U1XyAxjprZf6=7P4Q@mail.gmail.com> <CADnDZ8_pd5ZrnucZAoK5WDXUgK9gQhHm+GJe7PihDQzx1uUsaw@mail.gmail.com> <alpine.DEB.2.00.1301051010080.26235@uplift.swm.pp.se>
To: Mikael Abrahamsson <swmike@swm.pp.se>
X-Mailer: Apple Mail (2.1499)
X-Gm-Message-State: ALoCoQmoBwVGHwj9sBjXPkjVR/IqjQt1Ya623b8L6vhxMKxyVBIRXABuagHU8rXBhuM9oH4AL2mh
Cc: ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Jan 2013 06:16:20 -0000

On Jan 5, 2013, at 3:13 AM, Mikael Abrahamsson <swmike@swm.pp.se> wrote:

> On Sat, 5 Jan 2013, Abdussalam Baryun wrote:
>=20
>> Hi Mikael
>>=20
>>> Also what it means following things in it that is not RFC2119 =
language.
>>=20
>> It will mean, you should understand me/english/ietf/procedure even if
>> I don't have to explain, and you need to understand English well even
>> if you are a great implementor or great programming language speaker.
>=20
> The problem here is that I want them to pay back some of the money (or =
take back the equipment totally and give back all money) for breach of =
contract, when I discover that they haven't correctly (as in intention =
and interop) implemented the RFC they said they said they were compliant =
in supporting.
>=20
> Ianal, but it feels that it should easier to do this if there are MUST =
and SHOULD in there and I asked them to document all deviations from =
these.
>=20

What about when the MUST and SHOULD are in the context of "Alice MUST =
send a request message to Bob" and you don't have users named Alice or =
Bob?

Seriously -- at what point does replacing all action verbs with 2119 =
language make the protocol spec LESS useful for compliance =
certification?

--
Dean


From dean.willis@softarmor.com  Mon Jan 14 22:19:27 2013
Return-Path: <dean.willis@softarmor.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8414D21F8906 for <ietf@ietfa.amsl.com>; Mon, 14 Jan 2013 22:19:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.599
X-Spam-Level: 
X-Spam-Status: No, score=-103.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
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 drxJzS6ljT1c for <ietf@ietfa.amsl.com>; Mon, 14 Jan 2013 22:19:26 -0800 (PST)
Received: from mail-oa0-f41.google.com (mail-oa0-f41.google.com [209.85.219.41]) by ietfa.amsl.com (Postfix) with ESMTP id 9B61921F88C4 for <ietf@ietf.org>; Mon, 14 Jan 2013 22:19:26 -0800 (PST)
Received: by mail-oa0-f41.google.com with SMTP id k14so4928345oag.0 for <ietf@ietf.org>; Mon, 14 Jan 2013 22:19:25 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=softarmor.com; s=google; h=x-received:content-type:mime-version:subject:from:in-reply-to:date :cc:content-transfer-encoding:message-id:references:to:x-mailer; bh=fM+hsiQ1RxjxVmyOYFbruAYpokAmi3GSOQDEZo0caOM=; b=c/PrA+iYZkwr8jpzlD5w0Jal+cpjNS6XC7UEt4Z8y9ZTdQE2ll9WtanvUeiWZ1R2ED dV3mRYBgmeU/PRrtcdQYIf7+lJoMZkqyftZu+zL04slY5xP79zGnnoW3jrZai25uXnDF 6X8Ty5E2XGKvfasZvotq+brPIgAh27kyWdApc=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:content-type:mime-version:subject:from:in-reply-to:date :cc:content-transfer-encoding:message-id:references:to:x-mailer :x-gm-message-state; bh=fM+hsiQ1RxjxVmyOYFbruAYpokAmi3GSOQDEZo0caOM=; b=HydmDcUQ357KKrN9AdiijEoHZS3XjcGz1FC6GJtgw5qMzjWIK4PdCwfWBW4co2HBTU y5xeIoK7/4jIxFpt/VXI9mn2/zIOxhJIyZk2iW5kCbW882rorXRrAnkwWVUaIAYSlgp3 oCbDCbsFpcZvN+qh6iPOKNSyUHZukfRyKZWgJ+DLtwPuflqLbNOBOioD6yeNp1ZoI2Dc O8WLAZgHklemgmV9miyzpHasawuxvuzuWicpT1/7jQHBIAzIXsbOpX1hqvsC5Ju48wiE E17sHQPj5jmBFlgEourRlxhpZummKNgkEcM62BB5+YinwSrO3laikP9DY24OieFSHtnz rITg==
X-Received: by 10.182.48.33 with SMTP id i1mr8968430obn.49.1358230765647; Mon, 14 Jan 2013 22:19:25 -0800 (PST)
Received: from [192.168.2.115] (cpe-72-181-157-19.tx.res.rr.com. [72.181.157.19]) by mx.google.com with ESMTPS id rn9sm7761414obb.11.2013.01.14.22.19.24 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 14 Jan 2013 22:19:25 -0800 (PST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Subject: Re: Making RFC2119 key language easier to Protocol Readers
From: Dean Willis <dean.willis@softarmor.com>
In-Reply-To: <1D12E3A12F3C30D3066A13E6@JcK-HP8200.jck.com>
Date: Tue, 15 Jan 2013 00:19:23 -0600
Content-Transfer-Encoding: quoted-printable
Message-Id: <C381A966-AC3A-4209-8834-F20A59D80012@softarmor.com>
References: <CADnDZ8-yCxUbrD9oFyQKkJuTgDZbamnV8K4GU+sAN5SekpyHAA@mail.gmail.com> <CADnDZ88XgyNXiu1fdK3WB7jrZTmfuvAc5U1XyAxjprZf6=7P4Q@mail.gmail.com> <CADnDZ8_pd5ZrnucZAoK5WDXUgK9gQhHm+GJe7PihDQzx1uUsaw@mail.gmail.com> <alpine.DEB.2.00.1301051010080.26235@uplift.swm.pp.se> <1D12E3A12F3C30D3066A13E6@JcK-HP8200.jck.com>
To: John C Klensin <john-ietf@jck.com>
X-Mailer: Apple Mail (2.1499)
X-Gm-Message-State: ALoCoQlHWlkdX8AfxB7b19GODAC9t68Tr32K+HczGu+mkHsODheRbJjvbBERX8Y9v9Ryj5cuCQSm
Cc: ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Jan 2013 06:19:27 -0000

On Jan 5, 2013, at 10:03 AM, John C Klensin <john-ietf@jck.com> wrote:

> And, again, that is further complicated by the observation that
> IETF Standards are used for procurement and even for litigation
> about product quality.   We either need to accept that fact and,
> where necessary, adjust our specification style to match or we
> run the risk of bodies springing up who will profile our
> Standards, write procurement-quality conformance statements for
> their profiles, and become, de facto, the real standards-setter
> for the marketplace (and obviously do so without any element of
> IETF consensus). =20

I'm not sure that's not a good thing. Witness for example the work SIP =
Forum has done with the SIPConnect standards, which have made it MUCH =
easier to order a box that will work with a SIP Trunking service.

--
Dean



From brian.e.carpenter@gmail.com  Tue Jan 15 00:02:03 2013
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 391D521F8AA6 for <ietf@ietfa.amsl.com>; Tue, 15 Jan 2013 00:02:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.447
X-Spam-Level: 
X-Spam-Status: No, score=-101.447 tagged_above=-999 required=5 tests=[AWL=0.244, BAYES_00=-2.599, RCVD_ILLEGAL_IP=1.908, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
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 S0JuS4ms0wkO for <ietf@ietfa.amsl.com>; Tue, 15 Jan 2013 00:02:02 -0800 (PST)
Received: from mail-wi0-f175.google.com (mail-wi0-f175.google.com [209.85.212.175]) by ietfa.amsl.com (Postfix) with ESMTP id 7B09421F8A1E for <ietf@ietf.org>; Tue, 15 Jan 2013 00:02:02 -0800 (PST)
Received: by mail-wi0-f175.google.com with SMTP id hm11so2003992wib.14 for <ietf@ietf.org>; Tue, 15 Jan 2013 00:02:01 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:organization:user-agent :mime-version:to:cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=VphZ7IoNol/hbXlc5xym1P8ZAQAK722R2JUJJyyO4GA=; b=AhXZQKIP79nKqxHJQ0A24QcIq1lK34fVs/Hj+SKSymbLKeRe4fK2BwqzYRnqYowCCo aJTwYY4xodQRbQkT2gGCSERsVVabD2V2aW3LQFNucSrRz3Q/eFr08zw2Jb95sMfbAdvO GV8xdMSG0K1m93S8sn0Ti3RVThEBmXnQ4rrVX6GmtAn2jqSo3oKpQwbYTP4eqvdQLP9R saugfmTAURG2cI+KciIP47kOxMJ1qJM72TEC52Yf7LftUWr+ClhaR3LhQTHEm7d5fR16 vxQ8GiCuxRVDR+D8LCMRiOQIxK5ib3dGSh2Kk1raPqvCtF9lzkTfc2rUW/Z47TxLYe4U SaTg==
X-Received: by 10.180.107.129 with SMTP id hc1mr1823156wib.34.1358236921642; Tue, 15 Jan 2013 00:02:01 -0800 (PST)
Received: from [192.168.1.65] (host-2-102-216-126.as13285.net. [2.102.216.126]) by mx.google.com with ESMTPS id h19sm2290471wiv.7.2013.01.15.00.02.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 15 Jan 2013 00:02:01 -0800 (PST)
Message-ID: <50F50CF9.9010703@gmail.com>
Date: Tue, 15 Jan 2013 08:02:01 +0000
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Dean Willis <dean.willis@softarmor.com>
Subject: Re: Making RFC2119 key language easier to Protocol Readers
References: <CADnDZ8-yCxUbrD9oFyQKkJuTgDZbamnV8K4GU+sAN5SekpyHAA@mail.gmail.com>	<CADnDZ88XgyNXiu1fdK3WB7jrZTmfuvAc5U1XyAxjprZf6=7P4Q@mail.gmail.com>	<CADnDZ8_pd5ZrnucZAoK5WDXUgK9gQhHm+GJe7PihDQzx1uUsaw@mail.gmail.com>	<alpine.DEB.2.00.1301051010080.26235@uplift.swm.pp.se> <119BCE53-84DD-41F7-813C-B0644B4C82F9@softarmor.com>
In-Reply-To: <119BCE53-84DD-41F7-813C-B0644B4C82F9@softarmor.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Jan 2013 08:02:03 -0000

On 15/01/2013 06:16, Dean Willis wrote:
...
> Seriously -- at what point does replacing all action verbs with 2119 language make the protocol spec LESS useful for compliance certification?

Wrong question. What we (the IETF) care about is the existence of interoperable
implementations, not mathematical compliance.

If you ask "at what point does replacing all action verbs with 2119 language make
the protocol spec LESS useful for coding interoperable versions?", I think
the answer will be something like "when it makes the spec so ugly and
difficult to read that people get things wrong as a result."

On 15/01/2013 06:19, Dean Willis wrote:
> On Jan 5, 2013, at 10:03 AM, John C Klensin <john-ietf@jck.com> wrote:
> 
>> > And, again, that is further complicated by the observation that
>> > IETF Standards are used for procurement and even for litigation
>> > about product quality.   We either need to accept that fact and,
>> > where necessary, adjust our specification style to match or we
>> > run the risk of bodies springing up who will profile our
>> > Standards, write procurement-quality conformance statements for
>> > their profiles, and become, de facto, the real standards-setter
>> > for the marketplace (and obviously do so without any element of
>> > IETF consensus).  
> 
> I'm not sure that's not a good thing. Witness for example the work SIP Forum has done with the SIPConnect standards, which have made it MUCH easier to order a box that will work with a SIP Trunking service.

I think there are cases of standards of extreme complexity, such as
SIP, where such profiles may be useful, because otherwise interoperability
cannot be achieved. But perhaps the lesson for the IETF here is slightly
different - don't design standards which allow that degree of complexity
in the first place.

    Brian

From stephen.farrell@cs.tcd.ie  Tue Jan 15 01:42:26 2013
Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6E7A121F8AD4 for <ietf@ietfa.amsl.com>; Tue, 15 Jan 2013 01:42:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.742
X-Spam-Level: 
X-Spam-Status: No, score=-102.742 tagged_above=-999 required=5 tests=[AWL=-0.142, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 hcXe3mgOwmvt for <ietf@ietfa.amsl.com>; Tue, 15 Jan 2013 01:42:25 -0800 (PST)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) by ietfa.amsl.com (Postfix) with ESMTP id 8F8DE21F8B11 for <ietf@ietf.org>; Tue, 15 Jan 2013 01:42:25 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id 8EF00BE3B; Tue, 15 Jan 2013 09:42:03 +0000 (GMT)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XV88y1Hwi3ha; Tue, 15 Jan 2013 09:42:02 +0000 (GMT)
Received: from [IPv6:2001:770:10:203:1d04:f17:b1f3:7a33] (unknown [IPv6:2001:770:10:203:1d04:f17:b1f3:7a33]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id A1D04BE32; Tue, 15 Jan 2013 09:42:02 +0000 (GMT)
Message-ID: <50F5246B.9040504@cs.tcd.ie>
Date: Tue, 15 Jan 2013 09:42:03 +0000
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130106 Thunderbird/17.0.2
MIME-Version: 1.0
To: mrex@sap.com
Subject: Re: Last Call: <draft-farrell-ft-03.txt> (A Fast-Track way to RFC with Running Code) to Experimental RFC
References: <20130115021032.00A0D1A454@ld9781.wdf.sap.corp>
In-Reply-To: <20130115021032.00A0D1A454@ld9781.wdf.sap.corp>
X-Enigmail-Version: 1.5
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: John Leslie <john@jlc.net>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Jan 2013 09:42:26 -0000

Martin,

On 01/15/2013 02:10 AM, Martin Rex wrote:
> John Leslie wrote:
>>
>>> ... 
>>> But more to the point, I think that in a lot of cases where
>>> the IETF has done a good job, there has been running code
>>> before the WG even started...
>>
>>    This perhaps explains where Stephen is coming from. Such
>> cases do exist; and it is arguable that the process Stephen has
>> describe in this draft are well-suited to such cases (though I
>> would still have to quibble about some details).
>>
>>    I remain unconvinced, however, that fast-tracking the cases
>> that start from running code is a good use of WG efforts. Such
>> cases seem better suited to Independent Submissions from a
>> design team (which would _greatly_ speed the process). When
>> a WG is formed, IMHO, they should be encouraged to look at the
>> problem from some quite different angles, in search of a way
>> to "Simplify!".
> 
> I also believe that being more honest about something that is
> more a design team effort than the result of more traditional
> WG work should probably carry through that notion of an
> Independent Submission, and, when being fast-tracked, that it
> is essentially a request for rubber-stamping.

Oh come on. That seems like a fairly wild exaggeration. Please
explain how this experiment as documented in this draft could
lead to some new way to get things "rubber stamped."  If it did
have that effect then I'd be against it, but that just seems
like nonsense to be honest.

S.

> 
> 
> -Martin
> 

From brian.e.carpenter@gmail.com  Tue Jan 15 02:55:32 2013
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7DBA421F8584 for <ietf@ietfa.amsl.com>; Tue, 15 Jan 2013 02:55:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.246
X-Spam-Level: 
X-Spam-Status: No, score=-103.246 tagged_above=-999 required=5 tests=[AWL=0.353, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
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 kO8Y7eDRQ6M7 for <ietf@ietfa.amsl.com>; Tue, 15 Jan 2013 02:55:32 -0800 (PST)
Received: from mail-wi0-f177.google.com (mail-wi0-f177.google.com [209.85.212.177]) by ietfa.amsl.com (Postfix) with ESMTP id B5FF921F8578 for <ietf@ietf.org>; Tue, 15 Jan 2013 02:55:31 -0800 (PST)
Received: by mail-wi0-f177.google.com with SMTP id hm2so2154080wib.16 for <ietf@ietf.org>; Tue, 15 Jan 2013 02:55:31 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:organization:user-agent :mime-version:to:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=OsBDsKOda5+TDs1Ghixh5lYT3cbjzDHvS+3cViF0wk0=; b=SPJYFjuLKXxZGknckTA4dG05sgoC/hEwgeCl+kn32DQJlCZS6uzSsv/0G/xMetRVQ8 aHN0NjNWhqAqUVNDHoqldbbHwBj1k5w6ynhC8zXATLlv2JHes+aiBrtt9ekW4/f5w12X 6pJBTBjhjDTZkTCvb65ASAEHrPYsg4gN0WGbA/P8huL9bLfoAtmWm11ymVEGAyMiq85J WaYNJB/3GcCWyM6Nmw4k02cMXQpdMoLjJhY2Hi0OcGFfOv1Rti7v57UFL5BOON8UosOk 7O21hAvpcsSPdQUjQwvMIBjDzqIhQSCC4yF1UJl4omg/K5Loz8RWsAK2dCHKDeVx9rEz LxxQ==
X-Received: by 10.181.13.195 with SMTP id fa3mr2862333wid.8.1358247330894; Tue, 15 Jan 2013 02:55:30 -0800 (PST)
Received: from [128.232.110.102] (c102.al.cl.cam.ac.uk. [128.232.110.102]) by mx.google.com with ESMTPS id hg17sm2924967wib.1.2013.01.15.02.55.29 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 15 Jan 2013 02:55:30 -0800 (PST)
Message-ID: <50F535A7.1090506@gmail.com>
Date: Tue, 15 Jan 2013 10:55:35 +0000
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: IETF discussion list <ietf@ietf.org>
Subject: Re: Last Call: <draft-farrell-ft-03.txt> (A Fast-Track way to RFC with	Running Code) to Experimental RFC
References: <20130111151453.22161.50884.idtracker@ietfa.amsl.com>
In-Reply-To: <20130111151453.22161.50884.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Jan 2013 10:55:32 -0000

On balance I think this experiment is safe to carry out, and therefore
probably should be carried out. There are a few comments below.

However, I would urge the IESG to update the page at
http://www.ietf.org/iesg/process-experiment.html, including current
status of the experiments mentioned, and the history of concluded
experiments, which I'm pretty sure was there a few years ago.
At least, the history of the RFC 4693 experiment isn't there.

1. It seems clear that the explicit mention of GPLv3 should be removed.
It's contentious for a number of reasons. The phrase "e.g., under a Free
Software or Open Source license" seems necessary and sufficient.

2. There's a slight inconsistency between the mention of interoperablity
in a few places and the proposal to use *one* implementation as a
criterion. It doesn't seem unreasonable to use one implementation
as a criterion for PS, since a criterion for IS under RFC 6410 is
multiple interoperable implementations. But we should not imply that
one successful implementation implies anything at all about
interoperability. I think this needs to be stated quite explicitly:

Note that the existence of one implementation does not in any way
demonstrate the interoperability required for advancement on the
standards track [RFC6410].

3. However, I remember very bad experience some years ago with the
6NET project attempting to deploy Mobile IPv6 based on implementations
of several different versions of the main MIPv6 draft. They simply
could not interoperate. There is a risk that fast-tracking a draft could
actually be damaging in such a situation. I think we would need a clear
consensus that the draft is stable as well as viable. I suggest adding
an item in section 4 something like this:

The WG chairs and responsible AD must be satisfied that the draft is
in a stable state and that significant technical changes are unlikely
to be proposed in the near future.

Regards
   Brian


From petithug@acm.org  Tue Jan 15 03:21:32 2013
Return-Path: <petithug@acm.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A6C5B21F8800 for <ietf@ietfa.amsl.com>; Tue, 15 Jan 2013 03:21:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.495
X-Spam-Level: 
X-Spam-Status: No, score=-102.495 tagged_above=-999 required=5 tests=[AWL=0.105, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
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 PMad9sEyzAp4 for <ietf@ietfa.amsl.com>; Tue, 15 Jan 2013 03:21:32 -0800 (PST)
Received: from implementers.org (implementers.org [IPv6:2604:3400:dc1:41:216:3eff:fe5b:8240]) by ietfa.amsl.com (Postfix) with ESMTP id 7CEB521F87FF for <ietf@ietf.org>; Tue, 15 Jan 2013 03:21:31 -0800 (PST)
Received: from [IPv6:2601:9:4b80:32:b858:b5d1:71bb:65c] (unknown [IPv6:2601:9:4b80:32:b858:b5d1:71bb:65c]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (Client CN "Marc Petit-Huguenin", Issuer "implementers.org" (verified OK)) by implementers.org (Postfix) with ESMTPS id 9C60520373; Tue, 15 Jan 2013 11:21:29 +0000 (UTC)
Message-ID: <50F53BC5.3060901@acm.org>
Date: Tue, 15 Jan 2013 03:21:41 -0800
From: Marc Petit-Huguenin <petithug@acm.org>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.11) Gecko/20121122 Icedove/10.0.11
MIME-Version: 1.0
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: Making RFC2119 key language easier to Protocol Readers
References: <CADnDZ8-yCxUbrD9oFyQKkJuTgDZbamnV8K4GU+sAN5SekpyHAA@mail.gmail.com>	<CADnDZ88XgyNXiu1fdK3WB7jrZTmfuvAc5U1XyAxjprZf6=7P4Q@mail.gmail.com>	<CADnDZ8_pd5ZrnucZAoK5WDXUgK9gQhHm+GJe7PihDQzx1uUsaw@mail.gmail.com>	<alpine.DEB.2.00.1301051010080.26235@uplift.swm.pp.se> <119BCE53-84DD-41F7-813C-B0644B4C82F9@softarmor.com> <50F50CF9.9010703@gmail.com>
In-Reply-To: <50F50CF9.9010703@gmail.com>
X-Enigmail-Version: 1.4.1
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: ietf <ietf@ietf.org>, Dean Willis <dean.willis@softarmor.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Jan 2013 11:21:32 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On 01/15/2013 12:02 AM, Brian E Carpenter wrote:
> On 15/01/2013 06:16, Dean Willis wrote: ...
>> Seriously -- at what point does replacing all action verbs with 2119
>> language make the protocol spec LESS useful for compliance
>> certification?
> 
> Wrong question. What we (the IETF) care about is the existence of
> interoperable implementations, not mathematical compliance.
> 
> If you ask "at what point does replacing all action verbs with 2119
> language make the protocol spec LESS useful for coding interoperable
> versions?", I think the answer will be something like "when it makes the
> spec so ugly and difficult to read that people get things wrong as a
> result."
> 
> On 15/01/2013 06:19, Dean Willis wrote:
>> On Jan 5, 2013, at 10:03 AM, John C Klensin <john-ietf@jck.com> wrote:
>> 
>>>> And, again, that is further complicated by the observation that IETF
>>>> Standards are used for procurement and even for litigation about
>>>> product quality.   We either need to accept that fact and, where
>>>> necessary, adjust our specification style to match or we run the risk
>>>> of bodies springing up who will profile our Standards, write
>>>> procurement-quality conformance statements for their profiles, and
>>>> become, de facto, the real standards-setter for the marketplace (and
>>>> obviously do so without any element of IETF consensus).
>> 
>> I'm not sure that's not a good thing. Witness for example the work SIP
>> Forum has done with the SIPConnect standards, which have made it MUCH
>> easier to order a box that will work with a SIP Trunking service.
> 
> I think there are cases of standards of extreme complexity, such as SIP,
> where such profiles may be useful, because otherwise interoperability 
> cannot be achieved.

I would not call SIP a standard of extreme complexity, but anyway there is
more and more protocols on a similar complexity - just two protocols that I am
working with currently - RSTP 2.0 and RELOAD - are of similar complexity.

> But perhaps the lesson for the IETF here is slightly different - don't
> design standards which allow that degree of complexity in the first place.

There is no simple solution to a complex problem, so as the problems we try to
solve increase in complexity, so are our solutions to them.  But perhaps you
are right in a way.  Perhaps the problem is simply that RFC 2119, and the
issues I and other see with the approach in using as little of the keywords as
possible, was designed for a time when problems - and solutions - were
simpler.  Perhaps RFC 2119 imposes an upper limit on the complexity that a
protocol developed with it can reach, and we are just hitting this threshold
more and more often.

I am not saying that it is a bad thing - I certainly like simple protocols,
but perhaps the IETF is simply the wrong place for developing complex protocols.

- -- 
Marc Petit-Huguenin
Email: marc@petit-huguenin.org
Blog: http://blog.marc.petit-huguenin.org
Profile: http://www.linkedin.com/in/petithug
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iQIcBAEBCAAGBQJQ9Tu8AAoJECnERZXWan7EH5oQAK7GF0bHQipOJfZiizI0EJRJ
TwWtJOjpI7gF81gWBUo5tgpNXWRPLWVoG5rzD4LgsustSJk1sWwNSTH6lcfm1J3Y
BSRvUZFXR92Y7SJLcP7fdRKhVK4vYPSF6lNHuGM0busAmCfmUcXCPe5zxqcvxgYR
aM+GjAUrzQlVe69oVIEQ2lSShEfaLWy+6pWkxuoylT/fPLWqxTTwb+EiuWsH5oHe
u0v9YcohByTtxvXHUurBF7kbUMFjNUnDPEgt0BtjwcQciGo1Pjyy8SGvpNF9Tr9f
2mNjk+A+0b9kaIxP06qEPe4oe3m//HdexLOyqesFDdXNdpWGs4ETExiUfo5wOcJn
QfgA6JF9AyQSVmmkXAv7v5YeNwa+PJk2FrTghl18CFyXdrDJL+6GkVwPEnA404Ek
1QY8Nnf+cpfwjNHk9iu19lDpo6uBpCWqvwFpvikWtMeQ5n6yQk434y1ZJ5GNSERU
Bd55+PY5TMTLV1B7ZO0ViLQ7bmAJ+lsQ4DK2vz+3+UdJL0MvAUs2MIIlpCklqMJV
iCm7gqDpfuiXzLm7vLuRgC6PgU9KGsbnKlispCb7T7sZjRgd9vqIfCwOpEQht4s8
X7v3+Ltzelapec4HwDerlhymoDUrPgn26lPFuqy1MtkjAqPqiRKszB3X/jMjoqLk
CjkDUD5QfHD9Cwunr0Qv
=bBSa
-----END PGP SIGNATURE-----

From stephen.farrell@cs.tcd.ie  Tue Jan 15 03:33:11 2013
Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4867621F8610 for <ietf@ietfa.amsl.com>; Tue, 15 Jan 2013 03:33:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.723
X-Spam-Level: 
X-Spam-Status: No, score=-102.723 tagged_above=-999 required=5 tests=[AWL=-0.124, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 C5i0OYQgKw4c for <ietf@ietfa.amsl.com>; Tue, 15 Jan 2013 03:33:10 -0800 (PST)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) by ietfa.amsl.com (Postfix) with ESMTP id 1C9BA21F860A for <ietf@ietf.org>; Tue, 15 Jan 2013 03:33:09 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id F1DA3BE25; Tue, 15 Jan 2013 11:32:47 +0000 (GMT)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aJ7jmLYPpiLB; Tue, 15 Jan 2013 11:32:46 +0000 (GMT)
Received: from [IPv6:2001:770:10:203:1d04:f17:b1f3:7a33] (unknown [IPv6:2001:770:10:203:1d04:f17:b1f3:7a33]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id DFA1EBE58; Tue, 15 Jan 2013 11:32:34 +0000 (GMT)
Message-ID: <50F53E53.8030705@cs.tcd.ie>
Date: Tue, 15 Jan 2013 11:32:35 +0000
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130106 Thunderbird/17.0.2
MIME-Version: 1.0
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: Last Call: <draft-farrell-ft-03.txt> (A Fast-Track way to RFC with	Running Code) to Experimental RFC
References: <20130111151453.22161.50884.idtracker@ietfa.amsl.com> <50F535A7.1090506@gmail.com>
In-Reply-To: <50F535A7.1090506@gmail.com>
X-Enigmail-Version: 1.5
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Jan 2013 11:33:11 -0000

Hi Brian,

On 01/15/2013 10:55 AM, Brian E Carpenter wrote:
> On balance I think this experiment is safe to carry out, and therefore
> probably should be carried out. There are a few comments below.
> 
> However, I would urge the IESG to update the page at
> http://www.ietf.org/iesg/process-experiment.html, including current
> status of the experiments mentioned, and the history of concluded
> experiments, which I'm pretty sure was there a few years ago.
> At least, the history of the RFC 4693 experiment isn't there.

Fair point. I've noted that that ought happen in the working
copy, [1] just so's we remember to look at it again later
during/after this LC.

> 
> 1. It seems clear that the explicit mention of GPLv3 should be removed.
> It's contentious for a number of reasons. The phrase "e.g., under a Free
> Software or Open Source license" seems necessary and sufficient.

Ok, I reluctantly fold on that since I got other off-list comments
to the same effect. My working copy now says:

   There is no requirement here as to the licensing of the
   implementation whether open- or closed-source.  At one end of a
   spectrum the source code of the implementation could be available
   under a Free Software or Open Source License.  Publishing the code
   source under such a license permits the public at large to read,
   compile and run it and removes all ambiguity about the existence of
   the implementation.  At the other end of the spectrum, a public
   statement by an employee of a known vendor, or the publication of an
   interoperability report from multiple implementers, can give
   sufficient confidence.  In all cases the WG chairs and AD do need to
   be able to say why they consider the implementation is appropriate
   for fast-track processing.

> 2. There's a slight inconsistency between the mention of interoperablity
> in a few places and the proposal to use *one* implementation as a
> criterion. It doesn't seem unreasonable to use one implementation
> as a criterion for PS, since a criterion for IS under RFC 6410 is
> multiple interoperable implementations. But we should not imply that
> one successful implementation implies anything at all about
> interoperability. I think this needs to be stated quite explicitly:
> 
> Note that the existence of one implementation does not in any way
> demonstrate the interoperability required for advancement on the
> standards track [RFC6410].

Seems ok to me. Added to working copy. Changed the reference
to BCP9 which includes 6410.

> 3. However, I remember very bad experience some years ago with the
> 6NET project attempting to deploy Mobile IPv6 based on implementations
> of several different versions of the main MIPv6 draft. They simply
> could not interoperate. There is a risk that fast-tracking a draft could
> actually be damaging in such a situation. I think we would need a clear
> consensus that the draft is stable as well as viable. I suggest adding
> an item in section 4 something like this:
> 
> The WG chairs and responsible AD must be satisfied that the draft is
> in a stable state and that significant technical changes are unlikely
> to be proposed in the near future.

That would be reasonable to add, yes. But, there are lots of
other similar things that could be reasonable to add, that
cumulatively might result in the experiment not happening (e.g.
things from Olafur and Stephan yesterday). While this one is
less of a deal maybe, I'm still reluctant to add it because
if we add everyone's favourite nugget of wisdom, then we'll
likely end up with something unworkable.

Would it be reasonable to either add a section on "stuff that
came up in IETF LC that the IESG ought consider after the
experiment" or else to put this kind of thing in the wiki
for the experiment rather than state it as a rule or guidance
in the draft?

Cheers,
S.

[1] http://down.dsg.cs.tcd.ie/misc/draft-farrell-ft-04.txt

> 
> Regards
>    Brian
> 
> 
> 

From brian.e.carpenter@gmail.com  Tue Jan 15 03:49:51 2013
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1518521F8717 for <ietf@ietfa.amsl.com>; Tue, 15 Jan 2013 03:49:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.387
X-Spam-Level: 
X-Spam-Status: No, score=-103.387 tagged_above=-999 required=5 tests=[AWL=0.212, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
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 YZqPdj1UPnwV for <ietf@ietfa.amsl.com>; Tue, 15 Jan 2013 03:49:50 -0800 (PST)
Received: from mail-wg0-f49.google.com (mail-wg0-f49.google.com [74.125.82.49]) by ietfa.amsl.com (Postfix) with ESMTP id A238021F86E8 for <ietf@ietf.org>; Tue, 15 Jan 2013 03:49:49 -0800 (PST)
Received: by mail-wg0-f49.google.com with SMTP id 15so2799777wgd.16 for <ietf@ietf.org>; Tue, 15 Jan 2013 03:49:48 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:organization:user-agent :mime-version:to:cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=oEEqNXPNWVoXP5Sv5weW/FvqcuIPUxKHdaxBE2n2LX0=; b=NwCpu+kY7oZSVjhA3aBS1d9HcWbUAMFEv6VbrYxbyEi0AC1otNu8fdwsqo4NcXU4Ou 3o1WX66jB3NtfV6D/ACjuY+8y69oKbvzGUEEO0pukmtshnIsgphhBGJwOT6ySVFHdlOE 82Wd3uqsPyI18eNumTsFkwsxfbYkSYK8q9eaN1VYCYXtQdDcB3DaiYfvTI9tWCxI/PTv 8U8xNcjwM9BAY5BXzHFO+Dj/lE29bxD4zkEKG/PRdExX9S3vQiTUxst5aaTtq9Ddr0PY nzAcwk5QLbiNv8htpHEnC0Dkus+FeSrTLR5Nnu73bqD/3xr0xmsFtE+NDU5pq5eTw6nv k+2w==
X-Received: by 10.194.179.34 with SMTP id dd2mr141179915wjc.1.1358250588846; Tue, 15 Jan 2013 03:49:48 -0800 (PST)
Received: from [128.232.110.102] (c102.al.cl.cam.ac.uk. [128.232.110.102]) by mx.google.com with ESMTPS id bw9sm3107822wib.5.2013.01.15.03.49.47 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 15 Jan 2013 03:49:48 -0800 (PST)
Message-ID: <50F54261.4070705@gmail.com>
Date: Tue, 15 Jan 2013 11:49:53 +0000
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Subject: Re: Last Call: <draft-farrell-ft-03.txt> (A Fast-Track way to RFC with	Running Code) to Experimental RFC
References: <20130111151453.22161.50884.idtracker@ietfa.amsl.com> <50F535A7.1090506@gmail.com> <50F53E53.8030705@cs.tcd.ie>
In-Reply-To: <50F53E53.8030705@cs.tcd.ie>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Jan 2013 11:49:51 -0000

See below...

On 15/01/2013 11:32, Stephen Farrell wrote:
> Hi Brian,
> 
> On 01/15/2013 10:55 AM, Brian E Carpenter wrote:
>> On balance I think this experiment is safe to carry out, and therefore
>> probably should be carried out. There are a few comments below.
>>
>> However, I would urge the IESG to update the page at
>> http://www.ietf.org/iesg/process-experiment.html, including current
>> status of the experiments mentioned, and the history of concluded
>> experiments, which I'm pretty sure was there a few years ago.
>> At least, the history of the RFC 4693 experiment isn't there.
> 
> Fair point. I've noted that that ought happen in the working
> copy, [1] just so's we remember to look at it again later
> during/after this LC.
> 
>> 1. It seems clear that the explicit mention of GPLv3 should be removed.
>> It's contentious for a number of reasons. The phrase "e.g., under a Free
>> Software or Open Source license" seems necessary and sufficient.
> 
> Ok, I reluctantly fold on that since I got other off-list comments
> to the same effect. My working copy now says:
> 
>    There is no requirement here as to the licensing of the
>    implementation whether open- or closed-source.  At one end of a
>    spectrum the source code of the implementation could be available
>    under a Free Software or Open Source License.  Publishing the code
>    source under such a license permits the public at large to read,
>    compile and run it and removes all ambiguity about the existence of
>    the implementation.  At the other end of the spectrum, a public
>    statement by an employee of a known vendor, or the publication of an
>    interoperability report from multiple implementers, can give
>    sufficient confidence.  In all cases the WG chairs and AD do need to
>    be able to say why they consider the implementation is appropriate
>    for fast-track processing.
> 
>> 2. There's a slight inconsistency between the mention of interoperablity
>> in a few places and the proposal to use *one* implementation as a
>> criterion. It doesn't seem unreasonable to use one implementation
>> as a criterion for PS, since a criterion for IS under RFC 6410 is
>> multiple interoperable implementations. But we should not imply that
>> one successful implementation implies anything at all about
>> interoperability. I think this needs to be stated quite explicitly:
>>
>> Note that the existence of one implementation does not in any way
>> demonstrate the interoperability required for advancement on the
>> standards track [RFC6410].
> 
> Seems ok to me. Added to working copy. Changed the reference
> to BCP9 which includes 6410.
> 
>> 3. However, I remember very bad experience some years ago with the
>> 6NET project attempting to deploy Mobile IPv6 based on implementations
>> of several different versions of the main MIPv6 draft. They simply
>> could not interoperate. There is a risk that fast-tracking a draft could
>> actually be damaging in such a situation. I think we would need a clear
>> consensus that the draft is stable as well as viable. I suggest adding
>> an item in section 4 something like this:
>>
>> The WG chairs and responsible AD must be satisfied that the draft is
>> in a stable state and that significant technical changes are unlikely
>> to be proposed in the near future.
> 
> That would be reasonable to add, yes. But, there are lots of
> other similar things that could be reasonable to add, that
> cumulatively might result in the experiment not happening (e.g.
> things from Olafur and Stephan yesterday). While this one is
> less of a deal maybe, I'm still reluctant to add it because
> if we add everyone's favourite nugget of wisdom, then we'll
> likely end up with something unworkable.
> 
> Would it be reasonable to either add a section on "stuff that
> came up in IETF LC that the IESG ought consider after the
> experiment" or else to put this kind of thing in the wiki
> for the experiment rather than state it as a rule or guidance
> in the draft?

I hate it when we end up legislating for common sense, so I
agree that for the experiment, this point could be put in the
wiki. Perhaps we could just add "Participants must exercise
common sense at all times" to the Note Well.

   Brian
> 
> Cheers,
> S.
> 
> [1] http://down.dsg.cs.tcd.ie/misc/draft-farrell-ft-04.txt
> 
>> Regards
>>    Brian
>>
>>
>>
> 

From abdussalambaryun@gmail.com  Tue Jan 15 04:54:09 2013
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 87C0E21F875C for <ietf@ietfa.amsl.com>; Tue, 15 Jan 2013 04:54:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.578
X-Spam-Level: 
X-Spam-Status: No, score=-3.578 tagged_above=-999 required=5 tests=[AWL=0.021,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 ss-1JICZqdfb for <ietf@ietfa.amsl.com>; Tue, 15 Jan 2013 04:54:07 -0800 (PST)
Received: from mail-vc0-f171.google.com (mail-vc0-f171.google.com [209.85.220.171]) by ietfa.amsl.com (Postfix) with ESMTP id 8310621F873B for <ietf@ietf.org>; Tue, 15 Jan 2013 04:54:07 -0800 (PST)
Received: by mail-vc0-f171.google.com with SMTP id n11so55742vch.2 for <ietf@ietf.org>; Tue, 15 Jan 2013 04:54:06 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=MQe9cijB0vj8l5OTHFIXGTD1+ZOfO1kWmw6AliSR4us=; b=jMrmxBf9rfhoyWZEkNqojTNBzAz+GCdYbOEK0PVf/hgGf8mPzN7XCuxUNFCMxcgbT5 VH6VN/qrH/nD+NY/6X9iJYayjzWK72C2bet1mTcbSbedJlcTi+yOCvl31Cs15YPPHwbI FUQL9vbg24BSqd+xx1BmqvWaM7sJTylntP/5vGoBiTIjKeC84SSvnukqR7T1lmqoJDLt eJCqjdbw233PGN3BMs0Rtn/D9uINm2+puuUxi/VLxKMzg1QtMphIbLoFDU91gAngChIm gRrJsLkFzWzrC1AakJPW/aRUcF0zsSxH7Exs2P4zisApMhF2D2DF3eNsjc3MSCNRZozQ fgmw==
MIME-Version: 1.0
Received: by 10.52.27.50 with SMTP id q18mr92640423vdg.20.1358254446592; Tue, 15 Jan 2013 04:54:06 -0800 (PST)
Received: by 10.220.145.5 with HTTP; Tue, 15 Jan 2013 04:54:06 -0800 (PST)
In-Reply-To: <CADnDZ89r3ZobS7aL6SkQzMdf-1vXoAtq5BZna6yXvSZQ2HAPBw@mail.gmail.com>
References: <CADnDZ89r3ZobS7aL6SkQzMdf-1vXoAtq5BZna6yXvSZQ2HAPBw@mail.gmail.com>
Date: Tue, 15 Jan 2013 13:54:06 +0100
Message-ID: <CADnDZ89dgT4m7kGE0ya67d7jN1MER7bK_WQDbcsbcs7KCENTvw@mail.gmail.com>
Subject: Re: Making RFC2119 key language easier to Protocol Readers
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: petithug@acm.org
Content-Type: text/plain; charset=ISO-8859-1
Cc: ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Jan 2013 12:54:09 -0000

Hi Marc Petit-Huguenin,

I agree that we need to be able to make complex protocol's readable in IETF,
That is why I am doing an update ID for the RFC2119, I know many don't
think it is a right thing to do, but I think maybe in future while
making new versions of the update draft I will get to better
discussions,

AB
++++++++++++++++++++++++++++++++

Date: Tue, 15 Jan 2013 03:21:41 -0800

> I think there are cases of standards of extreme complexity, such as SIP,
> where such profiles may be useful, because otherwise interoperability
> cannot be achieved.

I would not call SIP a standard of extreme complexity, but anyway there is
more and more protocols on a similar complexity - just two protocols that I am
working with currently - RSTP 2.0 and RELOAD - are of similar complexity.

> But perhaps the lesson for the IETF here is slightly different - don't
> design standards which allow that degree of complexity in the first place.

There is no simple solution to a complex problem, so as the problems we try to
solve increase in complexity, so are our solutions to them.  But perhaps you
are right in a way.  Perhaps the problem is simply that RFC 2119, and the
issues I and other see with the approach in using as little of the keywords as
possible, was designed for a time when problems - and solutions - were
simpler.  Perhaps RFC 2119 imposes an upper limit on the complexity that a
protocol developed with it can reach, and we are just hitting this threshold
more and more often.

I am not saying that it is a bad thing - I certainly like simple protocols,
but perhaps the IETF is simply the wrong place for developing complex protocols.

- --
Marc Petit-Huguenin
Email: marc at petit-huguenin.org

From stephen.farrell@cs.tcd.ie  Tue Jan 15 05:15:24 2013
Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 75E4621F867E for <ietf@ietfa.amsl.com>; Tue, 15 Jan 2013 05:15:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.718
X-Spam-Level: 
X-Spam-Status: No, score=-102.718 tagged_above=-999 required=5 tests=[AWL=-0.119, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 JzZe8eJjOoJQ for <ietf@ietfa.amsl.com>; Tue, 15 Jan 2013 05:15:23 -0800 (PST)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) by ietfa.amsl.com (Postfix) with ESMTP id 6941021F865B for <ietf@ietf.org>; Tue, 15 Jan 2013 05:15:23 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id 0158DBE35; Tue, 15 Jan 2013 13:15:00 +0000 (GMT)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id juknX3M+xOmF; Tue, 15 Jan 2013 13:14:58 +0000 (GMT)
Received: from [IPv6:2001:770:10:203:1d04:f17:b1f3:7a33] (unknown [IPv6:2001:770:10:203:1d04:f17:b1f3:7a33]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id C9B30BDCA; Tue, 15 Jan 2013 13:14:58 +0000 (GMT)
Message-ID: <50F55654.7040307@cs.tcd.ie>
Date: Tue, 15 Jan 2013 13:15:00 +0000
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130106 Thunderbird/17.0.2
MIME-Version: 1.0
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: Last Call: <draft-farrell-ft-03.txt> (A Fast-Track way to RFC with	Running Code) to Experimental RFC
References: <20130111151453.22161.50884.idtracker@ietfa.amsl.com> <50F535A7.1090506@gmail.com> <50F53E53.8030705@cs.tcd.ie> <50F54261.4070705@gmail.com>
In-Reply-To: <50F54261.4070705@gmail.com>
X-Enigmail-Version: 1.5
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Jan 2013 13:15:24 -0000

Hiya,

On 01/15/2013 11:49 AM, Brian E Carpenter wrote:
> I hate it when we end up legislating for common sense, so I
> agree that for the experiment, this point could be put in the
> wiki. 

Great. I'm accumulating stuff like that in the "changes"
section (9.1) of the working version [1] for now, so when
we get towards the end of LC, I'll look at adding things
to the wiki.

> Perhaps we could just add "Participants must exercise
> common sense at all times" to the Note Well.

But if that worked, we'd have much less fun;-)

S.

[1] http://down.dsg.cs.tcd.ie/misc/draft-farrell-ft-04.txt



From petithug@acm.org  Tue Jan 15 05:20:08 2013
Return-Path: <petithug@acm.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6C28821F867E for <ietf@ietfa.amsl.com>; Tue, 15 Jan 2013 05:20:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.505
X-Spam-Level: 
X-Spam-Status: No, score=-102.505 tagged_above=-999 required=5 tests=[AWL=0.095, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
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 X45HabMiTsRP for <ietf@ietfa.amsl.com>; Tue, 15 Jan 2013 05:20:07 -0800 (PST)
Received: from implementers.org (implementers.org [IPv6:2604:3400:dc1:41:216:3eff:fe5b:8240]) by ietfa.amsl.com (Postfix) with ESMTP id 31BF321F86CD for <ietf@ietf.org>; Tue, 15 Jan 2013 05:20:07 -0800 (PST)
Received: from [IPv6:2601:9:4b80:32:b858:b5d1:71bb:65c] (unknown [IPv6:2601:9:4b80:32:b858:b5d1:71bb:65c]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (Client CN "Marc Petit-Huguenin", Issuer "implementers.org" (verified OK)) by implementers.org (Postfix) with ESMTPS id 5C18720373; Tue, 15 Jan 2013 13:20:05 +0000 (UTC)
Message-ID: <50F55791.9090206@acm.org>
Date: Tue, 15 Jan 2013 05:20:17 -0800
From: Marc Petit-Huguenin <petithug@acm.org>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.11) Gecko/20121122 Icedove/10.0.11
MIME-Version: 1.0
To: Abdussalam Baryun <abdussalambaryun@gmail.com>
Subject: Re: Making RFC2119 key language easier to Protocol Readers
References: <CADnDZ89r3ZobS7aL6SkQzMdf-1vXoAtq5BZna6yXvSZQ2HAPBw@mail.gmail.com> <CADnDZ89dgT4m7kGE0ya67d7jN1MER7bK_WQDbcsbcs7KCENTvw@mail.gmail.com>
In-Reply-To: <CADnDZ89dgT4m7kGE0ya67d7jN1MER7bK_WQDbcsbcs7KCENTvw@mail.gmail.com>
X-Enigmail-Version: 1.4.1
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Jan 2013 13:20:08 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On 01/15/2013 04:54 AM, Abdussalam Baryun wrote:
> Hi Marc Petit-Huguenin,
> 
> I agree that we need to be able to make complex protocol's readable in
> IETF, That is why I am doing an update ID for the RFC2119, I know many
> don't think it is a right thing to do, but I think maybe in future while 
> making new versions of the update draft I will get to better discussions,

Changing RFC 2119 would perhaps permit to manage more complex protocols, but
this will delay the problem, not fix it.  Perhaps there is no other solution
than using formal languages when going beyond a threshold of complexity, and
that definitively not something that will be done at the IETF.

But perhaps there could be enough interest to create an IRTF working group, on
the subject of writing specifications for complex protocols.

> 
> AB ++++++++++++++++++++++++++++++++
> 
> Date: Tue, 15 Jan 2013 03:21:41 -0800
> 
>> I think there are cases of standards of extreme complexity, such as SIP, 
>> where such profiles may be useful, because otherwise interoperability 
>> cannot be achieved.
> 
> I would not call SIP a standard of extreme complexity, but anyway there is 
> more and more protocols on a similar complexity - just two protocols that I
> am working with currently - RSTP 2.0 and RELOAD - are of similar
> complexity.
> 
>> But perhaps the lesson for the IETF here is slightly different - don't 
>> design standards which allow that degree of complexity in the first
>> place.
> 
> There is no simple solution to a complex problem, so as the problems we try
> to solve increase in complexity, so are our solutions to them.  But perhaps
> you are right in a way.  Perhaps the problem is simply that RFC 2119, and
> the issues I and other see with the approach in using as little of the
> keywords as possible, was designed for a time when problems - and solutions
> - were simpler.  Perhaps RFC 2119 imposes an upper limit on the complexity
> that a protocol developed with it can reach, and we are just hitting this
> threshold more and more often.
> 
> I am not saying that it is a bad thing - I certainly like simple
> protocols, but perhaps the IETF is simply the wrong place for developing
> complex protocols.

- -- 
Marc Petit-Huguenin
Email: marc@petit-huguenin.org
Blog: http://blog.marc.petit-huguenin.org
Profile: http://www.linkedin.com/in/petithug
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iQIcBAEBCAAGBQJQ9VeLAAoJECnERZXWan7E+u0P/1howuEDFI+h9FSV77Cv2YBW
u5+Kfj9fhPp0nhqLr8z/1Hc4YAK/+YPmQ0gDzO5SVtnMTZwE5N3RgPx+yglOZ11X
peZdwNgftMTSZOwc2r1B/gdHdyeVgYtZnEFJicbVgxbW6VirRml8qtYrOGijeh5B
CAneVVqjpF1ou3BXjvGoxCXyP0Tw/XCPt+6+vGYpZ8GApfVizECViYljyZrOeDEG
ZW6vgGnBrV6G+vqRXJRRZELZu2WMnJaC2ADHfCpIdAKCTBKX6Lj7v+7Ni4IAjEYC
Z6hEDynBwaNVODMAuglbmVfC5I2kB45M5JwLoVu8sbfhOrGEJi7CnHDTbi1jW1N/
70ZdsQvHbDj0uJL4s6mulwnJOYCh3d7uqAeMEFM5uyMYA+U5/5Dr7RYOhrP/xD0Y
U+Y/YlFz+TLncsio7aYnzEpdjfFDYnbeLLyE0TdjM1kIGPkeKA3GPAdJbW4mDXpg
VAbxGgiS89mSXGOjhlUKjfMEmmF7R21e8kAcubonOp/chu/nqO821qE1lfAYNZ5i
WGHUPPTB/p5iXmhkt9cHESlOB1suW5r5y4Qq5qkz376FraIHIQgflSX4HuE0BBx1
DEbxoOhr9QgHU6INEt1GBuwxzJW076tD22hkprkl/w90KtbHP2HvjpK5bkNN/MA5
owExvo14qd9YEq0/SKhk
=YyMX
-----END PGP SIGNATURE-----

From john-ietf@jck.com  Tue Jan 15 06:02:09 2013
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E89ED21F8790 for <ietf@ietfa.amsl.com>; Tue, 15 Jan 2013 06:02:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.367
X-Spam-Level: 
X-Spam-Status: No, score=-102.367 tagged_above=-999 required=5 tests=[AWL=0.232, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 q3eeLVRqv9RG for <ietf@ietfa.amsl.com>; Tue, 15 Jan 2013 06:02:09 -0800 (PST)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 5264F21F8726 for <ietf@ietf.org>; Tue, 15 Jan 2013 06:02:09 -0800 (PST)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1Tv75a-000Gbt-LW; Tue, 15 Jan 2013 09:02:06 -0500
Date: Tue, 15 Jan 2013 09:02:01 -0500
From: John C Klensin <john-ietf@jck.com>
To: Dean Willis <dean.willis@softarmor.com>
Subject: Re: Making RFC2119 key language easier to Protocol Readers
Message-ID: <FBF6C8CF1070E32ACB9FBFE7@JcK-HP8200.jck.com>
In-Reply-To: <C381A966-AC3A-4209-8834-F20A59D80012@softarmor.com>
References: <CADnDZ8-yCxUbrD9oFyQKkJuTgDZbamnV8K4GU+sAN5SekpyHAA@mail.gmail.com> <CADnDZ88XgyNXiu1fdK3WB7jrZTmfuvAc5U1XyAxjprZf6=7P4Q@mail.gmail.c om> <CADnDZ8_pd5ZrnucZAoK5WDXUgK9gQhHm+GJe7PihDQzx1uUsaw@mail.gmail.com> <alpine.DEB.2.00.1301051010080.26235@uplift.swm.pp.se> <1D12E3A12F3C30D3066A13E6@JcK-HP8200.jck.com> <C381A966-AC3A-4209-8834-F20A59D80012@softarmor.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Cc: ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Jan 2013 14:02:10 -0000

--On Tuesday, January 15, 2013 00:19 -0600 Dean Willis
<dean.willis@softarmor.com> wrote:

> On Jan 5, 2013, at 10:03 AM, John C Klensin
> <john-ietf@jck.com> wrote:
> 
>> And, again, that is further complicated by the observation
>> that IETF Standards are used for procurement and even for
>> litigation about product quality.   We either need to accept
>> that fact and, where necessary, adjust our specification
>> style to match or we run the risk of bodies springing up who
>> will profile our Standards, write procurement-quality
>> conformance statements for their profiles, and become, de
>> facto, the real standards-setter for the marketplace (and
>> obviously do so without any element of IETF consensus).  
> 
> I'm not sure that's not a good thing. Witness for example the
> work SIP Forum has done with the SIPConnect standards, which
> have made it MUCH easier to order a box that will work with a
> SIP Trunking service.

Dean,

Historically, there are many cases where certification
arrangements have worked out well, many cases where they have
worked out badly, and many cases where evaluation of the
certification process has, itself, been controversial.   That
really isn't the point.  The issue is locus of authority in
practice because, if certification is important in the
marketplace, then the real standard is ability to conform to and
pass certification, not conformance to the published Standard or
the ability of implementations built to that published Standards
to interoperate.  

One can imagine a certification test that fatefully follows the
published Standard and verifies every feature and requirement
_and_ that that either the published Standard is well enough
written to not allow alternate interpretations that would not
interoperate or the certification process includes adequate
interoperability tests.  In that case, the difference between
"conform to (i.e., pass) certification test" and "conform to
published Standard" is mostly a matter of aesthetics and
perceptions of control.   

However, IETF has often been very concerned about change control
and, no matter how good everyone's intentions, successful
certification activities often switch the locus of that control
(sometimes, so do unsuccessful ones and ones that are mandated
by some authority).  In addition, some people would suggest that
the near-perfect certification test outlined above bears a
strong resemblance to provably-correct computer programs: the
proofs are possible and work well for very simple cases,
primarily those that are designed an constructed with proof in
mind and not for more complex and organic situations.

    john


From abdussalambaryun@gmail.com  Tue Jan 15 06:03:25 2013
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0004A21F86E7 for <ietf@ietfa.amsl.com>; Tue, 15 Jan 2013 06:03:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.579
X-Spam-Level: 
X-Spam-Status: No, score=-3.579 tagged_above=-999 required=5 tests=[AWL=0.020,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 HZLwtUzgma30 for <ietf@ietfa.amsl.com>; Tue, 15 Jan 2013 06:03:24 -0800 (PST)
Received: from mail-vc0-f175.google.com (mail-vc0-f175.google.com [209.85.220.175]) by ietfa.amsl.com (Postfix) with ESMTP id 9A8F421F84CC for <ietf@ietf.org>; Tue, 15 Jan 2013 06:03:23 -0800 (PST)
Received: by mail-vc0-f175.google.com with SMTP id fy7so127438vcb.6 for <ietf@ietf.org>; Tue, 15 Jan 2013 06:03:23 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=LZv0vPKBHx31//+ax2PpwMgLJNzLpS/qKnI4fYwuCIM=; b=mmMnFqc+juWHOpSHYWfZgIiaw3RYnxPV4rIBwrqnAVwtEdqTAQvgdEMkeSYUxZV3rU Uuqso+G4DH6PeyvK/aICV5imEaX4csgjwAg3vweQ4pvNUB5woN52eZd0BQANcZjETsSx SBfucP9TB1+CSnO30nKfSLvkf8KsQo1BGeaNr23yhdovu2vYl5Pnx/3owoNqPWUtfjxg h49HmWG8mEfk6zVHlC0JIUOBBRboC+sL6C9QjdaLss+aCevRmiBUexcQsXX2JJ0D3Yaa THOkBN7o0XxbH3vuFxbI598vW1dN/13bunzsb/bsepsC29C+ZemwJA0Qm/EUBtMT0jzy SBkg==
MIME-Version: 1.0
Received: by 10.58.31.200 with SMTP id c8mr25580486vei.23.1358258602857; Tue, 15 Jan 2013 06:03:22 -0800 (PST)
Received: by 10.220.145.5 with HTTP; Tue, 15 Jan 2013 06:03:22 -0800 (PST)
In-Reply-To: <50F55791.9090206@acm.org>
References: <CADnDZ89r3ZobS7aL6SkQzMdf-1vXoAtq5BZna6yXvSZQ2HAPBw@mail.gmail.com> <CADnDZ89dgT4m7kGE0ya67d7jN1MER7bK_WQDbcsbcs7KCENTvw@mail.gmail.com> <50F55791.9090206@acm.org>
Date: Tue, 15 Jan 2013 15:03:22 +0100
Message-ID: <CADnDZ89pQ5sNzexz2o_cOxA5StqP-xA=S5FOjZiWuBY0sxvdaw@mail.gmail.com>
Subject: Re: Making RFC2119 key language easier to Protocol Readers
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: Marc Petit-Huguenin <petithug@acm.org>
Content-Type: text/plain; charset=ISO-8859-1
Cc: ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Jan 2013 14:03:25 -0000

I don't think there is a general level of simple or complex protocol,
it always will depends on a point of view a machine,

AB

On 1/15/13, Marc Petit-Huguenin <petithug@acm.org> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
>
> On 01/15/2013 04:54 AM, Abdussalam Baryun wrote:
>> Hi Marc Petit-Huguenin,
>>
>> I agree that we need to be able to make complex protocol's readable in
>> IETF, That is why I am doing an update ID for the RFC2119, I know many
>> don't think it is a right thing to do, but I think maybe in future while
>> making new versions of the update draft I will get to better discussions,
>
> Changing RFC 2119 would perhaps permit to manage more complex protocols,
> but
> this will delay the problem, not fix it.  Perhaps there is no other
> solution
> than using formal languages when going beyond a threshold of complexity,
> and
> that definitively not something that will be done at the IETF.
>
> But perhaps there could be enough interest to create an IRTF working group,
> on
> the subject of writing specifications for complex protocols.
>
>>
>> AB ++++++++++++++++++++++++++++++++
>>
>> Date: Tue, 15 Jan 2013 03:21:41 -0800
>>
>>> I think there are cases of standards of extreme complexity, such as SIP,
>>>
>>> where such profiles may be useful, because otherwise interoperability
>>> cannot be achieved.
>>
>> I would not call SIP a standard of extreme complexity, but anyway there is
>>
>> more and more protocols on a similar complexity - just two protocols that
>> I
>> am working with currently - RSTP 2.0 and RELOAD - are of similar
>> complexity.
>>
>>> But perhaps the lesson for the IETF here is slightly different - don't
>>> design standards which allow that degree of complexity in the first
>>> place.
>>
>> There is no simple solution to a complex problem, so as the problems we
>> try
>> to solve increase in complexity, so are our solutions to them.  But
>> perhaps
>> you are right in a way.  Perhaps the problem is simply that RFC 2119, and
>> the issues I and other see with the approach in using as little of the
>> keywords as possible, was designed for a time when problems - and
>> solutions
>> - were simpler.  Perhaps RFC 2119 imposes an upper limit on the
>> complexity
>> that a protocol developed with it can reach, and we are just hitting this
>> threshold more and more often.
>>
>> I am not saying that it is a bad thing - I certainly like simple
>> protocols, but perhaps the IETF is simply the wrong place for developing
>> complex protocols.
>
> - --
> Marc Petit-Huguenin
> Email: marc@petit-huguenin.org
> Blog: http://blog.marc.petit-huguenin.org
> Profile: http://www.linkedin.com/in/petithug
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.12 (GNU/Linux)
>
> iQIcBAEBCAAGBQJQ9VeLAAoJECnERZXWan7E+u0P/1howuEDFI+h9FSV77Cv2YBW
> u5+Kfj9fhPp0nhqLr8z/1Hc4YAK/+YPmQ0gDzO5SVtnMTZwE5N3RgPx+yglOZ11X
> peZdwNgftMTSZOwc2r1B/gdHdyeVgYtZnEFJicbVgxbW6VirRml8qtYrOGijeh5B
> CAneVVqjpF1ou3BXjvGoxCXyP0Tw/XCPt+6+vGYpZ8GApfVizECViYljyZrOeDEG
> ZW6vgGnBrV6G+vqRXJRRZELZu2WMnJaC2ADHfCpIdAKCTBKX6Lj7v+7Ni4IAjEYC
> Z6hEDynBwaNVODMAuglbmVfC5I2kB45M5JwLoVu8sbfhOrGEJi7CnHDTbi1jW1N/
> 70ZdsQvHbDj0uJL4s6mulwnJOYCh3d7uqAeMEFM5uyMYA+U5/5Dr7RYOhrP/xD0Y
> U+Y/YlFz+TLncsio7aYnzEpdjfFDYnbeLLyE0TdjM1kIGPkeKA3GPAdJbW4mDXpg
> VAbxGgiS89mSXGOjhlUKjfMEmmF7R21e8kAcubonOp/chu/nqO821qE1lfAYNZ5i
> WGHUPPTB/p5iXmhkt9cHESlOB1suW5r5y4Qq5qkz376FraIHIQgflSX4HuE0BBx1
> DEbxoOhr9QgHU6INEt1GBuwxzJW076tD22hkprkl/w90KtbHP2HvjpK5bkNN/MA5
> owExvo14qd9YEq0/SKhk
> =YyMX
> -----END PGP SIGNATURE-----
>

From john-ietf@jck.com  Tue Jan 15 06:18:10 2013
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3002621F8715 for <ietf@ietfa.amsl.com>; Tue, 15 Jan 2013 06:18:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.413
X-Spam-Level: 
X-Spam-Status: No, score=-102.413 tagged_above=-999 required=5 tests=[AWL=0.186, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 jmD3HLKMUR0V for <ietf@ietfa.amsl.com>; Tue, 15 Jan 2013 06:18:09 -0800 (PST)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 9BEA521F8712 for <ietf@ietf.org>; Tue, 15 Jan 2013 06:18:09 -0800 (PST)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1Tv7L6-000Gcu-15; Tue, 15 Jan 2013 09:18:08 -0500
Date: Tue, 15 Jan 2013 09:18:02 -0500
From: John C Klensin <john-ietf@jck.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, Dean Willis <dean.willis@softarmor.com>
Subject: Re: Making RFC2119 key language easier to Protocol Readers
Message-ID: <6E90465C2F6F54F05F0B9602@JcK-HP8200.jck.com>
In-Reply-To: <50F50CF9.9010703@gmail.com>
References: <CADnDZ8-yCxUbrD9oFyQKkJuTgDZbamnV8K4GU+sAN5SekpyHAA@mail.gmail.com> <CADnDZ88XgyNXiu1fdK3WB7jrZTmfuvAc5U1XyAxjprZf6=7P4Q@mail.gmail.com> <CADnDZ8_pd5ZrnucZAoK5WDXUgK9gQhHm+GJe7PihDQzx1uUsaw@mail.gmail.com> <alpine.DEB.2.00.1301051010080.26235@uplift.swm.pp.se> <119BCE53-84DD-41F7-813C-B0644B4C82F9@softarmor.com> <50F50CF9.9010703@gmail.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Cc: ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Jan 2013 14:18:10 -0000

--On Tuesday, January 15, 2013 08:02 +0000 Brian E Carpenter
<brian.e.carpenter@gmail.com> wrote:

>> I'm not sure that's not a good thing. Witness for example the
>> work SIP Forum has done with the SIPConnect standards, which
>> have made it MUCH easier to order a box that will work with a
>> SIP Trunking service.
> 
> I think there are cases of standards of extreme complexity,
> such as SIP, where such profiles may be useful, because
> otherwise interoperability cannot be achieved. But perhaps the
> lesson for the IETF here is slightly different - don't design
> standards which allow that degree of complexity in the first
> place.

Yes.  And, if the certification test actually represents a
profile, then either:

(1) Implementations and certification tests that match a
different profile won't interoperate with this first one.  That
is a problem to which a number of ITU and ISO/IEC JTC1 standards
have fallen victim.

(2) If the profile represented by the tests is really widely
accepted as being the important core of the standard and IETF
believes in its own principles, we should immediately update and
replace the Standard to remove everything not included in that
profile, accomplishing an approximation to Brian's (and my)
lower-complexity specification the hard way.

    john

p.s. that latter issue raises another question about
draft-farrell-ft-03.txt and the associated Last Call.  The
ability to implement a spec does not demonstrate that it
contains the minimum level of complexity needed to do the job.
Would "more complex than necessary and therefore in need of
further work" be an acceptable Last Call comment and subject to
a DISCUSS within the intent of that document?





From bclaise@cisco.com  Tue Jan 15 06:49:22 2013
Return-Path: <bclaise@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 61A3C21F8650; Tue, 15 Jan 2013 06:49:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.582
X-Spam-Level: 
X-Spam-Status: No, score=-10.582 tagged_above=-999 required=5 tests=[AWL=0.016, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8]
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 AE0xIIH1jILy; Tue, 15 Jan 2013 06:49:18 -0800 (PST)
Received: from av-tac-bru.cisco.com (weird-brew.cisco.com [144.254.15.118]) by ietfa.amsl.com (Postfix) with ESMTP id 998FD21F8635; Tue, 15 Jan 2013 06:49:17 -0800 (PST)
X-TACSUNS: Virus Scanned
Received: from strange-brew.cisco.com (localhost.cisco.com [127.0.0.1]) by av-tac-bru.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id r0FEnCkM028129; Tue, 15 Jan 2013 15:49:13 +0100 (CET)
Received: from [10.60.67.84] (ams-bclaise-8913.cisco.com [10.60.67.84]) by strange-brew.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id r0FEmf99029043; Tue, 15 Jan 2013 15:48:51 +0100 (CET)
Message-ID: <50F56C49.6090103@cisco.com>
Date: Tue, 15 Jan 2013 15:48:41 +0100
From: Benoit Claise <bclaise@cisco.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: "draft-ietf-opsawg-oam-overview@tools.ietf.org" <draft-ietf-opsawg-oam-overview@tools.ietf.org>
Subject: Re: Last Call: <draft-ietf-opsawg-oam-overview-08.txt> (An Overview of Operations, Administration, and Maintenance (OAM) Mechanisms) to Informational RFC
References: <20130111193616.19158.16205.idtracker@ietfa.amsl.com> <50F437BF.8040005@cisco.com>
In-Reply-To: <50F437BF.8040005@cisco.com>
Content-Type: multipart/alternative; boundary="------------090504060000040407050407"
Cc: opsawg@ietf.org, ietf@ietf.org, Al Morton <acmorton@att.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Jan 2013 14:49:22 -0000

This is a multi-part message in MIME format.
--------------090504060000040407050407
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Some more feedback, send on behalf of Al Morton.

Regards, Benoit

=================================================
Hi Benoit,

Here are some additional comments, just checking a few things
I know a little about.

Al

-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

1.1. The Building Blocks of OAM
...
    o Performance Monitoring:
       Consists of 3 main functions

         o Loss Measurement (LM) - monitors the packet loss rate of a
           connection.

         o Delay Measurement (DM) - monitors the delay and delay
           variation between MPs.

         o Throughput measurement - monitors the throughput of a
           connection.

>>> Apparently, no OAM tool  currently measures Throughput,
     because no such tool is cited in the memo (and the term "throughput"
     never appears again).  my guess is that there was some reference to
     RFC 2544 that has now been removed. Remove Throughput from the list.

1.3 OAM Toolsets
...
    o OWAMP and TWAMP:
       The One Way Active Measurement Protocol (OWAMP) and the Two Way
       Active Measurement Protocols (TWAMP) are two protocols defined in
       the IP Performance Metrics (IPPM) working group in the IETF. These
       protocols allow delay and packet loss measurement in IP networks.

>>> and Delay variation,  duplication, reordering, etc. (all the metrics limited tools
     completely ignore).

1.4 IETF OAM Documents

>>> Expand Table 1 as noted  above, to include all the metrics they missed.


3.6.1
...
    TWAMP [TWAMP] is a similar protocol that enables measurement of
>>> both one-way and
    two-way (round trip) characteristics.

>>> sentence below is  simply not true, because the authors did not understand
    the one-way measurement capability:
    TWAMP does not require accurate
    time of day, and, furthermore, allows the use of a simple session
    reflector, making it an attractive alternative to OWAMP.
>>> go back and read the  memo...


3.7. Summary of OAM Functions

    Table 3 summarizes the OAM functions that are supported in each of
    the categories that were analyzed in this section.

+-----------+-------+--------+--------+-----------+-------+--------+
    | Standard |Continu|Connecti|Path    |Defect     |Perform|Other   |
    |           |ity    |vity |Discover|Indications|ance   |Function|
    |           |Check |Verifica|y       |           |Monitor|s       |
    |           |       |tion |        |           |ing    |        |
+-----------+-------+--------+--------+-----------+-------+--------+
...
    + --------- + ----- + ------ + ------ + --------- + ----- + ------ +
    |OWAMP and  |       | |        |           |-Delay |        |
    |TWAMP      |  Yes  |  Yes |        |           | measur|        |
    |           |       | |        |           | ement |        |
    |           |       | |        |           |-Packet|        |
    |           |       | |        |           | loss  |        |
    |           |       | |        |           | measur|        |
    |           |       | |        |           | ement |        |
+-----------+-------+--------+--------+-----------+-------+--------+
                      Table 3 Summary of OAM Functions

>>> Both Continuity Check  and Connectivity Verification are tested and
confirmed by establishing the *WAMP Control Protocol TCP connection,
so this should be indicated the table.


> draft-ietf-opsawg-oam-overview authors,
>
> Here is my feedback on this document.
>
> 1.
> Is this document in line with 
> http://tools.ietf.org/html/draft-ietf-trill-oam-req-04?
> * For example, the following definitions could be reused.
>     Fault: The term Fault refers to an inability to perform a required
>     action, e.g., an unsuccessful attempt to deliver a packet.
>
>     Defect: The term Defect refers to an interruption in the normal
>     operation, such that over a period of time no packets are delivered
>     successfully.
>
>     Failure: The term Failure refers to the termination of the required
>     function over a longer period of time. Persistence of a defect for a
>     period of time is interpreted as a failure.
>
> * For example, on the basic abstract
> Abstract
>
>     Operations, Administration, and Maintenance (OAM) is a general term
>     that refers to a toolset that can be used for fault detection and
>     isolation, and for performance measurement. OAM mechanisms have been
>     defined for various layers in the protocol stack, and are used with a
>     variety of protocols.
>
> Abstract (draft-ietf-trill-oam-req-04)
>
>     OAM (Operations, Administration and Maintenance) is a general term
>     used to identify functions and toolsets to troubleshoot and monitor
>     networks. This document presents, OAM Requirements applicable to
>     TRILL.
>
> So, as an example: does OAM include function?
> I advice to review draft-ietf-trill-oam-req-04
>
> 2.
> draft-ietf-trill-oam is not mentioned, while the abstract mentions:
>     This document presents an overview of the OAM mechanisms that have
>     been defined and are currently being defined by the IETF.
> Search for OAM in the current draft names (https://datatracker.ietf.org/), and you will find many references.
> Ok, I see later on:	
>     This document focuses on IETF
>     documents that have been published as RFCs, while other ongoing OAM-
>     related work is outside the scope.
> Ok, fine then: we don't need a reference to all the drafts.
> However, draft-ietf-trill-oam is closed to be a RFC, and should be mentioned.
>
>
> 3.
> Section 1
>     The term OAM in this document refers to Operations, Administration
>     and Maintenance [OAM-Def  <http://tools.ietf.org/html/draft-ietf-opsawg-oam-overview-08#ref-OAM-Def>], focusing on the forwarding plane of OAM.
> What does it mean "focusing on the forwarding plane of OAM"?
> Do you take a subset of the definition for this document?
> Btw, I don't see a definition in the terminology section.
> In section 2.2.3
>     A Maintenance Point (MP) is a functional entity that is defined at a
>     node in the network, and either initiates or reacts to OAM messages.
> Which plane is MP?
>
> 4.
> Section 1, Introduction
> "Hence, management aspects are outside the scope of this document."
> I don't understand which management aspects we speak about here.
> 5.
> Clarifying question regarding 1.2
> If speak about OWAMP or TWAMP 'synthetic traffic), is that data plane, 
> control plane, or management plane?
> Note that I found later on in the draft:
>     OWAMP and TWAMP use two separate protocols: a Control plane protocol,
>     and a Test plane protocol.
> Interestingly enough, after reading the document, I reviewed 
> http://datatracker.ietf.org/doc/draft-ietf-opsawg-oam-overview/ballot/, and 
> saw the same feedback from Stewart Bryant:
>
>     Provide a clear view of OAM functionality and its relationship
>     to various "planes" of networking (data plane, control plane,
>     management plane). In particular, the importance of
>     fate-sharing of OAM and user traffic flows in packet networks
>     should be explained.
>
> 6.
> I see a multiplication of "plane" terms in the IETF document, and in this document in particular.
> I could find: forwarding plane, management plane, control plane, data plane, user plane, and test plane.
> Way too many.
> Please be consistent
> 7.
>     Table 1 summarizes the IETF OAM related RFCs discussed in this
>     document.
>
>     Table 2 summarizes the OAM standards mentioned in this document.
>
> You need to change the Table 2 description. Do you want to say something along the lines of:
>     Table 2 summarizes the OAM standards specified by other Standard Development Organization
>     (SDO) than the IETF, along with IETF references where applicable.
>
>
> 8.
> Section 2.2.1
>     For a formal definition of each term, refer to the references at the end of
>     this document.
> Without a reference to a specific RFC, this is the type of statement which is not useful: you have 5 pages of references.
> You position this document as "An Overview of  Operations, Administration, and Maintenance (OAM) Mechanisms", but you tell the reader: "if you want to know about the terms,
> just read first all references!"
>
> 9.
> You specify some terms and some OAM categories,
>     2.2.2  <http://tools.ietf.org/html/draft-ietf-opsawg-oam-overview-08#section-2.2.2>. OAM Maintenance Entities ..........................13  <http://tools.ietf.org/html/draft-ietf-opsawg-oam-overview-08#page-13>
>           2.2.3  <http://tools.ietf.org/html/draft-ietf-opsawg-oam-overview-08#section-2.2.3>. OAM Maintenance Points ............................14  <http://tools.ietf.org/html/draft-ietf-opsawg-oam-overview-08#page-14>
>           2.2.4  <http://tools.ietf.org/html/draft-ietf-opsawg-oam-overview-08#section-2.2.4>. Proactive and On-demand activation ................15  <http://tools.ietf.org/html/draft-ietf-opsawg-oam-overview-08#page-15>
>           2.2.5  <http://tools.ietf.org/html/draft-ietf-opsawg-oam-overview-08#section-2.2.5>. Connectivity Verification and Continuity Checks ...15  <http://tools.ietf.org/html/draft-ietf-opsawg-oam-overview-08#page-15>
>           2.2.6  <http://tools.ietf.org/html/draft-ietf-opsawg-oam-overview-08#section-2.2.6>. Failures ..........................................15  <http://tools.ietf.org/html/draft-ietf-opsawg-oam-overview-08#page-15>
> ... but you don't use them in the section 3
>
> Just_one_example with section 3.2.2
> -
>     o Demand mode: in this mode, BFD control packets are sent on-demand.
>        Upon need, a system initiates a series of BFD control packets to
>        verify the liveness of the session
> Instead of liveness, you have defined Connectivity Verification and Continuity Checks  in section 2.2.5
> - OLD:
>     Each of the end-points of the monitored path maintains its own
>     session identification
> NEW:
>     Each of the MEP maintains its own session identification
> OR NEW (actually I don't know)
>     Each of the MP maintains its own session identification
> - OLD
> 	A BFD echo packet is sent to a peer system
> Peer system = MEP, MP, or something else?
> - etc...
>
> 10.
> This document is composed of a list of OAM content and references, but I'm really missing the document "scope and target audience".
> When we did RFC 6632, which is the companion document, we hadhttp://tools.ietf.org/html/rfc6632#section-1.1
>   
>     The target audience of the document is, on the one hand, IETF working
>     groups, which aim to select appropriate standard management protocols
>     and data models to address their needs concerning network management.
>     On the other hand, the document can be used as an overview and
>     guideline by non-IETF Standards Development Organizations (SDOs)
>     planning to use IETF management technologies and data models for the
>     realization of management applications.  The document can also be
>     used to initiate a discussion between the bodies with the goal to
>     gather new requirements and to detect possible gaps.  Finally, this
>     document is directed to all interested parties that seek to get an
>     overview of the current set of the IETF network management protocols
>     such as network administrators or newcomers to the IETF.
>
> You should have something similar.
>
>
> 11.
> Section 3.6.1, put the paragraph 2 at the end of the section. The "alternative" in the following sentence would then make sense
>     Alternative protocols for performance measurement are defined, for
>     example, in MPLS-TP OAM ([MPLS-LM-DM  <http://tools.ietf.org/html/draft-ietf-opsawg-oam-overview-08#ref-MPLS-LM-DM>], [TP-LM-DM  <http://tools.ietf.org/html/draft-ietf-opsawg-oam-overview-08#ref-TP-LM-DM>]), and in Ethernet
>     OAM [ITU-T-Y1731  <http://tools.ietf.org/html/draft-ietf-opsawg-oam-overview-08#ref-ITU-T-Y1731>].
>
>
> My conclusions: this document still needs some work
>
> Regards, Benoit
>   
>> The IESG has received a request from the Operations and Management Area
>> Working Group WG (opsawg) to consider the following document:
>> - 'An Overview of Operations, Administration, and Maintenance (OAM)
>>     Mechanisms'
>>    <draft-ietf-opsawg-oam-overview-08.txt> as Informational RFC
>>
>> The IESG plans to make a decision in the next few weeks, and solicits
>> final comments on this action. Please send substantive comments to the
>> ietf@ietf.org  mailing lists by 2013-01-25. Exceptionally, comments may be
>> sent toiesg@ietf.org  instead. In either case, please retain the
>> beginning of the Subject line to allow automated sorting.
>>
>> Abstract
>>
>>
>>     Operations, Administration, and Maintenance (OAM) is a general term
>>     that refers to a toolset that can be used for fault detection and
>>     isolation, and for performance measurement. OAM mechanisms have been
>>     defined for various layers in the protocol stack, and are used with a
>>     variety of protocols.
>>
>>     This document presents an overview of the OAM mechanisms that have
>>     been defined and are currently being defined by the IETF.
>>
>>
>>
>>
>> The file can be obtained via
>> http://datatracker.ietf.org/doc/draft-ietf-opsawg-oam-overview/
>>
>> IESG discussion can be tracked via
>> http://datatracker.ietf.org/doc/draft-ietf-opsawg-oam-overview/ballot/
>>
>>
>> No IPR declarations have been submitted directly on this I-D.
>>
>>
>>
>


--------------090504060000040407050407
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <div class="moz-cite-prefix">Some more feedback, send on behalf of
      Al Morton.<br>
      <br>
      Regards, Benoit<br>
      <br>
      =================================================<br>
      <span style="font-size:10.0pt;font-family:&quot;Courier
        New&quot;;color:windowtext">Hi Benoit,<o:p></o:p></span><br>
      <span style="font-size:10.0pt;font-family:&quot;Courier
        New&quot;;color:windowtext"><o:p>&nbsp;</o:p></span><br>
      <span style="font-size:10.0pt;font-family:&quot;Courier
        New&quot;;color:windowtext">Here are some additional comments,
        just checking a few things<o:p></o:p></span><br>
      <span style="font-size:10.0pt;font-family:&quot;Courier
        New&quot;;color:windowtext">I know a little about.<o:p></o:p></span><br>
      <span style="font-size:10.0pt;font-family:&quot;Courier
        New&quot;;color:windowtext"><o:p>&nbsp;</o:p></span><br>
      <span style="font-size:10.0pt;font-family:&quot;Courier
        New&quot;;color:windowtext">Al<o:p></o:p></span><br>
      <span style="font-size:10.0pt;font-family:&quot;Courier
        New&quot;;color:windowtext"><o:p>&nbsp;</o:p></span><br>
      <span style="font-size:10.0pt;font-family:&quot;Courier
        New&quot;;color:windowtext">-=-=-=-=-=-=-=-=-=-=-=-=-=-=-<o:p></o:p></span><br>
      <span style="font-size:10.0pt;font-family:&quot;Courier
        New&quot;;color:windowtext"><o:p>&nbsp;</o:p></span><br>
      <span style="font-size:10.0pt;font-family:&quot;Courier
        New&quot;;color:windowtext">1.1. The Building Blocks of OAM<o:p></o:p></span><br>
      <span style="font-size:10.0pt;font-family:&quot;Courier
        New&quot;;color:windowtext">...<o:p></o:p></span><br>
      <span style="font-size:10.0pt;font-family:&quot;Courier
        New&quot;;color:windowtext">&nbsp;&nbsp; o Performance Monitoring:<o:p></o:p></span><br>
      <span style="font-size:10.0pt;font-family:&quot;Courier
        New&quot;;color:windowtext">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Consists of 3 main functions<o:p></o:p></span><br>
      <span style="font-size:10.0pt;font-family:&quot;Courier
        New&quot;;color:windowtext"><o:p>&nbsp;</o:p></span><br>
      <span style="font-size:10.0pt;font-family:&quot;Courier
        New&quot;;color:windowtext">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; o Loss Measurement (LM) -
        monitors the packet loss rate of a<o:p></o:p></span><br>
      <span style="font-size:10.0pt;font-family:&quot;Courier
        New&quot;;color:windowtext">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; connection.<o:p></o:p></span><br>
      <span style="font-size:10.0pt;font-family:&quot;Courier
        New&quot;;color:windowtext"><o:p>&nbsp;</o:p></span><br>
      <span style="font-size:10.0pt;font-family:&quot;Courier
        New&quot;;color:windowtext">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; o Delay Measurement (DM) -
        monitors the delay and delay<o:p></o:p></span><br>
      <span style="font-size:10.0pt;font-family:&quot;Courier
        New&quot;;color:windowtext">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; variation between MPs.<o:p></o:p></span><br>
      <span style="font-size:10.0pt;font-family:&quot;Courier
        New&quot;;color:windowtext"><o:p>&nbsp;</o:p></span><br>
      <span style="font-size:10.0pt;font-family:&quot;Courier
        New&quot;;color:windowtext">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; o Throughput measurement -
        monitors the throughput of a<o:p></o:p></span><br>
      <span style="font-size:10.0pt;font-family:&quot;Courier
        New&quot;;color:windowtext">&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;connection.<o:p></o:p></span><br>
      <span style="font-size:10.0pt;font-family:&quot;Courier
        New&quot;;color:windowtext"><o:p>&nbsp;</o:p></span><br>
      <span style="font-size:10.0pt;font-family:&quot;Courier
        New&quot;;color:windowtext">&gt;&gt;&gt; Apparently, no OAM tool
        currently measures Throughput, <o:p></o:p></span><br>
      <span style="font-size:10.0pt;font-family:&quot;Courier
        New&quot;;color:windowtext">&nbsp;&nbsp;&nbsp;&nbsp;because no such tool is cited in
        the memo (and the term &#8220;throughput&#8221;<o:p></o:p></span><br>
      <span style="font-size:10.0pt;font-family:&quot;Courier
        New&quot;;color:windowtext">&nbsp;&nbsp;&nbsp; never appears again). &nbsp;my guess
        is that there was some reference to<o:p></o:p></span><br>
      <span style="font-size:10.0pt;font-family:&quot;Courier
        New&quot;;color:windowtext">&nbsp;&nbsp;&nbsp; RFC 2544 that has now been
        removed. Remove Throughput from the list.<o:p></o:p></span><br>
      <span style="font-size:10.0pt;font-family:&quot;Courier
        New&quot;;color:windowtext"><o:p>&nbsp;</o:p></span><br>
      <span style="font-size:10.0pt;font-family:&quot;Courier
        New&quot;;color:windowtext">1.3 OAM Toolsets<o:p></o:p></span><br>
      <span style="font-size:10.0pt;font-family:&quot;Courier
        New&quot;;color:windowtext">... <o:p></o:p></span><br>
      <span style="font-size:10.0pt;font-family:&quot;Courier
        New&quot;;color:windowtext">&nbsp;&nbsp;&nbsp;o OWAMP and TWAMP:<o:p></o:p></span><br>
      <span style="font-size:10.0pt;font-family:&quot;Courier
        New&quot;;color:windowtext">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; The One Way Active Measurement
        Protocol (OWAMP) and the Two Way<o:p></o:p></span><br>
      <span style="font-size:10.0pt;font-family:&quot;Courier
        New&quot;;color:windowtext">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Active Measurement Protocols
        (TWAMP) are two protocols defined in<o:p></o:p></span><br>
      <span style="font-size:10.0pt;font-family:&quot;Courier
        New&quot;;color:windowtext">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the IP Performance Metrics
        (IPPM) working group in the IETF. These<o:p></o:p></span><br>
      <span style="font-size:10.0pt;font-family:&quot;Courier
        New&quot;;color:windowtext">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; protocols allow delay and
        packet loss measurement in IP networks.<o:p></o:p></span><br>
      <span style="font-size:10.0pt;font-family:&quot;Courier
        New&quot;;color:windowtext"><o:p>&nbsp;</o:p></span><br>
      <span style="font-size:10.0pt;font-family:&quot;Courier
        New&quot;;color:windowtext">&gt;&gt;&gt; and Delay variation,
        duplication, reordering, etc. (all the metrics limited tools<o:p></o:p></span><br>
      <span style="font-size:10.0pt;font-family:&quot;Courier
        New&quot;;color:windowtext">&nbsp;&nbsp;&nbsp; completely ignore). <o:p></o:p></span><br>
      <span style="font-size:10.0pt;font-family:&quot;Courier
        New&quot;;color:windowtext"><o:p>&nbsp;</o:p></span><br>
      <span style="font-size:10.0pt;font-family:&quot;Courier
        New&quot;;color:windowtext">1.4 IETF OAM Documents<o:p></o:p></span><br>
      <span style="font-size:10.0pt;font-family:&quot;Courier
        New&quot;;color:windowtext"><o:p>&nbsp;</o:p></span><br>
      <span style="font-size:10.0pt;font-family:&quot;Courier
        New&quot;;color:windowtext">&gt;&gt;&gt; Expand Table 1 as noted
        above, to include all the metrics they missed.<o:p></o:p></span><br>
      <span style="font-size:10.0pt;font-family:&quot;Courier
        New&quot;;color:windowtext"><o:p>&nbsp;</o:p></span><br>
      <span style="font-size:10.0pt;font-family:&quot;Courier
        New&quot;;color:windowtext"><o:p>&nbsp;</o:p></span><br>
      <span style="font-size:10.0pt;font-family:&quot;Courier
        New&quot;;color:windowtext">3.6.1<o:p></o:p></span><br>
      <span style="font-size:10.0pt;font-family:&quot;Courier
        New&quot;;color:windowtext">...<o:p></o:p></span><br>
      <span style="font-size:10.0pt;font-family:&quot;Courier
        New&quot;;color:windowtext">&nbsp;&nbsp; TWAMP [TWAMP] is a similar
        protocol that enables measurement of <o:p></o:p></span><br>
      <span style="font-size:10.0pt;font-family:&quot;Courier
        New&quot;;color:windowtext">&gt;&gt;&gt; both one-way and <o:p></o:p></span><br>
      <span style="font-size:10.0pt;font-family:&quot;Courier
        New&quot;;color:windowtext">&nbsp;&nbsp;&nbsp;two-way (round trip)
        characteristics.&nbsp; <o:p></o:p></span><br>
      <span style="font-size:10.0pt;font-family:&quot;Courier
        New&quot;;color:windowtext"><o:p>&nbsp;</o:p></span><br>
      <span style="font-size:10.0pt;font-family:&quot;Courier
        New&quot;;color:windowtext">&gt;&gt;&gt; sentence below is
        simply not true, because the authors did not understand<o:p></o:p></span><br>
      <span style="font-size:10.0pt;font-family:&quot;Courier
        New&quot;;color:windowtext">&nbsp;&nbsp; the one-way measurement
        capability:<o:p></o:p></span><br>
      <span style="font-size:10.0pt;font-family:&quot;Courier
        New&quot;;color:windowtext">&nbsp;&nbsp; TWAMP does not require accurate<o:p></o:p></span><br>
      <span style="font-size:10.0pt;font-family:&quot;Courier
        New&quot;;color:windowtext">&nbsp;&nbsp; time of day, and, furthermore,
        allows the use of a simple session<o:p></o:p></span><br>
      <span style="font-size:10.0pt;font-family:&quot;Courier
        New&quot;;color:windowtext">&nbsp;&nbsp; reflector, making it an
        attractive alternative to OWAMP.<o:p></o:p></span><br>
      <span style="font-size:10.0pt;font-family:&quot;Courier
        New&quot;;color:windowtext">&gt;&gt;&gt; go back and read the
        memo...<o:p></o:p></span><br>
      <span style="font-size:10.0pt;font-family:&quot;Courier
        New&quot;;color:windowtext"><o:p>&nbsp;</o:p></span><br>
      <span style="font-size:10.0pt;font-family:&quot;Courier
        New&quot;;color:windowtext"><o:p>&nbsp;</o:p></span><br>
      <span style="font-size:10.0pt;font-family:&quot;Courier
        New&quot;;color:windowtext">3.7. Summary of OAM Functions<o:p></o:p></span><br>
      <span style="font-size:10.0pt;font-family:&quot;Courier
        New&quot;;color:windowtext"><o:p>&nbsp;</o:p></span><br>
      <span style="font-size:10.0pt;font-family:&quot;Courier
        New&quot;;color:windowtext">&nbsp;&nbsp; Table 3 summarizes the OAM
        functions that are supported in each of<o:p></o:p></span><br>
      <span style="font-size:10.0pt;font-family:&quot;Courier
        New&quot;;color:windowtext">&nbsp;&nbsp; the categories that were analyzed
        in this section.<o:p></o:p></span><br>
      <span style="font-size:10.0pt;font-family:&quot;Courier
        New&quot;;color:windowtext"><o:p>&nbsp;</o:p></span><br>
      <span style="font-size:10.0pt;font-family:&quot;Courier
        New&quot;;color:windowtext">&nbsp;&nbsp;
        +-----------+-------+--------+--------+-----------+-------+--------+<o:p></o:p></span><br>
      <span style="font-size:10.0pt;font-family:&quot;Courier
        New&quot;;color:windowtext">&nbsp;&nbsp; | Standard&nbsp;
        |Continu|Connecti|Path&nbsp;&nbsp;&nbsp; |Defect&nbsp;&nbsp;&nbsp;&nbsp; |Perform|Other&nbsp;&nbsp; |<o:p></o:p></span><br>
      <span style="font-size:10.0pt;font-family:&quot;Courier
        New&quot;;color:windowtext">&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |ity&nbsp;&nbsp;&nbsp; |vity&nbsp;&nbsp;&nbsp;
        |Discover|Indications|ance&nbsp;&nbsp; |Function|<o:p></o:p></span><br>
      <span style="font-size:10.0pt;font-family:&quot;Courier
        New&quot;;color:windowtext">&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |Check&nbsp;
        |Verifica|y&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |Monitor|s&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |<o:p></o:p></span><br>
      <span style="font-size:10.0pt;font-family:&quot;Courier
        New&quot;;color:windowtext">&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |tion&nbsp;&nbsp;&nbsp;
        |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |ing&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |<o:p></o:p></span><br>
      <span style="font-size:10.0pt;font-family:&quot;Courier
        New&quot;;color:windowtext">&nbsp;&nbsp;
        +-----------+-------+--------+--------+-----------+-------+--------+<o:p></o:p></span><br>
      <span style="font-size:10.0pt;font-family:&quot;Courier
        New&quot;;color:windowtext">...<o:p></o:p></span><br>
      <span style="font-size:10.0pt;font-family:&quot;Courier
        New&quot;;color:windowtext">&nbsp;&nbsp; + --------- + ----- + ------ +
        ------ + --------- + ----- + ------ +<o:p></o:p></span><br>
      <span style="font-size:10.0pt;font-family:&quot;Courier
        New&quot;;color:windowtext">&nbsp;&nbsp; |OWAMP and&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
        |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |-Delay |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |<o:p></o:p></span><br>
      <span style="font-size:10.0pt;font-family:&quot;Courier
        New&quot;;color:windowtext">&nbsp;&nbsp; |TWAMP&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp; Yes&nbsp; |&nbsp; Yes&nbsp;&nbsp;
        |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; | measur|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |<o:p></o:p></span><br>
      <span style="font-size:10.0pt;font-family:&quot;Courier
        New&quot;;color:windowtext">&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
        |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; | ement |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |<o:p></o:p></span><br>
      <span style="font-size:10.0pt;font-family:&quot;Courier
        New&quot;;color:windowtext">&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
        |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |-Packet|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |<o:p></o:p></span><br>
      <span style="font-size:10.0pt;font-family:&quot;Courier
        New&quot;;color:windowtext">&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
        |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; | loss&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |<o:p></o:p></span><br>
      <span style="font-size:10.0pt;font-family:&quot;Courier
        New&quot;;color:windowtext">&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
        |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; | measur|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |<o:p></o:p></span><br>
      <span style="font-size:10.0pt;font-family:&quot;Courier
        New&quot;;color:windowtext">&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
        |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; | ement |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |<o:p></o:p></span><br>
      <span style="font-size:10.0pt;font-family:&quot;Courier
        New&quot;;color:windowtext">&nbsp;&nbsp;
        +-----------+-------+--------+--------+-----------+-------+--------+<o:p></o:p></span><br>
      <span style="font-size:10.0pt;font-family:&quot;Courier
        New&quot;;color:windowtext">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Table 3 Summary
        of OAM Functions<o:p></o:p></span><br>
      <span style="font-size:10.0pt;font-family:&quot;Courier
        New&quot;;color:windowtext"><o:p>&nbsp;</o:p></span><br>
      <span style="font-size:10.0pt;font-family:&quot;Courier
        New&quot;;color:windowtext">&gt;&gt;&gt; Both Continuity Check
        and Connectivity Verification are tested and<o:p></o:p></span><br>
      <span style="font-size:10.0pt;font-family:&quot;Courier
        New&quot;;color:windowtext">confirmed by establishing the *WAMP
        Control Protocol TCP connection,<o:p></o:p></span><br>
      <span style="font-size:10.0pt;font-family:&quot;Courier
        New&quot;;color:windowtext">so this should be indicated the
        table.</span><br>
      <br>
      <br>
    </div>
    <blockquote cite="mid:50F437BF.8040005@cisco.com" type="cite">
      <meta content="text/html; charset=ISO-8859-1"
        http-equiv="Content-Type">
      <div class="moz-cite-prefix">draft-ietf-opsawg-oam-overview
        authors,<br>
        <br>
        Here is my feedback on this document.<br>
        <br>
        1.<br>
        Is this document in line with <a moz-do-not-send="true"
          class="moz-txt-link-freetext"
          href="http://tools.ietf.org/html/draft-ietf-trill-oam-req-04">http://tools.ietf.org/html/draft-ietf-trill-oam-req-04</a>?
        <br>
        * For example, the following definitions could be reused.<br>
        <pre class="newpage">   Fault: The term Fault refers to an inability to perform a required
   action, e.g., an unsuccessful attempt to deliver a packet.

   Defect: The term Defect refers to an interruption in the normal
   operation, such that over a period of time no packets are delivered
   successfully.

   Failure: The term Failure refers to the termination of the required
   function over a longer period of time. Persistence of a defect for a
   period of time is interpreted as a failure.

* For example, on the basic abstract 
Abstract

   Operations, Administration, and Maintenance (OAM) is a general term
   that refers to a toolset that can be used for fault detection and
   isolation, and for performance measurement. OAM mechanisms have been
   defined for various layers in the protocol stack, and are used with a
   variety of protocols.

Abstract (draft-ietf-trill-oam-req-04)

   OAM (Operations, Administration and Maintenance) is a general term
   used to identify functions and toolsets to troubleshoot and monitor
   networks. This document presents, OAM Requirements applicable to
   TRILL. 

So, as an example: does OAM include function? 
I advice to review draft-ietf-trill-oam-req-04

2. 
draft-ietf-trill-oam is not mentioned, while the abstract mentions:
   This document presents an overview of the OAM mechanisms that have
   been defined and are currently being defined by the IETF.
Search for OAM in the current draft names (<a moz-do-not-send="true" class="moz-txt-link-freetext" href="https://datatracker.ietf.org/">https://datatracker.ietf.org/</a>), and you will find many references.
Ok, I see later on:	
   This document focuses on IETF
   documents that have been published as RFCs, while other ongoing OAM-
   related work is outside the scope.
Ok, fine then: we don't need a reference to all the drafts. 
However, draft-ietf-trill-oam is closed to be a RFC, and should be mentioned.


3.
Section 1
   The term OAM in this document refers to Operations, Administration
   and Maintenance [<a moz-do-not-send="true" href="http://tools.ietf.org/html/draft-ietf-opsawg-oam-overview-08#ref-OAM-Def" title="&quot;Guidelines for the use of the OAM acronym in the IETF &quot;">OAM-Def</a>], focusing on the forwarding plane of OAM.
What does it mean "focusing on the forwarding plane of OAM"?
Do you take a subset of the definition for this document?
Btw, I don't see a definition in the terminology section.
In section 2.2.3
   A Maintenance Point (MP) is a functional entity that is defined at a
   node in the network, and either initiates or reacts to OAM messages.
Which plane is MP?

4.
Section 1, Introduction
"Hence, management aspects are outside the scope of this document."
I don't understand which management aspects we speak about here.
</pre>
        5.<br>
        Clarifying question regarding 1.2<br>
        If speak about OWAMP or TWAMP 'synthetic traffic), is that data
        plane, control plane, or management plane?<br>
        Note that I found later on in the draft:<br>
        <pre class="newpage">   OWAMP and TWAMP use two separate protocols: a Control plane protocol,
   and a Test plane protocol.</pre>
        Interestingly enough, after reading the document, I reviewed <a
          moz-do-not-send="true" class="moz-txt-link-freetext"
href="http://datatracker.ietf.org/doc/draft-ietf-opsawg-oam-overview/ballot/">http://datatracker.ietf.org/doc/draft-ietf-opsawg-oam-overview/ballot/</a>,
        and saw the same feedback from Stewart Bryant:<br>
        <blockquote>
          <pre>Provide a clear view of OAM functionality and its relationship
to various &#8220;planes&#8221; of networking (data plane, control plane,
management plane). In particular, the importance of
fate-sharing of OAM and user traffic flows in packet networks
should be explained.</pre>
        </blockquote>
        6.<br>
        <pre class="newpage">I see a multiplication of "plane" terms in the IETF document, and in this document in particular.
I could find: forwarding plane, management plane, control plane, data plane, user plane, and test plane.
Way too many.
Please be consistent
</pre>
        7.<br>
        <pre class="newpage">   Table 1 summarizes the IETF OAM related RFCs discussed in this
   document.

   Table 2 summarizes the OAM standards mentioned in this document. 

You need to change the Table 2 description. Do you want to say something along the lines of:
   Table 2 summarizes the OAM standards specified by other Standard Development Organization 
   (SDO) than the IETF, along with IETF references where applicable.


8.
Section 2.2.1
   For a formal definition of each term, refer to the references at the end of
   this document.
Without a reference to a specific RFC, this is the type of statement which is not useful: you have 5 pages of references.
You position this document as "An Overview of<span class="h1"></span> Operations, Administration, and Maintenance (OAM) Mechanisms<span class="h1"></span>", but you tell the reader: "if you want to know about the terms,
just read first all references!"

9.
You specify some terms and some OAM categories, 
   <a moz-do-not-send="true" href="http://tools.ietf.org/html/draft-ietf-opsawg-oam-overview-08#section-2.2.2">2.2.2</a>. OAM Maintenance Entities .......................... <a moz-do-not-send="true" href="http://tools.ietf.org/html/draft-ietf-opsawg-oam-overview-08#page-13">13</a>
         <a moz-do-not-send="true" href="http://tools.ietf.org/html/draft-ietf-opsawg-oam-overview-08#section-2.2.3">2.2.3</a>. OAM Maintenance Points ............................ <a moz-do-not-send="true" href="http://tools.ietf.org/html/draft-ietf-opsawg-oam-overview-08#page-14">14</a>
         <a moz-do-not-send="true" href="http://tools.ietf.org/html/draft-ietf-opsawg-oam-overview-08#section-2.2.4">2.2.4</a>. Proactive and On-demand activation ................ <a moz-do-not-send="true" href="http://tools.ietf.org/html/draft-ietf-opsawg-oam-overview-08#page-15">15</a>
         <a moz-do-not-send="true" href="http://tools.ietf.org/html/draft-ietf-opsawg-oam-overview-08#section-2.2.5">2.2.5</a>. Connectivity Verification and Continuity Checks ... <a moz-do-not-send="true" href="http://tools.ietf.org/html/draft-ietf-opsawg-oam-overview-08#page-15">15</a>
         <a moz-do-not-send="true" href="http://tools.ietf.org/html/draft-ietf-opsawg-oam-overview-08#section-2.2.6">2.2.6</a>. Failures .......................................... <a moz-do-not-send="true" href="http://tools.ietf.org/html/draft-ietf-opsawg-oam-overview-08#page-15">15</a>
... but you don't use them in the section 3

Just <u>one </u>example with section 3.2.2
-
   o Demand mode: in this mode, BFD control packets are sent on-demand.
      Upon need, a system initiates a series of BFD control packets to
      verify the liveness of the session
Instead of liveness, you have defined Connectivity Verification and Continuity Checks<span class="h4"></span> in section 2.2.5
- OLD:
   Each of the end-points of the monitored path maintains its own
   session identification
NEW:
   Each of the MEP maintains its own session identification
OR NEW (actually I don't know)
   Each of the MP maintains its own session identification
- OLD
	A BFD echo packet is sent to a peer system
Peer system = MEP, MP, or something else?
- etc... 

10. 
This document is composed of a list of OAM content and references, but I'm really missing the document "scope and target audience".
When we did RFC 6632, which is the companion document, we had <a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://tools.ietf.org/html/rfc6632#section-1.1">http://tools.ietf.org/html/rfc6632#section-1.1</a>
&nbsp;
   The target audience of the document is, on the one hand, IETF working
   groups, which aim to select appropriate standard management protocols
   and data models to address their needs concerning network management.
   On the other hand, the document can be used as an overview and
   guideline by non-IETF Standards Development Organizations (SDOs)
   planning to use IETF management technologies and data models for the
   realization of management applications.  The document can also be
   used to initiate a discussion between the bodies with the goal to
   gather new requirements and to detect possible gaps.  Finally, this
   document is directed to all interested parties that seek to get an
   overview of the current set of the IETF network management protocols
   such as network administrators or newcomers to the IETF.

You should have something similar.


11.
Section 3.6.1, put the paragraph 2 at the end of the section. The "alternative" in the following sentence would then make sense
   Alternative protocols for performance measurement are defined, for
   example, in MPLS-TP OAM ([<a moz-do-not-send="true" href="http://tools.ietf.org/html/draft-ietf-opsawg-oam-overview-08#ref-MPLS-LM-DM" title="&quot;Packet Loss and Delay Measurement for MPLS Networks&quot;">MPLS-LM-DM</a>], [<a moz-do-not-send="true" href="http://tools.ietf.org/html/draft-ietf-opsawg-oam-overview-08#ref-TP-LM-DM" title="&quot;A Packet Loss and Delay Measurement Profile for MPLS-Based Transport Networks&quot;">TP-LM-DM</a>]), and in Ethernet
   OAM [<a moz-do-not-send="true" href="http://tools.ietf.org/html/draft-ietf-opsawg-oam-overview-08#ref-ITU-T-Y1731" title="&quot;OAM Functions and Mechanisms for Ethernet-based Networks&quot;">ITU-T-Y1731</a>].


My conclusions: this document still needs some work

Regards, Benoit
&nbsp;
</pre>
      </div>
      <blockquote
        cite="mid:20130111193616.19158.16205.idtracker@ietfa.amsl.com"
        type="cite">
        <pre wrap="">The IESG has received a request from the Operations and Management Area
Working Group WG (opsawg) to consider the following document:
- 'An Overview of Operations, Administration, and Maintenance (OAM)
   Mechanisms'
  &lt;draft-ietf-opsawg-oam-overview-08.txt&gt; as Informational RFC

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action. Please send substantive comments to the
<a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:ietf@ietf.org">ietf@ietf.org</a> mailing lists by 2013-01-25. Exceptionally, comments may be
sent to <a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:iesg@ietf.org">iesg@ietf.org</a> instead. In either case, please retain the
beginning of the Subject line to allow automated sorting.

Abstract


   Operations, Administration, and Maintenance (OAM) is a general term
   that refers to a toolset that can be used for fault detection and
   isolation, and for performance measurement. OAM mechanisms have been
   defined for various layers in the protocol stack, and are used with a
   variety of protocols.

   This document presents an overview of the OAM mechanisms that have
   been defined and are currently being defined by the IETF.




The file can be obtained via
<a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://datatracker.ietf.org/doc/draft-ietf-opsawg-oam-overview/">http://datatracker.ietf.org/doc/draft-ietf-opsawg-oam-overview/</a>

IESG discussion can be tracked via
<a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://datatracker.ietf.org/doc/draft-ietf-opsawg-oam-overview/ballot/">http://datatracker.ietf.org/doc/draft-ietf-opsawg-oam-overview/ballot/</a>


No IPR declarations have been submitted directly on this I-D.



</pre>
      </blockquote>
      <br>
    </blockquote>
    <br>
  </body>
</html>

--------------090504060000040407050407--

From ron.even.tlv@gmail.com  Tue Jan 15 10:41:02 2013
Return-Path: <ron.even.tlv@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B5A8111E809C; Tue, 15 Jan 2013 10:41:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.598
X-Spam-Level: 
X-Spam-Status: No, score=-3.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
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 d3aIB-CXFGa2; Tue, 15 Jan 2013 10:41:01 -0800 (PST)
Received: from mail-ee0-f44.google.com (mail-ee0-f44.google.com [74.125.83.44]) by ietfa.amsl.com (Postfix) with ESMTP id C547A11E809A; Tue, 15 Jan 2013 10:41:00 -0800 (PST)
Received: by mail-ee0-f44.google.com with SMTP id l10so236861eei.31 for <multiple recipients>; Tue, 15 Jan 2013 10:40:59 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:from:to:subject:date:message-id:mime-version :content-type:x-mailer:thread-index:content-language; bh=WKPDju+JPCbM83W2GVLoz8IfSkjLl39OmKuzDC8BWuc=; b=vK6bjl9uZdS8+/nutD9TO4C3Ohg4mxuG1JaY3WnhG3F3oK/t+HqrYIF0yoPbdj6HPR G0H6Aw2aIuu9mbG4TbklkUDgPywQ5qRv3va5rNWuWcn3ooslmbl+orlIW3lNom1zJ0jr y7xrDRa5I12MaEHzu0VLya4crc4X1w5Gh75R6cv4f4t6HUWKda8aZVN2vajoJSY6LUbs mF6QgUwJegg7q0t/8fM7tsgEwILMM1DJdCA1t89mBYilD2tCVTZoBj/CVItIajczVpn4 HxQNOwMQvbfEiQ73g7IryHaPKc0sQnojftCKIz9/qlbfw+jAkK+Ableeny2n+sb46wsI udsg==
X-Received: by 10.14.216.70 with SMTP id f46mr244159636eep.12.1358275259605; Tue, 15 Jan 2013 10:40:59 -0800 (PST)
Received: from RoniE ([109.66.27.172]) by mx.google.com with ESMTPS id q44sm26658616eep.5.2013.01.15.10.40.56 (version=TLSv1 cipher=RC4-SHA bits=128/128); Tue, 15 Jan 2013 10:40:58 -0800 (PST)
From: "Roni Even" <ron.even.tlv@gmail.com>
To: <draft-ietf-rmt-fcast.all@tools.ietf.org>, <ietf@ietf.org>, <gen-art@ietf.org>
Subject: GenART LC review of draft-ietf-rmt-fcast-07
Date: Tue, 15 Jan 2013 20:38:06 +0200
Message-ID: <032b01cdf34f$7714f300$653ed900$@gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_032C_01CDF360.3A9E8650"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: Ac3zT0ZtllB8hJOVSo65/X34kqqtaw==
Content-Language: en-us
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Jan 2013 18:41:02 -0000

This is a multipart message in MIME format.

------=_NextPart_000_032C_01CDF360.3A9E8650
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

I am the assigned Gen-ART reviewer for this draft. For background on
Gen-ART, please see the FAQ at
<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

 

Please resolve these comments along with any other Last Call comments you
may receive.

 

Document: draft-ietf-rmt-fcast-07

Reviewer: Roni Even

Review Date:2013-1-15

IETF LC End Date: 2013-1-22

IESG Telechat date: 

 

Summary: This draft is almost ready for publication as Standard track RFC.

 

 

Major issues:

 

Minor issues:

 

1.       I had some problem when reading the document about what is
mandatory to support. The distinction between what is  required to be
supported and used is mentioned in section 5. Also section 3.3 discusses
what compliant implementation is, but section 5 provides the full
information. I think that it will be better to move section 5 before or at
the beginning of section 3 or as part of  3.3.  no need to have the
information twice.

2.       In section 3.3 "The support of GZIP encoding, or any other
solution, remains optional." I think that support is mandatory. 

 

 

Nits/editorial comments:

1.	In section 5.1 at the end of first table "in-bound" should be
"in-band"
2.	In section 6 in the paragraph after the bullet points "possibly
possibly"
3.	In section 7 "This specification requires IANA to create two new
registries" I think there are three new registries.
4.	In section 7.1 second paragraph "registry registry"

 


------=_NextPart_000_032C_01CDF360.3A9E8650
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><META =
HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 14 =
(filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin-top:0in;
	margin-right:0in;
	margin-bottom:10.0pt;
	margin-left:0in;
	line-height:115%;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.5pt;
	font-family:Consolas;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:Consolas;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:400056174;
	mso-list-type:hybrid;
	mso-list-template-ids:-253189604 67698703 67698713 67698715 67698703 =
67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level2
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level3
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l0:level4
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level5
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level6
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l0:level7
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level8
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level9
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l1
	{mso-list-id:1143233528;
	mso-list-type:hybrid;
	mso-list-template-ids:-863498940 67698703 67698713 67698715 67698703 =
67698713 67698715 67698703 67698713 67698715;}
@list l1:level1
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level2
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level3
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l1:level4
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level5
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level6
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l1:level7
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level8
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level9
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><a =
name=3D"OLE_LINK1"></a><a name=3D"OLE_LINK2">I am the assigned Gen-ART =
reviewer for this draft. For background on Gen-ART, please see the FAQ =
at &lt;</a><a =
href=3D"http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq" =
target=3D"_blank">http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq=
</a>&gt;.<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal>Please resolve these comments along with any other =
Last Call comments you may receive.<o:p></o:p></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Document: =
</span><span style=3D'font-family:"Courier =
New"'>draft-ietf-rmt-fcast-07</span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p></o:p>=
</span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Reviewer: =
Roni Even<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Review =
Date:2013&#8211;1&#8211;15<o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>IETF LC =
End Date: 2013-1&#8211;22<o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>IESG =
Telechat date: <o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Summary: =
This draft is almost ready for publication as Standard track =
RFC</span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>.<o:p></o:p=
></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Major =
issues:<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Minor =
issues:<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText =
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 =
lfo1'><![if !supportLists]><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><span =
style=3D'mso-list:Ignore'>1.<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span></span><![endif]><span dir=3DLTR></span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>I had some =
problem when reading the document about what is mandatory to support. =
The distinction between what is &nbsp;required to be &nbsp;supported and =
used is mentioned in section 5. Also section 3.3 discusses what =
compliant implementation is, but section 5 provides the full =
information. I think that it will be better to move section 5 before or =
at the beginning of section 3 or as part of &nbsp;3.3. &nbsp;no need to =
have the information twice.<o:p></o:p></span></p><p class=3DMsoPlainText =
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 =
lfo1'><![if !supportLists]><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><span =
style=3D'mso-list:Ignore'>2.<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span></span><![endif]><span dir=3DLTR></span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>In section =
3.3 &#8220;</span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>The =
support of GZIP encoding, or any other solution, remains =
optional.&#8221; I think that support is mandatory. =
<o:p></o:p></span></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoNormal>Nits/editorial =
comments:<o:p></o:p></p><ol style=3D'margin-top:0in' start=3D1 =
type=3D1><li class=3DMsoNormal style=3D'mso-list:l1 level1 lfo2'>In =
section 5.1 at the end of first table &#8220;in-bound&#8221; should be =
&#8220;in-band&#8221;<o:p></o:p></li><li class=3DMsoNormal =
style=3D'mso-list:l1 level1 lfo2'>In section 6 in the paragraph after =
the bullet points &#8220;possibly possibly&#8221;<o:p></o:p></li><li =
class=3DMsoNormal style=3D'mso-list:l1 level1 lfo2'>In section 7 =
&#8220;This specification requires IANA to create two new =
registries&#8221; I think there are three new =
registries.<o:p></o:p></li><li class=3DMsoNormal style=3D'mso-list:l1 =
level1 lfo2'>In section 7.1 second paragraph &#8220;registry =
registry&#8221;<o:p></o:p></li></ol><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></body></html>
------=_NextPart_000_032C_01CDF360.3A9E8650--


From aldrin.ietf@gmail.com  Tue Jan 15 10:59:13 2013
Return-Path: <aldrin.ietf@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C913811E80C5; Tue, 15 Jan 2013 10:59:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.202
X-Spam-Level: 
X-Spam-Status: No, score=-2.202 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=1.396, RCVD_IN_DNSWL_LOW=-1]
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 jtXkx3joNYtw; Tue, 15 Jan 2013 10:59:11 -0800 (PST)
Received: from mail-pa0-f51.google.com (mail-pa0-f51.google.com [209.85.220.51]) by ietfa.amsl.com (Postfix) with ESMTP id 8B29921F8551; Tue, 15 Jan 2013 10:59:11 -0800 (PST)
Received: by mail-pa0-f51.google.com with SMTP id fb11so276772pad.38 for <multiple recipients>; Tue, 15 Jan 2013 10:59:11 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:content-type:mime-version:subject:from:in-reply-to:date :cc:message-id:references:to:x-mailer; bh=YzcBT5nLQNXMdXo/5/4ZUbNMNo6Wub6c0o4Qk87HyGw=; b=rUxbVUmWxq0lmZP/zbFIax/LFnTIMRRiTwBarm2rl5qJmLmvhm6EXX/HEDzzR5caOP f2/obixcuh9kdtb7AOcwF2Zonj72DCJNwgWcIb6/n0WwBuiC+jEf5u64a1c7t7lxRjZc 1nTBIVn0oBQEZJtkiYI95IOdVJLST1Gpzid2snbiG/h5efS3ygpUUA8BWABzchHYVhR9 LvxsAI7bLtQGcC/Mb9lI1vGXO/VXWkeN1Z5rK8qwN3ZykjfQlCEH7JrfBp7Vn7EHS6Nz MNyTBFfqk8ZkSs4QTA76tl6+Vh1pLBbjrs8BebeoyC0CTtH7MUnH/ndrbJ6RwyNbM7Ag oDLw==
X-Received: by 10.69.1.73 with SMTP id be9mr271540385pbd.116.1358276351087; Tue, 15 Jan 2013 10:59:11 -0800 (PST)
Received: from [192.168.1.5] (c-98-248-237-85.hsd1.ca.comcast.net. [98.248.237.85]) by mx.google.com with ESMTPS id p10sm11309189pax.27.2013.01.15.10.59.08 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 15 Jan 2013 10:59:10 -0800 (PST)
Content-Type: multipart/alternative; boundary="Apple-Mail=_0CA0F3E7-DA67-4945-AAF7-F63024E8843F"
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Subject: Re: Last Call: <draft-ietf-opsawg-oam-overview-08.txt> (An Overview of Operations, Administration, and Maintenance (OAM) Mechanisms) to Informational RFC
From: Sam Aldrin <aldrin.ietf@gmail.com>
In-Reply-To: <50F56C49.6090103@cisco.com>
Date: Tue, 15 Jan 2013 10:59:07 -0800
Message-Id: <9AFD354D-2EF4-4541-9473-BF2A99784406@gmail.com>
References: <20130111193616.19158.16205.idtracker@ietfa.amsl.com> <50F437BF.8040005@cisco.com> <50F56C49.6090103@cisco.com>
To: Benoit Claise <bclaise@cisco.com>
X-Mailer: Apple Mail (2.1499)
Cc: "draft-ietf-opsawg-oam-overview@tools.ietf.org" <draft-ietf-opsawg-oam-overview@tools.ietf.org>, Al Morton <acmorton@att.com>, opsawg@ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Jan 2013 18:59:13 -0000

--Apple-Mail=_0CA0F3E7-DA67-4945-AAF7-F63024E8843F
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252

Here are my comments.

#1
1.1. The Building Blocks of OAM

   An OAM protocol is run in the context of a Maintenance Domain,
   consisting of two or more nodes that run the OAM protocol, referred
   to as Maintenance Points (MP).
%sam - I do not think that, MP, MEP, etc.,  terminology is used in OAM =
across different layers. It was introduced in MPLS-TP and later in =
TRILL, but prior to that, it is not. Is it the authors intention that =
this new terminology be used going forward?

#2
Sec 1.1 - An OAM protocol typically supports one or more of the
   tools described below.
%sam - what is OAM protocol? Shouldn't it be management plane OR OAM =
tools?

#3=20
Section 1.2 The considerations of the control-plane maintenance tools or =
the
   functionality of the management-plane are out of scope for this
   document, which will concentrate on presenting the forwarding-plane
   tools that are used for OAM.
%sam - Why is it out of scope? For example, checking consistency of =
control plane to forwarding plane is part of OAM or not?=20

#4
Section 1.3 The set of OAM
   mechanisms described in this memo are applicable to IP unicast, MPLS,
   pseudowires, and MPLS for the transport environment (MPLS-TP).
%sam - For ex: Is ATM OAM (RFC4717) within the scope of this draft? I =
did't see any mention of it or FR. I know that they are legacy, but =
still within IETF. One day even MPLS will be legacy protocol (just =
saying :D)

#5
Over all draft
%sam - I do not think this draft even considered 'multicast traffic'. =
There are rfc's in ever layer supporting multicast. There is no =
reference I could find. Ex: RFC6450, RFC6425 etc

#6
Sec 3.5=20
%sam - I think it is good to add details on different types of VCCV =
types of CC and CV and their use.=20

#7
General
%sam - Do you consider MIB part of OAM? Does Traps considered as error =
reporting or fault indication?

#8=20
Sec 3.4.3.8 and 9
%sam - Do these consider actual packet LM and DM or synthetic packets?=20=


#9=20
Section 4
%sam - I think this section should provide more details on what the =
general security issues are with OAM messages etc. And how they could be =
mitigated. For in-depth details, one could go into each of those =
documents.

#10
Sec 3.7
I do not think this is complete representation. For ex: no =
representation of multicast. BFD could be used for RDI, I think.=20

#11
IP Ping and Traceroute
%sam - When you say IP ping, does it imply ICMP ping or IP/UDP ping?


cheers
-sam
On Jan 15, 2013, at 6:48 AM, Benoit Claise <bclaise@cisco.com> wrote:

> Some more feedback, send on behalf of Al Morton.
>=20
> Regards, Benoit
>=20
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=

> Hi Benoit,
> =20
> Here are some additional comments, just checking a few things
> I know a little about.
> =20
> Al
> =20
> -=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-
> =20
> 1.1. The Building Blocks of OAM
> ...
>    o Performance Monitoring:
>       Consists of 3 main functions
> =20
>         o Loss Measurement (LM) - monitors the packet loss rate of a
>           connection.
> =20
>         o Delay Measurement (DM) - monitors the delay and delay
>           variation between MPs.
> =20
>         o Throughput measurement - monitors the throughput of a
>           connection.
> =20
> >>> Apparently, no OAM tool currently measures Throughput,=20
>     because no such tool is cited in the memo (and the term =
=93throughput=94
>     never appears again).  my guess is that there was some reference =
to
>     RFC 2544 that has now been removed. Remove Throughput from the =
list.
> =20
> 1.3 OAM Toolsets
> ...=20
>    o OWAMP and TWAMP:
>       The One Way Active Measurement Protocol (OWAMP) and the Two Way
>       Active Measurement Protocols (TWAMP) are two protocols defined =
in
>       the IP Performance Metrics (IPPM) working group in the IETF. =
These
>       protocols allow delay and packet loss measurement in IP =
networks.
> =20
> >>> and Delay variation, duplication, reordering, etc. (all the =
metrics limited tools
>     completely ignore).=20
> =20
> 1.4 IETF OAM Documents
> =20
> >>> Expand Table 1 as noted above, to include all the metrics they =
missed.
> =20
> =20
> 3.6.1
> ...
>    TWAMP [TWAMP] is a similar protocol that enables measurement of=20
> >>> both one-way and=20
>    two-way (round trip) characteristics. =20
> =20
> >>> sentence below is simply not true, because the authors did not =
understand
>    the one-way measurement capability:
>    TWAMP does not require accurate
>    time of day, and, furthermore, allows the use of a simple session
>    reflector, making it an attractive alternative to OWAMP.
> >>> go back and read the memo...
> =20
> =20
> 3.7. Summary of OAM Functions
> =20
>    Table 3 summarizes the OAM functions that are supported in each of
>    the categories that were analyzed in this section.
> =20
>    =
+-----------+-------+--------+--------+-----------+-------+--------+
>    | Standard  |Continu|Connecti|Path    |Defect     |Perform|Other   =
|
>    |           |ity    |vity    |Discover|Indications|ance   =
|Function|
>    |           |Check  |Verifica|y       |           |Monitor|s       =
|
>    |           |       |tion    |        |           |ing    |        =
|
>    =
+-----------+-------+--------+--------+-----------+-------+--------+
> ...
>    + --------- + ----- + ------ + ------ + --------- + ----- + ------ =
+
>    |OWAMP and  |       |        |        |           |-Delay |        =
|
>    |TWAMP      |  Yes  |  Yes   |        |           | measur|        =
|
>    |           |       |        |        |           | ement |        =
|
>    |           |       |        |        |           |-Packet|        =
|
>    |           |       |        |        |           | loss  |        =
|
>    |           |       |        |        |           | measur|        =
|
>    |           |       |        |        |           | ement |        =
|
>    =
+-----------+-------+--------+--------+-----------+-------+--------+
>                      Table 3 Summary of OAM Functions
> =20
> >>> Both Continuity Check and Connectivity Verification are tested and
> confirmed by establishing the *WAMP Control Protocol TCP connection,
> so this should be indicated the table.
>=20
>=20
>> draft-ietf-opsawg-oam-overview authors,
>>=20
>> Here is my feedback on this document.
>>=20
>> 1.
>> Is this document in line with =
http://tools.ietf.org/html/draft-ietf-trill-oam-req-04?=20
>> * For example, the following definitions could be reused.
>>    Fault: The term Fault refers to an inability to perform a required
>>    action, e.g., an unsuccessful attempt to deliver a packet.
>>=20
>>    Defect: The term Defect refers to an interruption in the normal
>>    operation, such that over a period of time no packets are =
delivered
>>    successfully.
>>=20
>>    Failure: The term Failure refers to the termination of the =
required
>>    function over a longer period of time. Persistence of a defect for =
a
>>    period of time is interpreted as a failure.
>>=20
>> * For example, on the basic abstract=20
>> Abstract
>>=20
>>    Operations, Administration, and Maintenance (OAM) is a general =
term
>>    that refers to a toolset that can be used for fault detection and
>>    isolation, and for performance measurement. OAM mechanisms have =
been
>>    defined for various layers in the protocol stack, and are used =
with a
>>    variety of protocols.
>>=20
>> Abstract (draft-ietf-trill-oam-req-04)
>>=20
>>    OAM (Operations, Administration and Maintenance) is a general term
>>    used to identify functions and toolsets to troubleshoot and =
monitor
>>    networks. This document presents, OAM Requirements applicable to
>>    TRILL.=20
>>=20
>> So, as an example: does OAM include function?=20
>> I advice to review draft-ietf-trill-oam-req-04
>>=20
>> 2.=20
>> draft-ietf-trill-oam is not mentioned, while the abstract mentions:
>>    This document presents an overview of the OAM mechanisms that have
>>    been defined and are currently being defined by the IETF.
>> Search for OAM in the current draft names =
(https://datatracker.ietf.org/), and you will find many references.
>> Ok, I see later on:=09
>>    This document focuses on IETF
>>    documents that have been published as RFCs, while other ongoing =
OAM-
>>    related work is outside the scope.
>> Ok, fine then: we don't need a reference to all the drafts.=20
>> However, draft-ietf-trill-oam is closed to be a RFC, and should be =
mentioned.
>>=20
>>=20
>> 3.
>> Section 1
>>    The term OAM in this document refers to Operations, Administration
>>    and Maintenance [OAM-Def], focusing on the forwarding plane of =
OAM.
>> What does it mean "focusing on the forwarding plane of OAM"?
>> Do you take a subset of the definition for this document?
>> Btw, I don't see a definition in the terminology section.
>> In section 2.2.3
>>    A Maintenance Point (MP) is a functional entity that is defined at =
a
>>    node in the network, and either initiates or reacts to OAM =
messages.
>> Which plane is MP?
>>=20
>> 4.
>> Section 1, Introduction
>> "Hence, management aspects are outside the scope of this document."
>> I don't understand which management aspects we speak about here.
>> 5.
>> Clarifying question regarding 1.2
>> If speak about OWAMP or TWAMP 'synthetic traffic), is that data =
plane, control plane, or management plane?
>> Note that I found later on in the draft:
>>    OWAMP and TWAMP use two separate protocols: a Control plane =
protocol,
>>    and a Test plane protocol.
>> Interestingly enough, after reading the document, I reviewed =
http://datatracker.ietf.org/doc/draft-ietf-opsawg-oam-overview/ballot/, =
and saw the same feedback from Stewart Bryant:
>> Provide a clear view of OAM functionality and its relationship
>> to various =93planes=94 of networking (data plane, control plane,
>> management plane). In particular, the importance of
>> fate-sharing of OAM and user traffic flows in packet networks
>> should be explained.
>> 6.
>> I see a multiplication of "plane" terms in the IETF document, and in =
this document in particular.
>> I could find: forwarding plane, management plane, control plane, data =
plane, user plane, and test plane.
>> Way too many.
>> Please be consistent
>> 7.
>>    Table 1 summarizes the IETF OAM related RFCs discussed in this
>>    document.
>>=20
>>    Table 2 summarizes the OAM standards mentioned in this document.=20=

>>=20
>> You need to change the Table 2 description. Do you want to say =
something along the lines of:
>>    Table 2 summarizes the OAM standards specified by other Standard =
Development Organization=20
>>    (SDO) than the IETF, along with IETF references where applicable.
>>=20
>>=20
>> 8.
>> Section 2.2.1
>>    For a formal definition of each term, refer to the references at =
the end of
>>    this document.
>> Without a reference to a specific RFC, this is the type of statement =
which is not useful: you have 5 pages of references.
>> You position this document as "An Overview of Operations, =
Administration, and Maintenance (OAM) Mechanisms", but you tell the =
reader: "if you want to know about the terms,
>> just read first all references!"
>>=20
>> 9.
>> You specify some terms and some OAM categories,=20
>>    2.2.2. OAM Maintenance Entities .......................... 13
>>          2.2.3. OAM Maintenance Points ............................ =
14
>>          2.2.4. Proactive and On-demand activation ................ =
15
>>          2.2.5. Connectivity Verification and Continuity Checks ... =
15
>>          2.2.6. Failures .......................................... =
15
>> ... but you don't use them in the section 3
>>=20
>> Just one example with section 3.2.2
>> -
>>    o Demand mode: in this mode, BFD control packets are sent =
on-demand.
>>       Upon need, a system initiates a series of BFD control packets =
to
>>       verify the liveness of the session
>> Instead of liveness, you have defined Connectivity Verification and =
Continuity Checks in section 2.2.5
>> - OLD:
>>    Each of the end-points of the monitored path maintains its own
>>    session identification
>> NEW:
>>    Each of the MEP maintains its own session identification
>> OR NEW (actually I don't know)
>>    Each of the MP maintains its own session identification
>> - OLD
>> 	A BFD echo packet is sent to a peer system
>> Peer system =3D MEP, MP, or something else?
>> - etc...=20
>>=20
>> 10.=20
>> This document is composed of a list of OAM content and references, =
but I'm really missing the document "scope and target audience".
>> When we did RFC 6632, which is the companion document, we had =
http://tools.ietf.org/html/rfc6632#section-1.1
>> =20
>>    The target audience of the document is, on the one hand, IETF =
working
>>    groups, which aim to select appropriate standard management =
protocols
>>    and data models to address their needs concerning network =
management.
>>    On the other hand, the document can be used as an overview and
>>    guideline by non-IETF Standards Development Organizations (SDOs)
>>    planning to use IETF management technologies and data models for =
the
>>    realization of management applications.  The document can also be
>>    used to initiate a discussion between the bodies with the goal to
>>    gather new requirements and to detect possible gaps.  Finally, =
this
>>    document is directed to all interested parties that seek to get an
>>    overview of the current set of the IETF network management =
protocols
>>    such as network administrators or newcomers to the IETF.
>>=20
>> You should have something similar.
>>=20
>>=20
>> 11.
>> Section 3.6.1, put the paragraph 2 at the end of the section. The =
"alternative" in the following sentence would then make sense
>>    Alternative protocols for performance measurement are defined, for
>>    example, in MPLS-TP OAM ([MPLS-LM-DM], [TP-LM-DM]), and in =
Ethernet
>>    OAM [ITU-T-Y1731].
>>=20
>>=20
>> My conclusions: this document still needs some work
>>=20
>> Regards, Benoit
>> =20
>>> The IESG has received a request from the Operations and Management =
Area
>>> Working Group WG (opsawg) to consider the following document:
>>> - 'An Overview of Operations, Administration, and Maintenance (OAM)
>>>    Mechanisms'
>>>   <draft-ietf-opsawg-oam-overview-08.txt> as Informational RFC
>>>=20
>>> The IESG plans to make a decision in the next few weeks, and =
solicits
>>> final comments on this action. Please send substantive comments to =
the
>>> ietf@ietf.org mailing lists by 2013-01-25. Exceptionally, comments =
may be
>>> sent to iesg@ietf.org instead. In either case, please retain the
>>> beginning of the Subject line to allow automated sorting.
>>>=20
>>> Abstract
>>>=20
>>>=20
>>>    Operations, Administration, and Maintenance (OAM) is a general =
term
>>>    that refers to a toolset that can be used for fault detection and
>>>    isolation, and for performance measurement. OAM mechanisms have =
been
>>>    defined for various layers in the protocol stack, and are used =
with a
>>>    variety of protocols.
>>>=20
>>>    This document presents an overview of the OAM mechanisms that =
have
>>>    been defined and are currently being defined by the IETF.
>>>=20
>>>=20
>>>=20
>>>=20
>>> The file can be obtained via
>>> http://datatracker.ietf.org/doc/draft-ietf-opsawg-oam-overview/
>>>=20
>>> IESG discussion can be tracked via
>>> =
http://datatracker.ietf.org/doc/draft-ietf-opsawg-oam-overview/ballot/
>>>=20
>>>=20
>>> No IPR declarations have been submitted directly on this I-D.
>>>=20
>>>=20
>>>=20
>>=20
>=20


--Apple-Mail=_0CA0F3E7-DA67-4945-AAF7-F63024E8843F
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=windows-1252

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dwindows-1252"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Here =
are my comments.<div><br></div><div><div>#1</div><div><pre =
style=3D"line-height: 1.2em; margin-top: 0px; margin-bottom: 0px; =
font-size: 13px; "><span class=3D"m_h" style=3D"font-family: arial; =
font-weight: bold; ">1.1. The Building Blocks of OAM</span>

   An OAM protocol is run in the context of a Maintenance Domain,
   consisting of two or more nodes that run the OAM protocol, referred
   to as Maintenance Points (MP).</pre><div>%sam - I do not think that, =
MP, MEP, etc., &nbsp;terminology is used in OAM across different layers. =
It was introduced in MPLS-TP and later in TRILL, but prior to that, it =
is not. Is it the authors intention that this new terminology be used =
going forward?</div></div><div><br></div><div>#2</div><div>Sec 1.1 =
-&nbsp;<span style=3D"font-size: 13px; line-height: 1.2em; ">An OAM =
protocol typically supports one or more of the</span></div><pre =
style=3D"line-height: 1.2em; margin-top: 0px; margin-bottom: 0px; =
font-size: 13px; ">   tools described below.</pre><div>%sam - what is =
OAM protocol? Shouldn't it be management plane OR OAM =
tools?</div><div><br></div><div>#3&nbsp;</div><div><pre =
style=3D"line-height: 1.2em; margin-top: 0px; margin-bottom: 0px; =
font-size: 13px; ">Section 1.2 The considerations of the control-plane =
maintenance tools or the
   functionality of the management-plane are out of scope for this
   document, which will concentrate on presenting the forwarding-plane
   tools that are used for OAM.</pre><div>%sam - Why is it out of scope? =
For example, checking consistency of control plane to forwarding plane =
is part of OAM or =
not?&nbsp;</div></div><div><br></div><div>#4</div><div>Section =
1.3&nbsp;<span style=3D"font-size: 13px; line-height: 1.2em; ">The set =
of OAM</span></div><pre style=3D"line-height: 1.2em; margin-top: 0px; =
margin-bottom: 0px; font-size: 13px; ">   mechanisms described in this =
memo are applicable to IP unicast, MPLS,
   pseudowires, and MPLS for the transport environment =
(MPLS-TP).</pre><div>%sam - For ex: Is ATM OAM (RFC4717) within the =
scope of this draft? I did't see any mention of it or FR. I know that =
they are legacy, but still within IETF. One day even MPLS will be legacy =
protocol (just saying :D)</div><div><br></div><div>#5</div><div>Over all =
draft</div><div>%sam - I do not think this draft even considered =
'multicast traffic'. There are rfc's in ever layer supporting multicast. =
There is no reference I could find. Ex: RFC6450, RFC6425 =
etc</div><div><br></div><div>#6</div><div>Sec 3.5&nbsp;</div><div>%sam - =
I think it is good to add details on different types of VCCV types of CC =
and CV and their =
use.&nbsp;</div><div><br></div><div>#7</div><div>General</div><div>%sam =
- Do you consider MIB part of OAM? Does Traps considered as error =
reporting or fault =
indication?</div><div><br></div><div>#8&nbsp;</div><div>Sec 3.4.3.8 and =
9</div><div>%sam - Do these consider actual packet LM and DM or =
synthetic =
packets?&nbsp;</div><div><br></div><div>#9&nbsp;</div><div>Section =
4</div><div>%sam - I think this section should provide more details on =
what the general security issues are with OAM messages etc. And how they =
could be mitigated. For in-depth details, one could go into each of =
those documents.</div><div><br></div><div>#10</div><div>Sec =
3.7</div><div>I do not think this is complete representation. For ex: no =
representation of multicast. BFD could be used for RDI, I =
think.&nbsp;</div><div><br></div><div>#11</div><div>IP Ping and =
Traceroute</div><div>%sam - When you say IP ping, does it imply ICMP =
ping or IP/UDP =
ping?</div><div><br></div><div><br></div><div>cheers</div><div>-sam</div><=
div><div>On Jan 15, 2013, at 6:48 AM, Benoit Claise &lt;<a =
href=3D"mailto:bclaise@cisco.com">bclaise@cisco.com</a>&gt; =
wrote:</div><br class=3D"Apple-interchange-newline"><blockquote =
type=3D"cite">
 =20
    <meta content=3D"text/html; charset=3DISO-8859-1" =
http-equiv=3D"Content-Type">
 =20
  <div text=3D"#000000" bgcolor=3D"#FFFFFF">
    <div class=3D"moz-cite-prefix">Some more feedback, send on behalf of
      Al Morton.<br>
      <br>
      Regards, Benoit<br>
      <br>
      =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D<br>
      <span style=3D"font-size:10.0pt;font-family:&quot;Courier
        New&quot;;color:windowtext">Hi Benoit,<o:p></o:p></span><br>
      <span style=3D"font-size:10.0pt;font-family:&quot;Courier
        New&quot;;color:windowtext">&nbsp;</span><br>
      <span style=3D"font-size:10.0pt;font-family:&quot;Courier
        New&quot;;color:windowtext">Here are some additional comments,
        just checking a few things<o:p></o:p></span><br>
      <span style=3D"font-size:10.0pt;font-family:&quot;Courier
        New&quot;;color:windowtext">I know a little =
about.<o:p></o:p></span><br>
      <span style=3D"font-size:10.0pt;font-family:&quot;Courier
        New&quot;;color:windowtext">&nbsp;</span><br>
      <span style=3D"font-size:10.0pt;font-family:&quot;Courier
        New&quot;;color:windowtext">Al<o:p></o:p></span><br>
      <span style=3D"font-size:10.0pt;font-family:&quot;Courier
        New&quot;;color:windowtext">&nbsp;</span><br>
      <span style=3D"font-size:10.0pt;font-family:&quot;Courier
        =
New&quot;;color:windowtext">-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D=
-=3D-=3D-<o:p></o:p></span><br>
      <span style=3D"font-size:10.0pt;font-family:&quot;Courier
        New&quot;;color:windowtext">&nbsp;</span><br>
      <span style=3D"font-size:10.0pt;font-family:&quot;Courier
        New&quot;;color:windowtext">1.1. The Building Blocks of =
OAM<o:p></o:p></span><br>
      <span style=3D"font-size:10.0pt;font-family:&quot;Courier
        New&quot;;color:windowtext">...<o:p></o:p></span><br>
      <span style=3D"font-size:10.0pt;font-family:&quot;Courier
        New&quot;;color:windowtext">&nbsp;&nbsp; o Performance =
Monitoring:<o:p></o:p></span><br>
      <span style=3D"font-size:10.0pt;font-family:&quot;Courier
        New&quot;;color:windowtext">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
Consists of 3 main functions<o:p></o:p></span><br>
      <span style=3D"font-size:10.0pt;font-family:&quot;Courier
        New&quot;;color:windowtext">&nbsp;</span><br>
      <span style=3D"font-size:10.0pt;font-family:&quot;Courier
        =
New&quot;;color:windowtext">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; o =
Loss Measurement (LM) -
        monitors the packet loss rate of a<o:p></o:p></span><br>
      <span style=3D"font-size:10.0pt;font-family:&quot;Courier
        =
New&quot;;color:windowtext">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp; connection.<o:p></o:p></span><br>
      <span style=3D"font-size:10.0pt;font-family:&quot;Courier
        New&quot;;color:windowtext">&nbsp;</span><br>
      <span style=3D"font-size:10.0pt;font-family:&quot;Courier
        =
New&quot;;color:windowtext">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; o =
Delay Measurement (DM) -
        monitors the delay and delay<o:p></o:p></span><br>
      <span style=3D"font-size:10.0pt;font-family:&quot;Courier
        =
New&quot;;color:windowtext">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp; variation between MPs.<o:p></o:p></span><br>
      <span style=3D"font-size:10.0pt;font-family:&quot;Courier
        New&quot;;color:windowtext">&nbsp;</span><br>
      <span style=3D"font-size:10.0pt;font-family:&quot;Courier
        =
New&quot;;color:windowtext">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; o =
Throughput measurement -
        monitors the throughput of a<o:p></o:p></span><br>
      <span style=3D"font-size:10.0pt;font-family:&quot;Courier
        New&quot;;color:windowtext">&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;connection.<o:p></o:p></sp=
an><br>
      <span style=3D"font-size:10.0pt;font-family:&quot;Courier
        New&quot;;color:windowtext">&nbsp;</span><br>
      <span style=3D"font-size:10.0pt;font-family:&quot;Courier
        New&quot;;color:windowtext">&gt;&gt;&gt; Apparently, no OAM tool
        currently measures Throughput, <o:p></o:p></span><br>
      <span style=3D"font-size:10.0pt;font-family:&quot;Courier
        New&quot;;color:windowtext">&nbsp;&nbsp;&nbsp;&nbsp;because no =
such tool is cited in
        the memo (and the term =93throughput=94<o:p></o:p></span><br>
      <span style=3D"font-size:10.0pt;font-family:&quot;Courier
        New&quot;;color:windowtext">&nbsp;&nbsp;&nbsp; never appears =
again). &nbsp;my guess
        is that there was some reference to<o:p></o:p></span><br>
      <span style=3D"font-size:10.0pt;font-family:&quot;Courier
        New&quot;;color:windowtext">&nbsp;&nbsp;&nbsp; RFC 2544 that has =
now been
        removed. Remove Throughput from the list.<o:p></o:p></span><br>
      <span style=3D"font-size:10.0pt;font-family:&quot;Courier
        New&quot;;color:windowtext">&nbsp;</span><br>
      <span style=3D"font-size:10.0pt;font-family:&quot;Courier
        New&quot;;color:windowtext">1.3 OAM =
Toolsets<o:p></o:p></span><br>
      <span style=3D"font-size:10.0pt;font-family:&quot;Courier
        New&quot;;color:windowtext">... <o:p></o:p></span><br>
      <span style=3D"font-size:10.0pt;font-family:&quot;Courier
        New&quot;;color:windowtext">&nbsp;&nbsp;&nbsp;o OWAMP and =
TWAMP:<o:p></o:p></span><br>
      <span style=3D"font-size:10.0pt;font-family:&quot;Courier
        New&quot;;color:windowtext">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; The =
One Way Active Measurement
        Protocol (OWAMP) and the Two Way<o:p></o:p></span><br>
      <span style=3D"font-size:10.0pt;font-family:&quot;Courier
        New&quot;;color:windowtext">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
Active Measurement Protocols
        (TWAMP) are two protocols defined in<o:p></o:p></span><br>
      <span style=3D"font-size:10.0pt;font-family:&quot;Courier
        New&quot;;color:windowtext">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the =
IP Performance Metrics
        (IPPM) working group in the IETF. These<o:p></o:p></span><br>
      <span style=3D"font-size:10.0pt;font-family:&quot;Courier
        New&quot;;color:windowtext">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
protocols allow delay and
        packet loss measurement in IP networks.<o:p></o:p></span><br>
      <span style=3D"font-size:10.0pt;font-family:&quot;Courier
        New&quot;;color:windowtext">&nbsp;</span><br>
      <span style=3D"font-size:10.0pt;font-family:&quot;Courier
        New&quot;;color:windowtext">&gt;&gt;&gt; and Delay variation,
        duplication, reordering, etc. (all the metrics limited =
tools<o:p></o:p></span><br>
      <span style=3D"font-size:10.0pt;font-family:&quot;Courier
        New&quot;;color:windowtext">&nbsp;&nbsp;&nbsp; completely =
ignore). <o:p></o:p></span><br>
      <span style=3D"font-size:10.0pt;font-family:&quot;Courier
        New&quot;;color:windowtext">&nbsp;</span><br>
      <span style=3D"font-size:10.0pt;font-family:&quot;Courier
        New&quot;;color:windowtext">1.4 IETF OAM =
Documents<o:p></o:p></span><br>
      <span style=3D"font-size:10.0pt;font-family:&quot;Courier
        New&quot;;color:windowtext">&nbsp;</span><br>
      <span style=3D"font-size:10.0pt;font-family:&quot;Courier
        New&quot;;color:windowtext">&gt;&gt;&gt; Expand Table 1 as noted
        above, to include all the metrics they =
missed.<o:p></o:p></span><br>
      <span style=3D"font-size:10.0pt;font-family:&quot;Courier
        New&quot;;color:windowtext">&nbsp;</span><br>
      <span style=3D"font-size:10.0pt;font-family:&quot;Courier
        New&quot;;color:windowtext">&nbsp;</span><br>
      <span style=3D"font-size:10.0pt;font-family:&quot;Courier
        New&quot;;color:windowtext">3.6.1<o:p></o:p></span><br>
      <span style=3D"font-size:10.0pt;font-family:&quot;Courier
        New&quot;;color:windowtext">...<o:p></o:p></span><br>
      <span style=3D"font-size:10.0pt;font-family:&quot;Courier
        New&quot;;color:windowtext">&nbsp;&nbsp; TWAMP [TWAMP] is a =
similar
        protocol that enables measurement of <o:p></o:p></span><br>
      <span style=3D"font-size:10.0pt;font-family:&quot;Courier
        New&quot;;color:windowtext">&gt;&gt;&gt; both one-way and =
<o:p></o:p></span><br>
      <span style=3D"font-size:10.0pt;font-family:&quot;Courier
        New&quot;;color:windowtext">&nbsp;&nbsp;&nbsp;two-way (round =
trip)
        characteristics.&nbsp; <o:p></o:p></span><br>
      <span style=3D"font-size:10.0pt;font-family:&quot;Courier
        New&quot;;color:windowtext">&nbsp;</span><br>
      <span style=3D"font-size:10.0pt;font-family:&quot;Courier
        New&quot;;color:windowtext">&gt;&gt;&gt; sentence below is
        simply not true, because the authors did not =
understand<o:p></o:p></span><br>
      <span style=3D"font-size:10.0pt;font-family:&quot;Courier
        New&quot;;color:windowtext">&nbsp;&nbsp; the one-way measurement
        capability:<o:p></o:p></span><br>
      <span style=3D"font-size:10.0pt;font-family:&quot;Courier
        New&quot;;color:windowtext">&nbsp;&nbsp; TWAMP does not require =
accurate<o:p></o:p></span><br>
      <span style=3D"font-size:10.0pt;font-family:&quot;Courier
        New&quot;;color:windowtext">&nbsp;&nbsp; time of day, and, =
furthermore,
        allows the use of a simple session<o:p></o:p></span><br>
      <span style=3D"font-size:10.0pt;font-family:&quot;Courier
        New&quot;;color:windowtext">&nbsp;&nbsp; reflector, making it an
        attractive alternative to OWAMP.<o:p></o:p></span><br>
      <span style=3D"font-size:10.0pt;font-family:&quot;Courier
        New&quot;;color:windowtext">&gt;&gt;&gt; go back and read the
        memo...<o:p></o:p></span><br>
      <span style=3D"font-size:10.0pt;font-family:&quot;Courier
        New&quot;;color:windowtext">&nbsp;</span><br>
      <span style=3D"font-size:10.0pt;font-family:&quot;Courier
        New&quot;;color:windowtext">&nbsp;</span><br>
      <span style=3D"font-size:10.0pt;font-family:&quot;Courier
        New&quot;;color:windowtext">3.7. Summary of OAM =
Functions<o:p></o:p></span><br>
      <span style=3D"font-size:10.0pt;font-family:&quot;Courier
        New&quot;;color:windowtext">&nbsp;</span><br>
      <span style=3D"font-size:10.0pt;font-family:&quot;Courier
        New&quot;;color:windowtext">&nbsp;&nbsp; Table 3 summarizes the =
OAM
        functions that are supported in each of<o:p></o:p></span><br>
      <span style=3D"font-size:10.0pt;font-family:&quot;Courier
        New&quot;;color:windowtext">&nbsp;&nbsp; the categories that =
were analyzed
        in this section.<o:p></o:p></span><br>
      <span style=3D"font-size:10.0pt;font-family:&quot;Courier
        New&quot;;color:windowtext">&nbsp;</span><br>
      <span style=3D"font-size:10.0pt;font-family:&quot;Courier
        New&quot;;color:windowtext">&nbsp;&nbsp;
        =
+-----------+-------+--------+--------+-----------+-------+--------+<o:p><=
/o:p></span><br>
      <span style=3D"font-size:10.0pt;font-family:&quot;Courier
        New&quot;;color:windowtext">&nbsp;&nbsp; | Standard&nbsp;
        |Continu|Connecti|Path&nbsp;&nbsp;&nbsp; =
|Defect&nbsp;&nbsp;&nbsp;&nbsp; |Perform|Other&nbsp;&nbsp; =
|<o:p></o:p></span><br>
      <span style=3D"font-size:10.0pt;font-family:&quot;Courier
        New&quot;;color:windowtext">&nbsp;&nbsp; =
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
|ity&nbsp;&nbsp;&nbsp; |vity&nbsp;&nbsp;&nbsp;
        |Discover|Indications|ance&nbsp;&nbsp; =
|Function|<o:p></o:p></span><br>
      <span style=3D"font-size:10.0pt;font-family:&quot;Courier
        New&quot;;color:windowtext">&nbsp;&nbsp; =
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
|Check&nbsp;
        |Verifica|y&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
|Monitor|s&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |<o:p></o:p></span><br>
      <span style=3D"font-size:10.0pt;font-family:&quot;Courier
        New&quot;;color:windowtext">&nbsp;&nbsp; =
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |tion&nbsp;&nbsp;&nbsp;
        |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
|ing&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
|<o:p></o:p></span><br>
      <span style=3D"font-size:10.0pt;font-family:&quot;Courier
        New&quot;;color:windowtext">&nbsp;&nbsp;
        =
+-----------+-------+--------+--------+-----------+-------+--------+<o:p><=
/o:p></span><br>
      <span style=3D"font-size:10.0pt;font-family:&quot;Courier
        New&quot;;color:windowtext">...<o:p></o:p></span><br>
      <span style=3D"font-size:10.0pt;font-family:&quot;Courier
        New&quot;;color:windowtext">&nbsp;&nbsp; + --------- + ----- + =
------ +
        ------ + --------- + ----- + ------ +<o:p></o:p></span><br>
      <span style=3D"font-size:10.0pt;font-family:&quot;Courier
        New&quot;;color:windowtext">&nbsp;&nbsp; |OWAMP and&nbsp; =
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
        |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |-Delay =
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |<o:p></o:p></span><br>
      <span style=3D"font-size:10.0pt;font-family:&quot;Courier
        New&quot;;color:windowtext">&nbsp;&nbsp; =
|TWAMP&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp; Yes&nbsp; |&nbsp; =
Yes&nbsp;&nbsp;
        |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; | =
measur|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
|<o:p></o:p></span><br>
      <span style=3D"font-size:10.0pt;font-family:&quot;Courier
        New&quot;;color:windowtext">&nbsp;&nbsp; =
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
        |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; | ement =
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |<o:p></o:p></span><br>
      <span style=3D"font-size:10.0pt;font-family:&quot;Courier
        New&quot;;color:windowtext">&nbsp;&nbsp; =
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
        |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
|-Packet|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
|<o:p></o:p></span><br>
      <span style=3D"font-size:10.0pt;font-family:&quot;Courier
        New&quot;;color:windowtext">&nbsp;&nbsp; =
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
        |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; | =
loss&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
|<o:p></o:p></span><br>
      <span style=3D"font-size:10.0pt;font-family:&quot;Courier
        New&quot;;color:windowtext">&nbsp;&nbsp; =
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
        |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; | =
measur|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
|<o:p></o:p></span><br>
      <span style=3D"font-size:10.0pt;font-family:&quot;Courier
        New&quot;;color:windowtext">&nbsp;&nbsp; =
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
        |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; | ement =
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |<o:p></o:p></span><br>
      <span style=3D"font-size:10.0pt;font-family:&quot;Courier
        New&quot;;color:windowtext">&nbsp;&nbsp;
        =
+-----------+-------+--------+--------+-----------+-------+--------+<o:p><=
/o:p></span><br>
      <span style=3D"font-size:10.0pt;font-family:&quot;Courier
        =
New&quot;;color:windowtext">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
 Table 3 Summary
        of OAM Functions<o:p></o:p></span><br>
      <span style=3D"font-size:10.0pt;font-family:&quot;Courier
        New&quot;;color:windowtext">&nbsp;</span><br>
      <span style=3D"font-size:10.0pt;font-family:&quot;Courier
        New&quot;;color:windowtext">&gt;&gt;&gt; Both Continuity Check
        and Connectivity Verification are tested =
and<o:p></o:p></span><br>
      <span style=3D"font-size:10.0pt;font-family:&quot;Courier
        New&quot;;color:windowtext">confirmed by establishing the *WAMP
        Control Protocol TCP connection,<o:p></o:p></span><br>
      <span style=3D"font-size:10.0pt;font-family:&quot;Courier
        New&quot;;color:windowtext">so this should be indicated the
        table.</span><br>
      <br>
      <br>
    </div>
    <blockquote cite=3D"mid:50F437BF.8040005@cisco.com" type=3D"cite">
      <meta content=3D"text/html; charset=3DISO-8859-1" =
http-equiv=3D"Content-Type">
      <div class=3D"moz-cite-prefix">draft-ietf-opsawg-oam-overview
        authors,<br>
        <br>
        Here is my feedback on this document.<br>
        <br>
        1.<br>
        Is this document in line with <a moz-do-not-send=3D"true" =
class=3D"moz-txt-link-freetext" =
href=3D"http://tools.ietf.org/html/draft-ietf-trill-oam-req-04">http://too=
ls.ietf.org/html/draft-ietf-trill-oam-req-04</a>?
        <br>
        * For example, the following definitions could be reused.<br>
        <pre class=3D"newpage">   Fault: The term Fault refers to an =
inability to perform a required
   action, e.g., an unsuccessful attempt to deliver a packet.

   Defect: The term Defect refers to an interruption in the normal
   operation, such that over a period of time no packets are delivered
   successfully.

   Failure: The term Failure refers to the termination of the required
   function over a longer period of time. Persistence of a defect for a
   period of time is interpreted as a failure.

* For example, on the basic abstract=20
Abstract

   Operations, Administration, and Maintenance (OAM) is a general term
   that refers to a toolset that can be used for fault detection and
   isolation, and for performance measurement. OAM mechanisms have been
   defined for various layers in the protocol stack, and are used with a
   variety of protocols.

Abstract (draft-ietf-trill-oam-req-04)

   OAM (Operations, Administration and Maintenance) is a general term
   used to identify functions and toolsets to troubleshoot and monitor
   networks. This document presents, OAM Requirements applicable to
   TRILL.=20

So, as an example: does OAM include function?=20
I advice to review draft-ietf-trill-oam-req-04

2.=20
draft-ietf-trill-oam is not mentioned, while the abstract mentions:
   This document presents an overview of the OAM mechanisms that have
   been defined and are currently being defined by the IETF.
Search for OAM in the current draft names (<a moz-do-not-send=3D"true" =
class=3D"moz-txt-link-freetext" =
href=3D"https://datatracker.ietf.org/">https://datatracker.ietf.org/</a>),=
 and you will find many references.
Ok, I see later on:=09
   This document focuses on IETF
   documents that have been published as RFCs, while other ongoing OAM-
   related work is outside the scope.
Ok, fine then: we don't need a reference to all the drafts.=20
However, draft-ietf-trill-oam is closed to be a RFC, and should be =
mentioned.


3.
Section 1
   The term OAM in this document refers to Operations, Administration
   and Maintenance [<a moz-do-not-send=3D"true" =
href=3D"http://tools.ietf.org/html/draft-ietf-opsawg-oam-overview-08#ref-O=
AM-Def" title=3D"&quot;Guidelines for the use of the OAM acronym in the =
IETF &quot;">OAM-Def</a>], focusing on the forwarding plane of OAM.
What does it mean "focusing on the forwarding plane of OAM"?
Do you take a subset of the definition for this document?
Btw, I don't see a definition in the terminology section.
In section 2.2.3
   A Maintenance Point (MP) is a functional entity that is defined at a
   node in the network, and either initiates or reacts to OAM messages.
Which plane is MP?

4.
Section 1, Introduction
"Hence, management aspects are outside the scope of this document."
I don't understand which management aspects we speak about here.
</pre>
        5.<br>
        Clarifying question regarding 1.2<br>
        If speak about OWAMP or TWAMP 'synthetic traffic), is that data
        plane, control plane, or management plane?<br>
        Note that I found later on in the draft:<br>
        <pre class=3D"newpage">   OWAMP and TWAMP use two separate =
protocols: a Control plane protocol,
   and a Test plane protocol.</pre>
        Interestingly enough, after reading the document, I reviewed <a =
moz-do-not-send=3D"true" class=3D"moz-txt-link-freetext" =
href=3D"http://datatracker.ietf.org/doc/draft-ietf-opsawg-oam-overview/bal=
lot/">http://datatracker.ietf.org/doc/draft-ietf-opsawg-oam-overview/ballo=
t/</a>,
        and saw the same feedback from Stewart Bryant:<br>
        <blockquote>
          <pre>Provide a clear view of OAM functionality and its =
relationship
to various =93planes=94 of networking (data plane, control plane,
management plane). In particular, the importance of
fate-sharing of OAM and user traffic flows in packet networks
should be explained.</pre>
        </blockquote>
        6.<br>
        <pre class=3D"newpage">I see a multiplication of "plane" terms =
in the IETF document, and in this document in particular.
I could find: forwarding plane, management plane, control plane, data =
plane, user plane, and test plane.
Way too many.
Please be consistent
</pre>
        7.<br>
        <pre class=3D"newpage">   Table 1 summarizes the IETF OAM =
related RFCs discussed in this
   document.

   Table 2 summarizes the OAM standards mentioned in this document.=20

You need to change the Table 2 description. Do you want to say something =
along the lines of:
   Table 2 summarizes the OAM standards specified by other Standard =
Development Organization=20
   (SDO) than the IETF, along with IETF references where applicable.


8.
Section 2.2.1
   For a formal definition of each term, refer to the references at the =
end of
   this document.
Without a reference to a specific RFC, this is the type of statement =
which is not useful: you have 5 pages of references.
You position this document as "An Overview of<span class=3D"h1"></span> =
Operations, Administration, and Maintenance (OAM) Mechanisms<span =
class=3D"h1"></span>", but you tell the reader: "if you want to know =
about the terms,
just read first all references!"

9.
You specify some terms and some OAM categories,=20
   <a moz-do-not-send=3D"true" =
href=3D"http://tools.ietf.org/html/draft-ietf-opsawg-oam-overview-08#secti=
on-2.2.2">2.2.2</a>. OAM Maintenance Entities .......................... =
<a moz-do-not-send=3D"true" =
href=3D"http://tools.ietf.org/html/draft-ietf-opsawg-oam-overview-08#page-=
13">13</a>
         <a moz-do-not-send=3D"true" =
href=3D"http://tools.ietf.org/html/draft-ietf-opsawg-oam-overview-08#secti=
on-2.2.3">2.2.3</a>. OAM Maintenance Points ............................ =
<a moz-do-not-send=3D"true" =
href=3D"http://tools.ietf.org/html/draft-ietf-opsawg-oam-overview-08#page-=
14">14</a>
         <a moz-do-not-send=3D"true" =
href=3D"http://tools.ietf.org/html/draft-ietf-opsawg-oam-overview-08#secti=
on-2.2.4">2.2.4</a>. Proactive and On-demand activation ................ =
<a moz-do-not-send=3D"true" =
href=3D"http://tools.ietf.org/html/draft-ietf-opsawg-oam-overview-08#page-=
15">15</a>
         <a moz-do-not-send=3D"true" =
href=3D"http://tools.ietf.org/html/draft-ietf-opsawg-oam-overview-08#secti=
on-2.2.5">2.2.5</a>. Connectivity Verification and Continuity Checks ... =
<a moz-do-not-send=3D"true" =
href=3D"http://tools.ietf.org/html/draft-ietf-opsawg-oam-overview-08#page-=
15">15</a>
         <a moz-do-not-send=3D"true" =
href=3D"http://tools.ietf.org/html/draft-ietf-opsawg-oam-overview-08#secti=
on-2.2.6">2.2.6</a>. Failures .......................................... =
<a moz-do-not-send=3D"true" =
href=3D"http://tools.ietf.org/html/draft-ietf-opsawg-oam-overview-08#page-=
15">15</a>
... but you don't use them in the section 3

Just <u>one </u>example with section 3.2.2
-
   o Demand mode: in this mode, BFD control packets are sent on-demand.
      Upon need, a system initiates a series of BFD control packets to
      verify the liveness of the session
Instead of liveness, you have defined Connectivity Verification and =
Continuity Checks<span class=3D"h4"></span> in section 2.2.5
- OLD:
   Each of the end-points of the monitored path maintains its own
   session identification
NEW:
   Each of the MEP maintains its own session identification
OR NEW (actually I don't know)
   Each of the MP maintains its own session identification
- OLD
	A BFD echo packet is sent to a peer system
Peer system =3D MEP, MP, or something else?
- etc...=20

10.=20
This document is composed of a list of OAM content and references, but =
I'm really missing the document "scope and target audience".
When we did RFC 6632, which is the companion document, we had <a =
moz-do-not-send=3D"true" class=3D"moz-txt-link-freetext" =
href=3D"http://tools.ietf.org/html/rfc6632#section-1.1">http://tools.ietf.=
org/html/rfc6632#section-1.1</a>
&nbsp;
   The target audience of the document is, on the one hand, IETF working
   groups, which aim to select appropriate standard management protocols
   and data models to address their needs concerning network management.
   On the other hand, the document can be used as an overview and
   guideline by non-IETF Standards Development Organizations (SDOs)
   planning to use IETF management technologies and data models for the
   realization of management applications.  The document can also be
   used to initiate a discussion between the bodies with the goal to
   gather new requirements and to detect possible gaps.  Finally, this
   document is directed to all interested parties that seek to get an
   overview of the current set of the IETF network management protocols
   such as network administrators or newcomers to the IETF.

You should have something similar.


11.
Section 3.6.1, put the paragraph 2 at the end of the section. The =
"alternative" in the following sentence would then make sense
   Alternative protocols for performance measurement are defined, for
   example, in MPLS-TP OAM ([<a moz-do-not-send=3D"true" =
href=3D"http://tools.ietf.org/html/draft-ietf-opsawg-oam-overview-08#ref-M=
PLS-LM-DM" title=3D"&quot;Packet Loss and Delay Measurement for MPLS =
Networks&quot;">MPLS-LM-DM</a>], [<a moz-do-not-send=3D"true" =
href=3D"http://tools.ietf.org/html/draft-ietf-opsawg-oam-overview-08#ref-T=
P-LM-DM" title=3D"&quot;A Packet Loss and Delay Measurement Profile for =
MPLS-Based Transport Networks&quot;">TP-LM-DM</a>]), and in Ethernet
   OAM [<a moz-do-not-send=3D"true" =
href=3D"http://tools.ietf.org/html/draft-ietf-opsawg-oam-overview-08#ref-I=
TU-T-Y1731" title=3D"&quot;OAM Functions and Mechanisms for =
Ethernet-based Networks&quot;">ITU-T-Y1731</a>].


My conclusions: this document still needs some work

Regards, Benoit
&nbsp;
</pre>
      </div>
      <blockquote =
cite=3D"mid:20130111193616.19158.16205.idtracker@ietfa.amsl.com" =
type=3D"cite">
        <pre wrap=3D"">The IESG has received a request from the =
Operations and Management Area
Working Group WG (opsawg) to consider the following document:
- 'An Overview of Operations, Administration, and Maintenance (OAM)
   Mechanisms'
  &lt;draft-ietf-opsawg-oam-overview-08.txt&gt; as Informational RFC

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action. Please send substantive comments to the
<a moz-do-not-send=3D"true" class=3D"moz-txt-link-abbreviated" =
href=3D"mailto:ietf@ietf.org">ietf@ietf.org</a> mailing lists by =
2013-01-25. Exceptionally, comments may be
sent to <a moz-do-not-send=3D"true" class=3D"moz-txt-link-abbreviated" =
href=3D"mailto:iesg@ietf.org">iesg@ietf.org</a> instead. In either case, =
please retain the
beginning of the Subject line to allow automated sorting.

Abstract


   Operations, Administration, and Maintenance (OAM) is a general term
   that refers to a toolset that can be used for fault detection and
   isolation, and for performance measurement. OAM mechanisms have been
   defined for various layers in the protocol stack, and are used with a
   variety of protocols.

   This document presents an overview of the OAM mechanisms that have
   been defined and are currently being defined by the IETF.




The file can be obtained via
<a moz-do-not-send=3D"true" class=3D"moz-txt-link-freetext" =
href=3D"http://datatracker.ietf.org/doc/draft-ietf-opsawg-oam-overview/">h=
ttp://datatracker.ietf.org/doc/draft-ietf-opsawg-oam-overview/</a>

IESG discussion can be tracked via
<a moz-do-not-send=3D"true" class=3D"moz-txt-link-freetext" =
href=3D"http://datatracker.ietf.org/doc/draft-ietf-opsawg-oam-overview/bal=
lot/">http://datatracker.ietf.org/doc/draft-ietf-opsawg-oam-overview/ballo=
t/</a>


No IPR declarations have been submitted directly on this I-D.



</pre>
      </blockquote>
      <br>
    </blockquote>
    <br>
  </div>

</blockquote></div><br></div></body></html>=

--Apple-Mail=_0CA0F3E7-DA67-4945-AAF7-F63024E8843F--

From ned+ietf@mauve.mrochek.com  Tue Jan 15 15:03:27 2013
Return-Path: <ned+ietf@mauve.mrochek.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5E58611E80A4 for <ietf@ietfa.amsl.com>; Tue, 15 Jan 2013 15:03:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.932
X-Spam-Level: 
X-Spam-Status: No, score=-2.932 tagged_above=-999 required=5 tests=[AWL=-0.333, BAYES_00=-2.599]
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 iv-Q1mx6Ov-6 for <ietf@ietfa.amsl.com>; Tue, 15 Jan 2013 15:03:26 -0800 (PST)
Received: from mauve.mrochek.com (mauve.mrochek.com [66.59.230.40]) by ietfa.amsl.com (Postfix) with ESMTP id C404121F85E8 for <ietf@ietf.org>; Tue, 15 Jan 2013 15:03:26 -0800 (PST)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01OP0UAXIZQ8004KH6@mauve.mrochek.com> for ietf@ietf.org; Tue, 15 Jan 2013 14:58:25 -0800 (PST)
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01OOJ8U2Q2U800008S@mauve.mrochek.com> (original mail from NED@mauve.mrochek.com) for ietf@ietf.org; Tue, 15 Jan 2013 14:58:22 -0800 (PST)
From: ned+ietf@mauve.mrochek.com
Message-id: <01OP0UAW31X800008S@mauve.mrochek.com>
Date: Tue, 15 Jan 2013 14:31:24 -0800 (PST)
Subject: Re: Last Call: <draft-farrell-ft-03.txt> (A Fast-Track way to	RFC with Running Code) to Experimental RFC
In-reply-to: "Your message dated Mon, 14 Jan 2013 21:32:52 +0100 (CET)" <20130114203252.E331A1A455@ld9781.wdf.sap.corp>
MIME-version: 1.0
Content-type: TEXT/PLAIN
References: <20130114130541.GK62444@verdi> <20130114203252.E331A1A455@ld9781.wdf.sap.corp>
To: mrex@sap.com
Cc: John Leslie <john@jlc.net>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Jan 2013 23:03:27 -0000

Martin Rex wrote:

> John Leslie wrote:
> >
> >    I'm pretty darn uncomfortable _ever_ picking a fight with any
> > sitting AD, But I feel obligated to say this seems like a terrible
> > idea to me.
> >
> >    As a background, I'm a long-time believer in "rough consensus" for
> > Proposed Standard and "running code" for advancement along the
> > standards track. I do not believe the two mix well.

> I don't have the resource to participate the discussion, but
> these statements capture my opinion pretty well.

I'm reluctantly going to have to join John and Martin, with one very important
difference: I think there is huge value in implementing specifications during
the process leading up to proposed standard. (As many people know, I do this
myself quite often for drafts I'm interested in.) I would rather phrase it as
having demonstrable interoperability for advancement, and ideally having
implementations done much earlier.

More specifically, where I part ways with this draft is in believing that very
early implementation helps find interoperability issues. I have not found that
to be the case. What it helps find are issues affecting implementability. In
the applications area at least, it's surprisingly easy to specify things that
look good on paper but turn out to suck when you try to code them. (My own sins
in this area are well known - RFC 2231 - and one of the reasons for that it is
one of the few RFCs I've written without implementing it first.)

Now, it's quite true that implementability problems can lead to
interoperability problems, like when different people take different shortcuts
in coding an unnecessarily problematic specification. But other outcomes are
possible, including fragility, unnecessary restrictions, and most especially
scalability problems.

Another problem with focusing on interoperability specifically as opposed to
overall implementability is that it makes it hard to argue that one or two
implementations provide that much benefit. In my experience having just one
implementation, even one done by a draft author, is surprisingly helpful in
cleaning up drafts.

I guess what I would like to see is for the draft to talk a little more about
finding implementation issues in general and a lot less about finding
interoperability issues specifically. I also think the draft goes a bit far in
the "carrots" it provides, but that may have more to do with my own experiences
in the applications area, where important comments have a way of only showing
up at the last second and where therefore the abbreviated process might be a
little dangerous to use.

Finally, I'm going to apologize for the tardiness of this comment, which really
should have been made sooner. I'm also going to apologize in advance for
probably not being able to fully participate in this discussion due to severe
time constraints.

				Ned

From stephen.farrell@cs.tcd.ie  Tue Jan 15 15:14:40 2013
Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A5A3111E80FD for <ietf@ietfa.amsl.com>; Tue, 15 Jan 2013 15:14:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 mvNKPc0TJZm7 for <ietf@ietfa.amsl.com>; Tue, 15 Jan 2013 15:14:38 -0800 (PST)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) by ietfa.amsl.com (Postfix) with ESMTP id 602E811E80F9 for <ietf@ietf.org>; Tue, 15 Jan 2013 15:14:38 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id 4022EBE49; Tue, 15 Jan 2013 23:14:16 +0000 (GMT)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BC+VFAVKdafy; Tue, 15 Jan 2013 23:14:15 +0000 (GMT)
Received: from [10.87.48.11] (unknown [86.42.17.1]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id D5DC6BE3B; Tue, 15 Jan 2013 23:14:14 +0000 (GMT)
Message-ID: <50F5E2C6.4070900@cs.tcd.ie>
Date: Tue, 15 Jan 2013 23:14:14 +0000
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130106 Thunderbird/17.0.2
MIME-Version: 1.0
To: ned+ietf@mauve.mrochek.com
Subject: Re: Last Call: <draft-farrell-ft-03.txt> (A Fast-Track way to	RFC with Running Code) to Experimental RFC
References: <20130114130541.GK62444@verdi> <20130114203252.E331A1A455@ld9781.wdf.sap.corp> <01OP0UAW31X800008S@mauve.mrochek.com>
In-Reply-To: <01OP0UAW31X800008S@mauve.mrochek.com>
X-Enigmail-Version: 1.5
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: John Leslie <john@jlc.net>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Jan 2013 23:14:40 -0000

Hi Ned,

at the end...

On 01/15/2013 10:31 PM, ned+ietf@mauve.mrochek.com wrote:
> Martin Rex wrote:
> 
>> John Leslie wrote:
>>>
>>>    I'm pretty darn uncomfortable _ever_ picking a fight with any
>>> sitting AD, But I feel obligated to say this seems like a terrible
>>> idea to me.
>>>
>>>    As a background, I'm a long-time believer in "rough consensus" for
>>> Proposed Standard and "running code" for advancement along the
>>> standards track. I do not believe the two mix well.
> 
>> I don't have the resource to participate the discussion, but
>> these statements capture my opinion pretty well.
> 
> I'm reluctantly going to have to join John and Martin, with one very important
> difference: I think there is huge value in implementing specifications during
> the process leading up to proposed standard. (As many people know, I do this
> myself quite often for drafts I'm interested in.) I would rather phrase it as
> having demonstrable interoperability for advancement, and ideally having
> implementations done much earlier.
> 
> More specifically, where I part ways with this draft is in believing that very
> early implementation helps find interoperability issues. I have not found that
> to be the case. What it helps find are issues affecting implementability. In
> the applications area at least, it's surprisingly easy to specify things that
> look good on paper but turn out to suck when you try to code them. (My own sins
> in this area are well known - RFC 2231 - and one of the reasons for that it is
> one of the few RFCs I've written without implementing it first.)
> 
> Now, it's quite true that implementability problems can lead to
> interoperability problems, like when different people take different shortcuts
> in coding an unnecessarily problematic specification. But other outcomes are
> possible, including fragility, unnecessary restrictions, and most especially
> scalability problems.
> 
> Another problem with focusing on interoperability specifically as opposed to
> overall implementability is that it makes it hard to argue that one or two
> implementations provide that much benefit. In my experience having just one
> implementation, even one done by a draft author, is surprisingly helpful in
> cleaning up drafts.
> 
> I guess what I would like to see is for the draft to talk a little more about
> finding implementation issues in general and a lot less about finding
> interoperability issues specifically. I also think the draft goes a bit far in
> the "carrots" it provides, but that may have more to do with my own experiences
> in the applications area, where important comments have a way of only showing
> up at the last second and where therefore the abbreviated process might be a
> little dangerous to use.
> 
> Finally, I'm going to apologize for the tardiness of this comment, which really
> should have been made sooner. I'm also going to apologize in advance for
> probably not being able to fully participate in this discussion due to severe
> time constraints.

Actually I think you make a couple of great points that ought be
mentioned in the draft about implementability. (No chance you'd
have time to craft a paragraph? If not, I'll try pinch text from
above:-) Now that you point it out like that, I'm irritated at
myself for not having included it already! (It rings bells for me.)

Cheers,
S.

> 
> 				Ned
> 
> 

From ned+ietf@mauve.mrochek.com  Tue Jan 15 19:58:22 2013
Return-Path: <ned+ietf@mauve.mrochek.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B285611E80A5 for <ietf@ietfa.amsl.com>; Tue, 15 Jan 2013 19:58:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.849
X-Spam-Level: 
X-Spam-Status: No, score=-2.849 tagged_above=-999 required=5 tests=[AWL=-0.250, BAYES_00=-2.599]
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 i2FzLjBsjDVC for <ietf@ietfa.amsl.com>; Tue, 15 Jan 2013 19:58:22 -0800 (PST)
Received: from mauve.mrochek.com (mauve.mrochek.com [66.59.230.40]) by ietfa.amsl.com (Postfix) with ESMTP id 430F611E809B for <ietf@ietf.org>; Tue, 15 Jan 2013 19:58:22 -0800 (PST)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01OP14LL6MCG00630Y@mauve.mrochek.com> for ietf@ietf.org; Tue, 15 Jan 2013 19:53:20 -0800 (PST)
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01OP10N6JLKW00008T@mauve.mrochek.com> (original mail from NED@mauve.mrochek.com) for ietf@ietf.org; Tue, 15 Jan 2013 19:53:18 -0800 (PST)
From: ned+ietf@mauve.mrochek.com
Message-id: <01OP14LJOQU200008T@mauve.mrochek.com>
Date: Tue, 15 Jan 2013 19:40:37 -0800 (PST)
Subject: Re: Last Call: <draft-farrell-ft-03.txt> (A Fast-Track way to	RFC	with Running Code) to Experimental RFC
In-reply-to: "Your message dated Tue, 15 Jan 2013 23:14:14 +0000" <50F5E2C6.4070900@cs.tcd.ie>
MIME-version: 1.0
Content-type: TEXT/PLAIN
References: <20130114130541.GK62444@verdi> <20130114203252.E331A1A455@ld9781.wdf.sap.corp> <01OP0UAW31X800008S@mauve.mrochek.com> <50F5E2C6.4070900@cs.tcd.ie>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 16 Jan 2013 03:58:22 -0000

> Actually I think you make a couple of great points that ought be
> mentioned in the draft about implementability. (No chance you'd
> have time to craft a paragraph? If not, I'll try pinch text from
> above:-) Now that you point it out like that, I'm irritated at
> myself for not having included it already! (It rings bells for me.)

OK, I think the place for a new paragraph is just before the last
paragraph of section 2. How about something along the lines of:

   A complete and correct specification is not in and of itself a guarantee of
   high quality implementations. What may seem like minor details can
   increase implementation difficulty substantially, leading to implementations
   that are fragile, contain unnecessary restrictions, or do not scale well.
   Implementation experience has the potential to catch these problems before
   the specification is finalized and becomes difficult to change.

You might also want to change the final paragraph of the section a bit in
light of the addition; I'll leave that to you to work out.

Hope this helps.

				Ned


From huubatwork@gmail.com  Wed Jan 16 02:17:33 2013
Return-Path: <huubatwork@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A55CB21F8667; Wed, 16 Jan 2013 02:17:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.341
X-Spam-Level: 
X-Spam-Status: No, score=-3.341 tagged_above=-999 required=5 tests=[AWL=0.258,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 tz9lpKrpPkNm; Wed, 16 Jan 2013 02:17:33 -0800 (PST)
Received: from mail-wi0-f176.google.com (mail-wi0-f176.google.com [209.85.212.176]) by ietfa.amsl.com (Postfix) with ESMTP id 5EA7021F865B; Wed, 16 Jan 2013 02:17:32 -0800 (PST)
Received: by mail-wi0-f176.google.com with SMTP id hm6so3268970wib.9 for <multiple recipients>; Wed, 16 Jan 2013 02:17:31 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:disposition-notification-to:date:from :reply-to:user-agent:mime-version:to:cc:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=JYtmR9C2esXbWiW9BwuUyu3B00IQUWbc8haoeQ1boec=; b=bZj4rdSKTkE9FIw6N8bqw7c3Ks4Ydbc5MrRqymCrol8wIQ7B8ACKWQW90FXRyM0j3k Z5JMIyhCZqYaztK0+jNPw+VXahw4WvfumrtswPB6xHErYZ4u5hCIVFe3u6Dvi59AjqyM GkcarqYVUFTOD7py/zmBiCMF6Bonc4ulDzwV1NFjOEFRGNaoeZ67dadjkQMODnJxnpYI QpEfQuvRJ6gJvkt7GAgUCAMU7lKTcPZhi7f2BHCAeGvFtAo+0sHsS/89/RR6LOe0cvpr 9jcLnBloTFbhoQaT6RvhHbYY8pzDL6Mjf9qn86Csk6ezqcYKoo253dbhXKAAZabt3f8m vSgQ==
X-Received: by 10.194.109.10 with SMTP id ho10mr1148645wjb.16.1358331451288; Wed, 16 Jan 2013 02:17:31 -0800 (PST)
Received: from McAsterix.local (dhcp-077-250-051-060.chello.nl. [77.250.51.60]) by mx.google.com with ESMTPS id hu8sm7589683wib.6.2013.01.16.02.17.29 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 16 Jan 2013 02:17:30 -0800 (PST)
Message-ID: <50F67E39.4080506@gmail.com>
Date: Wed, 16 Jan 2013 11:17:29 +0100
From: Huub van Helvoort <huubatwork@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130107 Thunderbird/17.0.2
MIME-Version: 1.0
To: "Bitar, Nabil N" <nabil.n.bitar@verizon.com>
Subject: Re: [PWE3] Gen-ART review of draft-ietf-pwe3-mpls-eth-oam-iwk-06
References: <CD117626.73FD3%nabil.n.bitar@verizon.com>
In-Reply-To: <CD117626.73FD3%nabil.n.bitar@verizon.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Greg Mirsky <gregimirsky@gmail.com>, "sajassi@cisco.com" <sajassi@cisco.com>, "ietf@ietf.org" <ietf@ietf.org>, "gen-art@ietf.org" <gen-art@ietf.org>, "dinmohan@hotmail.com" <dinmohan@hotmail.com>, "pwe3@ietf.org" <pwe3@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: huubatwork@gmail.com
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 16 Jan 2013 10:17:33 -0000

Hello Nabil,

You replied:

> I will folloup on the other emails. Just catching up in reverse order.

 > RDI (Reverse defect indication) is what is used in RFC 6310 to indicate
> failure in the rverse direction from the failure, and this document is
> aligned with that.

RDI is used to indicate that the *remote* end has detected a defect
in the forward direction from local node towards the remote node.
In the reverse direction (from remote node to local node) there
is *no* defect. Expanding RDI as Reverse Defect Indication will
put people on the wrong foot.

> At the same time, RDI as Remote defect indication is
> what is used for Ethernet CFM, so the attemot here is to call out
> the acronyms used and in this case it is the same acronym that correspond
> to two different terminologies, each with its own context identified.

The same RFC6310 refers to G.775 and in appendix A.2 to ATM which both
expand RDI into Remote Defect Indiction. And this expansion is used
several times in RFC6310.
The additional "for Continuity Check Message" is never used in any
of these.

So I strongly suggest to expand RDI *only* as:
"Remote Defect Indication"
to avoid creating any further confusion.

Regards, Huub.




From nabil.n.bitar@verizon.com  Wed Jan 16 11:59:43 2013
Return-Path: <nabil.n.bitar@verizon.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E484021F8758; Wed, 16 Jan 2013 11:59:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.404
X-Spam-Level: 
X-Spam-Status: No, score=-3.404 tagged_above=-999 required=5 tests=[AWL=0.195,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 jLWW3LEuKENc; Wed, 16 Jan 2013 11:59:43 -0800 (PST)
Received: from fldsmtpe01.verizon.com (fldsmtpe01.verizon.com [140.108.26.140]) by ietfa.amsl.com (Postfix) with ESMTP id 15B1721F871C; Wed, 16 Jan 2013 11:59:42 -0800 (PST)
X-IronPort-Anti-Spam-Filtered: false
Received: from unknown (HELO fldsmtpi01.verizon.com) ([166.68.71.143]) by fldsmtpe01.verizon.com with ESMTP; 16 Jan 2013 19:59:39 +0000
From: "Bitar, Nabil N" <nabil.n.bitar@verizon.com>
To: "huubatwork@gmail.com" <huubatwork@gmail.com>, "Bitar, Nabil N" <nabil.n.bitar@verizon.com>
X-IronPort-AV: E=Sophos;i="4.84,480,1355097600"; d="scan'208";a="402772015"
Received: from fldp1lumxc7hb05.verizon.com (HELO FLDP1LUMXC7HB05.us.one.verizon.com) ([166.68.75.87]) by fldsmtpi01.verizon.com with ESMTP; 16 Jan 2013 19:59:39 +0000
Received: from fldp1lumxc7v63.us.one.verizon.com ([166.68.45.45]) by FLDP1LUMXC7HB05.us.one.verizon.com ([166.68.75.87]) with mapi; Wed, 16 Jan 2013 14:59:39 -0500
Date: Wed, 16 Jan 2013 14:59:37 -0500
Subject: Re: [PWE3] Gen-ART review of draft-ietf-pwe3-mpls-eth-oam-iwk-06
Thread-Topic: [PWE3] Gen-ART review of draft-ietf-pwe3-mpls-eth-oam-iwk-06
Thread-Index: Ac30JAPrvQn6no/sS6+vuWFmisMUdw==
Message-ID: <CD1C6C1E.75AFC%nabil.n.bitar@verizon.com>
In-Reply-To: <50F67E39.4080506@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.2.3.120616
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: Greg Mirsky <gregimirsky@gmail.com>, "sajassi@cisco.com" <sajassi@cisco.com>, "ietf@ietf.org" <ietf@ietf.org>, "gen-art@ietf.org" <gen-art@ietf.org>, "dinmohan@hotmail.com" <dinmohan@hotmail.com>, "pwe3@ietf.org" <pwe3@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 16 Jan 2013 19:59:44 -0000

Hi Huub,
Please, see inline.

Thanks,
Nabil

On 1/16/13 5:17 AM, "Huub van Helvoort" <huubatwork@gmail.com> wrote:

>Hello Nabil,
>
>You replied:
>
>> I will folloup on the other emails. Just catching up in reverse order.
>
> > RDI (Reverse defect indication) is what is used in RFC 6310 to indicate
>> failure in the rverse direction from the failure, and this document is
>> aligned with that.
>
>RDI is used to indicate that the *remote* end has detected a defect
>in the forward direction from local node towards the remote node.
>In the reverse direction (from remote node to local node) there
>is *no* defect. Expanding RDI as Reverse Defect Indication will
>put people on the wrong foot.

<NB2>  CA Reverse defect indication is a logical definition in RFC 6310.
The mechanism used depends on the technology used. Here is what is in RFC
6310 and also in the draft in synergy with RFC 6310:

          Forward defect indication corresponds to the logical OR of:

* Local Attachment Circuit (ingress) Receive Fault,

* Local PSN-facing PW (egress) Transmit Fault, and

* PW Not Forwarding.

Reverse defect indication corresponds to the logical OR of:

* Local Attachment Circuit (egress) Transmit Fault and

* Local PSN-facing PW (ingress) Receive Fault.


Are you sating that there is a problem here, with RFC6310?
<NB2>=20


>
>> At the same time, RDI as Remote defect indication is
>> what is used for Ethernet CFM, so the attemot here is to call out
>> the acronyms used and in this case it is the same acronym that
>>correspond
>> to two different terminologies, each with its own context identified.

>
>The same RFC6310 refers to G.775 and in appendix A.2 to ATM which both
>expand RDI into Remote Defect Indiction. And this expansion is used
>several times in RFC6310.
>The additional "for Continuity Check Message" is never used in any
>of these.
<NB> CCM is ised in the Ethernet part which is this draft in here.
Ethernet is not covered in RFC 6310.
>
>So I strongly suggest to expand RDI *only* as:
>"Remote Defect Indication"
>to avoid creating any further confusion.

<NB> Please, see above. There are different contexts per above where the
expanded terminology is applied. Are you suggesting still using Reverse
Defect Indication per above where needed but not to abbreviate it? RDI as
Remote Defect Indication part of Ethernet CFM is already there.
>
>Regards, Huub.
>
>
>


From stephen.farrell@cs.tcd.ie  Wed Jan 16 13:23:53 2013
Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6E14811E80F8 for <ietf@ietfa.amsl.com>; Wed, 16 Jan 2013 13:23:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.299
X-Spam-Level: 
X-Spam-Status: No, score=-102.299 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, J_CHICKENPOX_52=0.6, USER_IN_WHITELIST=-100]
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 D6E4FBratYub for <ietf@ietfa.amsl.com>; Wed, 16 Jan 2013 13:23:52 -0800 (PST)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) by ietfa.amsl.com (Postfix) with ESMTP id 8F87C11E80E6 for <ietf@ietf.org>; Wed, 16 Jan 2013 13:23:52 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id D0606BE57; Wed, 16 Jan 2013 21:23:30 +0000 (GMT)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DtuzkPoE-wuy; Wed, 16 Jan 2013 21:23:29 +0000 (GMT)
Received: from [10.87.48.11] (unknown [86.41.51.179]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 613C0BE49; Wed, 16 Jan 2013 21:23:29 +0000 (GMT)
Message-ID: <50F71A51.50804@cs.tcd.ie>
Date: Wed, 16 Jan 2013 21:23:29 +0000
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130106 Thunderbird/17.0.2
MIME-Version: 1.0
To: Ned Freed <ned.freed@mrochek.com>
Subject: Re: Last Call: <draft-farrell-ft-03.txt> (A Fast-Track way to	RFC with Running Code) to Experimental RFC
References: <20130114130541.GK62444@verdi> <20130114203252.E331A1A455@ld9781.wdf.sap.corp> <01OP0UAW31X800008S@mauve.mrochek.com> <50F5E2C6.4070900@cs.tcd.ie> <01OP14LJOQU200008T@mauve.mrochek.com>
In-Reply-To: <01OP14LJOQU200008T@mauve.mrochek.com>
X-Enigmail-Version: 1.5
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 16 Jan 2013 21:23:53 -0000

Hi Ned,

On 01/16/2013 03:40 AM, Ned Freed wrote:
>> Actually I think you make a couple of great points that ought be
>> mentioned in the draft about implementability. (No chance you'd
>> have time to craft a paragraph? If not, I'll try pinch text from
>> above:-) Now that you point it out like that, I'm irritated at
>> myself for not having included it already! (It rings bells for me.)
> 
> OK, I think the place for a new paragraph is just before the last
> paragraph of section 2. How about something along the lines of:
> 
>    A complete and correct specification is not in and of itself a guarantee of
>    high quality implementations. What may seem like minor details can
>    increase implementation difficulty substantially, leading to implementations
>    that are fragile, contain unnecessary restrictions, or do not scale well.
>    Implementation experience has the potential to catch these problems before
>    the specification is finalized and becomes difficult to change.
> 
> You might also want to change the final paragraph of the section a bit in
> light of the addition; I'll leave that to you to work out.

Did that, working copy at [1]. Lemme know if there're any changes
that are needed.

I think that's a really good addition, thanks.

S.

[1] http://down.dsg.cs.tcd.ie/misc/draft-farrell-ft-04.txt

> 
> Hope this helps.
> 
> 				Ned
> 
> 

From ben@nostrum.com  Wed Jan 16 14:17:50 2013
Return-Path: <ben@nostrum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 02A2621F8528; Wed, 16 Jan 2013 14:17:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.6
X-Spam-Level: 
X-Spam-Status: No, score=-102.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, SPF_PASS=-0.001, USER_IN_WHITELIST=-100]
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 uPejM0OkvkdI; Wed, 16 Jan 2013 14:17:49 -0800 (PST)
Received: from shaman.nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id 52D4321F8523; Wed, 16 Jan 2013 14:17:49 -0800 (PST)
Received: from [10.119.75.174] (prod00.s.dfw.fullmeshnetworks.com [174.34.133.211] (may be forged)) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id r0GMHmwB046251 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Wed, 16 Jan 2013 16:17:48 -0600 (CST) (envelope-from ben@nostrum.com)
From: Ben Campbell <ben@nostrum.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Subject: Gen-ART LC Review of draft-ietf-ospf-ospfv3-iid-registry-update-00
Date: Wed, 16 Jan 2013 16:17:46 -0600
Message-Id: <CD0EC318-1015-41ED-8E0B-045D6EB258F9@nostrum.com>
To: draft-ietf-ospf-ospfv3-iid-registry-update.all@tools.ietf.org
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
X-Mailer: Apple Mail (2.1499)
Received-SPF: pass (nostrum.com: 174.34.133.211 is authenticated by a trusted mechanism)
Cc: "gen-art@ietf.org Review Team" <gen-art@ietf.org>, "ietf@ietf.org List" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 16 Jan 2013 22:17:50 -0000

I am the assigned Gen-ART reviewer for this draft. For background on
Gen-ART, please see the FAQ at

<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

Please resolve these comments along with any other Last Call comments
you may receive.

Document:  draft-ietf-ospf-ospfv3-iid-registry-update-00
Reviewer: Ben Campbell
Review Date: 2013-01-16
IETF LC End Date: 2013-01-24

Summary: This draft is not ready for publication as a proposed standard. =
There is a significant IANA registration issue described in the review =
body.

Major issues:

This draft carves out a significant part of a registry with an =
assignment policy of "standards action" for "private use". It offers =
very little motivation for the change. In my opinion, this sort of =
change should come with a clear justification.

Specifically, the draft modifies the OSPFv3 Address Family Instance ID =
registry to carve out half of the unassigned space for "private use". =
The justification for this is a single sentence saying that some =
networks need to use IIDs to identify specific applications. I think =
that needs significant elaboration in order to motivate the change in a =
way that the reader can evaluate.

My understanding from the OFPS list is that this is in support of =
draft-ietf-ospf-ipv4-embedded-ipv6-routing, which is an informational =
draft. I have to wonder why the draft under review was not simply the =
IANA considerations for that draft.

I suggest one of two paths forward:

1) If this change is in support of that draft in particular, then this =
draft should say that, and include a _normative_ reference. I recognize =
the normative downref would complicate things--but I think that =
complication is reasonable under the circumstances.

2) If this change is to support a general need that goes beyond =
draft-ietf-ospf-ipv4-embedded-ipv6-routing, then this draft should =
describe that need in enough detail for people to think about it, =
perhaps with an informative reference to =
draft-ietf-ospf-ipv4-embedded-ipv6-routing as an _example_.


Minor issues:

-- section 3:

I don't think it's appropriate to use normative language for IANA =
requests. Especially not "MUST". (I think the strongest thing we can do =
here is a polite request :-)  )   I suggest recasting that to =
descriptive language, and removing section 2 and the RFC 2119 reference.

Nits/editorial comments:

None.


From stpeter@stpeter.im  Wed Jan 16 15:22:08 2013
Return-Path: <stpeter@stpeter.im>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C461011E809C for <ietf@ietfa.amsl.com>; Wed, 16 Jan 2013 15:22:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.332
X-Spam-Level: 
X-Spam-Status: No, score=-102.332 tagged_above=-999 required=5 tests=[AWL=0.267, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 lUd6FtabQT2e for <ietf@ietfa.amsl.com>; Wed, 16 Jan 2013 15:22:08 -0800 (PST)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id 11AB011E809A for <ietf@ietf.org>; Wed, 16 Jan 2013 15:22:08 -0800 (PST)
Received: from [10.154.228.77] (unknown [128.107.239.234]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id EFAE14005D for <ietf@ietf.org>; Wed, 16 Jan 2013 16:27:40 -0700 (MST)
Message-ID: <50F73622.4030300@stpeter.im>
Date: Wed, 16 Jan 2013 15:22:10 -0800
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130107 Thunderbird/17.0.2
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Last Call: <draft-leiba-urnbis-ietf-namespace-01.txt> (Registration of Second-Level URI Namespaces Under "ietf") to Informational RFC
References: <20130114210810.2916.93307.idtracker@ietfa.amsl.com>
In-Reply-To: <20130114210810.2916.93307.idtracker@ietfa.amsl.com>
X-Enigmail-Version: 1.5
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 16 Jan 2013 23:22:09 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 1/14/13 1:08 PM, The IESG wrote:
> 
> The IESG has received a request from an individual submitter to
> consider the following document: - 'Registration of Second-Level
> URI Namespaces Under "ietf"' 
> <draft-leiba-urnbis-ietf-namespace-01.txt> as Informational RFC

I've reviewed this document and it appears to be a useful bit of
housecleaning.

Peter

- --
Peter Saint-Andre
https://stpeter.im/

-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.18 (Darwin)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iEYEARECAAYFAlD3NiIACgkQNL8k5A2w/vx59ACcC+p5rnr5g+4wVQzwrTJXirEJ
hjQAn1IDehrg5+j3ilbr+a7/yHLRzxSH
=ka59
-----END PGP SIGNATURE-----

From magnus.westerlund@ericsson.com  Thu Jan 17 02:59:13 2013
Return-Path: <magnus.westerlund@ericsson.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 279FD21F8B2F; Thu, 17 Jan 2013 02:59:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.163
X-Spam-Level: 
X-Spam-Status: No, score=-106.163 tagged_above=-999 required=5 tests=[AWL=0.086, BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 5BgTGHsXpr4X; Thu, 17 Jan 2013 02:59:12 -0800 (PST)
Received: from mailgw1.ericsson.se (mailgw1.ericsson.se [193.180.251.45]) by ietfa.amsl.com (Postfix) with ESMTP id A0AC521F86B3; Thu, 17 Jan 2013 02:59:11 -0800 (PST)
X-AuditID: c1b4fb2d-b7f316d0000028db-94-50f7d97e29da
Received: from esessmw0197.eemea.ericsson.se (Unknown_Domain [153.88.253.124]) by mailgw1.ericsson.se (Symantec Mail Security) with SMTP id 1B.A6.10459.E79D7F05; Thu, 17 Jan 2013 11:59:10 +0100 (CET)
Received: from [127.0.0.1] (153.88.115.8) by esessmw0197.eemea.ericsson.se (153.88.115.88) with Microsoft SMTP Server id 8.3.279.1; Thu, 17 Jan 2013 11:59:10 +0100
Message-ID: <50F7D97D.2030508@ericsson.com>
Date: Thu, 17 Jan 2013 11:59:09 +0100
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:17.0) Gecko/20130107 Thunderbird/17.0.2
MIME-Version: 1.0
To: Peter Yee <peter@akayla.com>
Subject: Re: Gen-ART review of draft-ietf-6man-udpchecksums-06
References: <000701cde358$da44c6a0$8ece53e0$@akayla.com>
In-Reply-To: <000701cde358$da44c6a0$8ece53e0$@akayla.com>
X-Enigmail-Version: 1.5
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprNLMWRmVeSWpSXmKPExsUyM+JvjW7dze8BBoeWyFp8vNTLaHH11WcW i2cb57NY3DvL5MDi0bEszWPJkp9MHl8uf2YLYI7isklJzcksSy3St0vgyljwZBdbwWv5ikWz r7A3MJ6T7GLk5JAQMJE4sn0BG4QtJnHh3nogm4tDSOAko8TEE6fYIZzljBIv7jwAq+IV0JbY 37GXsYuRg4NFQFVi4s4KkDCbgIXEzR+NYCWiAsESGw6uYoIoF5Q4OfMJC4gtIqAg8b35KZjN LBAu8XvnNRaQMcICdhKzOlRAwkJAY7b3HWQFsTkFLCXW3/3JDlIiISAuseYNB0SnnsSUqy2M ELa8RPPW2cwQrdoSDU0drBMYhWYhWTwLScssJC0LGJlXMbLnJmbmpJcbbmIEBvDBLb91dzCe OidyiFGag0VJnDfM9UKAkEB6YklqdmpqQWpRfFFpTmrxIUYmDk6pBsb4VU3qjEatbzRj65a/ LN6ty/L71izB++eNryk8Lv8v97L+iemnx4FrNv75NDPfnbPM/HKtjESI6KZLOew9Du0FClzR 7yx7zBXL2xNmujvIsvo9kpnJHF07+7bO7uusGTJSMxYIhR7k/Jkh1rqkoam/O0DjX6tu46Xp 0ZxONX+D9b4tSrJgVGIpzkg01GIuKk4EAPUe6LkuAgAA
Cc: draft-ietf-6man-udpchecksums.all@tools.ietf.org, gen-art@ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 17 Jan 2013 10:59:13 -0000

Hi Peter,

Thanks for your detailed review. An updated version has just been
submitted the includes fixes to your comments.

Thanks

Magnus

On 2012-12-26 12:05, Peter Yee wrote:
> I am the assigned Gen-ART reviewer for this draft. For background on
> Gen-ART, please see the FAQ at
> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>
> 
> Please wait for direction from your document shepherd or AD before posting a
> new version of the draft.
> 
> Document: draft-ietf-6man-udpchecksums-06
> Reviewer: Peter Yee
> Review Date: Dec-25-2012
> IETF LC End Date: Dec-25-2012
> IESG Telechat date: Unknown
> 
> Summary: This draft is basically ready for publication, but has nits that
> should be fixed before publication. [Ready with nits.]
> 
> This document provides an update to 2460 to allow the use of zero checksum
> UDP packets over IPv6 in certain
> cases involving protocols tunneled inside of UDP packets.
> 
> Nits:
> 
> General: a comma after "i.e." is preferred in American English.
> 
> General: it is not necessary to hyphenate "misdelivered" or "misdelivery".
> 
> General: put quotes around "Applicability Statement for the use of IPv6 UDP
> Datagrams with Zero  Checksums"
> 
> Abstract, first sentence: "when" -> "where"
> 
> Abstract, second sentence: "protocol" -> "protocols"
> 
> Section 1, second paragraph, first sentence: delete the comma after
> "packet".
> 
> Section 1, fourth paragraph, first sentence: move the comma in "AMT," to
> after the reference.
> 
> Section 1, fourth paragraph, last sentence: insert "the" after "applicable
> in".
> 
> Section 3, second sentence: delete the first occurrence of "where".
> Consider revising the sentence for clarity.
> 
> Section 4, second sentence: "Section" -> "Sections"
> 
> Section 4.1, it would be nice, but not necessary to have an enumeration of
> the corruption modes.  
> 
> Section 4.1, third bullet item, first sentence: a verb is missing here
> making the sentence difficult to parse.
> 
> Section 4.1, third bullet item, first sentence: "packets" -> "packet"
> 
> Section 4.1, third bullet item, third sub-bullet: put commas around "for
> example".
> 
> Section 4.2, first bullet item, last sentence: this sentence is hard to
> understand; consider revising.  (See next comment)
> 
> Section 4.2, first bullet item, last sentence: "an" -> "a" and "are" ->
> "is"; also not general comment about "misdelivered".
> 
> Section 4.2, third bullet item, third sentence: "effect" -> "affect"
> 
> Section 4.2, first paragraph after bullet items, first sentence: delete
> "this".
> 
> Section 4.2, first paragraph after bullet items, third sentence:
> "mis-delievery" -> "misdelivery".
> 
> Section 4.2, first paragraph after bullet items, third sentence: delete
> "that".
> 
> Section 4.3, first sentence: "middlebox devices" -> "middleboxes" unless
> this a specific usage from I-D.ietf-6man-udpzero.
> 
> Section 4.3, second sentence: "needs" -> "need"
> 
> Section 5, first paragraph, second sentence: insert "in" after "node
> requirements".
> 
> Section 5, first paragraph of replacement text, second sentence: delete
> "usage for", replace "some" with "certain", and replace second "protocols"
> with "those".
> 
> Section 5, last paragraph: delete first instance of "the".
> 
> Section 6, first bullet item, first sentence: "corruptions" -> "corruption"
> 
> Section 6, second bullet item, last sentence: change "This" to "UDP-Lite".
> 
> Section 8, first sentence: delete redundant "required".
> 
> 


-- 

Magnus Westerlund

----------------------------------------------------------------------
Multimedia Technologies, Ericsson Research EAB/TVM
----------------------------------------------------------------------
Ericsson AB                | Phone  +46 10 7148287
Färögatan 6                | Mobile +46 73 0949079
SE-164 80 Stockholm, Sweden| mailto: magnus.westerlund@ericsson.com
----------------------------------------------------------------------


From eburger@standardstrack.com  Thu Jan 17 05:06:29 2013
Return-Path: <eburger@standardstrack.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E930921F861A for <ietf@ietfa.amsl.com>; Thu, 17 Jan 2013 05:06:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.999
X-Spam-Level: 
X-Spam-Status: No, score=-99.999 tagged_above=-999 required=5 tests=[BAYES_50=0.001, USER_IN_WHITELIST=-100]
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 v68RtCWQV5LY for <ietf@ietfa.amsl.com>; Thu, 17 Jan 2013 05:06:29 -0800 (PST)
Received: from biz104.inmotionhosting.com (biz104.inmotionhosting.com [74.124.215.15]) by ietfa.amsl.com (Postfix) with ESMTP id 23A5E21F8614 for <ietf@ietf.org>; Thu, 17 Jan 2013 05:06:29 -0800 (PST)
Received: from ip68-100-199-8.dc.dc.cox.net ([68.100.199.8]:58135 helo=[192.168.15.177]) by biz104.inmotionhosting.com with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.80) (envelope-from <eburger@standardstrack.com>) id 1TvpAq-00020x-8g; Thu, 17 Jan 2013 05:06:28 -0800
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Subject: Re: Standards-essential patents under RAND licensing
From: Eric Burger <eburger@standardstrack.com>
In-Reply-To: <50EF3ADA.3030502@earthlink.net>
Date: Thu, 17 Jan 2013 08:06:31 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <68CF1BD4-AAF3-4977-9A6D-A8DD88B393FF@standardstrack.com>
References: <201301102122.r0ALMsW44942968@shell01.TheWorld.com> <50EF3ADA.3030502@earthlink.net>
To: tglassey <tglassey@earthlink.net>
X-Mailer: Apple Mail (2.1499)
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - biz104.inmotionhosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - standardstrack.com
X-Source: 
X-Source-Args: 
X-Source-Dir: 
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 17 Jan 2013 13:06:30 -0000

Absolutely nothing. We're screwed. That's why one has to laugh out loud =
when we charter a work group to produce a royalty-free version of foo, =
because there are encumbered versions of foo out there. Unless the =
people with the rights to foo are participating and have offered their =
rights as part of the standardization process, what will be produced =
will almost certainly not be royalty-free, unless an active, conscious =
effort is made to ensure the encumbrances in the existing foos are not =
present in the new foo.

On Jan 10, 2013, at 5:04 PM, tglassey <tglassey@earthlink.net> wrote:

> On 1/10/2013 1:22 PM, Dale R. Worley wrote:
>> Recent actions by the US Department of Justice, the US Patent Office,
>> the US Federal Trade Commission (which handles antitrust and consumer
>> protection matters), and the US International Trade Commission (which
>> has the power to exclude imports which violate US patents) suggest
>> that US officials are starting to understand the proper way to handle
>> "standards-essential patents", that is, patented inventions which are
>> incorporated into standards and the patent owner has promised to
>> license under "reasonable and non-discriminatory" terms.  It seems
>> that in some cases, patent owners have not followed through to issue
>> the required licenses, and then prosecuted other standard-users based
>> on patent infringement.
>>=20
>> In particular (from the New York Times article linked below):
>>=20
>>     Over the years [...] companies took Motorola at its word and
>>     developed products assuming they could routinely license =
Motorola's
>>     patents. But Motorola later refused to license its =
standard-essential
>>     patents and sought court injunctions to stop shipment of rival
>>     products.
>>=20
>>     "After Google purchased Motorola [...] it continued these same
>>     abusive practices."
>>=20
>>     In recent months, the F.T.C. has issued position papers and filed
>>     friend-of-the-court briefs, opposing the motions for injunctions =
using
>>     standard patents. The Justice Department and European regulators =
have
>>     echoed the commission's stance.
>>=20
>> "Justice Department and Patent Office Issue Policy Statement on
>> Patents"
>> =
http://bits.blogs.nytimes.com/2013/01/08/justice-department-and-patent-off=
ice-issue-policy-statement-on-patents/
>> "On Google, F.T.C. Set Rules of War Over Patents"
>> =
http://www.nytimes.com/2013/01/05/technology/in-google-patent-case-ftc-set=
-rules-of-engagement-for-battles.html?_r=3D0
>> "United States Department of Justice and United States Patent &
>> Trademark Office Policy Statement on Remedies for Standards-Essential
>> Patents Subject to Voluntary F/RAND Commitments"
>> http://www.justice.gov/atr/public/guidelines/290994.pdf
>>=20
>> Dale
>>=20
>=20
>=20
> What do you do where a patent predates any standards use of the IP. I =
understand the issues of developing IP but what about IP that already =
existed before the standards processes incorporated it into their work =
product?
>=20
> Todd
>=20
> --=20
> Regards TSG
> "Ex-Cruce-Leo"
>=20
> //Confidential Mailing - Please destroy this if you are not the =
intended recipient.
>=20


From ned+ietf@mauve.mrochek.com  Thu Jan 17 10:25:26 2013
Return-Path: <ned+ietf@mauve.mrochek.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7F98C21F87FA for <ietf@ietfa.amsl.com>; Thu, 17 Jan 2013 10:25:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.499
X-Spam-Level: 
X-Spam-Status: No, score=-2.499 tagged_above=-999 required=5 tests=[AWL=-0.500, BAYES_00=-2.599, J_CHICKENPOX_52=0.6]
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 g2DKpeOmtem9 for <ietf@ietfa.amsl.com>; Thu, 17 Jan 2013 10:25:25 -0800 (PST)
Received: from mauve.mrochek.com (mauve.mrochek.com [66.59.230.40]) by ietfa.amsl.com (Postfix) with ESMTP id A3D3D21F86CD for <ietf@ietf.org>; Thu, 17 Jan 2013 10:25:25 -0800 (PST)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01OP3D5SV2PS0062MT@mauve.mrochek.com> for ietf@ietf.org; Thu, 17 Jan 2013 10:20:18 -0800 (PST)
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01OOJ8U2Q2U800008S@mauve.mrochek.com> (original mail from NED@mauve.mrochek.com) for ietf@ietf.org; Thu, 17 Jan 2013 10:20:13 -0800 (PST)
From: ned+ietf@mauve.mrochek.com
Message-id: <01OP3D5Q7JPC00008S@mauve.mrochek.com>
Date: Thu, 17 Jan 2013 09:47:20 -0800 (PST)
Subject: Re: Last Call: <draft-farrell-ft-03.txt> (A Fast-Track way to	RFC with Running Code) to Experimental RFC
In-reply-to: "Your message dated Wed, 16 Jan 2013 21:23:29 +0000" <50F71A51.50804@cs.tcd.ie>
MIME-version: 1.0
Content-type: TEXT/PLAIN
References: <20130114130541.GK62444@verdi> <20130114203252.E331A1A455@ld9781.wdf.sap.corp> <01OP0UAW31X800008S@mauve.mrochek.com> <50F5E2C6.4070900@cs.tcd.ie> <01OP14LJOQU200008T@mauve.mrochek.com> <50F71A51.50804@cs.tcd.ie>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Cc: Ned Freed <ned.freed@mrochek.com>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 17 Jan 2013 18:25:26 -0000

> Hi Ned,

> On 01/16/2013 03:40 AM, Ned Freed wrote:
> >> Actually I think you make a couple of great points that ought be
> >> mentioned in the draft about implementability. (No chance you'd
> >> have time to craft a paragraph? If not, I'll try pinch text from
> >> above:-) Now that you point it out like that, I'm irritated at
> >> myself for not having included it already! (It rings bells for me.)
> >
> > OK, I think the place for a new paragraph is just before the last
> > paragraph of section 2. How about something along the lines of:
> >
> >    A complete and correct specification is not in and of itself a guarantee of
> >    high quality implementations. What may seem like minor details can
> >    increase implementation difficulty substantially, leading to implementations
> >    that are fragile, contain unnecessary restrictions, or do not scale well.
> >    Implementation experience has the potential to catch these problems before
> >    the specification is finalized and becomes difficult to change.
> >
> > You might also want to change the final paragraph of the section a bit in
> > light of the addition; I'll leave that to you to work out.

> Did that, working copy at [1]. Lemme know if there're any changes
> that are needed.

It looks good to me. 

I also note that there's a reference to interoperability in the fourth
paragraph of section 1. Perhaps changing

   For example, a framework draft will not be a good candidate because
   implementations of such documents are not, of themselves,
   interoperable.

to something like

   For example, a framework draft will not be a good candidate because
   implementations of such documents are incomplete and therefore do
   not demonstrate either implementability or interoperability of an
   entire protocol.

would be in order.

				Ned

From chair@ietf.org  Thu Jan 17 14:07:07 2013
Return-Path: <chair@ietf.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 043BF21F8A08; Thu, 17 Jan 2013 14:07:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 oPM6Ifd60D-K; Thu, 17 Jan 2013 14:06:58 -0800 (PST)
Received: from mail.amsl.com (mail.amsl.com [IPv6:2001:1890:123a::1:14]) by ietfa.amsl.com (Postfix) with ESMTP id C50F421F8A06; Thu, 17 Jan 2013 14:06:57 -0800 (PST)
Received: from localhost (c8a.amsl.com [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id BE87412681E; Thu, 17 Jan 2013 14:06:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from c8a.amsl.com ([127.0.0.1]) by localhost (c8a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TFfhSAWQ9wTt; Thu, 17 Jan 2013 14:06:57 -0800 (PST)
Received: from v150.vpn.iad.rg.net (v150.vpn.iad.rg.net [198.180.150.150]) by c8a.amsl.com (Postfix) with ESMTPSA id 1635812681C; Thu, 17 Jan 2013 14:06:56 -0800 (PST)
Subject: Bits-N-Bites Sponsors Needed for Orlando
Mime-Version: 1.0 (Apple Message framework v1085)
Content-Type: text/plain; charset=us-ascii
From: IETF Chair <chair@ietf.org>
In-Reply-To: <AACFEBDA-32AE-4EBE-BA33-098C57D0CA06@vigilsec.com>
Date: Thu, 17 Jan 2013 17:00:02 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <6A126845-0549-42FF-B207-524988C618A4@ietf.org>
References: <DE4124BA-DD93-402C-9ACE-6FA00D9A9CC9@isoc.org> <11724634-145D-4DB9-A8FB-F4737E246DF6@gmail.com> <19B867F4-E3E6-4DBC-AFDF-411DF63E20DE@isoc.org> <BB1F3D21-1A95-4333-B1E6-C1E7EAF462C4@gmail.com> <349E9555-336D-4C18-8A01-A5CBBFE5598B@isoc.org> <6F50A7D4-A3F3-45B5-A6CB-A52AE67CE853@gmail.com> <E4AB856A-1509-41A3-AAF1-54CC2C2933AA@isoc.org> <AACFEBDA-32AE-4EBE-BA33-098C57D0CA06@vigilsec.com>
To: IETF Announce <ietf-announce@ietf.org>
X-Mailer: Apple Mail (2.1085)
Cc: IETF <ietf@ietf.org>, Drew Dvorshak <dvorshak@isoc.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 17 Jan 2013 22:07:07 -0000

The IAOC has decided to continue with the Bits-N-Bites event for meeting =
in 2013.  We are seeking sponsors for the Bits-N-Bites event at IETF 86 =
in Orlando.

This is a fairly new community networking event.  The first Bits-N-Bites =
took place at IETF 84 in Vancouver.  The second Bits-N-Bites took place =
at IETF 85 in Atlanta. People had a good time at both events, and the =
sponsor tables were busy.

Bits-N-Bites will bring together IETF participants, with exhibitors, =
product vendors, and service providers to share information, and =
showcase products and services in a social setting with food and drink.  =
Participants have an opportunity to network, speak with the sponsors, =
and enjoy the complimentary beer, wine, and hors d'oeuvres. =20

Bits-N-Bites will be held Thursday evening, March 14th, from 7:00 - 9:00 =
PM at the meeting venue.

Sponsorship tables are still available!  For more information see =
<http://www.ietf.org/meeting/86/bits-n-bites.html> and contact Drew =
Dvorshak at dvorshak@isoc.org.

 Russ Housley
 IETF Chair

 Bob Hinden
 IAOC Chair


From d3e3e3@gmail.com  Thu Jan 17 17:10:18 2013
Return-Path: <d3e3e3@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D955C21F88AE for <ietf@ietfa.amsl.com>; Thu, 17 Jan 2013 17:10:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.063
X-Spam-Level: 
X-Spam-Status: No, score=-103.063 tagged_above=-999 required=5 tests=[AWL=0.536, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
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 uL5PtdsRgkGo for <ietf@ietfa.amsl.com>; Thu, 17 Jan 2013 17:10:17 -0800 (PST)
Received: from mail-ob0-f182.google.com (mail-ob0-f182.google.com [209.85.214.182]) by ietfa.amsl.com (Postfix) with ESMTP id A3F4521F8AE3 for <ietf@ietf.org>; Thu, 17 Jan 2013 17:10:17 -0800 (PST)
Received: by mail-ob0-f182.google.com with SMTP id 16so3230866obc.13 for <ietf@ietf.org>; Thu, 17 Jan 2013 17:10:17 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:mime-version:in-reply-to:references:from:date:message-id :subject:to:content-type; bh=H+ZCkyi2h4Rd/e5dXudRKyTL4awIcVGNP7EbHXsCkVQ=; b=DGMmkUfvWmoHuDc4vkwKMPA7GxzvNmyctaXRCQ5RwHKGmU1xC8tWKDwr8dV4+eArg6 Q6mdsFm/NMmGuEhunXAh0gUu0I8uquGu1Hv0XEhvhcBO3SJZoK3flQIW2+jsWbCM304c QT5QX7FavTsHkYABLqdbKNEbZzsfVC4GrJi9DRfy2eLYh2ln1sclzcVSppivofAb5S3v upg8CNTij1TtkfxRc+QkaRxLMze2pFHmWTcNBQjAyqDeirpzKFYb+VMZz3Jd4hO4maqU g6EFu69df9mPsY3DdoL03eD0yyh+/fEHqvh647+h9E74O16QDVXYOKm1mVDnEGeMfvIV e64w==
X-Received: by 10.60.7.167 with SMTP id k7mr5822822oea.20.1358471417228; Thu, 17 Jan 2013 17:10:17 -0800 (PST)
MIME-Version: 1.0
Received: by 10.76.110.239 with HTTP; Thu, 17 Jan 2013 17:09:57 -0800 (PST)
In-Reply-To: <20130117155728.23682.34461.idtracker@ietfa.amsl.com>
References: <20130117155728.23682.34461.idtracker@ietfa.amsl.com>
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Thu, 17 Jan 2013 20:09:57 -0500
Message-ID: <CAF4+nEGVKz4Kj8GZ=sjBTXz-0WD+BYg3hh_crJ9zkeeMYzS6gg@mail.gmail.com>
Subject: Re: Last Call: <draft-gp-obsolete-icmp-types-iana-01.txt> (Formally Deprecating Some ICMPv4 Message Types) to Proposed Standard
To: ietf@ietf.org
Content-Type: text/plain; charset=ISO-8859-1
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 18 Jan 2013 01:10:19 -0000

I have a wording problem with this as below:

On Thu, Jan 17, 2013 at 10:57 AM, The IESG <iesg-secretary@ietf.org> wrote:
>
> The IESG has received a request from an individual submitter to consider
> the following document:
> - 'Formally Deprecating Some ICMPv4 Message Types'
>   <draft-gp-obsolete-icmp-types-iana-01.txt> as Proposed Standard
>
> The IESG plans to make a decision in the next few weeks, and solicits
> final comments on this action. Please send substantive comments to the
> ietf@ietf.org mailing lists by 2013-02-14. Exceptionally, comments may be
> sent to iesg@ietf.org instead. In either case, please retain the
> beginning of the Subject line to allow automated sorting.
>
> Abstract
>
>    A number of ICMPv4 message types have become obsolete in practice,
>    but have never been formally deprecated.  This document deprecates
>    such ICMPv4 message types, thus cleaning up the corresponding IANA
>    registry.  Additionally, it updates RFC792 and RFC950, obsoletes
>    RFC1788, and requests the RFC Editor to change the status of RFC1788
>    to "Historic".

I'm OK with deprecating these ICMPv4 message types. But this could be
said to "clean up" the IANA registry only, in my opinion, if the
entries were removed, which would be a bad idea. But the draft does
not remove these entries or simplify the registry, it annotates the
entries. I consider the wording "clean up", as used here, to be
misleading.

I suggest the second sentence of the abstract be changed to "This
document deprecates such ICMPv4 message types and annotates the
corresponding IANA registry entries." and that corresponding changes
be made elsewhere in the draft where "clean up" is used.

Thanks,
Donald
=============================
 Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
 155 Beaver Street, Milford, MA 01757 USA
 d3e3e3@gmail.com

> The file can be obtained via
> http://datatracker.ietf.org/doc/draft-gp-obsolete-icmp-types-iana/
>
> IESG discussion can be tracked via
> http://datatracker.ietf.org/doc/draft-gp-obsolete-icmp-types-iana/ballot/
>
>
> No IPR declarations have been submitted directly on this I-D.
>
>

From narten@us.ibm.com  Thu Jan 17 21:53:12 2013
Return-Path: <narten@us.ibm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C70EC21F8AB7 for <ietf@ietfa.amsl.com>; Thu, 17 Jan 2013 21:53:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.599
X-Spam-Level: 
X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
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 lXF6UxCcRTkL for <ietf@ietfa.amsl.com>; Thu, 17 Jan 2013 21:53:11 -0800 (PST)
Received: from e32.co.us.ibm.com (e32.co.us.ibm.com [32.97.110.150]) by ietfa.amsl.com (Postfix) with ESMTP id 81EB021F8427 for <ietf@ietf.org>; Thu, 17 Jan 2013 21:53:10 -0800 (PST)
Received: from /spool/local by e32.co.us.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for <ietf@ietf.org> from <narten@us.ibm.com>; Thu, 17 Jan 2013 22:53:08 -0700
Received: from d03dlp01.boulder.ibm.com (9.17.202.177) by e32.co.us.ibm.com (192.168.1.132) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted;  Thu, 17 Jan 2013 22:53:06 -0700
Received: from d03relay04.boulder.ibm.com (d03relay04.boulder.ibm.com [9.17.195.106]) by d03dlp01.boulder.ibm.com (Postfix) with ESMTP id 6C9761FF0027 for <ietf@ietf.org>; Thu, 17 Jan 2013 22:52:54 -0700 (MST)
Received: from d03av04.boulder.ibm.com (d03av04.boulder.ibm.com [9.17.195.170]) by d03relay04.boulder.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id r0I5r5IZ376936 for <ietf@ietf.org>; Thu, 17 Jan 2013 22:53:05 -0700
Received: from d03av04.boulder.ibm.com (loopback [127.0.0.1]) by d03av04.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP id r0I5r4gS011539 for <ietf@ietf.org>; Thu, 17 Jan 2013 22:53:04 -0700
Received: from rotala.raleigh.ibm.com (rotala.raleigh.ibm.com [9.44.115.148]) by d03av04.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVin) with ESMTP id r0I5r49H011511 for <ietf@ietf.org>; Thu, 17 Jan 2013 22:53:04 -0700
Received: from rotala.raleigh.ibm.com (localhost.localdomain [127.0.0.1]) by rotala.raleigh.ibm.com (8.14.5/8.12.5) with ESMTP id r0I5r3Mc014275 for <ietf@ietf.org>; Fri, 18 Jan 2013 00:53:03 -0500
Received: (from narten@localhost) by rotala.raleigh.ibm.com (8.14.5/8.14.5/Submit) id r0I5r33c014230 for ietf@ietf.org; Fri, 18 Jan 2013 00:53:03 -0500
From: Thomas Narten <narten@us.ibm.com>
Message-Id: <201301180553.r0I5r33c014230@rotala.raleigh.ibm.com>
Date: Fri, 18 Jan 2013 00:53:03 -0500
To: ietf@ietf.org
Subject: Weekly posting summary for ietf@ietf.org
User-Agent: Heirloom mailx 12.5 7/5/10
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Content-Scanned: Fidelis XPS MAILER
x-cbid: 13011805-5406-0000-0000-0000044DD1BF
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 18 Jan 2013 05:53:13 -0000

Total of 101 messages in the last 7 days.
 
script run at: Fri Jan 18 00:53:02 EST 2013
 
    Messages   |      Bytes        | Who
--------+------+--------+----------+------------------------
 17.82% |   18 | 18.44% |   184336 | stephen.farrell@cs.tcd.ie
  6.93% |    7 |  4.59% |    45869 | abdussalambaryun@gmail.com
  4.95% |    5 |  6.55% |    65472 | stewe@stewe.org
  5.94% |    6 |  4.84% |    48342 | petithug@acm.org
  3.96% |    4 |  6.79% |    67832 | nabil.n.bitar@verizon.com
  1.98% |    2 |  7.49% |    74822 | bclaise@cisco.com
  4.95% |    5 |  4.16% |    41564 | brian.e.carpenter@gmail.com
  4.95% |    5 |  2.95% |    29481 | randy@psg.com
  3.96% |    4 |  3.03% |    30257 | sm@resistor.net
  3.96% |    4 |  2.74% |    27382 | john-ietf@jck.com
  0.99% |    1 |  5.58% |    55789 | aldrin.ietf@gmail.com
  3.96% |    4 |  2.59% |    25847 | drc@virtualized.org
  2.97% |    3 |  2.48% |    24757 | lars@netapp.com
  2.97% |    3 |  2.00% |    20008 | ned+ietf@mauve.mrochek.com
  2.97% |    3 |  1.91% |    19120 | mrex@sap.com
  1.98% |    2 |  2.28% |    22756 | john@jlc.net
  1.98% |    2 |  1.90% |    18978 | magnus.westerlund@ericsson.com
  1.98% |    2 |  1.60% |    16022 | ogud@ogud.com
  1.98% |    2 |  1.48% |    14769 | dean.willis@softarmor.com
  0.99% |    1 |  1.69% |    16871 | ron.even.tlv@gmail.com
  0.99% |    1 |  1.48% |    14824 | bernard_aboba@hotmail.com
  0.99% |    1 |  1.08% |    10763 | hsantos@isdg.net
  0.99% |    1 |  1.07% |    10707 | shanna@juniper.net
  0.99% |    1 |  1.02% |    10205 | benl@google.com
  0.99% |    1 |  0.98% |     9840 | narten@us.ibm.com
  0.99% |    1 |  0.88% |     8797 | barryleiba@computer.org
  0.99% |    1 |  0.84% |     8382 | ncamwing@cisco.com
  0.99% |    1 |  0.82% |     8183 | eburger@standardstrack.com
  0.99% |    1 |  0.78% |     7804 | arturo.servin@gmail.com
  0.99% |    1 |  0.73% |     7331 | adrian@olddog.co.uk
  0.99% |    1 |  0.73% |     7328 | d3e3e3@gmail.com
  0.99% |    1 |  0.71% |     7106 | ben@nostrum.com
  0.99% |    1 |  0.70% |     7035 | dhc@dcrocker.net
  0.99% |    1 |  0.70% |     6954 | huubatwork@gmail.com
  0.99% |    1 |  0.66% |     6628 | sm+ietf@elandsys.com
  0.99% |    1 |  0.62% |     6242 | chair@ietf.org
  0.99% |    1 |  0.59% |     5863 | lee@asgard.org
  0.99% |    1 |  0.53% |     5290 | stpeter@stpeter.im
--------+------+--------+----------+------------------------
100.00% |  101 |100.00% |   999556 | Total


From bclaise@cisco.com  Fri Jan 18 08:07:02 2013
Return-Path: <bclaise@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9C54021F8880; Fri, 18 Jan 2013 08:07:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0
X-Spam-Level: 
X-Spam-Status: No, score=x tagged_above=-999 required=5 tests=[]
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 MD4AcoEKbqDn; Fri, 18 Jan 2013 08:07:01 -0800 (PST)
Received: from av-tac-bru.cisco.com (weird-brew.cisco.com [144.254.15.118]) by ietfa.amsl.com (Postfix) with ESMTP id E418421F88B5; Fri, 18 Jan 2013 08:06:59 -0800 (PST)
X-TACSUNS: Virus Scanned
Received: from strange-brew.cisco.com (localhost.cisco.com [127.0.0.1]) by av-tac-bru.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id r0IG6wnT001438; Fri, 18 Jan 2013 17:06:58 +0100 (CET)
Received: from [10.60.67.84] (ams-bclaise-8913.cisco.com [10.60.67.84]) by strange-brew.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id r0IG6K8H010215; Fri, 18 Jan 2013 17:06:30 +0100 (CET)
Message-ID: <50F972FC.2030707@cisco.com>
Date: Fri, 18 Jan 2013 17:06:20 +0100
From: Benoit Claise <bclaise@cisco.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130107 Thunderbird/17.0.2
MIME-Version: 1.0
To: "draft-ietf-opsawg-oam-overview@tools.ietf.org" <draft-ietf-opsawg-oam-overview@tools.ietf.org>
Subject: Re: Last Call: <draft-ietf-opsawg-oam-overview-08.txt> (An Overview of Operations, Administration, and Maintenance (OAM) Mechanisms) to Informational RFC
References: <20130111193616.19158.16205.idtracker@ietfa.amsl.com> <50F437BF.8040005@cisco.com>
In-Reply-To: <50F437BF.8040005@cisco.com>
Content-Type: multipart/alternative; boundary="------------080205090701090609030103"
Cc: opsawg@ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 18 Jan 2013 16:07:02 -0000

This is a multi-part message in MIME format.
--------------080205090701090609030103
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Here is Tom Nadeau's feedback, forwarded with permission:

Regards, Benoit

==============

Some general comments:

 1. I did not find any discussion around use of configuration within OAM
    mechanisms. This is clearly something that is happening in groups
    like PWE3 and CCAMP. The motivation for this should be explained and
    documented to at least guide these efforts.

2. There is no real discussion around the security aspects of these 
tools. Should there be?

3. While the document provides a nice taxonomy of various OAM tools, it 
does not really discuss the techniques for using them. I do not expect 
anything in detail, but it is not obvious that many of these tools can 
be orchestrated to form a "toolset" that can be used to do multi-layer 
OAM functions for services such as carrier Ethernet over VPLS over MPLS, 
for example.

4. It might be useful to at least mention in the performance metrics 
section, a discussion around the accuracy of these tools and how it 
depends on scale, implementation and network configurations.


My detailed comments inline starting with TOM:

--Tom






    Expires: July 2013                                Nokia Siemens Networks
        E. Bellagamba
             Ericsson
        Y. Weingarten

      January 9, 2013

                                   An Overview of
             Operations, Administration, and Maintenance (OAM) Mechanisms
      draft-ietf-opsawg-oam-overview-08.txt


    Abstract

        Operations, Administration, and Maintenance (OAM) is a general term

        that refers to a toolset that can be used for fault detection and
        isolation, and for performance measurement. OAM mechanisms have been
        defined for various layers in the protocol stack, and are used
    with a
        variety of protocols.

        This document presents an overview of the OAM mechanisms that have
        been defined and are currently being defined by the IETF.

    Status of this Memo

        This Internet-Draft is submitted to IETF in full conformance
    with the
        provisions of BCP 78 and BCP 79.

        Internet-Drafts are working documents of the Internet Engineering
        Task Force (IETF), its areas, and its working groups.  Note that
        other groups may also distribute working documents as Internet-
        Drafts.

        Internet-Drafts are draft documents valid for a maximum of six
    months
        and may be updated, replaced, or obsoleted by other documents at any
        time.  It is inappropriate to use Internet-Drafts as reference
        material or to cite them other than as "work in progress."

        The list of current Internet-Drafts can be accessed at
        http://www.ietf.org/ietf/1id-abstracts.txt.

        The list of Internet-Draft Shadow Directories can be accessed at
        http://www.ietf.org/shadow.html.

        This Internet-Draft will expire on July 9, 2013.



    Mizrahi, et al.         Expires July 9, 2013        [Page 1]
    Internet-Draft       Overview of OAM Mechanisms   January 2013


    Copyright Notice

        Copyright (c) 2013 IETF Trust and the persons identified as the
        document authors. All rights reserved.

        This document is subject to BCP 78 and the IETF Trust's Legal
        Provisions Relating to IETF Documents
        (http://trustee.ietf.org/license-info) in effect on the date of
        publication of this document. Please review these documents
        carefully, as they describe your rights and restrictions with
    respect
        to this document. Code Components extracted from this document must
        include Simplified BSD License text as described in Section 4.e of
        the Trust Legal Provisions and are provided without warranty as
        described in the Simplified BSD License.

    Table of Contents


        1. Introduction ................................................. 3
           1.1. The Building Blocks of OAM .............................. 3
           1.2. Forwarding Plane vs. Management Plane ................... 4
           1.3. The OAM toolsets ........................................ 4
           1.4. IETF OAM Documents ...................................... 6
           1.5. Non-IETF OAM Documents ................................. 10
        2. Basic Terminology ........................................... 12
           2.1. Abbreviations .......................................... 12
           2.2. Terminology used in OAM Standards ...................... 13
              2.2.1. General Terms ..................................... 13
              2.2.2. OAM Maintenance Entities .......................... 13
              2.2.3. OAM Maintenance Points ............................ 14
              2.2.4. Proactive and On-demand activation ................ 15
              2.2.5. Connectivity Verification and Continuity Checks ... 15
              2.2.6. Failures .......................................... 15
        3. OAM Tools ................................................... 16
           3.1. IP Ping and Traceroute ................................. 16
              3.1.1. Ping .............................................. 16
              3.1.2. Traceroute......................................... 16
           3.2. Bidirectional Forwarding Detection (BFD) ............... 17
              3.2.1. Overview .......................................... 17
              3.2.2. BFD Control ....................................... 17
              3.2.3. BFD Echo .......................................... 18
           3.3. MPLS OAM ............................................... 18
           3.4. MPLS-TP OAM ............................................ 19
              3.4.1. Overview .......................................... 19
              3.4.2. Generic Associated Channel ........................ 19
              3.4.3. MPLS-TP OAM Toolset ............................... 20
                 3.4.3.1. Continuity Check and Connectivity Verification 20


    Mizrahi, et al.         Expires July 9, 2013        [Page 2]
    Internet-Draft       Overview of OAM Mechanisms   January 2013


                 3.4.3.2. Route Tracing ................................ 21
                 3.4.3.3. Lock Instruct ................................ 21
                 3.4.3.4. Lock Reporting ............................... 21
                 3.4.3.5. Alarm Reporting .............................. 21
                 3.4.3.6. Remote Defect Indication ..................... 22
                 3.4.3.7. Client Failure Indication .................... 22
                 3.4.3.8. Packet Loss Measurement (LM) ................. 22
                 3.4.3.9. Packet Delay Measurement (DM) ................ 22
           3.5. PWE3 OAM ............................................... 23
              3.5.1. PWE3 OAM using Virtual Circuit Connectivity
    Verification
              (VCCV) ................................................... 23
              3.5.2. PWE3 OAM using G-ACh .............................. 24
           3.6. OWAMP and TWAMP......................................... 24
              3.6.1. Overview .......................................... 24
              3.6.2. Control and Test Protocols ........................ 24
              3.6.3. OWAMP ............................................. 25
              3.6.4. TWAMP ............................................. 26
           3.7. Summary of OAM Functions ............................... 26
        4. Security Considerations ..................................... 27
        5. IANA Considerations ......................................... 27
        6. Acknowledgments ............................................. 27
        7. References .................................................. 28
           7.1. Normative References ................................... 28
           7.2. Informative References ................................. 31

    1. Introduction

        OAM is a general term that refers to a toolset for detecting,
        isolating and reporting connection failures and performance
        degradation.


        This document summarizes the OAM tools and mechanisms defined in the
        IETF.

        The term OAM in this document refers to Operations, Administration
        and Maintenance [OAM-Def], focusing on the forwarding plane of OAM.
        Hence, management aspects are outside the scope of this document.


TOM: This is a curious sentence to me since to me, OAM is management, or 
a subset of it.   Also, if you look at the referenced documents, there 
are many indirect references to MIBs, Netconf, etc... making this 
sentence further confusing. It might be helpful to explain more clearly 
that the authors here intended to not cover those things explicitly 
rather than grouping them arbitrarily under the definition of 
"management aspects"  Further, to clarify, it might be useful to expand 
on what "forwarding plane" is here just to be clear.   That is, is this 
"in band" or "out-of band" or both? Some of the tools referred to here 
also are part of the control AND data planes.

    1.1. The Building Blocks of OAM

        An OAM protocol is run in the context of a Maintenance Domain,
        consisting of two or more nodes that run the OAM protocol, referred
        to as Maintenance Points (MP).

        This subsection provides a brief summary of the common tools used by
        OAM protocols. An OAM protocol typically supports one or more of the
        tools described below.


    Mizrahi, et al.         Expires July 9, 2013        [Page 3]
    Internet-Draft       Overview of OAM Mechanisms   January 2013


        o Continuity Checking (CC):
           Used for verifying the liveness of a connection between two MPs.

        o Connectivity Verification (CV):
           Allows an MP to check whether it is connected to a peer MP,
    and to
           verify that messages from the peer MP are received through the
           expected path.

        o Path Discovery / Fault Localization:
           An MP uses this mechanism to trace the route to a peer MP, i.e.,
           to identify the nodes along the path to the peer MP. When a
           connection fails, this mechanism also allows the MP to detect the
           location of the failure.


TOM: The definition calls this "path discovery" but then talks about 
tracing routes. A better way of describing this in the paragraph would 
be that there I a use of path tracing in order to discover (or 
re-discover) paths that have been changed, created or destroyed.


        o Performance Monitoring:
           Consists of 3 main functions

             o Loss Measurement (LM) - monitors the packet loss rate of a
               connection.

             o Delay Measurement (DM) - monitors the delay and delay
               variation between MPs.

             o Throughput measurement - monitors the throughput of a
               connection.


TOM: Along with the discussion above around path trace/discovery, it is 
imperative that paths be discovered (one way or another) in order to 
successfully d performance monitoring on those paths.

    1.2. Forwarding Plane vs. Management Plane

        While the OAM tools may, and quite often do, work in conjunction
    with
        a control-plane or management plane, they are usually defined to be
        independent of the control-plane.  The OAM tools communicate
    with the
        management plane to raise alarms, and often the on-demand tools may
        be activated by the management, e.g. to locate and localize
    problems.

        The considerations of the control-plane maintenance tools or the
        functionality of the management-plane are out of scope for this
        document, which will concentrate on presenting the forwarding-plane
        tools that are used for OAM.


TOM: What about the data plane? For example, the GACH OAM type is such 
an example. VCCV also operates within the data plane after its 
configuration capabilities have been signaled.  It should also be 
mentioned that it is imperative that when required, OAM tools are 
capable of testing the actual data plane in as much accuracy as 
possible, but that they all should note how accurate.   Not all OAM 
tools are created equal.


    1.3. The OAM toolsets

        This memo provides an overview of the different sets of OAM
        mechanisms defined by the IETF. It is intended for those with little
        or no familiarity with the described mechanisms. The set of OAM
        mechanisms described in this memo are applicable to IP unicast,
    MPLS,
        pseudowires, and MPLS for the transport environment (MPLS-TP). While
        OAM mechanisms that are applicable to other technologies exist, they


    Mizrahi, et al.         Expires July 9, 2013        [Page 4]
    Internet-Draft       Overview of OAM Mechanisms   January 2013


        are beyond the scope of this memo. This document focuses on IETF
        documents that have been published as RFCs, while other ongoing OAM-
        related work is outside the scope.

        The IETF has defined OAM protocols and mechanisms in several
        different fronts:

        o IP Ping and Traceroute:
           Ping is a very simple and common application for failure
    diagnosis


TOM: I am not sure the term "common" is necessary.

           that uses ICMP Echo requests, as defined in [ICMPv4], and
           [ICMPv6].
           Traceroute ([TCPIP-Tools], [NetTools]) is an application that
           allows users to trace the path between an IP source and an IP
           destination, i.e., to identify the nodes along the path.

        o BFD:
           Bidirectional Forwarding Detection (BFD) is defined in [BFD] as a
           framework for a lightweight generic OAM mechanism.  The intention
           is to define a base mechanism that can be used with various
           encapsulation types, network environments, and in various medium
           types.

        o MPLS OAM:
           MPLS LSP Ping, as defined in [MPLS-OAM], [MPLS-OAM-FW] and [LSP-
           Ping], is an OAM mechanism for point to point MPLS LSPs. It
           includes two main functions: Ping and Traceroute.

        o MPLS-TP OAM:
           MPLS-TP OAM is defined in a set of RFCs. The OAM requirements for
           MPLS Transport Profile (MPLS-TP) are defined in [MPLS-TP-OAM].
           Each of the tools in the OAM toolset is defined in its own
    RFC, as
           specified in Section 1.4.

        o PWE3 OAM:
           The PWE3 OAM architecture defines control channels that support
           the use of existing IETF OAM tools to be used for a pseudowire
           (PW).  The control channels that are defined in [VCCV] and [PW-G-
           ACH] may be used in conjunction with ICMP Ping, LSP Ping, and BFD
           to perform CC and CV functionality.  In addition the channels
           support use of any of the MPLS-TP based OAM tools for completing
           their respective OAM functionality for a PW.

        o OWAMP and TWAMP:
           The One Way Active Measurement Protocol (OWAMP) and the Two Way
           Active Measurement Protocols (TWAMP) are two protocols defined in
           the IP Performance Metrics (IPPM) working group in the IETF.
    These
           protocols allow delay and packet loss measurement in IP networks.


    Mizrahi, et al.         Expires July 9, 2013        [Page 5]
    Internet-Draft       Overview of OAM Mechanisms   January 2013


        This document summarizes the OAM mechanisms defined by the IETF. We
        first present a comparison of the terminology used in various OAM
        standards, and then summarize the OAM functions that each OAM
        standard provides.

    1.4. IETF OAM Documents

        Table 1 summarizes the IETF OAM related RFCs discussed in this
        document.

        The table includes a "Type" column, specifying the nature of each of
        the listed documents:

        o Tool: documents that define an OAM tool or mechanism.

        o Prof.: documents that define a profile or a variant for an OAM
           tool that is defined in other documents.

        o Inf.: documents that define an infrastructure that is used by OAM
           tools.

        o Misc.: other OAM related documents, e.g., OAM requirement and
           framework documents.

      +-----------+--------------------------------------+-----+----------+
        |           | Title  |Type | RFC      |
      +-----------+--------------------------------------+-----+----------+
        |IP Ping and| Internet Control Message Protocol  |Tool | RFC 792  |
        |Traceroute | [ICMPv4]                             |     |      
        |
        | +--------------------------------------+-----+----------+
        |           | Internet Control Message Protocol  |Tool | RFC 4443 |
        |           | (ICMPv6) for the Internet Protocol   |     |      
        |
        |           | Version 6 (IPv6) Specification       |     |      
        |
        |           | [ICMPv6]                             |     |      
        |
        | +--------------------------------------+-----+----------+
        |           | A Primer On Internet and TCP/IP  |Tool | RFC 2151 |
        |           | Tools and Utilities [TCPIP-Tools]    |     |      
        |
        | +--------------------------------------+-----+----------+
        |           | FYI on a Network Management Tool |Tool | RFC 1147 |
        |           | Catalog: Tools for Monitoring and    |     |      
        |
        |           | Debugging TCP/IP Internets and       |     |      
        |
        |           | Interconnected Devices [NetTools]    |     |      
        |
        | +--------------------------------------+-----+----------+
        |           | Extended ICMP to Support Multi-Part  |Tool | RFC
    4884 |


    Mizrahi, et al.         Expires July 9, 2013        [Page 6]
    Internet-Draft       Overview of OAM Mechanisms   January 2013


        |           | Messages [ICMP-MP]                   |     |      
        |
        | +--------------------------------------+-----+----------+
        |           | ICMP Extensions for Multiprotocol  |Tool | RFC 4950 |
        |           | Label Switching [ICMP-Ext]           |     |      
        |
        | +--------------------------------------+-----+----------+
        |           | Extending ICMP for Interface and |Tool | RFC 5837 |
        |           | Next-Hop Identification [ICMP-Int]   |     |      
        |
      +-----------+--------------------------------------+-----+----------+
        |BFD        | Bidirectional Forwarding Detection |Tool | RFC 5880 |
        |           | [BFD]                                |     |      
        |
        | +--------------------------------------+-----+----------+
        |           | Bidirectional Forwarding Detection |Prof.| RFC 5881 |
        |           | (BFD) for IPv4 and IPv6 (Single Hop) |     |      
        |
        |           | [BFD-IP]                             |     |      
        |
        | +--------------------------------------+-----+----------+
        |           | Generic Application of Bidirectional |Misc.| RFC
    5882 |
        |           | Forwarding Detection [BFD-Gen]       |     |      
        |
        | +--------------------------------------+-----+----------+
        |           | Bidirectional Forwarding Detection |Prof.| RFC 5883 |
        |           | (BFD) for Multihop Paths [BFD-Multi] |     |      
        |
        | +--------------------------------------+-----+----------+
        |           | Bidirectional Forwarding Detection |Prof.| RFC 5884 |
        |           | for MPLS Label Switched Paths (LSPs) |     |      
        |
        |           | [BFD-LSP]                            |     |      
        |
        | +--------------------------------------+-----+----------+
        |           | Bidirectional Forwarding Detection |Prof.| RFC 5885 |
        |           | for the Pseudowire Virtual Circuit   |     |      
        |
        |           | Connectivity Verification (VCCV)     |     |      
        |
        |           | [BFD-VCCV]                           |     |      
        |
      +-----------+--------------------------------------+-----+----------+
        |MPLS OAM   | Operations and Management (OAM)  |Misc.| RFC 4377 |
        |           | Requirements for Multi-Protocol Label|     |      
        |
        |           | Switched (MPLS) Networks [MPLS-OAM]  |     |      
        |
        | +--------------------------------------+-----+----------+
        |           | A Framework for Multi-Protocol |Misc.| RFC 4378 |
        |           | Label Switching (MPLS) Operations    |     |      
        |
        |           | and Management (OAM) [MPLS-OAM-FW]   |     |      
        |
        | +--------------------------------------+-----+----------+
        |           | Detecting Multi-Protocol Label |Tool | RFC 4379 |
        |           | Switched (MPLS) Data Plane Failures  |     |      
        |
        |           | [LSP-Ping]                           |     |      
        |


    Mizrahi, et al.         Expires July 9, 2013        [Page 7]
    Internet-Draft       Overview of OAM Mechanisms   January 2013


        | +--------------------------------------+-----+----------+
        |           | Operations and Management (OAM)  |Misc.| RFC 4687 |
        |           | Requirements for Point-to-Multipoint |     |      
        |
        |           | MPLS Networks [MPLS-P2MP]            |     |      
        |
      +-----------+--------------------------------------+-----+----------+
        |MPLS-TP    | Requirements for OAM in MPLS-TP  |Misc.| RFC 5860 |
        |OAM        | [MPLS-TP-OAM]                        |     |      
        |
        | +--------------------------------------+-----+----------+
        |           | MPLS Generic Associated Channel  |Inf. | RFC 5586 |
        |           | [G-ACh]                              |     |      
        |
        | +--------------------------------------+-----+----------+
        |           | MPLS-TP OAM Framework  |Misc.| RFC 6371 |
        |           | [TP-OAM-FW]                          |     |      
        |
        | +--------------------------------------+-----+----------+
        |           | Proactive Connectivity Verification, |Tool | RFC
    6428 |
        |           | Continuity Check, and Remote Defect  |     |      
        |
        |           | Indication for the MPLS Transport    |     |      
        |
        |           | Profile [TP-CC-CV]                   |     |      
        |
        | +--------------------------------------+-----+----------+
        |           | MPLS On-Demand Connectivity  |Tool | RFC 6426 |
        |           | Verification and Route Tracing       |     |      
        |
        |           | [OnDemand-CV]                        |     |      
        |
        | +--------------------------------------+-----+----------+
        |           | MPLS Fault Management Operations,  |Tool | RFC 6427 |
        |           | Administration, and Maintenance (OAM)|     |      
        |
        |           | [TP-Fault]                           |     |      
        |
        | +--------------------------------------+-----+----------+
        |           | MPLS Transport Profile Lock Instruct |Tool | RFC
    6435 |
        |           | and Loopback Functions [Lock-Loop]   |     |      
        |
        | +--------------------------------------+-----+----------+
        |           | Packet Loss and Delay Measurement for|Tool | RFC
    6374 |
        |           | MPLS Networks [MPLS-LM-DM]           |     |      
        |
        | +--------------------------------------+-----+----------+
        |           | A Packet Loss and Delay Measurement  |Prof.| RFC
    6375 |
        |           | Profile for MPLS-Based Transport     |     |      
        |
        |           | Networks [TP-LM-DM]                  |     |      
        |
      +-----------+--------------------------------------+-----+----------+
        |PWE3 OAM   | Pseudowire Virtual Circuit |Inf. | RFC 5085 |
        |           | Connectivity Verification (VCCV):    |     |      
        |
        |           | A Control Channel for Pseudowires    |     |      
        |
        |           | [VCCV]                               |     |      
        |


    Mizrahi, et al.         Expires July 9, 2013        [Page 8]
    Internet-Draft       Overview of OAM Mechanisms   January 2013


        | +--------------------------------------+-----+----------+
        |           | Bidirectional Forwarding Detection |Prof.| RFC 5885 |
        |           | for the Pseudowire Virtual Circuit   |     |      
        |
        |           | Connectivity Verification (VCCV)     |     |      
        |
        |           | [BFD-VCCV]                           |     |      
        |
        | +--------------------------------------+-----+----------+
        |           | Using the Generic Associated Channel |Inf. | RFC
    6423 |
        |           | Label for Pseudowire in the MPLS     |     |      
        |
        |           | Transport Profile (MPLS-TP)          |     |      
        |
        |           | [PW-G-ACh]                           |     |      
        |
        | +--------------------------------------+-----+----------+
        |           | Pseudowire (PW) Operations,  |Misc.| RFC 6310 |
        |           | Administration, and Maintenance (OAM)|     |      
        |
        |           | Message Mapping [PW-Map]             |     |      
        |
      +-----------+--------------------------------------+-----+----------+
        |OWAMP and  | A One-way Active Measurement Protocol|Tool | RFC
    4656 |
        |TWAMP      | [OWAMP]                              |     |      
        |
        | +--------------------------------------+-----+----------+
        |           | A Two-Way Active Measurement Protocol|Tool | RFC
    5357 |
        |           | [TWAMP]                              |     |      
        |
        | +--------------------------------------+-----+----------+
        |           | Framework for IP Performance Metrics |Misc.| RFC
    2330 |
        |           | [IPPM-FW]                            |     |      
        |
        | +--------------------------------------+-----+----------+
        |           | IPPM Metrics for Measuring |Misc.| RFC 2678 |
        |           | Connectivity [IPPM-Con]              |     |      
        |
        | +--------------------------------------+-----+----------+
        |           | A One-way Delay Metric for IPPM  |Misc.| RFC 2679 |
        |           | [IPPM-1DM]                           |     |      
        |
        | +--------------------------------------+-----+----------+
        |           | A One-way Packet Loss Metric for IPPM|Misc.| RFC
    2680 |
        |           | [IPPM-1LM]                           |     |      
        |
        | +--------------------------------------+-----+----------+
        |           | A Round-trip Delay Metric for IPPM |Misc.| RFC 2681 |
        |           | [IPPM-2DM]                           |     |      
        |
      +-----------+--------------------------------------+-----+----------+
                      Table 1 Summary of IETF OAM Related RFCs







    Mizrahi, et al.         Expires July 9, 2013        [Page 9]
    Internet-Draft       Overview of OAM Mechanisms   January 2013


    1.5. Non-IETF OAM Documents

        In addition to the OAM mechanisms defined by the IETF, the IEEE and
        ITU-T have also defined various OAM mechanisms that focus on
        Ethernet, and various other transport network environments. These
        various mechanisms, defined by the three standard organizations, are
        often tightly coupled, and have had a mutual effect on each other.
        The ITU-T and IETF have both defined OAM mechanisms for MPLS LSPs,
        [ITU-T-Y1711] and [LSP-Ping]. The following OAM standards by the
    IEEE
        and ITU-T are to some extent linked to IETF OAM mechanisms listed
        above and are mentioned here only as reference material:

        o OAM mechanisms for Ethernet based networks have been defined by
           both the ITU-T in [ITU-T-Y1731], and by the IEEE in
    [IEEE802.1ag].
           The IEEE 802.3 standard defines OAM for one-hop Ethernet links
           [IEEE802.3ah].

        o The ITU-T has defined OAM for MPLS LSPs in [ITU-T-Y1711], and
           MPLS-TP OAM in [ITU-G8113.1] and [ITU-G8113.2].

        Table 2 summarizes the OAM standards mentioned in this document.
    This
        document focuses on IETF OAM standards, but these non-IETF standards
        are referenced where relevant.

      +-----------+--------------------------------------+---------------+
        |           | Title  |Standard/Draft |
      +-----------+--------------------------------------+---------------+
        |ITU-T      | Operation & Maintenance mechanism    | ITU-T Y.1711  |
        |MPLS OAM   | for MPLS networks [ITU-T-Y1711]      |               |
        | +--------------------------------------+---------------+
        |           | Assignment of the 'OAM Alert Label'  | RFC 3429      |
        |           | for Multiprotocol Label Switching    |               |
        |           | Architecture (MPLS) Operation and    |               |
        |           | Maintenance (OAM) Functions          |               |
        |           | [OAM-Label]                          |               |
        |           |                                      |               |
        |           |  Note: although this is an IETF      |               |
        |           |  document, it is listed as one of the|               |
        |           |  non-IETF OAM standards, since it    |               |
        |           |  was defined as a complementary part |               |
        |           |  of ITU-T Y.1711.                    |               |
      +-----------+--------------------------------------+---------------+
        |ITU-T      | Operations, administration and |ITU-T G.8113.2 |
        |MPLS-TP OAM| Maintenance mechanisms for MPLS-TP   |               |


    Mizrahi, et al.         Expires July 9, 2013       [Page 10]
    Internet-Draft       Overview of OAM Mechanisms   January 2013


        |           | networks using the tools defined for |               |
        |           | MPLS [ITU-G8113.2]                   |               |
        |           |                                      |               |
        |           |  Note: this document describes the   |               |
        |           |  OAM toolset defined by the IETF for |               |
        |           |  MPLS-TP, whereas ITU-T G.8113.1     |               |
        |           |  describes the OAM toolset defined   |               |
        |           |  by the ITU-T.                       |               |
        | +--------------------------------------+---------------+
        |           | Operations, Administration and |ITU-T G.8113.1 |
        |           | Maintenance mechanism for MPLS-TP in |               |
        |           | Packet Transport Network (PTN)       |               |
        | +--------------------------------------+---------------+
        |           | Allocation of a Generic Associated   | RFC 6671      |
        |           | Channel Type for ITU-T MPLS Transport|               |
        |           | Profile Operation, Maintenance, and  |               |
        |           | Administration (MPLS-TP OAM)         |               |
        |           | [ITU-T-CT]                           |               |
        |           |                                      |               |
        |           |  Note: although this is an IETF      |               |
        |           |  document, it is listed as one of the|               |
        |           |  non-IETF OAM standards, since it    |               |
        |           |  was defined as a complementary part |               |
        |           |  of ITU-T G.8113.1.                  |               |
      +-----------+--------------------------------------+---------------+
        |ITU-T      | OAM Functions and Mechanisms for |[ITU-T-Y1731]  |
        |Ethernet   | Ethernet-based Networks              |               |
        |OAM        |                                      |               |
      +-----------+--------------------------------------+---------------+
        |IEEE       | Connectivity Fault Management        | IEEE 802.1ag  |
        |CFM        | [IEEE802.1ag]                        |               |
        |           |                                      |               |
        |           |  Note: CFM was originally published  |               |
        |           |  as IEEE 802.1ag, but is now         |               |
        |           |  incorporated in the 802.1Q standard.|               |
      +-----------+--------------------------------------+---------------+
        |IEEE       | Media Access Control Parameters,     | IEEE 802.3ah  |
        |802.3      | Physical Layers, and Management      |               |
        |link level | Parameters for Subscriber Access     |               |
        |OAM        | Networks [IEEE802.3ah]               |               |
        |           |                                      |               |


    Mizrahi, et al.         Expires July 9, 2013       [Page 11]
    Internet-Draft       Overview of OAM Mechanisms   January 2013


        |           |  Note: link level OAM was originally |               |
        |           |  defined in IEEE 802.3ah, and is now |               |
        |           |  incorporated in the 802.3 standard. |               |
      +-----------+--------------------------------------+---------------+
              Table 2 Non-IETF OAM Standards Mentioned in this Document

    2. Basic Terminology

    2.1. Abbreviations

        ACH    Associated Channel Header

        AIS    Alarm Indication Signal

        BFD    Bidirectional Forwarding Detection

        CC     Continuity Check

        CV     Connectivity Verification

        DM     Delay Measurement

        FEC    Forwarding Equivalence Class

        GAL    Generic Associated Label

        ICMP   Internet Control Message Protocol

        LDP    Label Distribution Protocol

        LM     Loss Measurement

        LSP    Label Switched Path

        ME     Maintenance Entity

        MEG    Maintenance Entity Group

        MEP    MEG End Point

        MIP    MEG Intermediate Point

        MP     Maintenance Point

        MPLS   Multiprotocol Label Switching



    Mizrahi, et al.         Expires July 9, 2013       [Page 12]
    Internet-Draft       Overview of OAM Mechanisms   January 2013


        MPLS-TP MPLS Transport Profile

        MTU    Maximum Transmission Unit

        OAM    Operations, Administration, and Maintenance

        PW     Pseudowire

        PWE3   Pseudowire Emulation Edge-to-Edge

        RDI    Remote Defect Indication

        TTL    Time To Live

        VCCV   Virtual Circuit Connectivity Verification



TOM: Why is this section not at the top of this document, as is 
customary for RFCs?


    2.2. Terminology used in OAM Standards

    2.2.1. General Terms

        A wide variety of terms is used in various OAM standards. Each
    of the
        OAM standards listed in the reference section includes a section
    that
        defines terms relevant to that tool. A thesaurus of terminology for
        MPLS-TP terms is presented in [TP-Term], and provides a good summary
        of some of the OAM related terminology.

        This section presents a comparison of the terms used in various OAM
        standards, without fully quoting the definition of each term. For a
        formal definition of each term, refer to the references at the
    end of
        this document.

    2.2.2. OAM Maintenance Entities

        OAM tools are designed to monitor and manage a Maintenance Entity
        (ME).  An ME, as defined in [TP-OAM-FW], defines a relationship
        between two points of a transport path to which maintenance and
        monitoring operations apply.

        The following related terms are also quoted from [TP-OAM-FW]:

        o MEP: The two points that define a maintenance entity.

        o MEG: The collection of one or more MEs that belongs to the same
           transport path and that are maintained and monitored as a group
           are known as a Maintenance Entity Group (MEG).




    Mizrahi, et al.         Expires July 9, 2013       [Page 13]
    Internet-Draft       Overview of OAM Mechanisms   January 2013


        o MIP: In between MEPs, there are zero or more intermediate points,
           called Maintenance Entity Group Intermediate Points (MIPs).

        A pair of MEPs engaged in an ME are connected by a communication
        link, which may be one of several types of connection, e.g. a single
        physical connection, a set of physical connections, or a virtual
    link
        such as an MPLS LSP.

        The term Maintenance Entity (ME) is used in ITU-T Recommendations
        (e.g. [ITU-T-Y1731]), as well as in the MPLS-TP terminology
    ([TP-OAM-
        FW]). Various terms are used to refer to an ME. For example, BFD
    does
        not explicitly use a term that is equivalent to ME, but rather uses
        the term "session", referring to the relationship between two nodes
        using a BFD protocol. The MPLS LSP Ping ([LSP-Ping]) terminology
        simply uses the term "LSP" in this context.

        MPLS-TP has defined the terms ME and Maintenance Entity Group (MEG)
        in [TP-OAM-FW], similar to the terms defined by ITU-T.  A MEG allows
        the monitoring of a compound set of MEs, for example when monitoring
        a p2mp MEG that is considered to be the set of MEs between the root
        and each individual destination MEP.

    2.2.3. OAM Maintenance Points

        A Maintenance Point (MP) is a functional entity that is defined at a
        node in the network, and either initiates or reacts to OAM messages.
        A Maintenance End Point (MEP) is one of the end points of an ME, and
        can initiate OAM messages and respond to them. A Maintenance
        Intermediate Point (MIP) is an intermediate point between two MEPs,
        that does not generally initiate OAM frames (one exception to
    this is
        the use of AIS notifications), but is able to respond to OAM frames
        that are destined to it. A MIP in MPLS-TP identifies OAM packets
        destined to it by the value of the TTL field in the OAM packet. The
        term Maintenance Point is a general term for MEPs and MIPs.

        The 802.1ag defines a finer distinction between Up MPs and Down MPs.
        An MP is a bridge interface, that is monitored by an OAM protocol
        either in the direction facing the network, or in the direction
        facing the bridge. A Down MP is an MP that receives OAM packets
    from,
        and transmits them to the direction of the network. An Up MP
    receives
        OAM packets from, and transmits them to the direction of the
    bridging
        entity.

        MPLS-TP ([TP-OAM-FW]) uses a similar distinction on the placement of
        the MP - either at the ingress, egress, or forwarding function
    of the
        node (Down / Up MPs).  This placement is important for localization
        of a connection failure.


    Mizrahi, et al.         Expires July 9, 2013       [Page 14]
    Internet-Draft       Overview of OAM Mechanisms   January 2013


    2.2.4. Proactive and On-demand activation

        The different OAM tools may be used in one of two basic types of
        activation:

        o Proactive activation - indicates that the tool is activated on a
           continual basis periodically, where messages are sent between the
           two MEPs, and errors are detected when a certain number of
           expected messages are not received.

        o On-demand activation - indicates that the tool is activated
           "manually" to detect a specific anomaly.  In this activation a
           small number of OAM messages are sent by a MEP and the reply
           message is received.

    2.2.5. Connectivity Verification and Continuity Checks

        Two distinct classes of failure management functions are used in OAM
        protocols, connectivity verification and continuity checks. The
        distinction between these terms is defined in [MPLS-TP-OAM], and is
        used similarly in this document.

        Continuity checks are used to verify the liveness of a connection or
        a path between two MPs, and are typically sent proactively, though
        they can be invoked on-demand as well.

        A connectivity verification function allows an MP to check
    whether it
        is connected to a peer MP or not. This function also allows the
    MP to
        verify that messages from the peer MP are received through the
        correct path, thereby verifying not only that the two MPs are
        connected, but also that they are connected through the expected
        path. This allows detection of unexpected topology changes. A
        connectivity verification (CV) protocol typically uses a CV message,
        followed by a CV reply that is sent back to the originator. A CV
        function can be applied proactively or on-demand.

        Connectivity verification and continuity checks are considered
        complementary mechanisms, and are often used in conjunction with
    each
        other.

    2.2.6. Failures

        The terms Failure, Fault, and Defect are used interchangeably in the
        standards, referring to a malfunction that can be detected by a
        connectivity or a continuity check. In some standards, such as
        [IEEE802.1ag], there is no distinction between these terms, while in



    Mizrahi, et al.         Expires July 9, 2013       [Page 15]
    Internet-Draft       Overview of OAM Mechanisms   January 2013


        other standards each of these terms refers to a different type of
        malfunction.

        The terminology used in IETF MPLS-TP OAM takes after the ITU-T,
    which
        distinguishes between these terms in [ITU-T-G.806]; The term Fault
        refers to an inability to perform a required action, e.g., an
        unsuccessful attempt to deliver a packet. The term Defect refers to
        an interruption in the normal operation, such as a consecutive
    period
        of time where no packets are delivered successfully. The term
    Failure
        refers to the termination of the required function. While a Defect
        typically refers to a limited period of time, a failure refers to a
        long period of time.

    3. OAM Tools

    3.1. IP Ping and Traceroute

    3.1.1. Ping

        Ping is a common network diagnosis application for IP networks that
        uses ICMP. The ICMP Echo request/reply exchange is a connectivity
        verification function for the Internet Protocol. The originator
        transmits an ICMP Echo request packet, and the receiver replies with
        an Echo reply. ICMP ping is defined in two variants, [ICMPv4] is
    used
        for IPv4, and [ICMPv6] is used for IPv6.

    3.1.2. Traceroute

        Traceroute ([TCPIP-Tools], [NetTools]) is an application that allows
        users to discover the path between an IP source and an IP
        destination. Traceroute sends a sequence of UDP packets to UDP port
        33434 at the destination. By default, Traceroute begins by sending
        three packets (the number of packets is configurable in most
        Traceroute implementations), each with an IP Time-To-Live (TTL)
    value
        of one to the destination. These packets expire as soon as they
    reach
        the first router in the path. That router responds by sending three
        ICMP Time Exceeded Messages to the Traceroute application.
    Traceroute
        now sends another three UDP packets, each with the TTL value of 2.
        These messages cause the second router to return ICMP messages. This
        process continues, with ever increasing values for the TTL field,
        until the packets actually reach the destination. Because no
        application listens to port 33434 at the destination, the
    destination
        returns ICMP Destination Unreachable Messages indicating an
        unreachable port. This event indicates to the Traceroute application
        that it is finished.  The Traceroute program displays the round-trip
        delay associated with each of the attempts.



    Mizrahi, et al.         Expires July 9, 2013       [Page 16]
    Internet-Draft       Overview of OAM Mechanisms   January 2013


        Note that IP routing may be asymmetric. While Traceroute reveals the
        path between a source and destination, it may not reveal the reverse
        path.

        A few ICMP extensions ([ICMP-Ext], [ICMP-MP], [ICMP-Int]) have been
        defined in the context of Traceroute. These extensions augment the
        ICMP Destination Unreachable message, and can be used by Traceroute
        applications.

    3.2. Bidirectional Forwarding Detection (BFD)

    3.2.1. Overview

        While multiple OAM mechanisms have been defined for various
    protocols
        in the protocol stack, Bidirectional Forwarding Detection [BFD],
        defined by the IETF BFD working group, is a generic OAM mechanism
        that can be deployed over various encapsulating protocols, and in
        various medium types. The IETF has defined variants of the protocol
        for IP ([BFD-IP], [BFD-Multi]), for MPLS LSPs [BFD-LSP], and for
    PWE3
        [BFD-VCCV]. The usage of BFD in MPLS-TP is defined in [MPLS-TP-CC-
        CV].

        BFD includes two main OAM functions, using two types of BFD packets:
        BFD Control packets, and BFD Echo packets.

    3.2.2. BFD Control

        BFD supports a bidirectional continuity check, using BFD control
        packets, that are exchanged within a BFD session. BFD sessions
        operate in one of two modes:

        o Asynchronous mode (i.e. proactive): in this mode BFD control
           packets are sent periodically. When the receiver detects that no
           BFD control packet have been received during a predetermined
           period of time, a failure is detected.

        o Demand mode: in this mode, BFD control packets are sent on-demand.
           Upon need, a system initiates a series of BFD control packets to
           verify the liveness of the session. BFD control packets are sent
           independently in each direction.

        Each of the end-points of the monitored path maintains its own
        session identification, called a Discriminator, both of which are
        included in the BFD Control Packets that are exchanged between the
        end-points.  At the time of session establishment, the
    Discriminators
        are exchanged between the two-end points.  In addition, the
        transmission (and reception) rate is negotiated between the two end-


    Mizrahi, et al.         Expires July 9, 2013       [Page 17]
    Internet-Draft       Overview of OAM Mechanisms   January 2013


        points, based on information included in the control packets.  These
        transmission rates may be renegotiated during the session.

        During normal operation of the session, i.e. no failures are
        detected, the BFD session is in the Up state.  If no BFD Control
        packets are received during a fixed period of time, called the


TOM: Fixed, pre-configured or negotiated period of time (i.e.: BFD interval)

        Detection Time, the session is declared to be Down. The detection
        time is a function of the negotiated transmission time, and a
        parameter called Detect Mult. Detect Mult determines the number of
        missing BFD Control packets that cause the session to be declared as
        Down. This parameter is included in the BFD Control packet.

    3.2.3. BFD Echo

        A BFD echo packet is sent to a peer system, and is looped back
    to the
        originator. The echo function can be used proactively, or on-demand.

        The BFD echo function has been defined in BFD for IPv4 and IPv6
        ([BFD-IP]), but is not used in BFD for MPLS LSPs, PWs, or in BFD for
        MPLS-TP.

    3.3. MPLS OAM

        The IETF MPLS working group has defined OAM for MPLS LSPs. The
        requirements and framework of this effort are defined in [MPLS-OAM-
        FW] and [MPLS-OAM], respectively. The corresponding OAM mechanism
        defined, in this context, is LSP Ping [LSP-Ping].

        LSP Ping is based on ICMP Ping and just like its predecessor may be
        used in one of two modes:

        o "Ping" mode: In this mode LSP ping is used for end-to-end
           connectivity verification between two LERs.

        o "Traceroute" mode: This mode is used for hop-by-hop fault
           isolation.

        LSP Ping extends the basic ICMP Ping operation (of data-plane
        connectivity verification) with functionality to verify data-plane
        vs. control-plane consistency for a Forwarding Equivalence Class
        (FEC) and also Maximum Transmission Unit (MTU) problems. The
        traceroute functionality may be used to isolate and localize the
    MPLS
        faults, using the Time-to-live (TTL) indicator to incrementally
        identify the sub-path of the LSP that is successfully traversed
        before the faulty link or node.




    Mizrahi, et al.         Expires July 9, 2013       [Page 18]
    Internet-Draft       Overview of OAM Mechanisms   January 2013


        It should be noted that LSP Ping supports unique identification of
        the LSP within an addressing domain. The identification is checked
        using the full FEC identification. LSP Ping is easily extensible to
        include additional information needed to support new functionality,
        by use of Type-Length-Value (TLV) constructs. The usage of TLVs is
        typically not easy to perform in hardware, and is thus typically
        handled by the control plane.

        LSP Ping supports both asynchronous, as well as, on-demand
        activation.

    3.4. MPLS-TP OAM

    3.4.1. Overview

        The MPLS working group is currently working on defining the OAM
        toolset that fulfills the requirements for MPLS-TP OAM. The full set
        of requirements for MPLS-TP OAM are defined in [MPLS-TP-OAM], and
        include both general requirements for the behavior of the OAM
        mechanisms and a set of operations that should be supported by the
        OAM toolset.  The set of mechanisms required are further elaborated
        in [TP-OAM-FW], which describes the general architecture of the OAM
        system as well as giving overviews of the functionality of the OAM
        toolset.

        Some of the basic requirements for the OAM toolset for MPLS-TP are:

        o MPLS-TP OAM must be able to support both an IP based and non-IP
           based environment. If the network is IP based, i.e. IP
    routing and
           forwarding are available, then the MPLS-TP OAM toolset should
    rely
           on the IP routing and forwarding capabilities. On the other hand,
           in environments where IP functionality is not available, the OAM
           tools must still be able to operate without dependence on IP
           forwarding and routing.

        o OAM packets and the user traffic are required to be congruent
           (i.e. OAM packets are transmitted in-band) and there is a need to
           differentiate OAM packets from user-plane ones. Inherent in this
           requirement is the principle that MPLS-TP OAM be independent of
           any existing control-plane, although it should not preclude
    use of
           the control-plane functionality.

    3.4.2. Generic Associated Channel

        In order to address the requirement for in-band transmission of
    MPLS-
        TP OAM traffic, MPLS-TP uses a Generic Associated Channel (G-ACh),
        defined in [G-ACh] for LSP-based OAM traffic. This mechanism is
    based


    Mizrahi, et al.         Expires July 9, 2013       [Page 19]
    Internet-Draft       Overview of OAM Mechanisms   January 2013


        on the same concepts as the PWE3 ACH and VCCV mechanisms.  However,
        to address the needs of LSPs as differentiated from PW, the
    following
        concepts were defined for [G-ACh]:

        o An Associated Channel Header (ACH), that uses a format similar to
           the PW Control Word, is a 4-byte header that is prepended to OAM
           packets.

        o A Generic Associated Label (GAL). The GAL is a reserved MPLS label
           value (13) that indicates that the packet is an ACH packet
    and the
           payload follows immediately after the label stack.

    3.4.3. MPLS-TP OAM Toolset

        To address the functionality that is required of the OAM
    toolset, the
        MPLS WG conducted an analysis of the existing IETF and ITU-T OAM
        mechanisms and their ability to fulfill the required functionality.
        The conclusions of this analysis are documented in [OAM-Analys]. The
        MPLS working group currently plans to use a mixture of OAM
    mechanisms
        that are based on various existing standards, and adapt them to the
        requirements of [MPLS-TP-OAM]. Some of the main building blocks of
        this solution are based on:

        o Bidirectional Forwarding Detection ([BFD], [BFD-LSP]) for
           proactive continuity check and connectivity verification.

        o LSP Ping as defined in [LSP-Ping] for on-demand connectivity
           verification.

        o New protocol packets, using G-ACH, to address different
           functionality.

        o Performance measurement protocols that are based on the
           functionality that is described in [ITU-T-Y1731].

        The following sub-sections describe the OAM tools defined for
    MPLS-TP
        as described in [TP-OAM-FW].

    3.4.3.1. Continuity Check and Connectivity Verification

        Continuity Check and Connectivity Verification are presented in
        Section 2.2.5. of this document.  As presented there, these
    tools may
        be used either proactively or on-demand.  When using these tools
        proactively, they are generally used in tandem.

        For MPLS-TP there are two distinct tools, the proactive tool is
        defined in [TP-CC-CV] while the on-demand tool is defined in


    Mizrahi, et al.         Expires July 9, 2013       [Page 20]
    Internet-Draft       Overview of OAM Mechanisms   January 2013


        [OnDemand-CV].Proactively [MPLS-TP-OAM] states that the function
        should allow the MEPs to monitor the liveness and connectivity of a
        transport path. In on-demand mode, this function should support
        monitoring between the MEPs and, in addition, between a MEP and MIP.
        [TP-OAM-FW] highlights,  when performing Connectivity Verification,
        the need for the CC-V messages to include unique identification of
        the MEG that is being monitored and the MEP that originated the
        message.

        The proactive tool [TP-CC-CV] is based on extensions to BFD (see
        Section 3.2. ) with the additional limitation that the transmission
        and receiving rates are based on configuration by the operator.  The
        on-demand tool [OnDemand-CV] is an adaptation of LSP Ping (see
        Section 3.3. ) for the required behavior of MPLS-TP.

    3.4.3.2. Route Tracing

        [MPLS-TP-OAM] defines that there is a need for functionality that
        would allow a path end-point to identify the intermediate and end-
        points of the path. This function would be used in on-demand mode.
        Normally, this path will be used for bidirectional PW, LSP, and
        sections, however, unidirectional paths may be supported only if a
        return path exists.  The tool for this is based on the LSP Ping (see
        Section 3.3. ) functionality and is described in [OnDemand-CV].

    3.4.3.3. Lock Instruct

        The Lock Instruct function [Lock-Loop] is used to notify a transport
        path end-point of an administrative need to disable the transport
        path.  This functionality will generally be used in conjunction with
        some intrusive OAM function, e.g. Performance measurement,
    Diagnostic
        testing, to minimize the side-effect on user data traffic.

    3.4.3.4. Lock Reporting

        Lock Reporting is a function used by an end-point of a path to
    report
        to its far-end end-point that a lock condition has been affected on
        the path.

    3.4.3.5. Alarm Reporting

        Alarm Reporting is a function used by an intermediate point of a
        path, that becomes aware of a fault on the path, to report to the
        end-points of the path. [TP-OAM-FW] states that this may occur as a
        result of a defect condition discovered at a server sub-layer. This
        generates an Alarm Indication Signal (AIS) that continues until the



    Mizrahi, et al.         Expires July 9, 2013       [Page 21]
    Internet-Draft       Overview of OAM Mechanisms   January 2013


        fault is cleared. The consequent action of this function is detailed
        in [TP-OAM-FW].

    3.4.3.6. Remote Defect Indication

        Remote Defect Indication (RDI) is used proactively by a path end-
        point to report to its peer end-point that a defect is detected on a
        bidirectional connection between them. [MPLS-TP-OAM] points out that
        this function may be applied to a unidirectional LSP only if there a
        return path exists.  [TP-OAM-FW] points out that this function is
        associated with the proactive CC-V function.

    3.4.3.7. Client Failure Indication

        Client Failure Indication (CFI) is defined in [MPLS-TP-OAM] to allow
        the propagation information from one edge of the network to the
        other. The information concerns a defect to a client, in the case
        that the client does not support alarm notification.

    3.4.3.8. Packet Loss Measurement (LM)

        Packet Loss Measurement is a function used to verify the quality of
        the service. This function indicates the ratio of packets that are
        not delivered out of all packets that are transmitted by the path
        source.

        There are two possible ways of determining this measurement:

        o Using OAM packets, it is possible to compute the statistics based
           on a series of OAM packets. This, however, has the
    disadvantage of
           being artificial, and may not be representative since part of the
           packet loss may be dependent upon packet sizes.


TOM: Not just packet sizes. Things like implementation (as I mentioned 
above with the comment about the accuracy or truthfulness of the data 
plane processing of OAM packets).  Doing very accurate RTT as a simple 
example, with just IP Pings, is a tricky thing to make work.  Also, it 
is important to mention that the scale in terms of number of packets, 
number of tests, etc... can and will impact these parameters too.


        o Sending delimiting messages for the start and end of a measurement
           period during which the source and sink of the path count the
           packets transmitted and received. After the end delimiter, the
           ratio would be calculated by the path OAM entity.

    3.4.3.9. Packet Delay Measurement (DM)

        Packet Delay Measurement is a function that is used to measure one-
        way or two-way delay of a packet transmission between a pair of the
        end-points of a path (PW, LSP, or Section). Where:






    Mizrahi, et al.         Expires July 9, 2013       [Page 22]
    Internet-Draft       Overview of OAM Mechanisms   January 2013


        o One-way packet delay is the time elapsed from the start of
           transmission of the first bit of the packet by a source node
    until
           the reception of the last bit of that packet by the destination
           node.

        o Two-way packet delay is the time elapsed from the start of
           transmission of the first bit of the packet by a source node
    until
           the reception of the last bit of the loop-backed packet by the
           same source node, when the loopback is performed at the packet's
           destination node.

        Similarly to the packet loss measurement this could be performed in
        either of the two ways outlined above.

    3.5. PWE3 OAM

    3.5.1. PWE3 OAM using Virtual Circuit Connectivity Verification (VCCV)

        VCCV, as defined in [VCCV], provides a means for end-to-end fault
        detection and diagnostics tools to be extended for PWs
    (regardless of
        the underlying tunneling technology). The VCCV switching function
        provides a control channel associated with each PW (based on the PW
        Associated Channel Header (ACH) which is defined in [PW-ACH]), and
        allows transmitting the OAM packets in-band with PW data (using CC
        Type 1: In-band VCCV).

        VCCV currently supports the following OAM mechanisms: ICMP Ping, LSP
        Ping, and BFD. ICMP and LSP Ping are IP encapsulated before being
        sent over the PW ACH. BFD for VCCV [BFD-VCCV] supports two modes of
        encapsulation - either IP/UDP encapsulated (with IP/UDP header) or
        PW-ACH encapsulated (with no IP/UDP header) and provides support to
        signal the AC status. The use of the VCCV control channel provides
        the context, based on the MPLS-PW label, required to bind and
        bootstrap the BFD session to a particular pseudo wire (FEC),
        eliminating the need to exchange Discriminator values.

        VCCV consists of two components: (1) signaled component to
        communicate VCCV capabilities as part of VC label, and (2) switching
        component to cause the PW payload to be treated as a control packet.

        VCCV is not directly dependent upon the presence of a control plane.
        The VCCV capability negotiation may be performed as part of the PW
        signaling when LDP is used. In case of manual configuration of the
        PW, it is the responsibility of the operator to set consistent
        options at both ends.


TOM: Might be helpful to note that the static mode was created 
specifically to handle the MPLS-TP cases where no control plane was a 
requirement. However, new use cases such as pure mobile backhaul, etc... 
find this functionality useful too.





    Mizrahi, et al.         Expires July 9, 2013       [Page 23]
    Internet-Draft       Overview of OAM Mechanisms   January 2013


    3.5.2. PWE3 OAM using G-ACh

        As mentioned above, VCCV enables OAM for PWs by using a control
        channel for OAM packets. When PWs are used in MPLS-TP networks,
        rather than the control channels defined in VCCV, the G-ACh can be
        used as an alternative control channel. The usage of the G-ACh for
        PWs is defined in [PW-G-ACh].

    3.6. OWAMP and TWAMP

    3.6.1. Overview

        The IPPM working group in the IETF defines common criteria and
        metrics for measuring performance of IP traffic ([IPPM-FW]). Some of
        the key RFCs published by this working group have defined
    metrics for
        measuring connectivity [IPPM-Con], delay ([IPPM-1DM], [IPPM-2DM]),
        and packet loss [IPPM-1LM].

        Alternative protocols for performance measurement are defined, for
        example, in MPLS-TP OAM ([MPLS-LM-DM], [TP-LM-DM]), and in Ethernet
        OAM [ITU-T-Y1731].

        The IPPM working group has defined not only metrics for performance
        measurement, but also protocols that define how the measurement is
        carried out. The One-way Active Measurement Protocol [OWAMP] and the
        Two-Way Active Measurement Protocol [TWAMP] define a method and
        protocol for measuring delay and packet loss in IP networks.

        OWAMP [OWAMP] enables measurement of one-way characteristics of IP
        networks, such as one-way packet loss and one-way delay.  For its
        proper operation OWAMP requires accurate time of day setting at its
        end points.

        TWAMP [TWAMP] is a similar protocol that enables measurement of two-
        way (round trip) characteristics.  TWAMP does not require accurate
        time of day, and, furthermore, allows the use of a simple session
        reflector, making it an attractive alternative to OWAMP.

        OWAMP and TWAMP use two separate protocols: a Control plane
    protocol,
        and a Test plane protocol.

    3.6.2. Control and Test Protocols

        OWAMP and TWAMP control protocols run over TCP, while the test
        protocols run over UDP.  The purpose of the control protocols is to
        initiate, start, and stop test sessions, and for OWAMP to fetch
        results.  The test protocols introduce test packets (which contain


    Mizrahi, et al.         Expires July 9, 2013       [Page 24]
    Internet-Draft       Overview of OAM Mechanisms   January 2013


        sequence numbers and timestamps) along the IP path under test
        according to a schedule, and record statistics of packet arrival.
        Multiple sessions may be simultaneously defined, each with a session
        identifier, and defining the number of packets to be sent, the
    amount
        of padding to be added (and thus the packet size), the start time,
        and the send schedule (which can be either a constant time between
        test packets or exponentially distributed pseudo-random). Statistics
        recorded conform to the relevant IPPM RFCs.

        OWAMP and TWAMP test traffic is designed with security in mind.
      Test
        packets are hard to detect because they are simply UDP streams
        between negotiated port numbers, with potentially nothing static in
        the packets.  OWAMP and TWAMP also include optional authentication
        and encryption for both control and test packets.

    3.6.3. OWAMP

        OWAMP defines the following logical roles: Session-Sender, Session-
        Receiver, Server, Control-Client, and Fetch-Client.  The Session-
        Sender originates test traffic that is received by the Session-
        Receiver.  The Server configures and manages the session, as well as
        returning the results.  The Control-Client initiates requests for
        test sessions, triggers their start, and may trigger their
        termination.  The Fetch-Client requests the results of a completed
        session.  Multiple roles may be combined in a single host - for
        example, one host may play the roles of Control-Client,
    Fetch-Client,
        and Session-Sender, and a second playing the roles of Server and
        Session-Receiver.

        In a typical OWAMP session the Control-Client establishes a TCP
        connection to port 861 of the Server, which responds with a server
        greeting message indicating supported security/integrity modes. The
        Control-Client responds with the chosen communications mode and the
        Server accepts the modes.  The Control-Client then requests and
    fully
        describes a test session to which the Server responds with its
        acceptance and supporting information.  More than one test session
        may be requested with additional messages.  The Control-Client then
        starts a test session and the Server acknowledges.  The Session-
        Sender then sends test packets with pseudorandom padding to the
        Session-Receiver until the session is complete or until the Control-
        client stops the session.  Once finished, the Fetch-Client sends a
        fetch request to the server, which responds with an acknowledgement
        and immediately thereafter the result data.






    Mizrahi, et al.         Expires July 9, 2013       [Page 25]
    Internet-Draft       Overview of OAM Mechanisms   January 2013


    3.6.4. TWAMP

        TWAMP defines the following logical roles: session-sender, session-
        reflector, server, and control-client.  These are similar to the
        OWAMP roles, except that the Session-Reflector does not collect any
        packet information, and there is no need for a Fetch-Client.

        In a typical TWAMP session the Control-Client establishes a TCP
        connection to port 862 of the Server, and mode is negotiated as in
        OWAMP.  The Control-Client then requests sessions and starts them.
        The Session-Sender sends test packets with pseudorandom padding to
        the Session-Reflector which returns them with insertion of
        timestamps.

    3.7. Summary of OAM Functions

        Table 3 summarizes the OAM functions that are supported in each of
        the categories that were analyzed in this section.

      +-----------+-------+--------+--------+-----------+-------+--------+
        | Standard  |Continu|Connecti|Path    |Defect |Perform|Other   |
        |           |ity    |vity  |Discover|Indications|ance   |Function|
        |           |Check  |Verifica|y       | |Monitor|s       |
        |           |       |tion    |        | |ing    |        |
      +-----------+-------+--------+--------+-----------+-------+--------+
        |IP Ping    |       |Echo    |        |           |       |        |
        + --------- + ----- + ------ + ------ + --------- + ----- + ------ +
        |IP         |       |        |Tracerou|           |       |        |
        |Traceroute |       |        |te      |           |       |        |
        + --------- + ----- + ------ + ------ + --------- + ----- + ------ +
        |BFD        |BFD    |BFD     |        |           |       |        |
        |           |Control|Echo    |        |           |       |        |
        + --------- + ----- + ------ + ------ + --------- + ----- + ------ +
        |MPLS OAM   |       |"Ping"  |"Tracero|           |       |        |
        |(LSP Ping) |       |mode    |ute"    |           |       |        |
        |           |       |        |mode    |           |       |        |
        + --------- + ----- + ------ + ------ + --------- + ----- + ------ +
        |MPLS-TP    |CC     |CV/pro- |Route   |-Alarm |-LM    |-Diagnos|
        |OAM        |       |active  |Tracing | Reporting |-DM    | tic Tes|
        |           |       |or on-  |        |-Client    |       | t      |
        |           |       |demand  |        | Failure   |       |-Lock   |
        |           |       |        |        | Indication|       |        |
        |           |       |        |        |-Remote    |       |        |



    Mizrahi, et al.         Expires July 9, 2013       [Page 26]
    Internet-Draft       Overview of OAM Mechanisms   January 2013


        |           |       |        |        | Defect    |       |        |
        |           |       |        |        | Indication|       |        |
        + --------- + ----- + ------ + ------ + --------- + ----- + ------ +
        |PWE3 OAM   |BFD    |-BFD    |LSP-Ping|           |       |        |
        |           |       |-ICMP   |        |           |       |        |
        |           |       | Ping   |        |           |       |        |
        |           |       |-LSP-   |        |           |       |        |
        |           |       | Ping   |        |           |       |        |
        + --------- + ----- + ------ + ------ + --------- + ----- + ------ +
        |OWAMP and  |       |        |        | |-Delay |        |
        |TWAMP      |       |        |        |           | measur|        |
        |           |       |        |        |           | ement |        |
        |           |       |        |        | |-Packet|        |
        |           |       |        |        |           | loss  |        |
        |           |       |        |        |           | measur|        |
        |           |       |        |        |           | ement |        |
      +-----------+-------+--------+--------+-----------+-------+--------+
                          Table 3 Summary of OAM Functions

    4. Security Considerations

        This memo presents an overview of existing OAM mechanisms, and
        proposes no new OAM mechanisms. Therefore, this document introduces
        no security considerations. However, the OAM mechanism reviewed in
        this document can and do present security issues. The reader is
        encouraged to review the Security Considerations section of each
        document reference by this memo.

    5. IANA Considerations

        There are no new IANA considerations implied by this document.

    6. Acknowledgments

        The authors gratefully acknowledge Sasha Vainshtein, Carlos
        Pignataro, David Harrington, Dan Romascanu, Ron Bonica and other
        members of the OPSAWG mailing list for their helpful comments.

        This document was prepared using 2-Word-v2.0.template.dot.







    Mizrahi, et al.         Expires July 9, 2013       [Page 27]
    Internet-Draft       Overview of OAM Mechanisms   January 2013


    7. References

    7.1. Normative References

        [LSP-Ping]    Kompella, K., Swallow, G., "Detecting Multi-Protocol
                      Label Switched (MPLS) Data Plane Failures", RFC 4379,
                      February 2006.

        [MPLS-OAM]    Nadeau, T., Morrow, M., Swallow, G., Allan, D.,
                      Matsushima, S., "Operations and Management (OAM)
                      Requirements for Multi-Protocol Label Switched (MPLS)
                      Networks", RFC 4377, February 2006.

        [MPLS-OAM-FW] Allan, D., Nadeau, T., "A Framework for Multi-Protocol
                      Label Switching (MPLS) Operations and Management
                      (OAM)", RFC 4378, February 2006.

        [OAM-Label]   Ohta, H., "Assignment of the 'OAM Alert Label' for
                      Multiprotocol Label Switching Architecture (MPLS)
                      Operation and Maintenance (OAM) Functions", RFC 3429,
                      November 2002.

        [MPLS-TP-OAM] Vigoureux, M., Ward, D., Betts, M., "Requirements for
                      OAM in MPLS Transport Networks", RFC 5860, May 2010.

        [G-ACh]       Bocci, M., Vigoureux, M., Bryant, S., "MPLS Generic
                      Associated Channel", RFC 5586, June 2009.

        [VCCV]        Nadeau, T., Pignataro, C., "Pseudowire Virtual Circuit
                      Connectivity Verification (VCCV): A Control Channel
                      for Pseudowires", RFC 5085, December 2007.

        [PW-ACH]      Bryant, S., Swallow, G., Martini, L., McPherson, D.,
                      "Pseudowire Emulation Edge-to-Edge (PWE3) Control Word
                      for Use over an MPLS PSN", RFC 4385, February 2006.

        [ICMPv4]      Postel, J., "Internet Control Message Protocol",
    STD 5,
                      RFC 792, September 1981.

        [ICMPv6]      Conta, A., Deering, S., and M. Gupta, "Internet
    Control
                      Message Protocol (ICMPv6) for the Internet Protocol
                      Version 6 (IPv6) Specification", RFC 4443, March 2006.

        [MPLS-P2MP]   Yasukawa, S., Farrel, A., King, D., Nadeau, T.,
                      "Operations and Management (OAM) Requirements for
                      Point-to-Multipoint MPLS Networks", RFC 4687,
                      September 2006.


    Mizrahi, et al.         Expires July 9, 2013       [Page 28]
    Internet-Draft       Overview of OAM Mechanisms   January 2013


        [ICMP-Ext]    Bonica, R., Gan, D., Tappan, D., Pignataro, C., "ICMP
                      Extensions for Multiprotocol Label Switching", RFC
                      4950, August 2007.

        [ICMP-MP]     Bonica, R., Gan, D., Tappan, D., Pignataro, C.,
                      "Extended ICMP to Support Multi-Part Messages", RFC
                      4884, April 2007.

        [ICMP-Int]    Atlas, A., Bonica, R., Pignataro, C., Shen, N.,
    Rivers,
                      JR., "Extending ICMP for Interface and Next-Hop
                      Identification", RFC 5837, April 2010.

        [TCPIP-Tools] Kessler, G., Shepard, S., "A Primer On Internet and
                      TCP/IP Tools and Utilities", RFC 2151, June 1997.

        [NetTools]    Stine, R., "FYI on a Network Management Tool Catalog:
                      Tools for Monitoring and Debugging TCP/IP Internets
                      and Interconnected Devices", RFC 1147, April 1990.

        [IPPM-FW]     Paxson, V., Almes, G., Mahdavi, J., and Mathis, M.,
                      "Framework for IP Performance Metrics", RFC 2330, May
                      1998.

        [IPPM-Con]    Mahdavi, J., Paxson, V., "IPPM Metrics for Measuring
                      Connectivity", RFC 2678, September 1999.

        [IPPM-1DM]    Almes, G., Kalidindi, S., Zekauskas, M., "A One-way
                      Delay Metric for IPPM", RFC 2679, September 1999.

        [IPPM-1LM]    Almes, G., Kalidindi, S., Zekauskas, M., "A One-way
                      Packet Loss Metric for IPPM", RFC 2680, September
                      1999.

        [IPPM-2DM]    Almes, G., Kalidindi, S., Zekauskas, M., "A Round-trip
                      Delay Metric for IPPM", RFC 2681, September 1999.

        [OWAMP]       Shalunov, S., Teitelbaum, B., Karp, A., Boote, J., and
                      Zekauskas, M., "A One-way Active Measurement Protocol
                      (OWAMP)", RFC 4656, September 2006.

        [TWAMP]       Hedayat, K., Krzanowski, R., Morton, A., Yum, K., and
                      Babiarz, J., "A Two-Way Active Measurement Protocol
                      (TWAMP)", RFC 5357, October 2008.

        [BFD]         Katz, D., Ward, D., "Bidirectional Forwarding
    Detection
                      (BFD)", RFC 5880, June 2010.



    Mizrahi, et al.         Expires July 9, 2013       [Page 29]
    Internet-Draft       Overview of OAM Mechanisms   January 2013


        [BFD-IP]      Katz, D., Ward, D., "Bidirectional Forwarding
    Detection
                      (BFD) for IPv4 and IPv6 (Single Hop)", RFC 5881, June
                      2010.

        [BFD-Gen]     Katz, D., Ward, D., "Generic Application of
                      Bidirectional Forwarding Detection (BFD)", RFC 5882,
                      June 2010.

        [BFD-Multi]   Katz, D., Ward, D., "Bidirectional Forwarding
    Detection
                      (BFD) for Multihop Paths", RFC 5883, June 2010.

        [BFD-LSP]     Aggarwal, R., Kompella, K., Nadeau, T., and Swallow,
                      G., "Bidirectional Forwarding Detection (BFD) for MPLS
                      Label Switched Paths (LSPs)", RFC 5884, June 2010.

        [BFD-VCCV]    Nadeau, T., Pignataro, C., "Bidirectional Forwarding
                      Detection (BFD) for the Pseudowire Virtual Circuit
                      Connectivity Verification (VCCV)", RFC 5885, June
                      2010.

        [TP-OAM-FW]   Busi, I., Allan, D., "Operations, Administration and
                      Maintenance Framework for MPLS-based Transport
                      Networks ", RFC 6371, September 2011.

        [TP-CC-CV]    Allan, D., Swallow, G., Drake, J., "Proactive
                      Connectivity Verification, Continuity Check and Remote
                      Defect indication for MPLS Transport Profile", RFC
                      6428, November 2011.

        [OnDemand-CV] Gray, E., Bahadur, N., Boutros, S., Aggarwal, R. "MPLS
                      On-Demand Connectivity Verification and Route
                      Tracing", RFC 6426, November 2011.

        [MPLS-LM-DM]  Frost, D., Bryant, S., "Packet Loss and Delay
                      Measurement for MPLS Networks", RFC 6374, September
                      2011.

        [TP-LM-DM]    Frost, D., Bryant, S., "A Packet Loss and Delay
                      Measurement Profile for MPLS-Based Transport
                      Networks", RFC 6375, September 2011.

        [TP-Fault]    Swallow, G., Fulignoli, A., Vigoureux, M.,
    Boutros, S.,
                      "MPLS Fault Management Operations, Administration, and
                      Maintenance (OAM)", RFC 6427, November 2011.





    Mizrahi, et al.         Expires July 9, 2013       [Page 30]
    Internet-Draft       Overview of OAM Mechanisms   January 2013


        [Lock-Loop]   Boutros, S., Sivabalan, S., Aggarwal, R., Vigoureux,
                      M., Dai, X., "MPLS Transport Profile Lock Instruct and
                      Loopback Functions", RFC 6435, November 2011.

        [ITU-T-CT]    Betts, M., "Allocation of a Generic Associated Channel
                      Type for ITU-T MPLS Transport Profile Operation,
                      Maintenance, and Administration (MPLS-TP OAM)", RFC
                      6671, November 2012.

        [PW-Map]      M. Aissaoui, P. Busschbach, L. Martini, M. Morrow, T.
                      Nadeau, "Pseudowire (PW) Operations, Administration,
                      and Maintenance (OAM) Message Mapping", RFC 6310, July
                      2011.

        [PW-G-ACh]    Li, H., Martini, L., He, J., Huang, F., "Using the
                      Generic Associated Channel Label for Pseudowire in the
                      MPLS Transport Profile (MPLS-TP)", RFC 6423, November
                      2011.

    7.2. Informative References

        [OAM-Def]     Andersson, L., Van Helvoort, H., Bonica, R.,
    Romascanu,
                      D., Mansfield, S., "Guidelines for the use of the OAM
                      acronym in the IETF ", RFC 6291, June 2011.

        [OAM-Analys]  Sprecher, N., Fang, L., "An Overview of the OAM Tool
                      Set for  MPLS based Transport Networks", RFC 6669,
                      July 2012.

        [TP-Term]     Van Helvoort, H., Andersson, L., Sprecher, N., "A
                      Thesaurus for the Terminology used in Multiprotocol
                      Label Switching Transport Profile (MPLS-TP)
                      drafts/RFCs and ITU-T's Transport Network
                      Recommendations", work-in-progress, draft-ietf-mpls-
                      tp-rosetta-stone, July 2012.

        [IEEE802.1ag] IEEE 802.1Q, "IEEE Standard for Local and metropolitan
                      area networks - Media Access Control (MAC) Bridges and
                      Virtual Bridged Local Area Networks", October 2012.

        [ITU-T-Y1731] ITU-T Recommendation G.8013/Y.1731, "OAM Functions and
                      Mechanisms for Ethernet-based Networks", July 2011.

        [ITU-T-Y1711] ITU-T Recommendation Y.1711, "Operation & Maintenance
                      mechanism for MPLS networks", February 2004.




    Mizrahi, et al.         Expires July 9, 2013       [Page 31]
    Internet-Draft       Overview of OAM Mechanisms   January 2013


        [IEEE802.3ah] IEEE 802.3, "IEEE Standard for Information
    technology -
                      Local and metropolitan area networks - Carrier sense
                      multiple access with collision detection (CSMA/CD)
                      access method and physical layer specifications",
                      clause 57, December 2008.

        [ITU-T-G.806] ITU-T Recommendation G.806, "Characteristics of
                      transport equipment - Description methodology and
                      generic functionality", January 2009.

        [ITU-G8113.2] ITU-T Recommendation G.8113.2/Y.1372.2, "Operations,
                      administration and maintenance mechanisms for MPLS-TP
                      networks using the tools defined for MPLS", November
                      2012.

        [ITU-G8113.1] ITU-T Recommendation G.8113.1/Y.1372.1, "Operations,
                      Administration and Maintenance mechanism for MPLS-TP
                      in Packet Transport Network (PTN)", November 2012.



    Authors' Addresses

        Tal Mizrahi
        Marvell
        6 Hamada St.
        Yokneam, 20692
        Israel

        Email: talmi@marvell.com


        Nurit Sprecher
        Nokia Siemens Networks
        3 Hanagar St. Neve Ne'eman B
        Hod Hasharon,   45241
        Israel

        Email: nurit.sprecher@nsn.com


        Elisa Bellagamba
        Ericsson
        6 Farogatan St.
        Stockholm,   164 40
        Sweden



    Mizrahi, et al.         Expires July 9, 2013       [Page 32]
    Internet-Draft       Overview of OAM Mechanisms   January 2013


        Phone: +46 761440785
        Email: elisa.bellagamba@ericsson.com


        Yaacov Weingarten
        34 Hagefen St.
        Karnei Shomron,   4485500
        Israel

        Email: wyaacov@gmail.com









> draft-ietf-opsawg-oam-overview authors,
>
> Here is my feedback on this document.
>
> 1.
> Is this document in line with 
> http://tools.ietf.org/html/draft-ietf-trill-oam-req-04?
> * For example, the following definitions could be reused.
>     Fault: The term Fault refers to an inability to perform a required
>     action, e.g., an unsuccessful attempt to deliver a packet.
>
>     Defect: The term Defect refers to an interruption in the normal
>     operation, such that over a period of time no packets are delivered
>     successfully.
>
>     Failure: The term Failure refers to the termination of the required
>     function over a longer period of time. Persistence of a defect for a
>     period of time is interpreted as a failure.
>
> * For example, on the basic abstract
> Abstract
>
>     Operations, Administration, and Maintenance (OAM) is a general term
>     that refers to a toolset that can be used for fault detection and
>     isolation, and for performance measurement. OAM mechanisms have been
>     defined for various layers in the protocol stack, and are used with a
>     variety of protocols.
>
> Abstract (draft-ietf-trill-oam-req-04)
>
>     OAM (Operations, Administration and Maintenance) is a general term
>     used to identify functions and toolsets to troubleshoot and monitor
>     networks. This document presents, OAM Requirements applicable to
>     TRILL.
>
> So, as an example: does OAM include function?
> I advice to review draft-ietf-trill-oam-req-04
>
> 2.
> draft-ietf-trill-oam is not mentioned, while the abstract mentions:
>     This document presents an overview of the OAM mechanisms that have
>     been defined and are currently being defined by the IETF.
> Search for OAM in the current draft names (https://datatracker.ietf.org/), and you will find many references.
> Ok, I see later on:	
>     This document focuses on IETF
>     documents that have been published as RFCs, while other ongoing OAM-
>     related work is outside the scope.
> Ok, fine then: we don't need a reference to all the drafts.
> However, draft-ietf-trill-oam is closed to be a RFC, and should be mentioned.
>
>
> 3.
> Section 1
>     The term OAM in this document refers to Operations, Administration
>     and Maintenance [OAM-Def  <http://tools.ietf.org/html/draft-ietf-opsawg-oam-overview-08#ref-OAM-Def>], focusing on the forwarding plane of OAM.
> What does it mean "focusing on the forwarding plane of OAM"?
> Do you take a subset of the definition for this document?
> Btw, I don't see a definition in the terminology section.
> In section 2.2.3
>     A Maintenance Point (MP) is a functional entity that is defined at a
>     node in the network, and either initiates or reacts to OAM messages.
> Which plane is MP?
>
> 4.
> Section 1, Introduction
> "Hence, management aspects are outside the scope of this document."
> I don't understand which management aspects we speak about here.
> 5.
> Clarifying question regarding 1.2
> If speak about OWAMP or TWAMP 'synthetic traffic), is that data plane, 
> control plane, or management plane?
> Note that I found later on in the draft:
>     OWAMP and TWAMP use two separate protocols: a Control plane protocol,
>     and a Test plane protocol.
> Interestingly enough, after reading the document, I reviewed 
> http://datatracker.ietf.org/doc/draft-ietf-opsawg-oam-overview/ballot/, and 
> saw the same feedback from Stewart Bryant:
>
>     Provide a clear view of OAM functionality and its relationship
>     to various "planes" of networking (data plane, control plane,
>     management plane). In particular, the importance of
>     fate-sharing of OAM and user traffic flows in packet networks
>     should be explained.
>
> 6.
> I see a multiplication of "plane" terms in the IETF document, and in this document in particular.
> I could find: forwarding plane, management plane, control plane, data plane, user plane, and test plane.
> Way too many.
> Please be consistent
> 7.
>     Table 1 summarizes the IETF OAM related RFCs discussed in this
>     document.
>
>     Table 2 summarizes the OAM standards mentioned in this document.
>
> You need to change the Table 2 description. Do you want to say something along the lines of:
>     Table 2 summarizes the OAM standards specified by other Standard Development Organization
>     (SDO) than the IETF, along with IETF references where applicable.
>
>
> 8.
> Section 2.2.1
>     For a formal definition of each term, refer to the references at the end of
>     this document.
> Without a reference to a specific RFC, this is the type of statement which is not useful: you have 5 pages of references.
> You position this document as "An Overview of  Operations, Administration, and Maintenance (OAM) Mechanisms", but you tell the reader: "if you want to know about the terms,
> just read first all references!"
>
> 9.
> You specify some terms and some OAM categories,
>     2.2.2  <http://tools.ietf.org/html/draft-ietf-opsawg-oam-overview-08#section-2.2.2>. OAM Maintenance Entities ..........................13  <http://tools.ietf.org/html/draft-ietf-opsawg-oam-overview-08#page-13>
>           2.2.3  <http://tools.ietf.org/html/draft-ietf-opsawg-oam-overview-08#section-2.2.3>. OAM Maintenance Points ............................14  <http://tools.ietf.org/html/draft-ietf-opsawg-oam-overview-08#page-14>
>           2.2.4  <http://tools.ietf.org/html/draft-ietf-opsawg-oam-overview-08#section-2.2.4>. Proactive and On-demand activation ................15  <http://tools.ietf.org/html/draft-ietf-opsawg-oam-overview-08#page-15>
>           2.2.5  <http://tools.ietf.org/html/draft-ietf-opsawg-oam-overview-08#section-2.2.5>. Connectivity Verification and Continuity Checks ...15  <http://tools.ietf.org/html/draft-ietf-opsawg-oam-overview-08#page-15>
>           2.2.6  <http://tools.ietf.org/html/draft-ietf-opsawg-oam-overview-08#section-2.2.6>. Failures ..........................................15  <http://tools.ietf.org/html/draft-ietf-opsawg-oam-overview-08#page-15>
> ... but you don't use them in the section 3
>
> Just_one_example with section 3.2.2
> -
>     o Demand mode: in this mode, BFD control packets are sent on-demand.
>        Upon need, a system initiates a series of BFD control packets to
>        verify the liveness of the session
> Instead of liveness, you have defined Connectivity Verification and Continuity Checks  in section 2.2.5
> - OLD:
>     Each of the end-points of the monitored path maintains its own
>     session identification
> NEW:
>     Each of the MEP maintains its own session identification
> OR NEW (actually I don't know)
>     Each of the MP maintains its own session identification
> - OLD
> 	A BFD echo packet is sent to a peer system
> Peer system = MEP, MP, or something else?
> - etc...
>
> 10.
> This document is composed of a list of OAM content and references, but I'm really missing the document "scope and target audience".
> When we did RFC 6632, which is the companion document, we hadhttp://tools.ietf.org/html/rfc6632#section-1.1
>   
>     The target audience of the document is, on the one hand, IETF working
>     groups, which aim to select appropriate standard management protocols
>     and data models to address their needs concerning network management.
>     On the other hand, the document can be used as an overview and
>     guideline by non-IETF Standards Development Organizations (SDOs)
>     planning to use IETF management technologies and data models for the
>     realization of management applications.  The document can also be
>     used to initiate a discussion between the bodies with the goal to
>     gather new requirements and to detect possible gaps.  Finally, this
>     document is directed to all interested parties that seek to get an
>     overview of the current set of the IETF network management protocols
>     such as network administrators or newcomers to the IETF.
>
> You should have something similar.
>
>
> 11.
> Section 3.6.1, put the paragraph 2 at the end of the section. The "alternative" in the following sentence would then make sense
>     Alternative protocols for performance measurement are defined, for
>     example, in MPLS-TP OAM ([MPLS-LM-DM  <http://tools.ietf.org/html/draft-ietf-opsawg-oam-overview-08#ref-MPLS-LM-DM>], [TP-LM-DM  <http://tools.ietf.org/html/draft-ietf-opsawg-oam-overview-08#ref-TP-LM-DM>]), and in Ethernet
>     OAM [ITU-T-Y1731  <http://tools.ietf.org/html/draft-ietf-opsawg-oam-overview-08#ref-ITU-T-Y1731>].
>
>
> My conclusions: this document still needs some work
>
> Regards, Benoit
>   
>> The IESG has received a request from the Operations and Management Area
>> Working Group WG (opsawg) to consider the following document:
>> - 'An Overview of Operations, Administration, and Maintenance (OAM)
>>     Mechanisms'
>>    <draft-ietf-opsawg-oam-overview-08.txt> as Informational RFC
>>
>> The IESG plans to make a decision in the next few weeks, and solicits
>> final comments on this action. Please send substantive comments to the
>> ietf@ietf.org  mailing lists by 2013-01-25. Exceptionally, comments may be
>> sent toiesg@ietf.org  instead. In either case, please retain the
>> beginning of the Subject line to allow automated sorting.
>>
>> Abstract
>>
>>
>>     Operations, Administration, and Maintenance (OAM) is a general term
>>     that refers to a toolset that can be used for fault detection and
>>     isolation, and for performance measurement. OAM mechanisms have been
>>     defined for various layers in the protocol stack, and are used with a
>>     variety of protocols.
>>
>>     This document presents an overview of the OAM mechanisms that have
>>     been defined and are currently being defined by the IETF.
>>
>>
>>
>>
>> The file can be obtained via
>> http://datatracker.ietf.org/doc/draft-ietf-opsawg-oam-overview/
>>
>> IESG discussion can be tracked via
>> http://datatracker.ietf.org/doc/draft-ietf-opsawg-oam-overview/ballot/
>>
>>
>> No IPR declarations have been submitted directly on this I-D.
>>
>>
>>
>


--------------080205090701090609030103
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <div class="moz-cite-prefix">Here is Tom Nadeau's feedback,
      forwarded with permission:<br>
      <br>
      Regards, Benoit<br>
      <br>
      ==============<br>
      <br>
      <div>Some general comments:</div>
      <div><br>
      </div>
      <ol>
        <li>I did not find any discussion around use of configuration
          within OAM mechanisms. This is clearly something that is
          happening in groups like PWE3 and CCAMP. The motivation for
          this should be explained and documented to at least guide
          these efforts.</li>
      </ol>
      <div><span class="Apple-tab-span" style="white-space:pre"></span>2.
        There is no real discussion around the security aspects of these
        tools. Should there be?</div>
      <div><br>
      </div>
      <div><span class="Apple-tab-span" style="white-space:pre"></span>3.
        While the document provides a nice taxonomy of various OAM
        tools, it does not really discuss the techniques for using them.
        I do not expect anything in detail, but it is not obvious that
        many of these tools can be orchestrated to form a "toolset" that
        can be used to do multi-layer OAM functions for services such as
        carrier Ethernet over VPLS over MPLS, for example.</div>
      <div><br>
      </div>
      <div><span class="Apple-tab-span" style="white-space:pre"></span>4.
        It might be useful to at least mention in the performance
        metrics section, a discussion around the accuracy of these tools
        and how it depends on scale, implementation and network
        configurations.</div>
      <div><br>
      </div>
      <div><br>
      </div>
      <div>My detailed comments inline starting with TOM:</div>
      <div><br>
      </div>
      <div><span class="Apple-tab-span" style="white-space:pre"></span>--Tom</div>
      <div><br>
      </div>
      <div><br>
      </div>
      <div><br>
      </div>
      <div><br>
      </div>
      <div><br>
      </div>
      <span id="OLK_SRC_BODY_SECTION">
        <blockquote id="MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE"
          style="BORDER-LEFT: #b5c4df 5 solid; PADDING:0 0 0 5; MARGIN:0
          0 0 5;">
          <div text="#000000" bgcolor="#FFFFFF"><br>
            <div>Expires: July 2013 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Nokia
              Siemens Networks</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
              &nbsp; &nbsp;E. Bellagamba</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
              &nbsp; &nbsp; &nbsp; &nbsp; Ericsson</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
              &nbsp; &nbsp;Y. Weingarten</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
              &nbsp;January 9, 2013</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; An Overview of</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; Operations, Administration, and Maintenance
              (OAM) Mechanisms</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
              &nbsp;draft-ietf-opsawg-oam-overview-08.txt</div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div>Abstract</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;Operations, Administration, and Maintenance (OAM) is
              a general term</div>
          </div>
        </blockquote>
      </span><span id="OLK_SRC_BODY_SECTION">
        <blockquote id="MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE"
          style="BORDER-LEFT: #b5c4df 5 solid; PADDING:0 0 0 5; MARGIN:0
          0 0 5;">
          <div text="#000000" bgcolor="#FFFFFF">
            <div>&nbsp; &nbsp;that refers to a toolset that can be used for fault
              detection and</div>
            <div>&nbsp; &nbsp;isolation, and for performance measurement. OAM
              mechanisms have been</div>
            <div>&nbsp; &nbsp;defined for various layers in the protocol stack,
              and are used with a</div>
            <div>&nbsp; &nbsp;variety of protocols.</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;This document presents an overview of the OAM
              mechanisms that have</div>
            <div>&nbsp; &nbsp;been defined and are currently being defined by the
              IETF.</div>
            <div><br>
            </div>
            <div>Status of this Memo</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;This Internet-Draft is submitted to IETF in full
              conformance with the</div>
            <div>&nbsp; &nbsp;provisions of BCP 78 and BCP 79.</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;Internet-Drafts are working documents of the
              Internet Engineering</div>
            <div>&nbsp; &nbsp;Task Force (IETF), its areas, and its working
              groups. &nbsp;Note that</div>
            <div>&nbsp; &nbsp;other groups may also distribute working documents
              as Internet-</div>
            <div>&nbsp; &nbsp;Drafts.</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;Internet-Drafts are draft documents valid for a
              maximum of six months</div>
            <div>&nbsp; &nbsp;and may be updated, replaced, or obsoleted by other
              documents at any</div>
            <div>&nbsp; &nbsp;time. &nbsp;It is inappropriate to use Internet-Drafts as
              reference</div>
            <div>&nbsp; &nbsp;material or to cite them other than as "work in
              progress."</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;The list of current Internet-Drafts can be accessed
              at</div>
            <div>&nbsp; &nbsp;<a class="moz-txt-link-freetext" href="http://www.ietf.org/ietf/1id-abstracts.txt">http://www.ietf.org/ietf/1id-abstracts.txt</a>.</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;The list of Internet-Draft Shadow Directories can be
              accessed at</div>
            <div>&nbsp; &nbsp;<a class="moz-txt-link-freetext" href="http://www.ietf.org/shadow.html">http://www.ietf.org/shadow.html</a>.</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;This Internet-Draft will expire on July 9, 2013.</div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div>Mizrahi, et al. &nbsp; &nbsp; &nbsp; &nbsp; Expires July 9, 2013 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
              &nbsp; &nbsp; &nbsp; &nbsp;[Page 1]</div>
            <div>Internet-Draft &nbsp; &nbsp; &nbsp; Overview of OAM Mechanisms &nbsp; &nbsp; &nbsp; &nbsp;
              &nbsp; January 2013</div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div>Copyright Notice</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;Copyright (c) 2013 IETF Trust and the persons
              identified as the</div>
            <div>&nbsp; &nbsp;document authors. All rights reserved.</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;This document is subject to BCP 78 and the IETF
              Trust's Legal</div>
            <div>&nbsp; &nbsp;Provisions Relating to IETF Documents</div>
            <div>&nbsp; &nbsp;(<a class="moz-txt-link-freetext" href="http://trustee.ietf.org/license-info">http://trustee.ietf.org/license-info</a>) in effect on
              the date of</div>
            <div>&nbsp; &nbsp;publication of this document. Please review these
              documents</div>
            <div>&nbsp; &nbsp;carefully, as they describe your rights and
              restrictions with respect</div>
            <div>&nbsp; &nbsp;to this document. Code Components extracted from
              this document must</div>
            <div>&nbsp; &nbsp;include Simplified BSD License text as described in
              Section 4.e of</div>
            <div>&nbsp; &nbsp;the Trust Legal Provisions and are provided without
              warranty as</div>
            <div>&nbsp; &nbsp;described in the Simplified BSD License.</div>
            <div><br>
            </div>
            <div>Table of Contents</div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;1. Introduction
              ................................................. 3</div>
            <div>&nbsp; &nbsp; &nbsp; 1.1. The Building Blocks of OAM
              .............................. 3</div>
            <div>&nbsp; &nbsp; &nbsp; 1.2. Forwarding Plane vs. Management Plane
              ................... 4</div>
            <div>&nbsp; &nbsp; &nbsp; 1.3. The OAM toolsets
              ........................................ 4</div>
            <div>&nbsp; &nbsp; &nbsp; 1.4. IETF OAM Documents
              ...................................... 6</div>
            <div>&nbsp; &nbsp; &nbsp; 1.5. Non-IETF OAM Documents
              ................................. 10</div>
            <div>&nbsp; &nbsp;2. Basic Terminology
              ........................................... 12</div>
            <div>&nbsp; &nbsp; &nbsp; 2.1. Abbreviations
              .......................................... 12</div>
            <div>&nbsp; &nbsp; &nbsp; 2.2. Terminology used in OAM Standards
              ...................... 13</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;2.2.1. General Terms
              ..................................... 13</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;2.2.2. OAM Maintenance Entities
              .......................... 13</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;2.2.3. OAM Maintenance Points
              ............................ 14</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;2.2.4. Proactive and On-demand activation
              ................ 15</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;2.2.5. Connectivity Verification and
              Continuity Checks ... 15</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;2.2.6. Failures
              .......................................... 15</div>
            <div>&nbsp; &nbsp;3. OAM Tools
              ................................................... 16</div>
            <div>&nbsp; &nbsp; &nbsp; 3.1. IP Ping and Traceroute
              ................................. 16</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;3.1.1. Ping
              .............................................. 16</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;3.1.2.
              Traceroute......................................... 16</div>
            <div>&nbsp; &nbsp; &nbsp; 3.2. Bidirectional Forwarding Detection (BFD)
              ............... 17</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;3.2.1. Overview
              .......................................... 17</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;3.2.2. BFD Control
              ....................................... 17</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;3.2.3. BFD Echo
              .......................................... 18</div>
            <div>&nbsp; &nbsp; &nbsp; 3.3. MPLS OAM
              ............................................... 18</div>
            <div>&nbsp; &nbsp; &nbsp; 3.4. MPLS-TP OAM
              ............................................ 19</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;3.4.1. Overview
              .......................................... 19</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;3.4.2. Generic Associated Channel
              ........................ 19</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;3.4.3. MPLS-TP OAM Toolset
              ............................... 20</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 3.4.3.1. Continuity Check and Connectivity
              Verification 20</div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div>Mizrahi, et al. &nbsp; &nbsp; &nbsp; &nbsp; Expires July 9, 2013 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
              &nbsp; &nbsp; &nbsp; &nbsp;[Page 2]</div>
            <div>Internet-Draft &nbsp; &nbsp; &nbsp; Overview of OAM Mechanisms &nbsp; &nbsp; &nbsp; &nbsp;
              &nbsp; January 2013</div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 3.4.3.2. Route Tracing
              ................................ 21</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 3.4.3.3. Lock Instruct
              ................................ 21</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 3.4.3.4. Lock Reporting
              ............................... 21</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 3.4.3.5. Alarm Reporting
              .............................. 21</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 3.4.3.6. Remote Defect Indication
              ..................... 22</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 3.4.3.7. Client Failure Indication
              .................... 22</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 3.4.3.8. Packet Loss Measurement (LM)
              ................. 22</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 3.4.3.9. Packet Delay Measurement (DM)
              ................ 22</div>
            <div>&nbsp; &nbsp; &nbsp; 3.5. PWE3 OAM
              ............................................... 23</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;3.5.1. PWE3 OAM using Virtual Circuit
              Connectivity Verification</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;(VCCV)
              ................................................... 23</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;3.5.2. PWE3 OAM using G-ACh
              .............................. 24</div>
            <div>&nbsp; &nbsp; &nbsp; 3.6. OWAMP and
              TWAMP......................................... 24</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;3.6.1. Overview
              .......................................... 24</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;3.6.2. Control and Test Protocols
              ........................ 24</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;3.6.3. OWAMP
              ............................................. 25</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;3.6.4. TWAMP
              ............................................. 26</div>
            <div>&nbsp; &nbsp; &nbsp; 3.7. Summary of OAM Functions
              ............................... 26</div>
            <div>&nbsp; &nbsp;4. Security Considerations
              ..................................... 27</div>
            <div>&nbsp; &nbsp;5. IANA Considerations
              ......................................... 27</div>
            <div>&nbsp; &nbsp;6. Acknowledgments
              ............................................. 27</div>
            <div>&nbsp; &nbsp;7. References
              .................................................. 28</div>
            <div>&nbsp; &nbsp; &nbsp; 7.1. Normative References
              ................................... 28</div>
            <div>&nbsp; &nbsp; &nbsp; 7.2. Informative References
              ................................. 31</div>
            <div><br>
            </div>
            <div>1. Introduction</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;OAM is a general term that refers to a toolset for
              detecting,</div>
            <div>&nbsp; &nbsp;isolating and reporting connection failures and
              performance</div>
            <div>&nbsp; &nbsp;degradation.</div>
          </div>
        </blockquote>
      </span><span id="OLK_SRC_BODY_SECTION">
        <blockquote id="MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE"
          style="BORDER-LEFT: #b5c4df 5 solid; PADDING:0 0 0 5; MARGIN:0
          0 0 5;">
          <div text="#000000" bgcolor="#FFFFFF">
            <div><br>
            </div>
            <div>&nbsp; &nbsp;This document summarizes the OAM tools and
              mechanisms defined in the</div>
            <div>&nbsp; &nbsp;IETF.</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;The term OAM in this document refers to Operations,
              Administration</div>
            <div>&nbsp; &nbsp;and Maintenance [OAM-Def], focusing on the
              forwarding plane of OAM.</div>
            <div>&nbsp; &nbsp;Hence, management aspects are outside the scope of
              this document.</div>
          </div>
        </blockquote>
      </span>
      <div><br>
      </div>
      <div>TOM: This is a curious sentence to me since to me, OAM is
        management, or a subset of it. &nbsp; Also, if you look at the
        referenced documents, there are many indirect references to
        MIBs, Netconf, etc&#8230; making this sentence further confusing. It
        might be helpful to explain more clearly that the authors here
        intended to not cover those things explicitly rather than
        grouping them arbitrarily under the definition of "management
        aspects" &nbsp;Further, to clarify, it might be useful to expand on
        what "forwarding plane" is here just to be clear. &nbsp; That is, is
        this "in band" or "out-of band" or both? Some of the tools
        referred to here also are part of the control AND data planes.&nbsp;</div>
      <div><br>
      </div>
      <span id="OLK_SRC_BODY_SECTION">
        <blockquote id="MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE"
          style="BORDER-LEFT: #b5c4df 5 solid; PADDING:0 0 0 5; MARGIN:0
          0 0 5;">
          <div text="#000000" bgcolor="#FFFFFF">
            <div>1.1. The Building Blocks of OAM</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;An OAM protocol is run in the context of a
              Maintenance Domain,</div>
            <div>&nbsp; &nbsp;consisting of two or more nodes that run the OAM
              protocol, referred</div>
            <div>&nbsp; &nbsp;to as Maintenance Points (MP).</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;This subsection provides a brief summary of the
              common tools used by</div>
            <div>&nbsp; &nbsp;OAM protocols. An OAM protocol typically supports
              one or more of the</div>
            <div>&nbsp; &nbsp;tools described below.</div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div>Mizrahi, et al. &nbsp; &nbsp; &nbsp; &nbsp; Expires July 9, 2013 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
              &nbsp; &nbsp; &nbsp; &nbsp;[Page 3]</div>
            <div>Internet-Draft &nbsp; &nbsp; &nbsp; Overview of OAM Mechanisms &nbsp; &nbsp; &nbsp; &nbsp;
              &nbsp; January 2013</div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;o Continuity Checking (CC):</div>
            <div>&nbsp; &nbsp; &nbsp; Used for verifying the liveness of a connection
              between two MPs.</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;o Connectivity Verification (CV):</div>
            <div>&nbsp; &nbsp; &nbsp; Allows an MP to check whether it is connected to
              a peer MP, and to</div>
            <div>&nbsp; &nbsp; &nbsp; verify that messages from the peer MP are
              received through the</div>
            <div>&nbsp; &nbsp; &nbsp; expected path.</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;o Path Discovery / Fault Localization:</div>
            <div>&nbsp; &nbsp; &nbsp; An MP uses this mechanism to trace the route to a
              peer MP, i.e.,</div>
            <div>&nbsp; &nbsp; &nbsp; to identify the nodes along the path to the peer
              MP. When a</div>
            <div>&nbsp; &nbsp; &nbsp; connection fails, this mechanism also allows the
              MP to detect the</div>
            <div>&nbsp; &nbsp; &nbsp; location of the failure.</div>
          </div>
        </blockquote>
      </span>
      <div><br>
      </div>
      <div>TOM: The definition calls this "path discovery" but then
        talks about tracing routes. A better way of describing this in
        the paragraph would be that there I a use of path tracing in
        order to discover (or re-discover) paths that have been changed,
        created or destroyed. &nbsp;</div>
      <div><br>
      </div>
      <span id="OLK_SRC_BODY_SECTION">
        <blockquote id="MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE"
          style="BORDER-LEFT: #b5c4df 5 solid; PADDING:0 0 0 5; MARGIN:0
          0 0 5;">
          <div text="#000000" bgcolor="#FFFFFF">
            <div><br>
            </div>
            <div>&nbsp; &nbsp;o Performance Monitoring:</div>
            <div>&nbsp; &nbsp; &nbsp; Consists of 3 main functions</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; o Loss Measurement (LM) - monitors the packet
              loss rate of a</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; connection.</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; o Delay Measurement (DM) - monitors the delay
              and delay</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; variation between MPs.</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; o Throughput measurement - monitors the
              throughput of a</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; connection.</div>
          </div>
        </blockquote>
      </span>
      <div><br>
      </div>
      <div>TOM: Along with the discussion above around path
        trace/discovery, it is imperative that paths be discovered (one
        way or another) in order to successfully d performance
        monitoring on those paths.</div>
      <div><br>
      </div>
      <span id="OLK_SRC_BODY_SECTION">
        <blockquote id="MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE"
          style="BORDER-LEFT: #b5c4df 5 solid; PADDING:0 0 0 5; MARGIN:0
          0 0 5;">
          <div text="#000000" bgcolor="#FFFFFF">
            <div>1.2. Forwarding Plane vs. Management Plane</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;While the OAM tools may, and quite often do, work in
              conjunction with</div>
            <div>&nbsp; &nbsp;a control-plane or management plane, they are
              usually defined to be</div>
            <div>&nbsp; &nbsp;independent of the control-plane. &nbsp;The OAM tools
              communicate with the</div>
            <div>&nbsp; &nbsp;management plane to raise alarms, and often the
              on-demand tools may</div>
            <div>&nbsp; &nbsp;be activated by the management, e.g. to locate and
              localize problems.</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;The considerations of the control-plane maintenance
              tools or the</div>
            <div>&nbsp; &nbsp;functionality of the management-plane are out of
              scope for this</div>
            <div>&nbsp; &nbsp;document, which will concentrate on presenting the
              forwarding-plane</div>
            <div>&nbsp; &nbsp;tools that are used for OAM.</div>
          </div>
        </blockquote>
      </span>
      <div><br>
      </div>
      <div>TOM: What about the data plane? For example, the GACH OAM
        type is such an example. VCCV also operates within the data
        plane after its configuration capabilities have been signaled.
        &nbsp;It should also be mentioned that it is imperative that when
        required, OAM tools are capable of testing the actual data plane
        in as much accuracy as possible, but that they all should note
        how accurate. &nbsp; Not all OAM tools are created equal.</div>
      <div><br>
      </div>
      <span id="OLK_SRC_BODY_SECTION">
        <blockquote id="MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE"
          style="BORDER-LEFT: #b5c4df 5 solid; PADDING:0 0 0 5; MARGIN:0
          0 0 5;">
          <div text="#000000" bgcolor="#FFFFFF">
            <div><br>
            </div>
            <div>1.3. The OAM toolsets</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;This memo provides an overview of the different sets
              of OAM</div>
            <div>&nbsp; &nbsp;mechanisms defined by the IETF. It is intended for
              those with little</div>
            <div>&nbsp; &nbsp;or no familiarity with the described mechanisms. The
              set of OAM</div>
            <div>&nbsp; &nbsp;mechanisms described in this memo are applicable to
              IP unicast, MPLS,</div>
            <div>&nbsp; &nbsp;pseudowires, and MPLS for the transport environment
              (MPLS-TP). While</div>
            <div>&nbsp; &nbsp;OAM mechanisms that are applicable to other
              technologies exist, they</div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div>Mizrahi, et al. &nbsp; &nbsp; &nbsp; &nbsp; Expires July 9, 2013 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
              &nbsp; &nbsp; &nbsp; &nbsp;[Page 4]</div>
            <div>Internet-Draft &nbsp; &nbsp; &nbsp; Overview of OAM Mechanisms &nbsp; &nbsp; &nbsp; &nbsp;
              &nbsp; January 2013</div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;are beyond the scope of this memo. This document
              focuses on IETF</div>
            <div>&nbsp; &nbsp;documents that have been published as RFCs, while
              other ongoing OAM-</div>
            <div>&nbsp; &nbsp;related work is outside the scope.</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;The IETF has defined OAM protocols and mechanisms in
              several</div>
            <div>&nbsp; &nbsp;different fronts:</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;o IP Ping and Traceroute:</div>
            <div>&nbsp; &nbsp; &nbsp; Ping is a very simple and common application for
              failure diagnosis</div>
          </div>
        </blockquote>
      </span>
      <div><br>
      </div>
      <div>TOM: I am not sure the term "common" is necessary.</div>
      <div><br>
      </div>
      <span id="OLK_SRC_BODY_SECTION">
        <blockquote id="MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE"
          style="BORDER-LEFT: #b5c4df 5 solid; PADDING:0 0 0 5; MARGIN:0
          0 0 5;">
          <div text="#000000" bgcolor="#FFFFFF">
            <div>&nbsp; &nbsp; &nbsp; that uses ICMP Echo requests, as defined in
              [ICMPv4], and</div>
            <div>&nbsp; &nbsp; &nbsp; [ICMPv6].</div>
            <div>&nbsp; &nbsp; &nbsp; Traceroute ([TCPIP-Tools], [NetTools]) is an
              application that</div>
            <div>&nbsp; &nbsp; &nbsp; allows users to trace the path between an IP
              source and an IP</div>
            <div>&nbsp; &nbsp; &nbsp; destination, i.e., to identify the nodes along
              the path.</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;o BFD:</div>
            <div>&nbsp; &nbsp; &nbsp; Bidirectional Forwarding Detection (BFD) is
              defined in [BFD] as a</div>
            <div>&nbsp; &nbsp; &nbsp; framework for a lightweight generic OAM
              mechanism. &nbsp;The intention</div>
            <div>&nbsp; &nbsp; &nbsp; is to define a base mechanism that can be used
              with various</div>
            <div>&nbsp; &nbsp; &nbsp; encapsulation types, network environments, and in
              various medium</div>
            <div>&nbsp; &nbsp; &nbsp; types.</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;o MPLS OAM:</div>
            <div>&nbsp; &nbsp; &nbsp; MPLS LSP Ping, as defined in [MPLS-OAM],
              [MPLS-OAM-FW] and [LSP-</div>
            <div>&nbsp; &nbsp; &nbsp; Ping], is an OAM mechanism for point to point
              MPLS LSPs. It</div>
            <div>&nbsp; &nbsp; &nbsp; includes two main functions: Ping and Traceroute.</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;o MPLS-TP OAM:</div>
            <div>&nbsp; &nbsp; &nbsp; MPLS-TP OAM is defined in a set of RFCs. The OAM
              requirements for</div>
            <div>&nbsp; &nbsp; &nbsp; MPLS Transport Profile (MPLS-TP) are defined in
              [MPLS-TP-OAM].</div>
            <div>&nbsp; &nbsp; &nbsp; Each of the tools in the OAM toolset is defined
              in its own RFC, as</div>
            <div>&nbsp; &nbsp; &nbsp; specified in Section 1.4.</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;o PWE3 OAM:</div>
            <div>&nbsp; &nbsp; &nbsp; The PWE3 OAM architecture defines control
              channels that support</div>
            <div>&nbsp; &nbsp; &nbsp; the use of existing IETF OAM tools to be used for
              a pseudowire</div>
            <div>&nbsp; &nbsp; &nbsp; (PW). &nbsp;The control channels that are defined in
              [VCCV] and [PW-G-</div>
            <div>&nbsp; &nbsp; &nbsp; ACH] may be used in conjunction with ICMP Ping,
              LSP Ping, and BFD</div>
            <div>&nbsp; &nbsp; &nbsp; to perform CC and CV functionality. &nbsp;In addition
              the channels</div>
            <div>&nbsp; &nbsp; &nbsp; support use of any of the MPLS-TP based OAM tools
              for completing</div>
            <div>&nbsp; &nbsp; &nbsp; their respective OAM functionality for a PW.</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;o OWAMP and TWAMP:</div>
            <div>&nbsp; &nbsp; &nbsp; The One Way Active Measurement Protocol (OWAMP)
              and the Two Way</div>
            <div>&nbsp; &nbsp; &nbsp; Active Measurement Protocols (TWAMP) are two
              protocols defined in</div>
            <div>&nbsp; &nbsp; &nbsp; the IP Performance Metrics (IPPM) working group
              in the IETF. These</div>
            <div>&nbsp; &nbsp; &nbsp; protocols allow delay and packet loss measurement
              in IP networks.</div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div>Mizrahi, et al. &nbsp; &nbsp; &nbsp; &nbsp; Expires July 9, 2013 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
              &nbsp; &nbsp; &nbsp; &nbsp;[Page 5]</div>
            <div>Internet-Draft &nbsp; &nbsp; &nbsp; Overview of OAM Mechanisms &nbsp; &nbsp; &nbsp; &nbsp;
              &nbsp; January 2013</div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;This document summarizes the OAM mechanisms defined
              by the IETF. We</div>
            <div>&nbsp; &nbsp;first present a comparison of the terminology used
              in various OAM</div>
            <div>&nbsp; &nbsp;standards, and then summarize the OAM functions that
              each OAM</div>
            <div>&nbsp; &nbsp;standard provides.</div>
            <div><br>
            </div>
            <div>1.4. IETF OAM Documents</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;Table 1 summarizes the IETF OAM related RFCs
              discussed in this</div>
            <div>&nbsp; &nbsp;document.</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;The table includes a "Type" column, specifying the
              nature of each of</div>
            <div>&nbsp; &nbsp;the listed documents:</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;o Tool: documents that define an OAM tool or
              mechanism.</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;o Prof.: documents that define a profile or a
              variant for an OAM</div>
            <div>&nbsp; &nbsp; &nbsp; tool that is defined in other documents.</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;o Inf.: documents that define an infrastructure that
              is used by OAM</div>
            <div>&nbsp; &nbsp; &nbsp; tools.</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;o Misc.: other OAM related documents, e.g., OAM
              requirement and</div>
            <div>&nbsp; &nbsp; &nbsp; framework documents.</div>
            <div><br>
            </div>
            <div>&nbsp;
              &nbsp;+-----------+--------------------------------------+-----+----------+</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | Title &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
              &nbsp;|Type | RFC &nbsp; &nbsp; &nbsp;|</div>
            <div>&nbsp;
              &nbsp;+-----------+--------------------------------------+-----+----------+</div>
            <div>&nbsp; &nbsp;|IP Ping and| Internet Control Message Protocol &nbsp;
              &nbsp;|Tool | RFC 792 &nbsp;|</div>
            <div>&nbsp; &nbsp;|Traceroute | [ICMPv4] &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |
              &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;|</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
              +--------------------------------------+-----+----------+</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | Internet Control Message Protocol &nbsp;
              &nbsp;|Tool | RFC 4443 |</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | (ICMPv6) for the Internet Protocol &nbsp; |
              &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;|</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | Version 6 (IPv6) Specification &nbsp; &nbsp; &nbsp; |
              &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;|</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | [ICMPv6] &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |
              &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;|</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
              +--------------------------------------+-----+----------+</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | A Primer On Internet and TCP/IP &nbsp; &nbsp;
              &nbsp;|Tool | RFC 2151 |</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | Tools and Utilities [TCPIP-Tools] &nbsp; &nbsp;|
              &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;|</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
              +--------------------------------------+-----+----------+</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | FYI on a Network Management Tool &nbsp; &nbsp;
              |Tool | RFC 1147 |</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | Catalog: Tools for Monitoring and &nbsp; &nbsp;|
              &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;|</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | Debugging TCP/IP Internets and &nbsp; &nbsp; &nbsp; |
              &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;|</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | Interconnected Devices [NetTools] &nbsp; &nbsp;|
              &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;|</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
              +--------------------------------------+-----+----------+</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | Extended ICMP to Support Multi-Part
              &nbsp;|Tool | RFC 4884 |</div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div>Mizrahi, et al. &nbsp; &nbsp; &nbsp; &nbsp; Expires July 9, 2013 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
              &nbsp; &nbsp; &nbsp; &nbsp;[Page 6]</div>
            <div>Internet-Draft &nbsp; &nbsp; &nbsp; Overview of OAM Mechanisms &nbsp; &nbsp; &nbsp; &nbsp;
              &nbsp; January 2013</div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | Messages [ICMP-MP] &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |
              &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;|</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
              +--------------------------------------+-----+----------+</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | ICMP Extensions for Multiprotocol &nbsp;
              &nbsp;|Tool | RFC 4950 |</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | Label Switching [ICMP-Ext] &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |
              &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;|</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
              +--------------------------------------+-----+----------+</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | Extending ICMP for Interface and &nbsp; &nbsp;
              |Tool | RFC 5837 |</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | Next-Hop Identification [ICMP-Int] &nbsp; |
              &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;|</div>
            <div>&nbsp;
              &nbsp;+-----------+--------------------------------------+-----+----------+</div>
            <div>&nbsp; &nbsp;|BFD &nbsp; &nbsp; &nbsp; &nbsp;| Bidirectional Forwarding Detection &nbsp;
              |Tool | RFC 5880 |</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | [BFD] &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;|
              &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;|</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
              +--------------------------------------+-----+----------+</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | Bidirectional Forwarding Detection &nbsp;
              |Prof.| RFC 5881 |</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | (BFD) for IPv4 and IPv6 (Single Hop) |
              &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;|</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | [BFD-IP] &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |
              &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;|</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
              +--------------------------------------+-----+----------+</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | Generic Application of Bidirectional
              |Misc.| RFC 5882 |</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | Forwarding Detection [BFD-Gen] &nbsp; &nbsp; &nbsp; |
              &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;|</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
              +--------------------------------------+-----+----------+</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | Bidirectional Forwarding Detection &nbsp;
              |Prof.| RFC 5883 |</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | (BFD) for Multihop Paths [BFD-Multi] |
              &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;|</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
              +--------------------------------------+-----+----------+</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | Bidirectional Forwarding Detection &nbsp;
              |Prof.| RFC 5884 |</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | for MPLS Label Switched Paths (LSPs) |
              &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;|</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | [BFD-LSP] &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;|
              &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;|</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
              +--------------------------------------+-----+----------+</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | Bidirectional Forwarding Detection &nbsp;
              |Prof.| RFC 5885 |</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | for the Pseudowire Virtual Circuit &nbsp; |
              &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;|</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | Connectivity Verification (VCCV) &nbsp; &nbsp; |
              &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;|</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | [BFD-VCCV] &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |
              &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;|</div>
            <div>&nbsp;
              &nbsp;+-----------+--------------------------------------+-----+----------+</div>
            <div>&nbsp; &nbsp;|MPLS OAM &nbsp; | Operations and Management (OAM) &nbsp; &nbsp;
              &nbsp;|Misc.| RFC 4377 |</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | Requirements for Multi-Protocol Label|
              &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;|</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | Switched (MPLS) Networks [MPLS-OAM] &nbsp;|
              &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;|</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
              +--------------------------------------+-----+----------+</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | A Framework for Multi-Protocol &nbsp; &nbsp; &nbsp;
              |Misc.| RFC 4378 |</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | Label Switching (MPLS) Operations &nbsp; &nbsp;|
              &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;|</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | and Management (OAM) [MPLS-OAM-FW] &nbsp; |
              &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;|</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
              +--------------------------------------+-----+----------+</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | Detecting Multi-Protocol Label &nbsp; &nbsp; &nbsp;
              |Tool | RFC 4379 |</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | Switched (MPLS) Data Plane Failures &nbsp;|
              &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;|</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | [LSP-Ping] &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |
              &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;|</div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div>Mizrahi, et al. &nbsp; &nbsp; &nbsp; &nbsp; Expires July 9, 2013 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
              &nbsp; &nbsp; &nbsp; &nbsp;[Page 7]</div>
            <div>Internet-Draft &nbsp; &nbsp; &nbsp; Overview of OAM Mechanisms &nbsp; &nbsp; &nbsp; &nbsp;
              &nbsp; January 2013</div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
              +--------------------------------------+-----+----------+</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | Operations and Management (OAM) &nbsp; &nbsp;
              &nbsp;|Misc.| RFC 4687 |</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | Requirements for Point-to-Multipoint |
              &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;|</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | MPLS Networks [MPLS-P2MP] &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;|
              &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;|</div>
            <div>&nbsp;
              &nbsp;+-----------+--------------------------------------+-----+----------+</div>
            <div>&nbsp; &nbsp;|MPLS-TP &nbsp; &nbsp;| Requirements for OAM in MPLS-TP &nbsp; &nbsp;
              &nbsp;|Misc.| RFC 5860 |</div>
            <div>&nbsp; &nbsp;|OAM &nbsp; &nbsp; &nbsp; &nbsp;| [MPLS-TP-OAM] &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;|
              &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;|</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
              +--------------------------------------+-----+----------+</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | MPLS Generic Associated Channel &nbsp; &nbsp;
              &nbsp;|Inf. | RFC 5586 |</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | [G-ACh] &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;|
              &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;|</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
              +--------------------------------------+-----+----------+</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | MPLS-TP OAM Framework &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
              &nbsp;|Misc.| RFC 6371 |</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | [TP-OAM-FW] &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;|
              &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;|</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
              +--------------------------------------+-----+----------+</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | Proactive Connectivity Verification,
              |Tool | RFC 6428 |</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | Continuity Check, and Remote Defect &nbsp;|
              &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;|</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | Indication for the MPLS Transport &nbsp; &nbsp;|
              &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;|</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | Profile [TP-CC-CV] &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |
              &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;|</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
              +--------------------------------------+-----+----------+</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | MPLS On-Demand Connectivity &nbsp; &nbsp; &nbsp; &nbsp;
              &nbsp;|Tool | RFC 6426 |</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | Verification and Route Tracing &nbsp; &nbsp; &nbsp; |
              &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;|</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | [OnDemand-CV] &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;|
              &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;|</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
              +--------------------------------------+-----+----------+</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | MPLS Fault Management Operations, &nbsp;
              &nbsp;|Tool | RFC 6427 |</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | Administration, and Maintenance (OAM)|
              &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;|</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | [TP-Fault] &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |
              &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;|</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
              +--------------------------------------+-----+----------+</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | MPLS Transport Profile Lock Instruct
              |Tool | RFC 6435 |</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | and Loopback Functions [Lock-Loop] &nbsp; |
              &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;|</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
              +--------------------------------------+-----+----------+</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | Packet Loss and Delay Measurement
              for|Tool | RFC 6374 |</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | MPLS Networks [MPLS-LM-DM] &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |
              &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;|</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
              +--------------------------------------+-----+----------+</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | A Packet Loss and Delay Measurement
              &nbsp;|Prof.| RFC 6375 |</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | Profile for MPLS-Based Transport &nbsp; &nbsp; |
              &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;|</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | Networks [TP-LM-DM] &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;|
              &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;|</div>
            <div>&nbsp;
              &nbsp;+-----------+--------------------------------------+-----+----------+</div>
            <div>&nbsp; &nbsp;|PWE3 OAM &nbsp; | Pseudowire Virtual Circuit &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
              |Inf. | RFC 5085 |</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | Connectivity Verification (VCCV): &nbsp; &nbsp;|
              &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;|</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | A Control Channel for Pseudowires &nbsp; &nbsp;|
              &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;|</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | [VCCV] &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |
              &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;|</div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div>Mizrahi, et al. &nbsp; &nbsp; &nbsp; &nbsp; Expires July 9, 2013 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
              &nbsp; &nbsp; &nbsp; &nbsp;[Page 8]</div>
            <div>Internet-Draft &nbsp; &nbsp; &nbsp; Overview of OAM Mechanisms &nbsp; &nbsp; &nbsp; &nbsp;
              &nbsp; January 2013</div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
              +--------------------------------------+-----+----------+</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | Bidirectional Forwarding Detection &nbsp;
              |Prof.| RFC 5885 |</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | for the Pseudowire Virtual Circuit &nbsp; |
              &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;|</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | Connectivity Verification (VCCV) &nbsp; &nbsp; |
              &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;|</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | [BFD-VCCV] &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |
              &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;|</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
              +--------------------------------------+-----+----------+</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | Using the Generic Associated Channel
              |Inf. | RFC 6423 |</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | Label for Pseudowire in the MPLS &nbsp; &nbsp; |
              &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;|</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | Transport Profile (MPLS-TP) &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;|
              &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;|</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | [PW-G-ACh] &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |
              &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;|</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
              +--------------------------------------+-----+----------+</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | Pseudowire (PW) Operations, &nbsp; &nbsp; &nbsp; &nbsp;
              &nbsp;|Misc.| RFC 6310 |</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | Administration, and Maintenance (OAM)|
              &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;|</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | Message Mapping [PW-Map] &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |
              &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;|</div>
            <div>&nbsp;
              &nbsp;+-----------+--------------------------------------+-----+----------+</div>
            <div>&nbsp; &nbsp;|OWAMP and &nbsp;| A One-way Active Measurement
              Protocol|Tool | RFC 4656 |</div>
            <div>&nbsp; &nbsp;|TWAMP &nbsp; &nbsp; &nbsp;| [OWAMP] &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;|
              &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;|</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
              +--------------------------------------+-----+----------+</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | A Two-Way Active Measurement
              Protocol|Tool | RFC 5357 |</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | [TWAMP] &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;|
              &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;|</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
              +--------------------------------------+-----+----------+</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | Framework for IP Performance Metrics
              |Misc.| RFC 2330 |</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | [IPPM-FW] &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;|
              &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;|</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
              +--------------------------------------+-----+----------+</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | IPPM Metrics for Measuring &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
              |Misc.| RFC 2678 |</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | Connectivity [IPPM-Con] &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;|
              &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;|</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
              +--------------------------------------+-----+----------+</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | A One-way Delay Metric for IPPM &nbsp; &nbsp;
              &nbsp;|Misc.| RFC 2679 |</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | [IPPM-1DM] &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |
              &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;|</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
              +--------------------------------------+-----+----------+</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | A One-way Packet Loss Metric for
              IPPM|Misc.| RFC 2680 |</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | [IPPM-1LM] &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |
              &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;|</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
              +--------------------------------------+-----+----------+</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | A Round-trip Delay Metric for IPPM &nbsp;
              |Misc.| RFC 2681 |</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | [IPPM-2DM] &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |
              &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;|</div>
            <div>&nbsp;
              &nbsp;+-----------+--------------------------------------+-----+----------+</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Table 1 Summary of IETF OAM Related
              RFCs</div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div>Mizrahi, et al. &nbsp; &nbsp; &nbsp; &nbsp; Expires July 9, 2013 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
              &nbsp; &nbsp; &nbsp; &nbsp;[Page 9]</div>
            <div>Internet-Draft &nbsp; &nbsp; &nbsp; Overview of OAM Mechanisms &nbsp; &nbsp; &nbsp; &nbsp;
              &nbsp; January 2013</div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div>1.5. Non-IETF OAM Documents</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;In addition to the OAM mechanisms defined by the
              IETF, the IEEE and</div>
            <div>&nbsp; &nbsp;ITU-T have also defined various OAM mechanisms that
              focus on</div>
            <div>&nbsp; &nbsp;Ethernet, and various other transport network
              environments. These</div>
            <div>&nbsp; &nbsp;various mechanisms, defined by the three standard
              organizations, are</div>
            <div>&nbsp; &nbsp;often tightly coupled, and have had a mutual effect
              on each other.</div>
            <div>&nbsp; &nbsp;The ITU-T and IETF have both defined OAM mechanisms
              for MPLS LSPs,</div>
            <div>&nbsp; &nbsp;[ITU-T-Y1711] and [LSP-Ping]. The following OAM
              standards by the IEEE</div>
            <div>&nbsp; &nbsp;and ITU-T are to some extent linked to IETF OAM
              mechanisms listed</div>
            <div>&nbsp; &nbsp;above and are mentioned here only as reference
              material:</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;o OAM mechanisms for Ethernet based networks have
              been defined by</div>
            <div>&nbsp; &nbsp; &nbsp; both the ITU-T in [ITU-T-Y1731], and by the IEEE
              in [IEEE802.1ag].</div>
            <div>&nbsp; &nbsp; &nbsp; The IEEE 802.3 standard defines OAM for one-hop
              Ethernet links</div>
            <div>&nbsp; &nbsp; &nbsp; [IEEE802.3ah].</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;o The ITU-T has defined OAM for MPLS LSPs in
              [ITU-T-Y1711], and</div>
            <div>&nbsp; &nbsp; &nbsp; MPLS-TP OAM in [ITU-G8113.1] and [ITU-G8113.2].</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;Table 2 summarizes the OAM standards mentioned in
              this document. This</div>
            <div>&nbsp; &nbsp;document focuses on IETF OAM standards, but these
              non-IETF standards</div>
            <div>&nbsp; &nbsp;are referenced where relevant.</div>
            <div><br>
            </div>
            <div>&nbsp;
              &nbsp;+-----------+--------------------------------------+---------------+</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | Title &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
              &nbsp;|Standard/Draft |</div>
            <div>&nbsp;
              &nbsp;+-----------+--------------------------------------+---------------+</div>
            <div>&nbsp; &nbsp;|ITU-T &nbsp; &nbsp; &nbsp;| Operation &amp; Maintenance mechanism
              &nbsp; &nbsp;| ITU-T Y.1711 &nbsp;|</div>
            <div>&nbsp; &nbsp;|MPLS OAM &nbsp; | for MPLS networks [ITU-T-Y1711] &nbsp; &nbsp; &nbsp;|
              &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
              +--------------------------------------+---------------+</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | Assignment of the 'OAM Alert Label' &nbsp;|
              RFC 3429 &nbsp; &nbsp; &nbsp;|</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | for Multiprotocol Label Switching &nbsp; &nbsp;|
              &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | Architecture (MPLS) Operation and &nbsp; &nbsp;|
              &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | Maintenance (OAM) Functions &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;|
              &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | [OAM-Label] &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;|
              &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;|
              &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | &nbsp;Note: although this is an IETF &nbsp; &nbsp; &nbsp;|
              &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | &nbsp;document, it is listed as one of the|
              &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | &nbsp;non-IETF OAM standards, since it &nbsp; &nbsp;|
              &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | &nbsp;was defined as a complementary part |
              &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | &nbsp;of ITU-T Y.1711. &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;|
              &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |</div>
            <div>&nbsp;
              &nbsp;+-----------+--------------------------------------+---------------+</div>
            <div>&nbsp; &nbsp;|ITU-T &nbsp; &nbsp; &nbsp;| Operations, administration and &nbsp; &nbsp; &nbsp;
              |ITU-T G.8113.2 |</div>
            <div>&nbsp; &nbsp;|MPLS-TP OAM| Maintenance mechanisms for MPLS-TP &nbsp; |
              &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |</div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div>Mizrahi, et al. &nbsp; &nbsp; &nbsp; &nbsp; Expires July 9, 2013 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
              &nbsp; &nbsp; &nbsp; [Page 10]</div>
            <div>Internet-Draft &nbsp; &nbsp; &nbsp; Overview of OAM Mechanisms &nbsp; &nbsp; &nbsp; &nbsp;
              &nbsp; January 2013</div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | networks using the tools defined for |
              &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | MPLS [ITU-G8113.2] &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |
              &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;|
              &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | &nbsp;Note: this document describes the &nbsp; |
              &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | &nbsp;OAM toolset defined by the IETF for |
              &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | &nbsp;MPLS-TP, whereas ITU-T G.8113.1 &nbsp; &nbsp; |
              &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | &nbsp;describes the OAM toolset defined &nbsp; |
              &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | &nbsp;by the ITU-T. &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |
              &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
              +--------------------------------------+---------------+</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | Operations, Administration and &nbsp; &nbsp; &nbsp;
              |ITU-T G.8113.1 |</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | Maintenance mechanism for MPLS-TP in |
              &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | Packet Transport Network (PTN) &nbsp; &nbsp; &nbsp; |
              &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
              +--------------------------------------+---------------+</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | Allocation of a Generic Associated &nbsp; |
              RFC 6671 &nbsp; &nbsp; &nbsp;|</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | Channel Type for ITU-T MPLS Transport|
              &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | Profile Operation, Maintenance, and &nbsp;|
              &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | Administration (MPLS-TP OAM) &nbsp; &nbsp; &nbsp; &nbsp; |
              &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | [ITU-T-CT] &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |
              &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;|
              &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | &nbsp;Note: although this is an IETF &nbsp; &nbsp; &nbsp;|
              &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | &nbsp;document, it is listed as one of the|
              &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | &nbsp;non-IETF OAM standards, since it &nbsp; &nbsp;|
              &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | &nbsp;was defined as a complementary part |
              &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | &nbsp;of ITU-T G.8113.1. &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;|
              &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |</div>
            <div>&nbsp;
              &nbsp;+-----------+--------------------------------------+---------------+</div>
            <div>&nbsp; &nbsp;|ITU-T &nbsp; &nbsp; &nbsp;| OAM Functions and Mechanisms for &nbsp; &nbsp;
              |[ITU-T-Y1731] &nbsp;|</div>
            <div>&nbsp; &nbsp;|Ethernet &nbsp; | Ethernet-based Networks &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;|
              &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |</div>
            <div>&nbsp; &nbsp;|OAM &nbsp; &nbsp; &nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;|
              &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |</div>
            <div>&nbsp;
              &nbsp;+-----------+--------------------------------------+---------------+</div>
            <div>&nbsp; &nbsp;|IEEE &nbsp; &nbsp; &nbsp; | Connectivity Fault Management &nbsp; &nbsp; &nbsp; &nbsp;|
              IEEE 802.1ag &nbsp;|</div>
            <div>&nbsp; &nbsp;|CFM &nbsp; &nbsp; &nbsp; &nbsp;| [IEEE802.1ag] &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;|
              &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;|
              &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | &nbsp;Note: CFM was originally published &nbsp;|
              &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | &nbsp;as IEEE 802.1ag, but is now &nbsp; &nbsp; &nbsp; &nbsp; |
              &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | &nbsp;incorporated in the 802.1Q standard.|
              &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |</div>
            <div>&nbsp;
              &nbsp;+-----------+--------------------------------------+---------------+</div>
            <div>&nbsp; &nbsp;|IEEE &nbsp; &nbsp; &nbsp; | Media Access Control Parameters, &nbsp; &nbsp; |
              IEEE 802.3ah &nbsp;|</div>
            <div>&nbsp; &nbsp;|802.3 &nbsp; &nbsp; &nbsp;| Physical Layers, and Management &nbsp; &nbsp; &nbsp;|
              &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |</div>
            <div>&nbsp; &nbsp;|link level | Parameters for Subscriber Access &nbsp; &nbsp; |
              &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |</div>
            <div>&nbsp; &nbsp;|OAM &nbsp; &nbsp; &nbsp; &nbsp;| Networks [IEEE802.3ah] &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |
              &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;|
              &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |</div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div>Mizrahi, et al. &nbsp; &nbsp; &nbsp; &nbsp; Expires July 9, 2013 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
              &nbsp; &nbsp; &nbsp; [Page 11]</div>
            <div>Internet-Draft &nbsp; &nbsp; &nbsp; Overview of OAM Mechanisms &nbsp; &nbsp; &nbsp; &nbsp;
              &nbsp; January 2013</div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | &nbsp;Note: link level OAM was originally |
              &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | &nbsp;defined in IEEE 802.3ah, and is now |
              &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | &nbsp;incorporated in the 802.3 standard. |
              &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |</div>
            <div>&nbsp;
              &nbsp;+-----------+--------------------------------------+---------------+</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Table 2 Non-IETF OAM Standards Mentioned in
              this Document</div>
            <div><br>
            </div>
            <div>2. Basic Terminology</div>
            <div><br>
            </div>
            <div>2.1. Abbreviations</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;ACH &nbsp; &nbsp;Associated Channel Header</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;AIS &nbsp; &nbsp;Alarm Indication Signal</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;BFD &nbsp; &nbsp;Bidirectional Forwarding Detection</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;CC &nbsp; &nbsp; Continuity Check</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;CV &nbsp; &nbsp; Connectivity Verification</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;DM &nbsp; &nbsp; Delay Measurement</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;FEC &nbsp; &nbsp;Forwarding Equivalence Class</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;GAL &nbsp; &nbsp;Generic Associated Label</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;ICMP &nbsp; Internet Control Message Protocol</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;LDP &nbsp; &nbsp;Label Distribution Protocol</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;LM &nbsp; &nbsp; Loss Measurement</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;LSP &nbsp; &nbsp;Label Switched Path</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;ME &nbsp; &nbsp; Maintenance Entity</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;MEG &nbsp; &nbsp;Maintenance Entity Group</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;MEP &nbsp; &nbsp;MEG End Point</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;MIP &nbsp; &nbsp;MEG Intermediate Point</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;MP &nbsp; &nbsp; Maintenance Point</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;MPLS &nbsp; Multiprotocol Label Switching</div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div>Mizrahi, et al. &nbsp; &nbsp; &nbsp; &nbsp; Expires July 9, 2013 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
              &nbsp; &nbsp; &nbsp; [Page 12]</div>
            <div>Internet-Draft &nbsp; &nbsp; &nbsp; Overview of OAM Mechanisms &nbsp; &nbsp; &nbsp; &nbsp;
              &nbsp; January 2013</div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;MPLS-TP MPLS Transport Profile</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;MTU &nbsp; &nbsp;Maximum Transmission Unit</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;OAM &nbsp; &nbsp;Operations, Administration, and Maintenance</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;PW &nbsp; &nbsp; Pseudowire</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;PWE3 &nbsp; Pseudowire Emulation Edge-to-Edge</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;RDI &nbsp; &nbsp;Remote Defect Indication</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;TTL &nbsp; &nbsp;Time To Live</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;VCCV &nbsp; Virtual Circuit Connectivity Verification</div>
          </div>
        </blockquote>
      </span>
      <div><br>
      </div>
      <div><br>
      </div>
      <div>TOM: Why is this section not at the top of this document, as
        is customary for RFCs? &nbsp;</div>
      <div><br>
      </div>
      <span id="OLK_SRC_BODY_SECTION">
        <blockquote id="MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE"
          style="BORDER-LEFT: #b5c4df 5 solid; PADDING:0 0 0 5; MARGIN:0
          0 0 5;">
          <div text="#000000" bgcolor="#FFFFFF">
            <div><br>
            </div>
            <div>2.2. Terminology used in OAM Standards</div>
            <div><br>
            </div>
            <div>2.2.1. General Terms</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;A wide variety of terms is used in various OAM
              standards. Each of the</div>
            <div>&nbsp; &nbsp;OAM standards listed in the reference section
              includes a section that</div>
            <div>&nbsp; &nbsp;defines terms relevant to that tool. A thesaurus of
              terminology for</div>
            <div>&nbsp; &nbsp;MPLS-TP terms is presented in [TP-Term], and
              provides a good summary</div>
            <div>&nbsp; &nbsp;of some of the OAM related terminology.</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;This section presents a comparison of the terms used
              in various OAM</div>
            <div>&nbsp; &nbsp;standards, without fully quoting the definition of
              each term. For a</div>
            <div>&nbsp; &nbsp;formal definition of each term, refer to the
              references at the end of</div>
            <div>&nbsp; &nbsp;this document.</div>
            <div><br>
            </div>
            <div>2.2.2. OAM Maintenance Entities</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;OAM tools are designed to monitor and manage a
              Maintenance Entity</div>
            <div>&nbsp; &nbsp;(ME). &nbsp;An ME, as defined in [TP-OAM-FW], defines a
              relationship</div>
            <div>&nbsp; &nbsp;between two points of a transport path to which
              maintenance and</div>
            <div>&nbsp; &nbsp;monitoring operations apply.</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;The following related terms are also quoted from
              [TP-OAM-FW]:</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;o MEP: The two points that define a maintenance
              entity.</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;o MEG: The collection of one or more MEs that
              belongs to the same</div>
            <div>&nbsp; &nbsp; &nbsp; transport path and that are maintained and
              monitored as a group</div>
            <div>&nbsp; &nbsp; &nbsp; are known as a Maintenance Entity Group (MEG).</div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div>Mizrahi, et al. &nbsp; &nbsp; &nbsp; &nbsp; Expires July 9, 2013 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
              &nbsp; &nbsp; &nbsp; [Page 13]</div>
            <div>Internet-Draft &nbsp; &nbsp; &nbsp; Overview of OAM Mechanisms &nbsp; &nbsp; &nbsp; &nbsp;
              &nbsp; January 2013</div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;o MIP: In between MEPs, there are zero or more
              intermediate points,</div>
            <div>&nbsp; &nbsp; &nbsp; called Maintenance Entity Group Intermediate
              Points (MIPs).</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;A pair of MEPs engaged in an ME are connected by a
              communication</div>
            <div>&nbsp; &nbsp;link, which may be one of several types of
              connection, e.g. a single</div>
            <div>&nbsp; &nbsp;physical connection, a set of physical connections,
              or a virtual link</div>
            <div>&nbsp; &nbsp;such as an MPLS LSP.</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;The term Maintenance Entity (ME) is used in ITU-T
              Recommendations</div>
            <div>&nbsp; &nbsp;(e.g. [ITU-T-Y1731]), as well as in the MPLS-TP
              terminology ([TP-OAM-</div>
            <div>&nbsp; &nbsp;FW]). Various terms are used to refer to an ME. For
              example, BFD does</div>
            <div>&nbsp; &nbsp;not explicitly use a term that is equivalent to ME,
              but rather uses</div>
            <div>&nbsp; &nbsp;the term "session", referring to the relationship
              between two nodes</div>
            <div>&nbsp; &nbsp;using a BFD protocol. The MPLS LSP Ping ([LSP-Ping])
              terminology</div>
            <div>&nbsp; &nbsp;simply uses the term "LSP" in this context.</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;MPLS-TP has defined the terms ME and Maintenance
              Entity Group (MEG)</div>
            <div>&nbsp; &nbsp;in [TP-OAM-FW], similar to the terms defined by
              ITU-T. &nbsp;A MEG allows</div>
            <div>&nbsp; &nbsp;the monitoring of a compound set of MEs, for example
              when monitoring</div>
            <div>&nbsp; &nbsp;a p2mp MEG that is considered to be the set of MEs
              between the root</div>
            <div>&nbsp; &nbsp;and each individual destination MEP.</div>
            <div><br>
            </div>
            <div>2.2.3. OAM Maintenance Points</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;A Maintenance Point (MP) is a functional entity that
              is defined at a</div>
            <div>&nbsp; &nbsp;node in the network, and either initiates or reacts
              to OAM messages.</div>
            <div>&nbsp; &nbsp;A Maintenance End Point (MEP) is one of the end
              points of an ME, and</div>
            <div>&nbsp; &nbsp;can initiate OAM messages and respond to them. A
              Maintenance</div>
            <div>&nbsp; &nbsp;Intermediate Point (MIP) is an intermediate point
              between two MEPs,</div>
            <div>&nbsp; &nbsp;that does not generally initiate OAM frames (one
              exception to this is</div>
            <div>&nbsp; &nbsp;the use of AIS notifications), but is able to
              respond to OAM frames</div>
            <div>&nbsp; &nbsp;that are destined to it. A MIP in MPLS-TP identifies
              OAM packets</div>
            <div>&nbsp; &nbsp;destined to it by the value of the TTL field in the
              OAM packet. The</div>
            <div>&nbsp; &nbsp;term Maintenance Point is a general term for MEPs
              and MIPs.</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;The 802.1ag defines a finer distinction between Up
              MPs and Down MPs.</div>
            <div>&nbsp; &nbsp;An MP is a bridge interface, that is monitored by an
              OAM protocol</div>
            <div>&nbsp; &nbsp;either in the direction facing the network, or in
              the direction</div>
            <div>&nbsp; &nbsp;facing the bridge. A Down MP is an MP that receives
              OAM packets from,</div>
            <div>&nbsp; &nbsp;and transmits them to the direction of the network.
              An Up MP receives</div>
            <div>&nbsp; &nbsp;OAM packets from, and transmits them to the
              direction of the bridging</div>
            <div>&nbsp; &nbsp;entity.</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;MPLS-TP ([TP-OAM-FW]) uses a similar distinction on
              the placement of</div>
            <div>&nbsp; &nbsp;the MP - either at the ingress, egress, or
              forwarding function of the</div>
            <div>&nbsp; &nbsp;node (Down / Up MPs). &nbsp;This placement is important
              for localization</div>
            <div>&nbsp; &nbsp;of a connection failure.</div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div>Mizrahi, et al. &nbsp; &nbsp; &nbsp; &nbsp; Expires July 9, 2013 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
              &nbsp; &nbsp; &nbsp; [Page 14]</div>
            <div>Internet-Draft &nbsp; &nbsp; &nbsp; Overview of OAM Mechanisms &nbsp; &nbsp; &nbsp; &nbsp;
              &nbsp; January 2013</div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div>2.2.4. Proactive and On-demand activation</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;The different OAM tools may be used in one of two
              basic types of</div>
            <div>&nbsp; &nbsp;activation:</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;o Proactive activation - indicates that the tool is
              activated on a</div>
            <div>&nbsp; &nbsp; &nbsp; continual basis periodically, where messages are
              sent between the</div>
            <div>&nbsp; &nbsp; &nbsp; two MEPs, and errors are detected when a certain
              number of</div>
            <div>&nbsp; &nbsp; &nbsp; expected messages are not received.</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;o On-demand activation - indicates that the tool is
              activated</div>
            <div>&nbsp; &nbsp; &nbsp; "manually" to detect a specific anomaly. &nbsp;In this
              activation a</div>
            <div>&nbsp; &nbsp; &nbsp; small number of OAM messages are sent by a MEP
              and the reply</div>
            <div>&nbsp; &nbsp; &nbsp; message is received.</div>
            <div><br>
            </div>
            <div>2.2.5. Connectivity Verification and Continuity Checks</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;Two distinct classes of failure management functions
              are used in OAM</div>
            <div>&nbsp; &nbsp;protocols, connectivity verification and continuity
              checks. The</div>
            <div>&nbsp; &nbsp;distinction between these terms is defined in
              [MPLS-TP-OAM], and is</div>
            <div>&nbsp; &nbsp;used similarly in this document.</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;Continuity checks are used to verify the liveness of
              a connection or</div>
            <div>&nbsp; &nbsp;a path between two MPs, and are typically sent
              proactively, though</div>
            <div>&nbsp; &nbsp;they can be invoked on-demand as well.</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;A connectivity verification function allows an MP to
              check whether it</div>
            <div>&nbsp; &nbsp;is connected to a peer MP or not. This function also
              allows the MP to</div>
            <div>&nbsp; &nbsp;verify that messages from the peer MP are received
              through the</div>
            <div>&nbsp; &nbsp;correct path, thereby verifying not only that the
              two MPs are</div>
            <div>&nbsp; &nbsp;connected, but also that they are connected through
              the expected</div>
            <div>&nbsp; &nbsp;path. This allows detection of unexpected topology
              changes. A</div>
            <div>&nbsp; &nbsp;connectivity verification (CV) protocol typically
              uses a CV message,</div>
            <div>&nbsp; &nbsp;followed by a CV reply that is sent back to the
              originator. A CV</div>
            <div>&nbsp; &nbsp;function can be applied proactively or on-demand.</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;Connectivity verification and continuity checks are
              considered</div>
            <div>&nbsp; &nbsp;complementary mechanisms, and are often used in
              conjunction with each</div>
            <div>&nbsp; &nbsp;other.</div>
            <div><br>
            </div>
            <div>2.2.6. Failures</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;The terms Failure, Fault, and Defect are used
              interchangeably in the</div>
            <div>&nbsp; &nbsp;standards, referring to a malfunction that can be
              detected by a</div>
            <div>&nbsp; &nbsp;connectivity or a continuity check. In some
              standards, such as</div>
            <div>&nbsp; &nbsp;[IEEE802.1ag], there is no distinction between these
              terms, while in</div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div>Mizrahi, et al. &nbsp; &nbsp; &nbsp; &nbsp; Expires July 9, 2013 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
              &nbsp; &nbsp; &nbsp; [Page 15]</div>
            <div>Internet-Draft &nbsp; &nbsp; &nbsp; Overview of OAM Mechanisms &nbsp; &nbsp; &nbsp; &nbsp;
              &nbsp; January 2013</div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;other standards each of these terms refers to a
              different type of</div>
            <div>&nbsp; &nbsp;malfunction.</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;The terminology used in IETF MPLS-TP OAM takes after
              the ITU-T, which</div>
            <div>&nbsp; &nbsp;distinguishes between these terms in [ITU-T-G.806];
              The term Fault</div>
            <div>&nbsp; &nbsp;refers to an inability to perform a required action,
              e.g., an</div>
            <div>&nbsp; &nbsp;unsuccessful attempt to deliver a packet. The term
              Defect refers to</div>
            <div>&nbsp; &nbsp;an interruption in the normal operation, such as a
              consecutive period</div>
            <div>&nbsp; &nbsp;of time where no packets are delivered successfully.
              The term Failure</div>
            <div>&nbsp; &nbsp;refers to the termination of the required function.
              While a Defect</div>
            <div>&nbsp; &nbsp;typically refers to a limited period of time, a
              failure refers to a</div>
            <div>&nbsp; &nbsp;long period of time.</div>
            <div><br>
            </div>
            <div>3. OAM Tools</div>
            <div><br>
            </div>
            <div>3.1. IP Ping and Traceroute</div>
            <div><br>
            </div>
            <div>3.1.1. Ping</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;Ping is a common network diagnosis application for
              IP networks that</div>
            <div>&nbsp; &nbsp;uses ICMP. The ICMP Echo request/reply exchange is a
              connectivity</div>
            <div>&nbsp; &nbsp;verification function for the Internet Protocol. The
              originator</div>
            <div>&nbsp; &nbsp;transmits an ICMP Echo request packet, and the
              receiver replies with</div>
            <div>&nbsp; &nbsp;an Echo reply. ICMP ping is defined in two variants,
              [ICMPv4] is used</div>
            <div>&nbsp; &nbsp;for IPv4, and [ICMPv6] is used for IPv6.</div>
            <div><br>
            </div>
            <div>3.1.2. Traceroute</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;Traceroute ([TCPIP-Tools], [NetTools]) is an
              application that allows</div>
            <div>&nbsp; &nbsp;users to discover the path between an IP source and
              an IP</div>
            <div>&nbsp; &nbsp;destination. Traceroute sends a sequence of UDP
              packets to UDP port</div>
            <div>&nbsp; &nbsp;33434 at the destination. By default, Traceroute
              begins by sending</div>
            <div>&nbsp; &nbsp;three packets (the number of packets is configurable
              in most</div>
            <div>&nbsp; &nbsp;Traceroute implementations), each with an IP
              Time-To-Live (TTL) value</div>
            <div>&nbsp; &nbsp;of one to the destination. These packets expire as
              soon as they reach</div>
            <div>&nbsp; &nbsp;the first router in the path. That router responds
              by sending three</div>
            <div>&nbsp; &nbsp;ICMP Time Exceeded Messages to the Traceroute
              application. Traceroute</div>
            <div>&nbsp; &nbsp;now sends another three UDP packets, each with the
              TTL value of 2.</div>
            <div>&nbsp; &nbsp;These messages cause the second router to return
              ICMP messages. This</div>
            <div>&nbsp; &nbsp;process continues, with ever increasing values for
              the TTL field,</div>
            <div>&nbsp; &nbsp;until the packets actually reach the destination.
              Because no</div>
            <div>&nbsp; &nbsp;application listens to port 33434 at the
              destination, the destination</div>
            <div>&nbsp; &nbsp;returns ICMP Destination Unreachable Messages
              indicating an</div>
            <div>&nbsp; &nbsp;unreachable port. This event indicates to the
              Traceroute application</div>
            <div>&nbsp; &nbsp;that it is finished. &nbsp;The Traceroute program
              displays the round-trip</div>
            <div>&nbsp; &nbsp;delay associated with each of the attempts.</div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div>Mizrahi, et al. &nbsp; &nbsp; &nbsp; &nbsp; Expires July 9, 2013 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
              &nbsp; &nbsp; &nbsp; [Page 16]</div>
            <div>Internet-Draft &nbsp; &nbsp; &nbsp; Overview of OAM Mechanisms &nbsp; &nbsp; &nbsp; &nbsp;
              &nbsp; January 2013</div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;Note that IP routing may be asymmetric. While
              Traceroute reveals the</div>
            <div>&nbsp; &nbsp;path between a source and destination, it may not
              reveal the reverse</div>
            <div>&nbsp; &nbsp;path.</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;A few ICMP extensions ([ICMP-Ext], [ICMP-MP],
              [ICMP-Int]) have been</div>
            <div>&nbsp; &nbsp;defined in the context of Traceroute. These
              extensions augment the</div>
            <div>&nbsp; &nbsp;ICMP Destination Unreachable message, and can be
              used by Traceroute</div>
            <div>&nbsp; &nbsp;applications.</div>
            <div><br>
            </div>
            <div>3.2. Bidirectional Forwarding Detection (BFD)</div>
            <div><br>
            </div>
            <div>3.2.1. Overview</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;While multiple OAM mechanisms have been defined for
              various protocols</div>
            <div>&nbsp; &nbsp;in the protocol stack, Bidirectional Forwarding
              Detection [BFD],</div>
            <div>&nbsp; &nbsp;defined by the IETF BFD working group, is a generic
              OAM mechanism</div>
            <div>&nbsp; &nbsp;that can be deployed over various encapsulating
              protocols, and in</div>
            <div>&nbsp; &nbsp;various medium types. The IETF has defined variants
              of the protocol</div>
            <div>&nbsp; &nbsp;for IP ([BFD-IP], [BFD-Multi]), for MPLS LSPs
              [BFD-LSP], and for PWE3</div>
            <div>&nbsp; &nbsp;[BFD-VCCV]. The usage of BFD in MPLS-TP is defined
              in [MPLS-TP-CC-</div>
            <div>&nbsp; &nbsp;CV].</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;BFD includes two main OAM functions, using two types
              of BFD packets:</div>
            <div>&nbsp; &nbsp;BFD Control packets, and BFD Echo packets.</div>
            <div><br>
            </div>
            <div>3.2.2. BFD Control</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;BFD supports a bidirectional continuity check, using
              BFD control</div>
            <div>&nbsp; &nbsp;packets, that are exchanged within a BFD session.
              BFD sessions</div>
            <div>&nbsp; &nbsp;operate in one of two modes:</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;o Asynchronous mode (i.e. proactive): in this mode
              BFD control</div>
            <div>&nbsp; &nbsp; &nbsp; packets are sent periodically. When the receiver
              detects that no</div>
            <div>&nbsp; &nbsp; &nbsp; BFD control packet have been received during a
              predetermined</div>
            <div>&nbsp; &nbsp; &nbsp; period of time, a failure is detected.</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;o Demand mode: in this mode, BFD control packets are
              sent on-demand.</div>
            <div>&nbsp; &nbsp; &nbsp; Upon need, a system initiates a series of BFD
              control packets to</div>
            <div>&nbsp; &nbsp; &nbsp; verify the liveness of the session. BFD control
              packets are sent</div>
            <div>&nbsp; &nbsp; &nbsp; independently in each direction.</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;Each of the end-points of the monitored path
              maintains its own</div>
            <div>&nbsp; &nbsp;session identification, called a Discriminator, both
              of which are</div>
            <div>&nbsp; &nbsp;included in the BFD Control Packets that are
              exchanged between the</div>
            <div>&nbsp; &nbsp;end-points. &nbsp;At the time of session establishment,
              the Discriminators</div>
            <div>&nbsp; &nbsp;are exchanged between the two-end points. &nbsp;In
              addition, the</div>
            <div>&nbsp; &nbsp;transmission (and reception) rate is negotiated
              between the two end-</div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div>Mizrahi, et al. &nbsp; &nbsp; &nbsp; &nbsp; Expires July 9, 2013 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
              &nbsp; &nbsp; &nbsp; [Page 17]</div>
            <div>Internet-Draft &nbsp; &nbsp; &nbsp; Overview of OAM Mechanisms &nbsp; &nbsp; &nbsp; &nbsp;
              &nbsp; January 2013</div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;points, based on information included in the control
              packets. &nbsp;These</div>
            <div>&nbsp; &nbsp;transmission rates may be renegotiated during the
              session.</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;During normal operation of the session, i.e. no
              failures are</div>
            <div>&nbsp; &nbsp;detected, the BFD session is in the Up state. &nbsp;If no
              BFD Control</div>
            <div>&nbsp; &nbsp;packets are received during a fixed period of time,
              called the</div>
          </div>
        </blockquote>
      </span>
      <div><br>
      </div>
      <div>TOM: Fixed, pre-configured or negotiated period of time
        (i.e.: BFD interval)</div>
      <div><br>
      </div>
      <span id="OLK_SRC_BODY_SECTION">
        <blockquote id="MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE"
          style="BORDER-LEFT: #b5c4df 5 solid; PADDING:0 0 0 5; MARGIN:0
          0 0 5;">
          <div text="#000000" bgcolor="#FFFFFF">
            <div>&nbsp; &nbsp;Detection Time, the session is declared to be Down.
              The detection</div>
            <div>&nbsp; &nbsp;time is a function of the negotiated transmission
              time, and a</div>
            <div>&nbsp; &nbsp;parameter called Detect Mult. Detect Mult determines
              the number of</div>
            <div>&nbsp; &nbsp;missing BFD Control packets that cause the session
              to be declared as</div>
            <div>&nbsp; &nbsp;Down. This parameter is included in the BFD Control
              packet.</div>
            <div><br>
            </div>
            <div>3.2.3. BFD Echo</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;A BFD echo packet is sent to a peer system, and is
              looped back to the</div>
            <div>&nbsp; &nbsp;originator. The echo function can be used
              proactively, or on-demand.</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;The BFD echo function has been defined in BFD for
              IPv4 and IPv6</div>
            <div>&nbsp; &nbsp;([BFD-IP]), but is not used in BFD for MPLS LSPs,
              PWs, or in BFD for</div>
            <div>&nbsp; &nbsp;MPLS-TP.</div>
            <div><br>
            </div>
            <div>3.3. MPLS OAM</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;The IETF MPLS working group has defined OAM for MPLS
              LSPs. The</div>
            <div>&nbsp; &nbsp;requirements and framework of this effort are
              defined in [MPLS-OAM-</div>
            <div>&nbsp; &nbsp;FW] and [MPLS-OAM], respectively. The corresponding
              OAM mechanism</div>
            <div>&nbsp; &nbsp;defined, in this context, is LSP Ping [LSP-Ping].</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;LSP Ping is based on ICMP Ping and just like its
              predecessor may be</div>
            <div>&nbsp; &nbsp;used in one of two modes:</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;o "Ping" mode: In this mode LSP ping is used for
              end-to-end</div>
            <div>&nbsp; &nbsp; &nbsp; connectivity verification between two LERs.</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;o "Traceroute" mode: This mode is used for
              hop-by-hop fault</div>
            <div>&nbsp; &nbsp; &nbsp; isolation.</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;LSP Ping extends the basic ICMP Ping operation (of
              data-plane</div>
            <div>&nbsp; &nbsp;connectivity verification) with functionality to
              verify data-plane</div>
            <div>&nbsp; &nbsp;vs. control-plane consistency for a Forwarding
              Equivalence Class</div>
            <div>&nbsp; &nbsp;(FEC) and also Maximum Transmission Unit (MTU)
              problems. The</div>
            <div>&nbsp; &nbsp;traceroute functionality may be used to isolate and
              localize the MPLS</div>
            <div>&nbsp; &nbsp;faults, using the Time-to-live (TTL) indicator to
              incrementally</div>
            <div>&nbsp; &nbsp;identify the sub-path of the LSP that is
              successfully traversed</div>
            <div>&nbsp; &nbsp;before the faulty link or node.</div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div>Mizrahi, et al. &nbsp; &nbsp; &nbsp; &nbsp; Expires July 9, 2013 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
              &nbsp; &nbsp; &nbsp; [Page 18]</div>
            <div>Internet-Draft &nbsp; &nbsp; &nbsp; Overview of OAM Mechanisms &nbsp; &nbsp; &nbsp; &nbsp;
              &nbsp; January 2013</div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;It should be noted that LSP Ping supports unique
              identification of</div>
            <div>&nbsp; &nbsp;the LSP within an addressing domain. The
              identification is checked</div>
            <div>&nbsp; &nbsp;using the full FEC identification. LSP Ping is
              easily extensible to</div>
            <div>&nbsp; &nbsp;include additional information needed to support new
              functionality,</div>
            <div>&nbsp; &nbsp;by use of Type-Length-Value (TLV) constructs. The
              usage of TLVs is</div>
            <div>&nbsp; &nbsp;typically not easy to perform in hardware, and is
              thus typically</div>
            <div>&nbsp; &nbsp;handled by the control plane.</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;LSP Ping supports both asynchronous, as well as,
              on-demand</div>
            <div>&nbsp; &nbsp;activation.</div>
            <div><br>
            </div>
            <div>3.4. MPLS-TP OAM</div>
            <div><br>
            </div>
            <div>3.4.1. Overview</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;The MPLS working group is currently working on
              defining the OAM</div>
            <div>&nbsp; &nbsp;toolset that fulfills the requirements for MPLS-TP
              OAM. The full set</div>
            <div>&nbsp; &nbsp;of requirements for MPLS-TP OAM are defined in
              [MPLS-TP-OAM], and</div>
            <div>&nbsp; &nbsp;include both general requirements for the behavior
              of the OAM</div>
            <div>&nbsp; &nbsp;mechanisms and a set of operations that should be
              supported by the</div>
            <div>&nbsp; &nbsp;OAM toolset. &nbsp;The set of mechanisms required are
              further elaborated</div>
            <div>&nbsp; &nbsp;in [TP-OAM-FW], which describes the general
              architecture of the OAM</div>
            <div>&nbsp; &nbsp;system as well as giving overviews of the
              functionality of the OAM</div>
            <div>&nbsp; &nbsp;toolset.</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;Some of the basic requirements for the OAM toolset
              for MPLS-TP are:</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;o MPLS-TP OAM must be able to support both an IP
              based and non-IP</div>
            <div>&nbsp; &nbsp; &nbsp; based environment. If the network is IP based,
              i.e. IP routing and</div>
            <div>&nbsp; &nbsp; &nbsp; forwarding are available, then the MPLS-TP OAM
              toolset should rely</div>
            <div>&nbsp; &nbsp; &nbsp; on the IP routing and forwarding capabilities. On
              the other hand,</div>
            <div>&nbsp; &nbsp; &nbsp; in environments where IP functionality is not
              available, the OAM</div>
            <div>&nbsp; &nbsp; &nbsp; tools must still be able to operate without
              dependence on IP</div>
            <div>&nbsp; &nbsp; &nbsp; forwarding and routing.</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;o OAM packets and the user traffic are required to
              be congruent</div>
            <div>&nbsp; &nbsp; &nbsp; (i.e. OAM packets are transmitted in-band) and
              there is a need to</div>
            <div>&nbsp; &nbsp; &nbsp; differentiate OAM packets from user-plane ones.
              Inherent in this</div>
            <div>&nbsp; &nbsp; &nbsp; requirement is the principle that MPLS-TP OAM be
              independent of</div>
            <div>&nbsp; &nbsp; &nbsp; any existing control-plane, although it should
              not preclude use of</div>
            <div>&nbsp; &nbsp; &nbsp; the control-plane functionality.</div>
            <div><br>
            </div>
            <div>3.4.2. Generic Associated Channel</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;In order to address the requirement for in-band
              transmission of MPLS-</div>
            <div>&nbsp; &nbsp;TP OAM traffic, MPLS-TP uses a Generic Associated
              Channel (G-ACh),</div>
            <div>&nbsp; &nbsp;defined in [G-ACh] for LSP-based OAM traffic. This
              mechanism is based</div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div>Mizrahi, et al. &nbsp; &nbsp; &nbsp; &nbsp; Expires July 9, 2013 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
              &nbsp; &nbsp; &nbsp; [Page 19]</div>
            <div>Internet-Draft &nbsp; &nbsp; &nbsp; Overview of OAM Mechanisms &nbsp; &nbsp; &nbsp; &nbsp;
              &nbsp; January 2013</div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;on the same concepts as the PWE3 ACH and VCCV
              mechanisms. &nbsp;However,</div>
            <div>&nbsp; &nbsp;to address the needs of LSPs as differentiated from
              PW, the following</div>
            <div>&nbsp; &nbsp;concepts were defined for [G-ACh]:</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;o An Associated Channel Header (ACH), that uses a
              format similar to</div>
            <div>&nbsp; &nbsp; &nbsp; the PW Control Word, is a 4-byte header that is
              prepended to OAM</div>
            <div>&nbsp; &nbsp; &nbsp; packets.</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;o A Generic Associated Label (GAL). The GAL is a
              reserved MPLS label</div>
            <div>&nbsp; &nbsp; &nbsp; value (13) that indicates that the packet is an
              ACH packet and the</div>
            <div>&nbsp; &nbsp; &nbsp; payload follows immediately after the label
              stack.</div>
            <div><br>
            </div>
            <div>3.4.3. MPLS-TP OAM Toolset</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;To address the functionality that is required of the
              OAM toolset, the</div>
            <div>&nbsp; &nbsp;MPLS WG conducted an analysis of the existing IETF
              and ITU-T OAM</div>
            <div>&nbsp; &nbsp;mechanisms and their ability to fulfill the required
              functionality.</div>
            <div>&nbsp; &nbsp;The conclusions of this analysis are documented in
              [OAM-Analys]. The</div>
            <div>&nbsp; &nbsp;MPLS working group currently plans to use a mixture
              of OAM mechanisms</div>
            <div>&nbsp; &nbsp;that are based on various existing standards, and
              adapt them to the</div>
            <div>&nbsp; &nbsp;requirements of [MPLS-TP-OAM]. Some of the main
              building blocks of</div>
            <div>&nbsp; &nbsp;this solution are based on:</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;o Bidirectional Forwarding Detection ([BFD],
              [BFD-LSP]) for</div>
            <div>&nbsp; &nbsp; &nbsp; proactive continuity check and connectivity
              verification.</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;o LSP Ping as defined in [LSP-Ping] for on-demand
              connectivity</div>
            <div>&nbsp; &nbsp; &nbsp; verification.</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;o New protocol packets, using G-ACH, to address
              different</div>
            <div>&nbsp; &nbsp; &nbsp; functionality.</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;o Performance measurement protocols that are based
              on the</div>
            <div>&nbsp; &nbsp; &nbsp; functionality that is described in [ITU-T-Y1731].</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;The following sub-sections describe the OAM tools
              defined for MPLS-TP</div>
            <div>&nbsp; &nbsp;as described in [TP-OAM-FW].</div>
            <div><br>
            </div>
            <div>3.4.3.1. Continuity Check and Connectivity Verification</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;Continuity Check and Connectivity Verification are
              presented in</div>
            <div>&nbsp; &nbsp;Section 2.2.5. of this document. &nbsp;As presented
              there, these tools may</div>
            <div>&nbsp; &nbsp;be used either proactively or on-demand. &nbsp;When using
              these tools</div>
            <div>&nbsp; &nbsp;proactively, they are generally used in tandem.</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;For MPLS-TP there are two distinct tools, the
              proactive tool is</div>
            <div>&nbsp; &nbsp;defined in [TP-CC-CV] while the on-demand tool is
              defined in</div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div>Mizrahi, et al. &nbsp; &nbsp; &nbsp; &nbsp; Expires July 9, 2013 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
              &nbsp; &nbsp; &nbsp; [Page 20]</div>
            <div>Internet-Draft &nbsp; &nbsp; &nbsp; Overview of OAM Mechanisms &nbsp; &nbsp; &nbsp; &nbsp;
              &nbsp; January 2013</div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;[OnDemand-CV].Proactively [MPLS-TP-OAM] states that
              the function</div>
            <div>&nbsp; &nbsp;should allow the MEPs to monitor the liveness and
              connectivity of a</div>
            <div>&nbsp; &nbsp;transport path. In on-demand mode, this function
              should support</div>
            <div>&nbsp; &nbsp;monitoring between the MEPs and, in addition,
              between a MEP and MIP.</div>
            <div>&nbsp; &nbsp;[TP-OAM-FW] highlights, &nbsp;when performing
              Connectivity Verification,</div>
            <div>&nbsp; &nbsp;the need for the CC-V messages to include unique
              identification of</div>
            <div>&nbsp; &nbsp;the MEG that is being monitored and the MEP that
              originated the</div>
            <div>&nbsp; &nbsp;message.</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;The proactive tool [TP-CC-CV] is based on extensions
              to BFD (see</div>
            <div>&nbsp; &nbsp;Section 3.2. ) with the additional limitation that
              the transmission</div>
            <div>&nbsp; &nbsp;and receiving rates are based on configuration by
              the operator. &nbsp;The</div>
            <div>&nbsp; &nbsp;on-demand tool [OnDemand-CV] is an adaptation of LSP
              Ping (see</div>
            <div>&nbsp; &nbsp;Section 3.3. ) for the required behavior of MPLS-TP.</div>
            <div><br>
            </div>
            <div>3.4.3.2. Route Tracing</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;[MPLS-TP-OAM] defines that there is a need for
              functionality that</div>
            <div>&nbsp; &nbsp;would allow a path end-point to identify the
              intermediate and end-</div>
            <div>&nbsp; &nbsp;points of the path. This function would be used in
              on-demand mode.</div>
            <div>&nbsp; &nbsp;Normally, this path will be used for bidirectional
              PW, LSP, and</div>
            <div>&nbsp; &nbsp;sections, however, unidirectional paths may be
              supported only if a</div>
            <div>&nbsp; &nbsp;return path exists. &nbsp;The tool for this is based on
              the LSP Ping (see</div>
            <div>&nbsp; &nbsp;Section 3.3. ) functionality and is described in
              [OnDemand-CV].</div>
            <div><br>
            </div>
            <div>3.4.3.3. Lock Instruct</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;The Lock Instruct function [Lock-Loop] is used to
              notify a transport</div>
            <div>&nbsp; &nbsp;path end-point of an administrative need to disable
              the transport</div>
            <div>&nbsp; &nbsp;path. &nbsp;This functionality will generally be used in
              conjunction with</div>
            <div>&nbsp; &nbsp;some intrusive OAM function, e.g. Performance
              measurement, Diagnostic</div>
            <div>&nbsp; &nbsp;testing, to minimize the side-effect on user data
              traffic.</div>
            <div><br>
            </div>
            <div>3.4.3.4. Lock Reporting</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;Lock Reporting is a function used by an end-point of
              a path to report</div>
            <div>&nbsp; &nbsp;to its far-end end-point that a lock condition has
              been affected on</div>
            <div>&nbsp; &nbsp;the path.</div>
            <div><br>
            </div>
            <div>3.4.3.5. Alarm Reporting</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;Alarm Reporting is a function used by an
              intermediate point of a</div>
            <div>&nbsp; &nbsp;path, that becomes aware of a fault on the path, to
              report to the</div>
            <div>&nbsp; &nbsp;end-points of the path. [TP-OAM-FW] states that this
              may occur as a</div>
            <div>&nbsp; &nbsp;result of a defect condition discovered at a server
              sub-layer. This</div>
            <div>&nbsp; &nbsp;generates an Alarm Indication Signal (AIS) that
              continues until the</div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div>Mizrahi, et al. &nbsp; &nbsp; &nbsp; &nbsp; Expires July 9, 2013 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
              &nbsp; &nbsp; &nbsp; [Page 21]</div>
            <div>Internet-Draft &nbsp; &nbsp; &nbsp; Overview of OAM Mechanisms &nbsp; &nbsp; &nbsp; &nbsp;
              &nbsp; January 2013</div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;fault is cleared. The consequent action of this
              function is detailed</div>
            <div>&nbsp; &nbsp;in [TP-OAM-FW].</div>
            <div><br>
            </div>
            <div>3.4.3.6. Remote Defect Indication</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;Remote Defect Indication (RDI) is used proactively
              by a path end-</div>
            <div>&nbsp; &nbsp;point to report to its peer end-point that a defect
              is detected on a</div>
            <div>&nbsp; &nbsp;bidirectional connection between them. [MPLS-TP-OAM]
              points out that</div>
            <div>&nbsp; &nbsp;this function may be applied to a unidirectional LSP
              only if there a</div>
            <div>&nbsp; &nbsp;return path exists. &nbsp;[TP-OAM-FW] points out that
              this function is</div>
            <div>&nbsp; &nbsp;associated with the proactive CC-V function.</div>
            <div><br>
            </div>
            <div>3.4.3.7. Client Failure Indication</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;Client Failure Indication (CFI) is defined in
              [MPLS-TP-OAM] to allow</div>
            <div>&nbsp; &nbsp;the propagation information from one edge of the
              network to the</div>
            <div>&nbsp; &nbsp;other. The information concerns a defect to a
              client, in the case</div>
            <div>&nbsp; &nbsp;that the client does not support alarm notification.</div>
            <div><br>
            </div>
            <div>3.4.3.8. Packet Loss Measurement (LM)</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;Packet Loss Measurement is a function used to verify
              the quality of</div>
            <div>&nbsp; &nbsp;the service. This function indicates the ratio of
              packets that are</div>
            <div>&nbsp; &nbsp;not delivered out of all packets that are
              transmitted by the path</div>
            <div>&nbsp; &nbsp;source.</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;There are two possible ways of determining this
              measurement:</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;o Using OAM packets, it is possible to compute the
              statistics based</div>
            <div>&nbsp; &nbsp; &nbsp; on a series of OAM packets. This, however, has
              the disadvantage of</div>
            <div>&nbsp; &nbsp; &nbsp; being artificial, and may not be representative
              since part of the</div>
            <div>&nbsp; &nbsp; &nbsp; packet loss may be dependent upon packet sizes.</div>
          </div>
        </blockquote>
      </span>
      <div><br>
      </div>
      <div>TOM: Not just packet sizes. Things like implementation (as I
        mentioned above with the comment about the accuracy or
        truthfulness of the data plane processing of OAM packets).
        &nbsp;Doing very accurate RTT as a simple example, with just IP
        Pings, is a tricky thing to make work. &nbsp;Also, it is important to
        mention that the scale in terms of number of packets, number of
        tests, etc&#8230; can and will impact these parameters too.</div>
      <div><br>
      </div>
      <span id="OLK_SRC_BODY_SECTION">
        <blockquote id="MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE"
          style="BORDER-LEFT: #b5c4df 5 solid; PADDING:0 0 0 5; MARGIN:0
          0 0 5;">
          <div text="#000000" bgcolor="#FFFFFF">
            <div><br>
            </div>
            <div>&nbsp; &nbsp;o Sending delimiting messages for the start and end
              of a measurement</div>
            <div>&nbsp; &nbsp; &nbsp; period during which the source and sink of the
              path count the</div>
            <div>&nbsp; &nbsp; &nbsp; packets transmitted and received. After the end
              delimiter, the</div>
            <div>&nbsp; &nbsp; &nbsp; ratio would be calculated by the path OAM entity.</div>
            <div><br>
            </div>
            <div>3.4.3.9. Packet Delay Measurement (DM)</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;Packet Delay Measurement is a function that is used
              to measure one-</div>
            <div>&nbsp; &nbsp;way or two-way delay of a packet transmission
              between a pair of the</div>
            <div>&nbsp; &nbsp;end-points of a path (PW, LSP, or Section). Where:</div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div>Mizrahi, et al. &nbsp; &nbsp; &nbsp; &nbsp; Expires July 9, 2013 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
              &nbsp; &nbsp; &nbsp; [Page 22]</div>
            <div>Internet-Draft &nbsp; &nbsp; &nbsp; Overview of OAM Mechanisms &nbsp; &nbsp; &nbsp; &nbsp;
              &nbsp; January 2013</div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;o One-way packet delay is the time elapsed from the
              start of</div>
            <div>&nbsp; &nbsp; &nbsp; transmission of the first bit of the packet by a
              source node until</div>
            <div>&nbsp; &nbsp; &nbsp; the reception of the last bit of that packet by
              the destination</div>
            <div>&nbsp; &nbsp; &nbsp; node.</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;o Two-way packet delay is the time elapsed from the
              start of</div>
            <div>&nbsp; &nbsp; &nbsp; transmission of the first bit of the packet by a
              source node until</div>
            <div>&nbsp; &nbsp; &nbsp; the reception of the last bit of the loop-backed
              packet by the</div>
            <div>&nbsp; &nbsp; &nbsp; same source node, when the loopback is performed
              at the packet's</div>
            <div>&nbsp; &nbsp; &nbsp; destination node.</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;Similarly to the packet loss measurement this could
              be performed in</div>
            <div>&nbsp; &nbsp;either of the two ways outlined above.</div>
            <div><br>
            </div>
            <div>3.5. PWE3 OAM</div>
            <div><br>
            </div>
            <div>3.5.1. PWE3 OAM using Virtual Circuit Connectivity
              Verification (VCCV)</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;VCCV, as defined in [VCCV], provides a means for
              end-to-end fault</div>
            <div>&nbsp; &nbsp;detection and diagnostics tools to be extended for
              PWs (regardless of</div>
            <div>&nbsp; &nbsp;the underlying tunneling technology). The VCCV
              switching function</div>
            <div>&nbsp; &nbsp;provides a control channel associated with each PW
              (based on the PW</div>
            <div>&nbsp; &nbsp;Associated Channel Header (ACH) which is defined in
              [PW-ACH]), and</div>
            <div>&nbsp; &nbsp;allows transmitting the OAM packets in-band with PW
              data (using CC</div>
            <div>&nbsp; &nbsp;Type 1: In-band VCCV).</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;VCCV currently supports the following OAM
              mechanisms: ICMP Ping, LSP</div>
            <div>&nbsp; &nbsp;Ping, and BFD. ICMP and LSP Ping are IP encapsulated
              before being</div>
            <div>&nbsp; &nbsp;sent over the PW ACH. BFD for VCCV [BFD-VCCV]
              supports two modes of</div>
            <div>&nbsp; &nbsp;encapsulation - either IP/UDP encapsulated (with
              IP/UDP header) or</div>
            <div>&nbsp; &nbsp;PW-ACH encapsulated (with no IP/UDP header) and
              provides support to</div>
            <div>&nbsp; &nbsp;signal the AC status. The use of the VCCV control
              channel provides</div>
            <div>&nbsp; &nbsp;the context, based on the MPLS-PW label, required to
              bind and</div>
            <div>&nbsp; &nbsp;bootstrap the BFD session to a particular pseudo
              wire (FEC),</div>
            <div>&nbsp; &nbsp;eliminating the need to exchange Discriminator
              values.</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;VCCV consists of two components: (1) signaled
              component to</div>
            <div>&nbsp; &nbsp;communicate VCCV capabilities as part of VC label,
              and (2) switching</div>
            <div>&nbsp; &nbsp;component to cause the PW payload to be treated as a
              control packet.</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;VCCV is not directly dependent upon the presence of
              a control plane.</div>
            <div>&nbsp; &nbsp;The VCCV capability negotiation may be performed as
              part of the PW</div>
            <div>&nbsp; &nbsp;signaling when LDP is used. In case of manual
              configuration of the</div>
            <div>&nbsp; &nbsp;PW, it is the responsibility of the operator to set
              consistent</div>
            <div>&nbsp; &nbsp;options at both ends.</div>
          </div>
        </blockquote>
      </span>
      <div><br>
      </div>
      <div>TOM: Might be helpful to note that the static mode was
        created specifically to handle the MPLS-TP cases where no
        control plane was a requirement. However, new use cases such as
        pure mobile backhaul, etc&#8230; find this functionality useful too.</div>
      <div><br>
      </div>
      <span id="OLK_SRC_BODY_SECTION">
        <blockquote id="MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE"
          style="BORDER-LEFT: #b5c4df 5 solid; PADDING:0 0 0 5; MARGIN:0
          0 0 5;">
          <div text="#000000" bgcolor="#FFFFFF">
            <div><br>
            </div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div>Mizrahi, et al. &nbsp; &nbsp; &nbsp; &nbsp; Expires July 9, 2013 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
              &nbsp; &nbsp; &nbsp; [Page 23]</div>
            <div>Internet-Draft &nbsp; &nbsp; &nbsp; Overview of OAM Mechanisms &nbsp; &nbsp; &nbsp; &nbsp;
              &nbsp; January 2013</div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div>3.5.2. PWE3 OAM using G-ACh</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;As mentioned above, VCCV enables OAM for PWs by
              using a control</div>
            <div>&nbsp; &nbsp;channel for OAM packets. When PWs are used in
              MPLS-TP networks,</div>
            <div>&nbsp; &nbsp;rather than the control channels defined in VCCV,
              the G-ACh can be</div>
            <div>&nbsp; &nbsp;used as an alternative control channel. The usage of
              the G-ACh for</div>
            <div>&nbsp; &nbsp;PWs is defined in [PW-G-ACh].</div>
            <div><br>
            </div>
            <div>3.6. OWAMP and TWAMP</div>
            <div><br>
            </div>
            <div>3.6.1. Overview</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;The IPPM working group in the IETF defines common
              criteria and</div>
            <div>&nbsp; &nbsp;metrics for measuring performance of IP traffic
              ([IPPM-FW]). Some of</div>
            <div>&nbsp; &nbsp;the key RFCs published by this working group have
              defined metrics for</div>
            <div>&nbsp; &nbsp;measuring connectivity [IPPM-Con], delay
              ([IPPM-1DM], [IPPM-2DM]),</div>
            <div>&nbsp; &nbsp;and packet loss [IPPM-1LM].</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;Alternative protocols for performance measurement
              are defined, for</div>
            <div>&nbsp; &nbsp;example, in MPLS-TP OAM ([MPLS-LM-DM], [TP-LM-DM]),
              and in Ethernet</div>
            <div>&nbsp; &nbsp;OAM [ITU-T-Y1731].</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;The IPPM working group has defined not only metrics
              for performance</div>
            <div>&nbsp; &nbsp;measurement, but also protocols that define how the
              measurement is</div>
            <div>&nbsp; &nbsp;carried out. The One-way Active Measurement Protocol
              [OWAMP] and the</div>
            <div>&nbsp; &nbsp;Two-Way Active Measurement Protocol [TWAMP] define a
              method and</div>
            <div>&nbsp; &nbsp;protocol for measuring delay and packet loss in IP
              networks.</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;OWAMP [OWAMP] enables measurement of one-way
              characteristics of IP</div>
            <div>&nbsp; &nbsp;networks, such as one-way packet loss and one-way
              delay. &nbsp;For its</div>
            <div>&nbsp; &nbsp;proper operation OWAMP requires accurate time of day
              setting at its</div>
            <div>&nbsp; &nbsp;end points.</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;TWAMP [TWAMP] is a similar protocol that enables
              measurement of two-</div>
            <div>&nbsp; &nbsp;way (round trip) characteristics. &nbsp;TWAMP does not
              require accurate</div>
            <div>&nbsp; &nbsp;time of day, and, furthermore, allows the use of a
              simple session</div>
            <div>&nbsp; &nbsp;reflector, making it an attractive alternative to
              OWAMP.</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;OWAMP and TWAMP use two separate protocols: a
              Control plane protocol,</div>
            <div>&nbsp; &nbsp;and a Test plane protocol.</div>
            <div><br>
            </div>
            <div>3.6.2. Control and Test Protocols</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;OWAMP and TWAMP control protocols run over TCP,
              while the test</div>
            <div>&nbsp; &nbsp;protocols run over UDP. &nbsp;The purpose of the control
              protocols is to</div>
            <div>&nbsp; &nbsp;initiate, start, and stop test sessions, and for
              OWAMP to fetch</div>
            <div>&nbsp; &nbsp;results. &nbsp;The test protocols introduce test packets
              (which contain</div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div>Mizrahi, et al. &nbsp; &nbsp; &nbsp; &nbsp; Expires July 9, 2013 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
              &nbsp; &nbsp; &nbsp; [Page 24]</div>
            <div>Internet-Draft &nbsp; &nbsp; &nbsp; Overview of OAM Mechanisms &nbsp; &nbsp; &nbsp; &nbsp;
              &nbsp; January 2013</div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;sequence numbers and timestamps) along the IP path
              under test</div>
            <div>&nbsp; &nbsp;according to a schedule, and record statistics of
              packet arrival.</div>
            <div>&nbsp; &nbsp;Multiple sessions may be simultaneously defined,
              each with a session</div>
            <div>&nbsp; &nbsp;identifier, and defining the number of packets to be
              sent, the amount</div>
            <div>&nbsp; &nbsp;of padding to be added (and thus the packet size),
              the start time,</div>
            <div>&nbsp; &nbsp;and the send schedule (which can be either a
              constant time between</div>
            <div>&nbsp; &nbsp;test packets or exponentially distributed
              pseudo-random). Statistics</div>
            <div>&nbsp; &nbsp;recorded conform to the relevant IPPM RFCs.</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;OWAMP and TWAMP test traffic is designed with
              security in mind. &nbsp;Test</div>
            <div>&nbsp; &nbsp;packets are hard to detect because they are simply
              UDP streams</div>
            <div>&nbsp; &nbsp;between negotiated port numbers, with potentially
              nothing static in</div>
            <div>&nbsp; &nbsp;the packets. &nbsp;OWAMP and TWAMP also include optional
              authentication</div>
            <div>&nbsp; &nbsp;and encryption for both control and test packets.</div>
            <div><br>
            </div>
            <div>3.6.3. OWAMP</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;OWAMP defines the following logical roles:
              Session-Sender, Session-</div>
            <div>&nbsp; &nbsp;Receiver, Server, Control-Client, and Fetch-Client.
              &nbsp;The Session-</div>
            <div>&nbsp; &nbsp;Sender originates test traffic that is received by
              the Session-</div>
            <div>&nbsp; &nbsp;Receiver. &nbsp;The Server configures and manages the
              session, as well as</div>
            <div>&nbsp; &nbsp;returning the results. &nbsp;The Control-Client initiates
              requests for</div>
            <div>&nbsp; &nbsp;test sessions, triggers their start, and may trigger
              their</div>
            <div>&nbsp; &nbsp;termination. &nbsp;The Fetch-Client requests the results
              of a completed</div>
            <div>&nbsp; &nbsp;session. &nbsp;Multiple roles may be combined in a single
              host - for</div>
            <div>&nbsp; &nbsp;example, one host may play the roles of
              Control-Client, Fetch-Client,</div>
            <div>&nbsp; &nbsp;and Session-Sender, and a second playing the roles
              of Server and</div>
            <div>&nbsp; &nbsp;Session-Receiver.</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;In a typical OWAMP session the Control-Client
              establishes a TCP</div>
            <div>&nbsp; &nbsp;connection to port 861 of the Server, which responds
              with a server</div>
            <div>&nbsp; &nbsp;greeting message indicating supported
              security/integrity modes. The</div>
            <div>&nbsp; &nbsp;Control-Client responds with the chosen
              communications mode and the</div>
            <div>&nbsp; &nbsp;Server accepts the modes. &nbsp;The Control-Client then
              requests and fully</div>
            <div>&nbsp; &nbsp;describes a test session to which the Server
              responds with its</div>
            <div>&nbsp; &nbsp;acceptance and supporting information. &nbsp;More than
              one test session</div>
            <div>&nbsp; &nbsp;may be requested with additional messages. &nbsp;The
              Control-Client then</div>
            <div>&nbsp; &nbsp;starts a test session and the Server acknowledges.
              &nbsp;The Session-</div>
            <div>&nbsp; &nbsp;Sender then sends test packets with pseudorandom
              padding to the</div>
            <div>&nbsp; &nbsp;Session-Receiver until the session is complete or
              until the Control-</div>
            <div>&nbsp; &nbsp;client stops the session. &nbsp;Once finished, the
              Fetch-Client sends a</div>
            <div>&nbsp; &nbsp;fetch request to the server, which responds with an
              acknowledgement</div>
            <div>&nbsp; &nbsp;and immediately thereafter the result data.</div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div>Mizrahi, et al. &nbsp; &nbsp; &nbsp; &nbsp; Expires July 9, 2013 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
              &nbsp; &nbsp; &nbsp; [Page 25]</div>
            <div>Internet-Draft &nbsp; &nbsp; &nbsp; Overview of OAM Mechanisms &nbsp; &nbsp; &nbsp; &nbsp;
              &nbsp; January 2013</div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div>3.6.4. TWAMP</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;TWAMP defines the following logical roles:
              session-sender, session-</div>
            <div>&nbsp; &nbsp;reflector, server, and control-client. &nbsp;These are
              similar to the</div>
            <div>&nbsp; &nbsp;OWAMP roles, except that the Session-Reflector does
              not collect any</div>
            <div>&nbsp; &nbsp;packet information, and there is no need for a
              Fetch-Client.</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;In a typical TWAMP session the Control-Client
              establishes a TCP</div>
            <div>&nbsp; &nbsp;connection to port 862 of the Server, and mode is
              negotiated as in</div>
            <div>&nbsp; &nbsp;OWAMP. &nbsp;The Control-Client then requests sessions
              and starts them.</div>
            <div>&nbsp; &nbsp;The Session-Sender sends test packets with
              pseudorandom padding to</div>
            <div>&nbsp; &nbsp;the Session-Reflector which returns them with
              insertion of</div>
            <div>&nbsp; &nbsp;timestamps.</div>
            <div><br>
            </div>
            <div>3.7. Summary of OAM Functions</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;Table 3 summarizes the OAM functions that are
              supported in each of</div>
            <div>&nbsp; &nbsp;the categories that were analyzed in this section.</div>
            <div><br>
            </div>
            <div>&nbsp;
              &nbsp;+-----------+-------+--------+--------+-----------+-------+--------+</div>
            <div>&nbsp; &nbsp;| Standard &nbsp;|Continu|Connecti|Path &nbsp; &nbsp;|Defect &nbsp; &nbsp;
              |Perform|Other &nbsp; |</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |ity &nbsp; &nbsp;|vity &nbsp;
              &nbsp;|Discover|Indications|ance &nbsp; |Function|</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |Check &nbsp;|Verifica|y &nbsp; &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
              |Monitor|s &nbsp; &nbsp; &nbsp; |</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; |tion &nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
              |ing &nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp;|</div>
            <div>&nbsp;
              &nbsp;+-----------+-------+--------+--------+-----------+-------+--------+</div>
            <div>&nbsp; &nbsp;|IP Ping &nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; |Echo &nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |
              &nbsp; &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; &nbsp;|</div>
            <div>&nbsp; &nbsp;+ --------- + ----- + ------ + ------ + --------- +
              ----- + ------ +</div>
            <div>&nbsp; &nbsp;|IP &nbsp; &nbsp; &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; &nbsp;|Tracerou| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |
              &nbsp; &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; &nbsp;|</div>
            <div>&nbsp; &nbsp;|Traceroute | &nbsp; &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; &nbsp;|te &nbsp; &nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |
              &nbsp; &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; &nbsp;|</div>
            <div>&nbsp; &nbsp;+ --------- + ----- + ------ + ------ + --------- +
              ----- + ------ +</div>
            <div>&nbsp; &nbsp;|BFD &nbsp; &nbsp; &nbsp; &nbsp;|BFD &nbsp; &nbsp;|BFD &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |
              &nbsp; &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; &nbsp;|</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |Control|Echo &nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |
              &nbsp; &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; &nbsp;|</div>
            <div>&nbsp; &nbsp;+ --------- + ----- + ------ + ------ + --------- +
              ----- + ------ +</div>
            <div>&nbsp; &nbsp;|MPLS OAM &nbsp; | &nbsp; &nbsp; &nbsp; |"Ping" &nbsp;|"Tracero| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |
              &nbsp; &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; &nbsp;|</div>
            <div>&nbsp; &nbsp;|(LSP Ping) | &nbsp; &nbsp; &nbsp; |mode &nbsp; &nbsp;|ute" &nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |
              &nbsp; &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; &nbsp;|</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; &nbsp;|mode &nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |
              &nbsp; &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; &nbsp;|</div>
            <div>&nbsp; &nbsp;+ --------- + ----- + ------ + ------ + --------- +
              ----- + ------ +</div>
            <div>&nbsp; &nbsp;|MPLS-TP &nbsp; &nbsp;|CC &nbsp; &nbsp; |CV/pro- |Route &nbsp; |-Alarm &nbsp; &nbsp;
              |-LM &nbsp; &nbsp;|-Diagnos|</div>
            <div>&nbsp; &nbsp;|OAM &nbsp; &nbsp; &nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; |active &nbsp;|Tracing | Reporting
              |-DM &nbsp; &nbsp;| tic Tes|</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; |or on- &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp;|-Client &nbsp; &nbsp;|
              &nbsp; &nbsp; &nbsp; | t &nbsp; &nbsp; &nbsp;|</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; |demand &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp;| Failure &nbsp; |
              &nbsp; &nbsp; &nbsp; |-Lock &nbsp; |</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp;| Indication|
              &nbsp; &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; &nbsp;|</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp;|-Remote &nbsp; &nbsp;|
              &nbsp; &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; &nbsp;|</div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div>Mizrahi, et al. &nbsp; &nbsp; &nbsp; &nbsp; Expires July 9, 2013 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
              &nbsp; &nbsp; &nbsp; [Page 26]</div>
            <div>Internet-Draft &nbsp; &nbsp; &nbsp; Overview of OAM Mechanisms &nbsp; &nbsp; &nbsp; &nbsp;
              &nbsp; January 2013</div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp;| Defect &nbsp; &nbsp;|
              &nbsp; &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; &nbsp;|</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp;| Indication|
              &nbsp; &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; &nbsp;|</div>
            <div>&nbsp; &nbsp;+ --------- + ----- + ------ + ------ + --------- +
              ----- + ------ +</div>
            <div>&nbsp; &nbsp;|PWE3 OAM &nbsp; |BFD &nbsp; &nbsp;|-BFD &nbsp; &nbsp;|LSP-Ping| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |
              &nbsp; &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; &nbsp;|</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; |-ICMP &nbsp; | &nbsp; &nbsp; &nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |
              &nbsp; &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; &nbsp;|</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; | Ping &nbsp; | &nbsp; &nbsp; &nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |
              &nbsp; &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; &nbsp;|</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; |-LSP- &nbsp; | &nbsp; &nbsp; &nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |
              &nbsp; &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; &nbsp;|</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; | Ping &nbsp; | &nbsp; &nbsp; &nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |
              &nbsp; &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; &nbsp;|</div>
            <div>&nbsp; &nbsp;+ --------- + ----- + ------ + ------ + --------- +
              ----- + ------ +</div>
            <div>&nbsp; &nbsp;|OWAMP and &nbsp;| &nbsp; &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
              |-Delay | &nbsp; &nbsp; &nbsp; &nbsp;|</div>
            <div>&nbsp; &nbsp;|TWAMP &nbsp; &nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |
              measur| &nbsp; &nbsp; &nbsp; &nbsp;|</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |
              ement | &nbsp; &nbsp; &nbsp; &nbsp;|</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
              |-Packet| &nbsp; &nbsp; &nbsp; &nbsp;|</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |
              loss &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp;|</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |
              measur| &nbsp; &nbsp; &nbsp; &nbsp;|</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |
              ement | &nbsp; &nbsp; &nbsp; &nbsp;|</div>
            <div>&nbsp;
              &nbsp;+-----------+-------+--------+--------+-----------+-------+--------+</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Table 3 Summary of OAM Functions</div>
            <div><br>
            </div>
            <div>4. Security Considerations</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;This memo presents an overview of existing OAM
              mechanisms, and</div>
            <div>&nbsp; &nbsp;proposes no new OAM mechanisms. Therefore, this
              document introduces</div>
            <div>&nbsp; &nbsp;no security considerations. However, the OAM
              mechanism reviewed in</div>
            <div>&nbsp; &nbsp;this document can and do present security issues.
              The reader is</div>
            <div>&nbsp; &nbsp;encouraged to review the Security Considerations
              section of each</div>
            <div>&nbsp; &nbsp;document reference by this memo.</div>
            <div><br>
            </div>
            <div>5. IANA Considerations</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;There are no new IANA considerations implied by this
              document.</div>
            <div><br>
            </div>
            <div>6. Acknowledgments</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;The authors gratefully acknowledge Sasha Vainshtein,
              Carlos</div>
            <div>&nbsp; &nbsp;Pignataro, David Harrington, Dan Romascanu, Ron
              Bonica and other</div>
            <div>&nbsp; &nbsp;members of the OPSAWG mailing list for their helpful
              comments.</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;This document was prepared using
              2-Word-v2.0.template.dot.</div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div>Mizrahi, et al. &nbsp; &nbsp; &nbsp; &nbsp; Expires July 9, 2013 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
              &nbsp; &nbsp; &nbsp; [Page 27]</div>
            <div>Internet-Draft &nbsp; &nbsp; &nbsp; Overview of OAM Mechanisms &nbsp; &nbsp; &nbsp; &nbsp;
              &nbsp; January 2013</div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div>7. References</div>
            <div><br>
            </div>
            <div>7.1. Normative References</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;[LSP-Ping] &nbsp; &nbsp;Kompella, K., Swallow, G., "Detecting
              Multi-Protocol</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Label Switched (MPLS) Data Plane
              Failures", RFC 4379,</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;February 2006.</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;[MPLS-OAM] &nbsp; &nbsp;Nadeau, T., Morrow, M., Swallow, G.,
              Allan, D.,</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Matsushima, S., "Operations and
              Management (OAM)</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Requirements for Multi-Protocol Label
              Switched (MPLS)</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Networks", RFC 4377, February 2006.</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;[MPLS-OAM-FW] Allan, D., Nadeau, T., "A Framework
              for Multi-Protocol</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Label Switching (MPLS) Operations and
              Management</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;(OAM)", RFC 4378, February 2006.</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;[OAM-Label] &nbsp; Ohta, H., "Assignment of the 'OAM
              Alert Label' for</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Multiprotocol Label Switching
              Architecture (MPLS)</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Operation and Maintenance (OAM)
              Functions", RFC 3429,</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;November 2002.</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;[MPLS-TP-OAM] Vigoureux, M., Ward, D., Betts, M.,
              "Requirements for</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;OAM in MPLS Transport Networks", RFC
              5860, May 2010.</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;[G-ACh] &nbsp; &nbsp; &nbsp; Bocci, M., Vigoureux, M., Bryant, S.,
              "MPLS Generic</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Associated Channel", RFC 5586, June
              2009.</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;[VCCV] &nbsp; &nbsp; &nbsp; &nbsp;Nadeau, T., Pignataro, C., "Pseudowire
              Virtual Circuit</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Connectivity Verification (VCCV): A
              Control Channel</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;for Pseudowires", RFC 5085, December
              2007.</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;[PW-ACH] &nbsp; &nbsp; &nbsp;Bryant, S., Swallow, G., Martini, L.,
              McPherson, D.,</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"Pseudowire Emulation Edge-to-Edge
              (PWE3) Control Word</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;for Use over an MPLS PSN", RFC 4385,
              February 2006.</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;[ICMPv4] &nbsp; &nbsp; &nbsp;Postel, J., "Internet Control Message
              Protocol", STD 5,</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;RFC 792, September 1981.</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;[ICMPv6] &nbsp; &nbsp; &nbsp;Conta, A., Deering, S., and M. Gupta,
              "Internet Control</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Message Protocol (ICMPv6) for the
              Internet Protocol</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Version 6 (IPv6) Specification", RFC
              4443, March 2006.</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;[MPLS-P2MP] &nbsp; Yasukawa, S., Farrel, A., King, D.,
              Nadeau, T.,</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"Operations and Management (OAM)
              Requirements for</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Point-to-Multipoint MPLS Networks",
              RFC 4687,</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;September 2006.</div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div>Mizrahi, et al. &nbsp; &nbsp; &nbsp; &nbsp; Expires July 9, 2013 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
              &nbsp; &nbsp; &nbsp; [Page 28]</div>
            <div>Internet-Draft &nbsp; &nbsp; &nbsp; Overview of OAM Mechanisms &nbsp; &nbsp; &nbsp; &nbsp;
              &nbsp; January 2013</div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;[ICMP-Ext] &nbsp; &nbsp;Bonica, R., Gan, D., Tappan, D.,
              Pignataro, C., "ICMP</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Extensions for Multiprotocol Label
              Switching", RFC</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;4950, August 2007.</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;[ICMP-MP] &nbsp; &nbsp; Bonica, R., Gan, D., Tappan, D.,
              Pignataro, C.,</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"Extended ICMP to Support Multi-Part
              Messages", RFC</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;4884, April 2007.</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;[ICMP-Int] &nbsp; &nbsp;Atlas, A., Bonica, R., Pignataro, C.,
              Shen, N., Rivers,</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;JR., "Extending ICMP for Interface and
              Next-Hop</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Identification", RFC 5837, April 2010.</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;[TCPIP-Tools] Kessler, G., Shepard, S., "A Primer On
              Internet and</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;TCP/IP Tools and Utilities", RFC 2151,
              June 1997.</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;[NetTools] &nbsp; &nbsp;Stine, R., "FYI on a Network
              Management Tool Catalog:</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Tools for Monitoring and Debugging
              TCP/IP Internets</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;and Interconnected Devices", RFC 1147,
              April 1990.</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;[IPPM-FW] &nbsp; &nbsp; Paxson, V., Almes, G., Mahdavi, J.,
              and Mathis, M.,</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"Framework for IP Performance
              Metrics", RFC 2330, May</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;1998.</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;[IPPM-Con] &nbsp; &nbsp;Mahdavi, J., Paxson, V., "IPPM Metrics
              for Measuring</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Connectivity", RFC 2678, September
              1999.</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;[IPPM-1DM] &nbsp; &nbsp;Almes, G., Kalidindi, S., Zekauskas,
              M., "A One-way</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Delay Metric for IPPM", RFC 2679,
              September 1999.</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;[IPPM-1LM] &nbsp; &nbsp;Almes, G., Kalidindi, S., Zekauskas,
              M., "A One-way</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Packet Loss Metric for IPPM", RFC
              2680, September</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;1999.</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;[IPPM-2DM] &nbsp; &nbsp;Almes, G., Kalidindi, S., Zekauskas,
              M., "A Round-trip</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Delay Metric for IPPM", RFC 2681,
              September 1999.</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;[OWAMP] &nbsp; &nbsp; &nbsp; Shalunov, S., Teitelbaum, B., Karp,
              A., Boote, J., and</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Zekauskas, M., "A One-way Active
              Measurement Protocol</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;(OWAMP)", RFC 4656, September 2006.</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;[TWAMP] &nbsp; &nbsp; &nbsp; Hedayat, K., Krzanowski, R., Morton,
              A., Yum, K., and</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Babiarz, J., "A Two-Way Active
              Measurement Protocol</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;(TWAMP)", RFC 5357, October 2008.</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;[BFD] &nbsp; &nbsp; &nbsp; &nbsp; Katz, D., Ward, D., "Bidirectional
              Forwarding Detection</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;(BFD)", RFC 5880, June 2010.</div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div>Mizrahi, et al. &nbsp; &nbsp; &nbsp; &nbsp; Expires July 9, 2013 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
              &nbsp; &nbsp; &nbsp; [Page 29]</div>
            <div>Internet-Draft &nbsp; &nbsp; &nbsp; Overview of OAM Mechanisms &nbsp; &nbsp; &nbsp; &nbsp;
              &nbsp; January 2013</div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;[BFD-IP] &nbsp; &nbsp; &nbsp;Katz, D., Ward, D., "Bidirectional
              Forwarding Detection</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;(BFD) for IPv4 and IPv6 (Single Hop)",
              RFC 5881, June</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;2010.</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;[BFD-Gen] &nbsp; &nbsp; Katz, D., Ward, D., "Generic
              Application of</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Bidirectional Forwarding Detection
              (BFD)", RFC 5882,</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;June 2010.</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;[BFD-Multi] &nbsp; Katz, D., Ward, D., "Bidirectional
              Forwarding Detection</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;(BFD) for Multihop Paths", RFC 5883,
              June 2010.</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;[BFD-LSP] &nbsp; &nbsp; Aggarwal, R., Kompella, K., Nadeau,
              T., and Swallow,</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;G., "Bidirectional Forwarding
              Detection (BFD) for MPLS</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Label Switched Paths (LSPs)", RFC
              5884, June 2010.</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;[BFD-VCCV] &nbsp; &nbsp;Nadeau, T., Pignataro, C.,
              "Bidirectional Forwarding</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Detection (BFD) for the Pseudowire
              Virtual Circuit</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Connectivity Verification (VCCV)", RFC
              5885, June</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;2010.</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;[TP-OAM-FW] &nbsp; Busi, I., Allan, D., "Operations,
              Administration and</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Maintenance Framework for MPLS-based
              Transport</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Networks ", RFC 6371, September 2011.</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;[TP-CC-CV] &nbsp; &nbsp;Allan, D., Swallow, G., Drake, J.,
              "Proactive</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Connectivity Verification, Continuity
              Check and Remote</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Defect indication for MPLS Transport
              Profile", RFC</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;6428, November 2011.</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;[OnDemand-CV] Gray, E., Bahadur, N., Boutros, S.,
              Aggarwal, R. "MPLS</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;On-Demand Connectivity Verification
              and Route</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Tracing", RFC 6426, November 2011.</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;[MPLS-LM-DM] &nbsp;Frost, D., Bryant, S., "Packet Loss
              and Delay</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Measurement for MPLS Networks", RFC
              6374, September</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;2011.</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;[TP-LM-DM] &nbsp; &nbsp;Frost, D., Bryant, S., "A Packet Loss
              and Delay</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Measurement Profile for MPLS-Based
              Transport</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Networks", RFC 6375, September 2011.</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;[TP-Fault] &nbsp; &nbsp;Swallow, G., Fulignoli, A., Vigoureux,
              M., Boutros, S.,</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"MPLS Fault Management Operations,
              Administration, and</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Maintenance (OAM)", RFC 6427, November
              2011.</div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div>Mizrahi, et al. &nbsp; &nbsp; &nbsp; &nbsp; Expires July 9, 2013 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
              &nbsp; &nbsp; &nbsp; [Page 30]</div>
            <div>Internet-Draft &nbsp; &nbsp; &nbsp; Overview of OAM Mechanisms &nbsp; &nbsp; &nbsp; &nbsp;
              &nbsp; January 2013</div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;[Lock-Loop] &nbsp; Boutros, S., Sivabalan, S., Aggarwal,
              R., Vigoureux,</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;M., Dai, X., "MPLS Transport Profile
              Lock Instruct and</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Loopback Functions", RFC 6435,
              November 2011.</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;[ITU-T-CT] &nbsp; &nbsp;Betts, M., "Allocation of a Generic
              Associated Channel</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Type for ITU-T MPLS Transport Profile
              Operation,</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Maintenance, and Administration
              (MPLS-TP OAM)", RFC</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;6671, November 2012.</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;[PW-Map] &nbsp; &nbsp; &nbsp;M. Aissaoui, P. Busschbach, L.
              Martini, M. Morrow, T.</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Nadeau, "Pseudowire (PW) Operations,
              Administration,</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;and Maintenance (OAM) Message
              Mapping", RFC 6310, July</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;2011.</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;[PW-G-ACh] &nbsp; &nbsp;Li, H., Martini, L., He, J., Huang,
              F., "Using the</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Generic Associated Channel Label for
              Pseudowire in the</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;MPLS Transport Profile (MPLS-TP)", RFC
              6423, November</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;2011.</div>
            <div><br>
            </div>
            <div>7.2. Informative References</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;[OAM-Def] &nbsp; &nbsp; Andersson, L., Van Helvoort, H.,
              Bonica, R., Romascanu,</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;D., Mansfield, S., "Guidelines for the
              use of the OAM</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;acronym in the IETF ", RFC 6291, June
              2011.</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;[OAM-Analys] &nbsp;Sprecher, N., Fang, L., "An Overview
              of the OAM Tool</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Set for &nbsp;MPLS based Transport
              Networks", RFC 6669,</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;July 2012.</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;[TP-Term] &nbsp; &nbsp; Van Helvoort, H., Andersson, L.,
              Sprecher, N., "A</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Thesaurus for the Terminology used in
              Multiprotocol</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Label Switching Transport Profile
              (MPLS-TP)</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;drafts/RFCs and ITU-T's Transport
              Network</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Recommendations", work-in-progress,
              draft-ietf-mpls-</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;tp-rosetta-stone, July 2012.</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;[IEEE802.1ag] IEEE 802.1Q, "IEEE Standard for Local
              and metropolitan</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;area networks - Media Access Control
              (MAC) Bridges and</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Virtual Bridged Local Area Networks",
              October 2012.</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;[ITU-T-Y1731] ITU-T Recommendation G.8013/Y.1731,
              "OAM Functions and</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Mechanisms for Ethernet-based
              Networks", July 2011.</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;[ITU-T-Y1711] ITU-T Recommendation Y.1711,
              "Operation &amp; Maintenance</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;mechanism for MPLS networks", February
              2004.</div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div>Mizrahi, et al. &nbsp; &nbsp; &nbsp; &nbsp; Expires July 9, 2013 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
              &nbsp; &nbsp; &nbsp; [Page 31]</div>
            <div>Internet-Draft &nbsp; &nbsp; &nbsp; Overview of OAM Mechanisms &nbsp; &nbsp; &nbsp; &nbsp;
              &nbsp; January 2013</div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;[IEEE802.3ah] IEEE 802.3, "IEEE Standard for
              Information technology -</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Local and metropolitan area networks -
              Carrier sense</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;multiple access with collision
              detection (CSMA/CD)</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;access method and physical layer
              specifications",</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;clause 57, December 2008.</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;[ITU-T-G.806] ITU-T Recommendation G.806,
              "Characteristics of</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;transport equipment - Description
              methodology and</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;generic functionality", January 2009.</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;[ITU-G8113.2] ITU-T Recommendation
              G.8113.2/Y.1372.2, "Operations,</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;administration and maintenance
              mechanisms for MPLS-TP</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;networks using the tools defined for
              MPLS", November</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;2012.</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;[ITU-G8113.1] ITU-T Recommendation
              G.8113.1/Y.1372.1, "Operations,</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Administration and Maintenance
              mechanism for MPLS-TP</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;in Packet Transport Network (PTN)",
              November 2012.</div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div>Authors' Addresses</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;Tal Mizrahi</div>
            <div>&nbsp; &nbsp;Marvell</div>
            <div>&nbsp; &nbsp;6 Hamada St.</div>
            <div>&nbsp; &nbsp;Yokneam, 20692</div>
            <div>&nbsp; &nbsp;Israel</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;Email: <a class="moz-txt-link-abbreviated" href="mailto:talmi@marvell.com">talmi@marvell.com</a></div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;Nurit Sprecher</div>
            <div>&nbsp; &nbsp;Nokia Siemens Networks</div>
            <div>&nbsp; &nbsp;3 Hanagar St. Neve Ne'eman B</div>
            <div>&nbsp; &nbsp;Hod Hasharon, &nbsp; 45241</div>
            <div>&nbsp; &nbsp;Israel</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;Email: <a class="moz-txt-link-abbreviated" href="mailto:nurit.sprecher@nsn.com">nurit.sprecher@nsn.com</a></div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;Elisa Bellagamba</div>
            <div>&nbsp; &nbsp;Ericsson</div>
            <div>&nbsp; &nbsp;6 Farogatan St.</div>
            <div>&nbsp; &nbsp;Stockholm, &nbsp; 164 40</div>
            <div>&nbsp; &nbsp;Sweden</div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div>Mizrahi, et al. &nbsp; &nbsp; &nbsp; &nbsp; Expires July 9, 2013 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
              &nbsp; &nbsp; &nbsp; [Page 32]</div>
            <div>Internet-Draft &nbsp; &nbsp; &nbsp; Overview of OAM Mechanisms &nbsp; &nbsp; &nbsp; &nbsp;
              &nbsp; January 2013</div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;Phone: +46 761440785</div>
            <div>&nbsp; &nbsp;Email: <a class="moz-txt-link-abbreviated" href="mailto:elisa.bellagamba@ericsson.com">elisa.bellagamba@ericsson.com</a></div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;Yaacov Weingarten</div>
            <div>&nbsp; &nbsp;34 Hagefen St.</div>
            <div>&nbsp; &nbsp;Karnei Shomron, &nbsp; 4485500</div>
            <div>&nbsp; &nbsp;Israel</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;Email: <a class="moz-txt-link-abbreviated" href="mailto:wyaacov@gmail.com">wyaacov@gmail.com</a></div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div><br>
            </div>
          </div>
        </blockquote>
      </span><br>
    </div>
    <blockquote cite="mid:50F437BF.8040005@cisco.com" type="cite">
      <meta content="text/html; charset=ISO-8859-1"
        http-equiv="Content-Type">
      <div class="moz-cite-prefix">draft-ietf-opsawg-oam-overview
        authors,<br>
        <br>
        Here is my feedback on this document.<br>
        <br>
        1.<br>
        Is this document in line with <a moz-do-not-send="true"
          class="moz-txt-link-freetext"
          href="http://tools.ietf.org/html/draft-ietf-trill-oam-req-04">http://tools.ietf.org/html/draft-ietf-trill-oam-req-04</a>?
        <br>
        * For example, the following definitions could be reused.<br>
        <pre class="newpage">   Fault: The term Fault refers to an inability to perform a required
   action, e.g., an unsuccessful attempt to deliver a packet.

   Defect: The term Defect refers to an interruption in the normal
   operation, such that over a period of time no packets are delivered
   successfully.

   Failure: The term Failure refers to the termination of the required
   function over a longer period of time. Persistence of a defect for a
   period of time is interpreted as a failure.

* For example, on the basic abstract 
Abstract

   Operations, Administration, and Maintenance (OAM) is a general term
   that refers to a toolset that can be used for fault detection and
   isolation, and for performance measurement. OAM mechanisms have been
   defined for various layers in the protocol stack, and are used with a
   variety of protocols.

Abstract (draft-ietf-trill-oam-req-04)

   OAM (Operations, Administration and Maintenance) is a general term
   used to identify functions and toolsets to troubleshoot and monitor
   networks. This document presents, OAM Requirements applicable to
   TRILL. 

So, as an example: does OAM include function? 
I advice to review draft-ietf-trill-oam-req-04

2. 
draft-ietf-trill-oam is not mentioned, while the abstract mentions:
   This document presents an overview of the OAM mechanisms that have
   been defined and are currently being defined by the IETF.
Search for OAM in the current draft names (<a moz-do-not-send="true" class="moz-txt-link-freetext" href="https://datatracker.ietf.org/">https://datatracker.ietf.org/</a>), and you will find many references.
Ok, I see later on:	
   This document focuses on IETF
   documents that have been published as RFCs, while other ongoing OAM-
   related work is outside the scope.
Ok, fine then: we don't need a reference to all the drafts. 
However, draft-ietf-trill-oam is closed to be a RFC, and should be mentioned.


3.
Section 1
   The term OAM in this document refers to Operations, Administration
   and Maintenance [<a moz-do-not-send="true" href="http://tools.ietf.org/html/draft-ietf-opsawg-oam-overview-08#ref-OAM-Def" title="&quot;Guidelines for the use of the OAM acronym in the IETF &quot;">OAM-Def</a>], focusing on the forwarding plane of OAM.
What does it mean "focusing on the forwarding plane of OAM"?
Do you take a subset of the definition for this document?
Btw, I don't see a definition in the terminology section.
In section 2.2.3
   A Maintenance Point (MP) is a functional entity that is defined at a
   node in the network, and either initiates or reacts to OAM messages.
Which plane is MP?

4.
Section 1, Introduction
"Hence, management aspects are outside the scope of this document."
I don't understand which management aspects we speak about here.
</pre>
        5.<br>
        Clarifying question regarding 1.2<br>
        If speak about OWAMP or TWAMP 'synthetic traffic), is that data
        plane, control plane, or management plane?<br>
        Note that I found later on in the draft:<br>
        <pre class="newpage">   OWAMP and TWAMP use two separate protocols: a Control plane protocol,
   and a Test plane protocol.</pre>
        Interestingly enough, after reading the document, I reviewed <a
          moz-do-not-send="true" class="moz-txt-link-freetext"
href="http://datatracker.ietf.org/doc/draft-ietf-opsawg-oam-overview/ballot/">http://datatracker.ietf.org/doc/draft-ietf-opsawg-oam-overview/ballot/</a>,
        and saw the same feedback from Stewart Bryant:<br>
        <blockquote>
          <pre>Provide a clear view of OAM functionality and its relationship
to various &#8220;planes&#8221; of networking (data plane, control plane,
management plane). In particular, the importance of
fate-sharing of OAM and user traffic flows in packet networks
should be explained.</pre>
        </blockquote>
        6.<br>
        <pre class="newpage">I see a multiplication of "plane" terms in the IETF document, and in this document in particular.
I could find: forwarding plane, management plane, control plane, data plane, user plane, and test plane.
Way too many.
Please be consistent
</pre>
        7.<br>
        <pre class="newpage">   Table 1 summarizes the IETF OAM related RFCs discussed in this
   document.

   Table 2 summarizes the OAM standards mentioned in this document. 

You need to change the Table 2 description. Do you want to say something along the lines of:
   Table 2 summarizes the OAM standards specified by other Standard Development Organization 
   (SDO) than the IETF, along with IETF references where applicable.


8.
Section 2.2.1
   For a formal definition of each term, refer to the references at the end of
   this document.
Without a reference to a specific RFC, this is the type of statement which is not useful: you have 5 pages of references.
You position this document as "An Overview of<span class="h1"></span> Operations, Administration, and Maintenance (OAM) Mechanisms<span class="h1"></span>", but you tell the reader: "if you want to know about the terms,
just read first all references!"

9.
You specify some terms and some OAM categories, 
   <a moz-do-not-send="true" href="http://tools.ietf.org/html/draft-ietf-opsawg-oam-overview-08#section-2.2.2">2.2.2</a>. OAM Maintenance Entities .......................... <a moz-do-not-send="true" href="http://tools.ietf.org/html/draft-ietf-opsawg-oam-overview-08#page-13">13</a>
         <a moz-do-not-send="true" href="http://tools.ietf.org/html/draft-ietf-opsawg-oam-overview-08#section-2.2.3">2.2.3</a>. OAM Maintenance Points ............................ <a moz-do-not-send="true" href="http://tools.ietf.org/html/draft-ietf-opsawg-oam-overview-08#page-14">14</a>
         <a moz-do-not-send="true" href="http://tools.ietf.org/html/draft-ietf-opsawg-oam-overview-08#section-2.2.4">2.2.4</a>. Proactive and On-demand activation ................ <a moz-do-not-send="true" href="http://tools.ietf.org/html/draft-ietf-opsawg-oam-overview-08#page-15">15</a>
         <a moz-do-not-send="true" href="http://tools.ietf.org/html/draft-ietf-opsawg-oam-overview-08#section-2.2.5">2.2.5</a>. Connectivity Verification and Continuity Checks ... <a moz-do-not-send="true" href="http://tools.ietf.org/html/draft-ietf-opsawg-oam-overview-08#page-15">15</a>
         <a moz-do-not-send="true" href="http://tools.ietf.org/html/draft-ietf-opsawg-oam-overview-08#section-2.2.6">2.2.6</a>. Failures .......................................... <a moz-do-not-send="true" href="http://tools.ietf.org/html/draft-ietf-opsawg-oam-overview-08#page-15">15</a>
... but you don't use them in the section 3

Just <u>one </u>example with section 3.2.2
-
   o Demand mode: in this mode, BFD control packets are sent on-demand.
      Upon need, a system initiates a series of BFD control packets to
      verify the liveness of the session
Instead of liveness, you have defined Connectivity Verification and Continuity Checks<span class="h4"></span> in section 2.2.5
- OLD:
   Each of the end-points of the monitored path maintains its own
   session identification
NEW:
   Each of the MEP maintains its own session identification
OR NEW (actually I don't know)
   Each of the MP maintains its own session identification
- OLD
	A BFD echo packet is sent to a peer system
Peer system = MEP, MP, or something else?
- etc... 

10. 
This document is composed of a list of OAM content and references, but I'm really missing the document "scope and target audience".
When we did RFC 6632, which is the companion document, we had <a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://tools.ietf.org/html/rfc6632#section-1.1">http://tools.ietf.org/html/rfc6632#section-1.1</a>
&nbsp;
   The target audience of the document is, on the one hand, IETF working
   groups, which aim to select appropriate standard management protocols
   and data models to address their needs concerning network management.
   On the other hand, the document can be used as an overview and
   guideline by non-IETF Standards Development Organizations (SDOs)
   planning to use IETF management technologies and data models for the
   realization of management applications.  The document can also be
   used to initiate a discussion between the bodies with the goal to
   gather new requirements and to detect possible gaps.  Finally, this
   document is directed to all interested parties that seek to get an
   overview of the current set of the IETF network management protocols
   such as network administrators or newcomers to the IETF.

You should have something similar.


11.
Section 3.6.1, put the paragraph 2 at the end of the section. The "alternative" in the following sentence would then make sense
   Alternative protocols for performance measurement are defined, for
   example, in MPLS-TP OAM ([<a moz-do-not-send="true" href="http://tools.ietf.org/html/draft-ietf-opsawg-oam-overview-08#ref-MPLS-LM-DM" title="&quot;Packet Loss and Delay Measurement for MPLS Networks&quot;">MPLS-LM-DM</a>], [<a moz-do-not-send="true" href="http://tools.ietf.org/html/draft-ietf-opsawg-oam-overview-08#ref-TP-LM-DM" title="&quot;A Packet Loss and Delay Measurement Profile for MPLS-Based Transport Networks&quot;">TP-LM-DM</a>]), and in Ethernet
   OAM [<a moz-do-not-send="true" href="http://tools.ietf.org/html/draft-ietf-opsawg-oam-overview-08#ref-ITU-T-Y1731" title="&quot;OAM Functions and Mechanisms for Ethernet-based Networks&quot;">ITU-T-Y1731</a>].


My conclusions: this document still needs some work

Regards, Benoit
&nbsp;
</pre>
      </div>
      <blockquote
        cite="mid:20130111193616.19158.16205.idtracker@ietfa.amsl.com"
        type="cite">
        <pre wrap="">The IESG has received a request from the Operations and Management Area
Working Group WG (opsawg) to consider the following document:
- 'An Overview of Operations, Administration, and Maintenance (OAM)
   Mechanisms'
  &lt;draft-ietf-opsawg-oam-overview-08.txt&gt; as Informational RFC

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action. Please send substantive comments to the
<a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:ietf@ietf.org">ietf@ietf.org</a> mailing lists by 2013-01-25. Exceptionally, comments may be
sent to <a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:iesg@ietf.org">iesg@ietf.org</a> instead. In either case, please retain the
beginning of the Subject line to allow automated sorting.

Abstract


   Operations, Administration, and Maintenance (OAM) is a general term
   that refers to a toolset that can be used for fault detection and
   isolation, and for performance measurement. OAM mechanisms have been
   defined for various layers in the protocol stack, and are used with a
   variety of protocols.

   This document presents an overview of the OAM mechanisms that have
   been defined and are currently being defined by the IETF.




The file can be obtained via
<a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://datatracker.ietf.org/doc/draft-ietf-opsawg-oam-overview/">http://datatracker.ietf.org/doc/draft-ietf-opsawg-oam-overview/</a>

IESG discussion can be tracked via
<a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://datatracker.ietf.org/doc/draft-ietf-opsawg-oam-overview/ballot/">http://datatracker.ietf.org/doc/draft-ietf-opsawg-oam-overview/ballot/</a>


No IPR declarations have been submitted directly on this I-D.



</pre>
      </blockquote>
      <br>
    </blockquote>
    <br>
  </body>
</html>

--------------080205090701090609030103--

From fernando@gont.com.ar  Fri Jan 18 10:45:51 2013
Return-Path: <fernando@gont.com.ar>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C93B121F8765 for <ietf@ietfa.amsl.com>; Fri, 18 Jan 2013 10:45:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.607
X-Spam-Level: 
X-Spam-Status: No, score=-1.607 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, DATE_IN_PAST_12_24=0.992]
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 OSqXFgw2pT1G for <ietf@ietfa.amsl.com>; Fri, 18 Jan 2013 10:45:51 -0800 (PST)
Received: from web01.jbserver.net (web01.jbserver.net [93.186.182.34]) by ietfa.amsl.com (Postfix) with ESMTP id E9E1921F8757 for <ietf@ietf.org>; Fri, 18 Jan 2013 10:45:50 -0800 (PST)
Received: from 95-132-17-190.fibertel.com.ar ([190.17.132.95] helo=[192.168.1.113]) by web01.jbserver.net with esmtpsa (TLSv1:DHE-RSA-CAMELLIA256-SHA:256) (Exim 4.80.1) (envelope-from <fernando@gont.com.ar>) id 1TwGwI-0000Y3-SW; Fri, 18 Jan 2013 19:45:25 +0100
Message-ID: <50F8EB76.9010009@gont.com.ar>
Date: Fri, 18 Jan 2013 03:28:06 -0300
From: Fernando Gont <fernando@gont.com.ar>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130106 Thunderbird/17.0.2
MIME-Version: 1.0
To: Donald Eastlake <d3e3e3@gmail.com>
Subject: Re: Last Call: <draft-gp-obsolete-icmp-types-iana-01.txt> (Formally Deprecating Some ICMPv4 Message Types) to Proposed Standard
References: <20130117155728.23682.34461.idtracker@ietfa.amsl.com> <CAF4+nEGVKz4Kj8GZ=sjBTXz-0WD+BYg3hh_crJ9zkeeMYzS6gg@mail.gmail.com>
In-Reply-To: <CAF4+nEGVKz4Kj8GZ=sjBTXz-0WD+BYg3hh_crJ9zkeeMYzS6gg@mail.gmail.com>
X-Enigmail-Version: 1.4.6
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 18 Jan 2013 18:45:52 -0000

Hi, Donald,

Thanks so much for your feedback! Please find my comments in-line....

On 01/17/2013 10:09 PM, Donald Eastlake wrote:
>>    A number of ICMPv4 message types have become obsolete in practice,
>>    but have never been formally deprecated.  This document deprecates
>>    such ICMPv4 message types, thus cleaning up the corresponding IANA
>>    registry.  Additionally, it updates RFC792 and RFC950, obsoletes
>>    RFC1788, and requests the RFC Editor to change the status of RFC1788
>>    to "Historic".
> 
> I'm OK with deprecating these ICMPv4 message types. But this could be
> said to "clean up" the IANA registry only, in my opinion, if the
> entries were removed, which would be a bad idea.

FWIW, what we meant by "cleaning up" is that once the registry is
annotated as appropriate, the registry becomes useful for e.g. knowing
which icmp messages are still relevant.



> But the draft does
> not remove these entries or simplify the registry, it annotates the
> entries. I consider the wording "clean up", as used here, to be
> misleading.
> 
> I suggest the second sentence of the abstract be changed to "This
> document deprecates such ICMPv4 message types and annotates the
> corresponding IANA registry entries." and that corresponding changes
> be made elsewhere in the draft where "clean up" is used.

I have no problem with applying this change. So unless anyone argues on
the contrary, I'll rev the document accordingly.

Thanks!

Best regards,
-- 
Fernando Gont
e-mail: fernando@gont.com.ar || fgont@si6networks.com
PGP Fingerprint: 7809 84F5 322E 45C7 F1C9 3945 96EE A9EF D076 FFF1




From cpignata@cisco.com  Fri Jan 18 11:43:35 2013
Return-Path: <cpignata@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DCAB421F8536 for <ietf@ietfa.amsl.com>; Fri, 18 Jan 2013 11:43:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.599
X-Spam-Level: 
X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
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 Z9A63tEWRza4 for <ietf@ietfa.amsl.com>; Fri, 18 Jan 2013 11:43:34 -0800 (PST)
Received: from rcdn-iport-1.cisco.com (rcdn-iport-1.cisco.com [173.37.86.72]) by ietfa.amsl.com (Postfix) with ESMTP id 9D8BA21F85EB for <ietf@ietf.org>; Fri, 18 Jan 2013 11:43:33 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2781; q=dns/txt; s=iport; t=1358538213; x=1359747813; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=WC4qhkMnmSQ1ZwSwc4Tgb2PRFnWNxbcEQT1Tuu1b920=; b=CIMydbg/pzOTl4JbIdGH7diWYTHoEsVMscgQ0SfwCiWdTbrbnveI1/4k VN2LTYEF53otj0vIOpkk2KWW/F77s34Z/DSTBYA2EbsE7daV7Et4x7VZX Tis9yBXYY9ooshsmbQfLDWRm1mA8s31gFBvX3ijgwnDQYX/HvyVw3128G 0=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av8EAPSk+VCtJXG9/2dsb2JhbABBA746FnOCHgEBAQMBbgsFCwIBCA4KChkLIRElAgQOBQiHfwMJBgyzcg2IXowJggKCTWEDiCyMCoJyihuFEoJ1giQ
X-IronPort-AV: E=Sophos;i="4.84,494,1355097600"; d="scan'208";a="164404709"
Received: from rcdn-core2-2.cisco.com ([173.37.113.189]) by rcdn-iport-1.cisco.com with ESMTP; 18 Jan 2013 19:43:33 +0000
Received: from xhc-aln-x12.cisco.com (xhc-aln-x12.cisco.com [173.36.12.86]) by rcdn-core2-2.cisco.com (8.14.5/8.14.5) with ESMTP id r0IJhWqd010342 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 18 Jan 2013 19:43:32 GMT
Received: from xmb-aln-x02.cisco.com ([169.254.5.197]) by xhc-aln-x12.cisco.com ([173.36.12.86]) with mapi id 14.02.0318.004; Fri, 18 Jan 2013 13:43:32 -0600
From: "Carlos Pignataro (cpignata)" <cpignata@cisco.com>
To: Donald Eastlake <d3e3e3@gmail.com>
Subject: Re: Last Call: <draft-gp-obsolete-icmp-types-iana-01.txt> (Formally Deprecating Some ICMPv4 Message Types) to Proposed Standard
Thread-Topic: Last Call: <draft-gp-obsolete-icmp-types-iana-01.txt> (Formally Deprecating Some ICMPv4 Message Types) to Proposed Standard
Thread-Index: AQHN9bQYjbb4hGNLzkKNNcz8HNrUag==
Date: Fri, 18 Jan 2013 19:43:32 +0000
Message-ID: <95067C434CE250468B77282634C96ED3228CCCB6@xmb-aln-x02.cisco.com>
References: <20130117155728.23682.34461.idtracker@ietfa.amsl.com> <CAF4+nEGVKz4Kj8GZ=sjBTXz-0WD+BYg3hh_crJ9zkeeMYzS6gg@mail.gmail.com>
In-Reply-To: <CAF4+nEGVKz4Kj8GZ=sjBTXz-0WD+BYg3hh_crJ9zkeeMYzS6gg@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.117.115.54]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <4A26A7ED24B2504DA3E2371EC6AB4CA0@cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 18 Jan 2013 19:43:35 -0000

Donald,

On Jan 17, 2013, at 8:09 PM, Donald Eastlake <d3e3e3@gmail.com> wrote:

> I have a wording problem with this as below:
>=20
> On Thu, Jan 17, 2013 at 10:57 AM, The IESG <iesg-secretary@ietf.org> wrot=
e:
>>=20
>> The IESG has received a request from an individual submitter to consider
>> the following document:
>> - 'Formally Deprecating Some ICMPv4 Message Types'
>>  <draft-gp-obsolete-icmp-types-iana-01.txt> as Proposed Standard
>>=20
>> The IESG plans to make a decision in the next few weeks, and solicits
>> final comments on this action. Please send substantive comments to the
>> ietf@ietf.org mailing lists by 2013-02-14. Exceptionally, comments may b=
e
>> sent to iesg@ietf.org instead. In either case, please retain the
>> beginning of the Subject line to allow automated sorting.
>>=20
>> Abstract
>>=20
>>   A number of ICMPv4 message types have become obsolete in practice,
>>   but have never been formally deprecated.  This document deprecates
>>   such ICMPv4 message types, thus cleaning up the corresponding IANA
>>   registry.  Additionally, it updates RFC792 and RFC950, obsoletes
>>   RFC1788, and requests the RFC Editor to change the status of RFC1788
>>   to "Historic".
>=20
> I'm OK with deprecating these ICMPv4 message types. But this could be
> said to "clean up" the IANA registry only, in my opinion, if the
> entries were removed, which would be a bad idea. But the draft does
> not remove these entries or simplify the registry, it annotates the
> entries. I consider the wording "clean up", as used here, to be
> misleading.
>=20
> I suggest the second sentence of the abstract be changed to "This
> document deprecates such ICMPv4 message types and annotates the
> corresponding IANA registry entries." and that corresponding changes
> be made elsewhere in the draft where "clean up" is used.
>=20

I think this is a good call out and support the proposal, "annotate" being =
more precise. Does it also need to qualify usability aspects of an annotate=
d registry (i.e., the value of a bit more organized up-to-some-point-in-tim=
e)? I think implicit is fine, but thought I'd bring it up.

Thanks,

-- Carlos.


> Thanks,
> Donald
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D
> Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
> 155 Beaver Street, Milford, MA 01757 USA
> d3e3e3@gmail.com
>=20
>> The file can be obtained via
>> http://datatracker.ietf.org/doc/draft-gp-obsolete-icmp-types-iana/
>>=20
>> IESG discussion can be tracked via
>> http://datatracker.ietf.org/doc/draft-gp-obsolete-icmp-types-iana/ballot=
/
>>=20
>>=20
>> No IPR declarations have been submitted directly on this I-D.
>>=20
>>=20
>=20


From iad@ietf.org  Fri Jan 18 11:46:09 2013
Return-Path: <iad@ietf.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2A42C21F8759; Fri, 18 Jan 2013 11:46:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 kSM7FR4yxaMV; Fri, 18 Jan 2013 11:46:08 -0800 (PST)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AC7DE21F8536; Fri, 18 Jan 2013 11:46:08 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: IETF Administrative Director <iad@ietf.org>
To: IETF Announcement List <ietf-announce@ietf.org>
Subject: IETF Meeting Hotels for 2013
X-Test-IDTracker: no
X-IETF-IDTracker: 4.37
Message-ID: <20130118194608.726.21941.idtracker@ietfa.amsl.com>
Date: Fri, 18 Jan 2013 11:46:08 -0800
Cc: iaoc@ietf.org, iab@iab.org, ietf@ietf.org, wgchairs@ietf.org, iesg@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 18 Jan 2013 19:46:09 -0000

The IAOC has approved giving advance notice of the IETF Meeting hotel venue=
s for 2013 as an experiment. =

Customarily such information has not been provided prior to registration op=
ening for that meeting, however =

the IAOC is persuaded that it may be advantageous to attendees and wants to=
 determine whether there are any =

unintended consequences.

IETF 88	March 10 - 15
Location: Orlando, FL
Venue:	Caribe Royale
		Registration now open:  <https://www.ietf.org/meeting/86/index.html>

IETF 87 	July 28 - August 2
Location: Berlin, Germany
Venue:  	InterContinental Berlin  =

		(Note: Reservations to open approximately 12 weeks before the meeting.)

IETF 88	November 3-8
Location: 	Vancouver, BC, Canada
Venue:  	Hyatt Regency Vancouver  =

		(Note: Reservations to open approximately 12 weeks before the meeting.)

Providing Venue information for 2013 is an experiment to determine impacts =
to participants, Secretariat, =

contracts, venue, and budget.  A decision will be made whether to continue =
to provide Venue information =

for 2014 after IETF 88.

Ray
IETF Administrative Director

From chair@ietf.org  Fri Jan 18 18:47:29 2013
Return-Path: <chair@ietf.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A22B921F85FC; Fri, 18 Jan 2013 18:47:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.949
X-Spam-Level: 
X-Spam-Status: No, score=-102.949 tagged_above=-999 required=5 tests=[AWL=-0.349, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 HKqLXP4rHHec; Fri, 18 Jan 2013 18:47:28 -0800 (PST)
Received: from mail.amsl.com (mail.amsl.com [IPv6:2001:1890:123a::1:14]) by ietfa.amsl.com (Postfix) with ESMTP id E328621F84DD; Fri, 18 Jan 2013 18:47:28 -0800 (PST)
Received: from localhost (c8a.amsl.com [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id D0A311244F4; Fri, 18 Jan 2013 18:47:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from c8a.amsl.com ([127.0.0.1]) by localhost (c8a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JqNTwA2ILhKC; Fri, 18 Jan 2013 18:47:28 -0800 (PST)
Received: from [192.168.2.105] (pool-96-255-37-162.washdc.fios.verizon.net [96.255.37.162]) by c8a.amsl.com (Postfix) with ESMTPSA id 42FD81244F1; Fri, 18 Jan 2013 18:47:28 -0800 (PST)
Subject: Beta testing of xml2rfc version 2
Mime-Version: 1.0 (Apple Message framework v1085)
Content-Type: text/plain; charset=us-ascii
From: IETF Chair <chair@ietf.org>
In-Reply-To: <50EDF9D2.1070303@levkowetz.com>
Date: Fri, 18 Jan 2013 19:52:41 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <99A1B3AF-EDE8-4767-9F6A-DD9BA14CF8B7@ietf.org>
References: <50EDE851.2020207@levkowetz.com> <D8E4800F-1561-4ED3-B0A2-C28E669BD944@vigilsec.com> <29F1CEC4-BCF4-4B24-BA74-94BBF5D27A6E@gmail.com> <50EDF9D2.1070303@levkowetz.com>
To: IETF Announce <ietf-announce@ietf.org>
X-Mailer: Apple Mail (2.1085)
Cc: xml2rfc@ietf.org, IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 19 Jan 2013 02:47:29 -0000

This announces the new xml2rfc implementation for beta testing.  There =
are two components: a command line interface and graphical user =
interfaces.

XML2RFC Version 2
-----------------

The rewrite of xml2rfc in python, tagged with version numbers 2.x.y, =
have been unofficially available for some time, and it is now officially =
announced as available for use.

This package is a complete rewrite of the xml2rfc command-line =
functionality in python.  The command line tool is available from the =
main Python package repository, PyPi:

 http://pypi.python.org/pypi/xml2rfc

or alternatively from:

 http://tools.ietf.org/tools/xml2rfc2/cli/

A number of alternative installation methods are available, described on =
the PyPi page for xml2rfc.

There are some known issues with the current release, none of them =
major.  These are listed in the issue tracker:

 http://tools.ietf.org/tools/xml2rfc/trac/report/9

Bug fixing is actively happening.  If you find bugs which are not =
already listed in the tracker, please add them.  Please help us find the =
bugs.  They cannot be fixed if we do not know about them.  Also, =
suggestions for improvements are welcome.

New releases will be announced at the xml2rfc mail list.


GUI Frontends
-------------

There are also GUI frontends available for Mac, Linux and Windows.  =
These are not undergoing active bugfixing at the moment, but should =
overall be in good enough shape for production use if you prefer a GUI =
interface instead of command-line for your XML to draft/rfc operations.

If you are going to install the GUI version, it is suggested that you =
first install the latest command-line version, and then the GUI =
front-end.

The GUI components can be downloaded from here:

 http://tools.ietf.org/tools/xml2rfc2/gui/

Please note that in some cases, the GUI installers come with an embedded =
version of the base tool, and this version will not necessarily be the =
latest version available.  If you download and install a later version =
of the command-line tool, the GUI component should use that if it comes =
before the embedded version in your PATH, which will normally be the =
case.


Feedback
--------

I hope you'll find that the rewrite of xml2rfc works well for you; it =
will certainly be easier to extend and bugfix than the previous version. =
 If you have feedback, regarding bugs or enhancement suggestions, please =
use the issue tracker at:

 http://tools.ietf.org/tools/xml2rfc/trac/newticket


Best regards,

   Russ Housley
   IETF Chair

   Henrik Levkowetz
   IETF Tools Program Manager=

From cntreras@gmail.com  Sat Jan 19 05:55:18 2013
Return-Path: <cntreras@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A332E21F85AC for <ietf@ietfa.amsl.com>; Sat, 19 Jan 2013 05:55:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.598
X-Spam-Level: 
X-Spam-Status: No, score=-103.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
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 ccVe4oEzd0+4 for <ietf@ietfa.amsl.com>; Sat, 19 Jan 2013 05:55:18 -0800 (PST)
Received: from mail-ea0-f178.google.com (mail-ea0-f178.google.com [209.85.215.178]) by ietfa.amsl.com (Postfix) with ESMTP id DE7CC21F85A0 for <ietf@ietf.org>; Sat, 19 Jan 2013 05:55:17 -0800 (PST)
Received: by mail-ea0-f178.google.com with SMTP id a14so1880042eaa.37 for <ietf@ietf.org>; Sat, 19 Jan 2013 05:55:16 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type; bh=2fkGCq2wbVnH7DOQiVl26IlOoENr9GDRgddnG1xBfRk=; b=ln8Ayg8t5sL39iDE75W/yiNIfODN7iYG+5v76UtMdouKN3SvkPdaU2yT4CVa2QC5Bp m6Y9SOM1v+UATF2IxBXXsW8cqqZJQTUt/nxP6SvlQ8SWYxnRs2J3d/q1HTAiM0sW+5+s yrlu4VL3n3qpHVa1dFp/F0VRGdKKM9OIhYVEEZnJRK2dgfYVthowEkj+i+AEvT19Wj15 MDnP9uSo+N2fj89koCxGyxKnbduVkB5Ycp1duqvL1KTP3Moq5d02DCCUzwlEQEEqt+4P RjgeflW2huOWZ7cS4uW8jSnvjD773C06FvyqX1bThcW9nf71g9NYJcP/EltT3m2AAAPs JqOQ==
MIME-Version: 1.0
X-Received: by 10.14.215.6 with SMTP id d6mr38197309eep.40.1358603716707; Sat, 19 Jan 2013 05:55:16 -0800 (PST)
Received: by 10.14.180.72 with HTTP; Sat, 19 Jan 2013 05:55:16 -0800 (PST)
Date: Sat, 19 Jan 2013 07:55:16 -0600
Message-ID: <CAP0PwYbegCgxXUxT5FpXOs5NUROkrd=WTRX1xi3ARJAiHsk=9A@mail.gmail.com>
Subject: Discussion of BCP79 on the IPR-WG List
From: Jorge Contreras <cntreras@gmail.com>
To: IETF discussion list <ietf@ietf.org>
Content-Type: multipart/alternative; boundary=047d7b5dbec2ecc6ea04d3a493d8
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 19 Jan 2013 13:55:18 -0000

--047d7b5dbec2ecc6ea04d3a493d8
Content-Type: text/plain; charset=ISO-8859-1

All - I wanted to bring to your attention that a new I-D relating to the
IETF's patent policy (BCP79) has been released and is being discussed on
the IPR-WG mailing list.  I am taking the liberty of letting everyone know,
since the IPR-WG list hasn't been particularly active over the past few
years, and this is an important policy document that the community should
be aware of.

I look forward to the discussion!

Jorge Contreras

--047d7b5dbec2ecc6ea04d3a493d8
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

All - I wanted to bring to your attention that a new I-D relating to the IE=
TF&#39;s patent policy (BCP79) has been released and is being discussed on =
the IPR-WG mailing list. =A0I am taking the liberty of letting everyone kno=
w, since the IPR-WG list hasn&#39;t been particularly active over the past =
few years, and this is an important policy document that the community shou=
ld be aware of.<div>
<br></div><div>I look forward to the discussion!</div><div><br></div><div>J=
orge Contreras</div>

--047d7b5dbec2ecc6ea04d3a493d8--

From adrian@olddog.co.uk  Sat Jan 19 08:33:23 2013
Return-Path: <adrian@olddog.co.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 33AAD21F84D3 for <ietf@ietfa.amsl.com>; Sat, 19 Jan 2013 08:33:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.565
X-Spam-Level: 
X-Spam-Status: No, score=-2.565 tagged_above=-999 required=5 tests=[AWL=0.033,  BAYES_00=-2.599, HTML_MESSAGE=0.001]
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 brr0GC+cz0Hz for <ietf@ietfa.amsl.com>; Sat, 19 Jan 2013 08:33:19 -0800 (PST)
Received: from asmtp1.iomartmail.com (asmtp1.iomartmail.com [62.128.201.248]) by ietfa.amsl.com (Postfix) with ESMTP id 4F4B821F84D1 for <ietf@ietf.org>; Sat, 19 Jan 2013 08:33:16 -0800 (PST)
Received: from asmtp1.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp1.iomartmail.com (8.13.8/8.13.8) with ESMTP id r0JGXEdZ010482;  Sat, 19 Jan 2013 16:33:14 GMT
Received: from 950129200 (089144192047.atnat0001.highway.a1.net [89.144.192.47]) (authenticated bits=0) by asmtp1.iomartmail.com (8.13.8/8.13.8) with ESMTP id r0JGWuXo010416 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Sat, 19 Jan 2013 16:33:05 GMT
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "'IETF discussion list'" <ietf@ietf.org>
References: <CAP0PwYbegCgxXUxT5FpXOs5NUROkrd=WTRX1xi3ARJAiHsk=9A@mail.gmail.com>
In-Reply-To: <CAP0PwYbegCgxXUxT5FpXOs5NUROkrd=WTRX1xi3ARJAiHsk=9A@mail.gmail.com>
Subject: RE: Discussion of BCP79 on the IPR-WG List
Date: Sat, 19 Jan 2013 16:32:55 -0000
Message-ID: <008f01cdf662$a93a98b0$fbafca10$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0090_01CDF662.A93A98B0"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQIXLoG+PVg8z9KEHfEwK/bvO0fuy5e+ZtzA
Content-Language: en-gb
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: adrian@olddog.co.uk
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 19 Jan 2013 16:33:23 -0000

This is a multipart message in MIME format.

------=_NextPart_000_0090_01CDF662.A93A98B0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

Just to help this along a bit...
 
The IPR WG was concluded in November 2008. However, the mailing list remained
active for the discussion of IPR issues: subscribe via
https://www.ietf.org/mailman/listinfo/ipr-wg.
 
The list archive is at
http://www.ietf.org/mail-archive/web/ipr-wg/current/maillist.html, and Jorge
appears to be referring to "Intellectual Property Rights in IETF Technology"
http://datatracker.ietf.org/doc/draft-bradner-rfc3979bis/
 
Thanks, 
Adrian
 
 
From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of Jorge
Contreras
Sent: 19 January 2013 13:55
To: IETF discussion list
Subject: Discussion of BCP79 on the IPR-WG List
 
All - I wanted to bring to your attention that a new I-D relating to the IETF's
patent policy (BCP79) has been released and is being discussed on the IPR-WG
mailing list.  I am taking the liberty of letting everyone know, since the
IPR-WG list hasn't been particularly active over the past few years, and this is
an important policy document that the community should be aware of.
 
I look forward to the discussion!
 
Jorge Contreras

------=_NextPart_000_0090_01CDF662.A93A98B0
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta =
http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii"><meta name=3DProgId content=3DWord.Document><meta =
name=3DGenerator content=3D"Microsoft Word 14"><meta name=3DOriginator =
content=3D"Microsoft Word 14"><link rel=3DFile-List =
href=3D"cid:filelist.xml@01CDF662.92F54D70"><!--[if gte mso 9]><xml>
<o:OfficeDocumentSettings>
<o:AllowPNG/>
</o:OfficeDocumentSettings>
</xml><![endif]--><!--[if gte mso 9]><xml>
<w:WordDocument>
<w:SpellingState>Clean</w:SpellingState>
<w:TrackMoves/>
<w:TrackFormatting/>
<w:EnvelopeVis/>
<w:ValidateAgainstSchemas/>
<w:SaveIfXMLInvalid>false</w:SaveIfXMLInvalid>
<w:IgnoreMixedContent>false</w:IgnoreMixedContent>
<w:AlwaysShowPlaceholderText>false</w:AlwaysShowPlaceholderText>
<w:DoNotPromoteQF/>
<w:LidThemeOther>EN-GB</w:LidThemeOther>
<w:LidThemeAsian>X-NONE</w:LidThemeAsian>
<w:LidThemeComplexScript>X-NONE</w:LidThemeComplexScript>
<w:Compatibility>
<w:DoNotExpandShiftReturn/>
<w:BreakWrappedTables/>
<w:SplitPgBreakAndParaMark/>
<w:EnableOpenTypeKerning/>
</w:Compatibility>
<m:mathPr>
<m:mathFont m:val=3D"Cambria Math"/>
<m:brkBin m:val=3D"before"/>
<m:brkBinSub m:val=3D"&#45;-"/>
<m:smallFrac m:val=3D"off"/>
<m:dispDef/>
<m:lMargin m:val=3D"0"/>
<m:rMargin m:val=3D"0"/>
<m:defJc m:val=3D"centerGroup"/>
<m:wrapIndent m:val=3D"1440"/>
<m:intLim m:val=3D"subSup"/>
<m:naryLim m:val=3D"undOvr"/>
</m:mathPr></w:WordDocument>
</xml><![endif]--><!--[if gte mso 9]><xml>
<w:LatentStyles DefLockedState=3D"false" DefUnhideWhenUsed=3D"true" =
DefSemiHidden=3D"true" DefQFormat=3D"false" DefPriority=3D"99" =
LatentStyleCount=3D"267">
<w:LsdException Locked=3D"false" Priority=3D"0" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Normal"/>
<w:LsdException Locked=3D"false" Priority=3D"9" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"heading 1"/>
<w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" =
Name=3D"heading 2"/>
<w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" =
Name=3D"heading 3"/>
<w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" =
Name=3D"heading 4"/>
<w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" =
Name=3D"heading 5"/>
<w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" =
Name=3D"heading 6"/>
<w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" =
Name=3D"heading 7"/>
<w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" =
Name=3D"heading 8"/>
<w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" =
Name=3D"heading 9"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 1"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 2"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 3"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 4"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 5"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 6"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 7"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 8"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 9"/>
<w:LsdException Locked=3D"false" Priority=3D"35" QFormat=3D"true" =
Name=3D"caption"/>
<w:LsdException Locked=3D"false" Priority=3D"10" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Title"/>
<w:LsdException Locked=3D"false" Priority=3D"1" Name=3D"Default =
Paragraph Font"/>
<w:LsdException Locked=3D"false" Priority=3D"11" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Subtitle"/>
<w:LsdException Locked=3D"false" Priority=3D"22" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Strong"/>
<w:LsdException Locked=3D"false" Priority=3D"20" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Emphasis"/>
<w:LsdException Locked=3D"false" Priority=3D"59" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Table Grid"/>
<w:LsdException Locked=3D"false" UnhideWhenUsed=3D"false" =
Name=3D"Placeholder Text"/>
<w:LsdException Locked=3D"false" Priority=3D"1" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"No Spacing"/>
<w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Shading"/>
<w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light List"/>
<w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Grid"/>
<w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1"/>
<w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2"/>
<w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 1"/>
<w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 2"/>
<w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1"/>
<w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2"/>
<w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3"/>
<w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Dark List"/>
<w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Shading"/>
<w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful List"/>
<w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Grid"/>
<w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light List Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 1"/>
<w:LsdException Locked=3D"false" UnhideWhenUsed=3D"false" =
Name=3D"Revision"/>
<w:LsdException Locked=3D"false" Priority=3D"34" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"List Paragraph"/>
<w:LsdException Locked=3D"false" Priority=3D"29" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Quote"/>
<w:LsdException Locked=3D"false" Priority=3D"30" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Intense Quote"/>
<w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light List Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light List Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light List Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light List Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light List Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"19" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Subtle Emphasis"/>
<w:LsdException Locked=3D"false" Priority=3D"21" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Intense Emphasis"/>
<w:LsdException Locked=3D"false" Priority=3D"31" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Subtle Reference"/>
<w:LsdException Locked=3D"false" Priority=3D"32" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Intense Reference"/>
<w:LsdException Locked=3D"false" Priority=3D"33" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Book Title"/>
<w:LsdException Locked=3D"false" Priority=3D"37" Name=3D"Bibliography"/>
<w:LsdException Locked=3D"false" Priority=3D"39" QFormat=3D"true" =
Name=3D"TOC Heading"/>
</w:LatentStyles>
</xml><![endif]--><style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;
	mso-font-charset:0;
	mso-generic-font-family:swiss;
	mso-font-pitch:variable;
	mso-font-signature:-536870145 1073786111 1 0 415 0;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;
	mso-font-charset:0;
	mso-generic-font-family:swiss;
	mso-font-pitch:variable;
	mso-font-signature:-520081665 -1073717157 41 0 66047 0;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{mso-style-unhide:no;
	mso-style-qformat:yes;
	mso-style-parent:"";
	margin:0cm;
	margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";
	mso-fareast-font-family:Calibri;}
a:link, span.MsoHyperlink
	{mso-style-noshow:yes;
	mso-style-priority:99;
	color:blue;
	text-decoration:underline;
	text-underline:single;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-noshow:yes;
	mso-style-priority:99;
	color:purple;
	text-decoration:underline;
	text-underline:single;}
span.EmailStyle17
	{mso-style-type:personal-reply;
	mso-style-noshow:yes;
	mso-style-unhide:no;
	mso-ansi-font-size:11.0pt;
	mso-bidi-font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	mso-ascii-font-family:Calibri;
	mso-fareast-font-family:Calibri;
	mso-hansi-font-family:Calibri;
	mso-bidi-font-family:"Times New Roman";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	mso-default-props:yes;
	mso-ascii-font-family:Calibri;
	mso-fareast-font-family:Calibri;
	mso-hansi-font-family:Calibri;
	mso-bidi-font-family:"Times New Roman";
	mso-fareast-language:EN-US;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 72.0pt 72.0pt 72.0pt;
	mso-header-margin:36.0pt;
	mso-footer-margin:36.0pt;
	mso-paper-source:0;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 10]><style>/* Style Definitions */
table.MsoNormalTable
	{mso-style-name:"Table Normal";
	mso-tstyle-rowband-size:0;
	mso-tstyle-colband-size:0;
	mso-style-noshow:yes;
	mso-style-priority:99;
	mso-style-parent:"";
	mso-padding-alt:0cm 5.4pt 0cm 5.4pt;
	mso-para-margin:0cm;
	mso-para-margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	mso-ascii-font-family:Calibri;
	mso-hansi-font-family:Calibri;
	mso-fareast-language:EN-US;}
</style><![endif]--><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-GB link=3Dblue =
vlink=3Dpurple style=3D'tab-interval:36.0pt'><div =
class=3DWordSection1><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-bidi-fon=
t-family:"Times New Roman";color:#1F497D'>Just to help this along a =
bit...<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-bidi-fon=
t-family:"Times New Roman";color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-bidi-fon=
t-family:"Times New Roman";color:#1F497D'>The IPR WG was concluded in =
November 2008. However, the mailing list remained active for the =
discussion of IPR issues: subscribe via =
https://www.ietf.org/mailman/listinfo/ipr-wg.<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-bidi-fon=
t-family:"Times New Roman";color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-bidi-fon=
t-family:"Times New Roman";color:#1F497D'>The list archive is at =
http://www.ietf.org/mail-archive/web/ipr-wg/current/maillist.html, and =
Jorge appears to be referring to &quot;Intellectual Property Rights in =
IETF Technology&quot; =
http://datatracker.ietf.org/doc/draft-bradner-rfc3979bis/<o:p></o:p></spa=
n></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-bidi-fon=
t-family:"Times New Roman";color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-bidi-fon=
t-family:"Times New Roman";color:#1F497D'>Thanks, =
<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-bidi-fon=
t-family:"Times New Roman";color:#1F497D'>Adrian<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-bidi-fon=
t-family:"Times New Roman";color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-bidi-fon=
t-family:"Times New =
Roman";color:#1F497D'><o:p>&nbsp;</o:p></span></p><div =
style=3D'border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm =
4.0pt'><div><div style=3D'border:none;border-top:solid #B5C4DF =
1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=3DMsoNormal><b><span =
lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";mso-fareast-f=
ont-family:"Times New =
Roman";mso-ansi-language:EN-US'>From:</span></b><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";mso-fareast-f=
ont-family:"Times New Roman";mso-ansi-language:EN-US'> =
ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] <b>On Behalf Of =
</b>Jorge Contreras<br><b>Sent:</b> 19 January 2013 13:55<br><b>To:</b> =
IETF discussion list<br><b>Subject:</b> Discussion of BCP79 on the =
IPR-WG List<o:p></o:p></span></p></div></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>All - I =
wanted to bring to your attention that a new I-D relating to the IETF's =
patent policy (BCP79) has been released and is being discussed on the =
IPR-WG mailing list. &nbsp;I am taking the liberty of letting everyone =
know, since the IPR-WG list hasn't been particularly active over the =
past few years, and this is an important policy document that the =
community should be aware of.<o:p></o:p></p><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p class=3DMsoNormal>I =
look forward to the discussion!<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>Jorge =
Contreras<o:p></o:p></p></div></div></div></body></html>
------=_NextPart_000_0090_01CDF662.A93A98B0--


From abdussalambaryun@gmail.com  Sat Jan 19 12:38:09 2013
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 86CB421F8415 for <ietf@ietfa.amsl.com>; Sat, 19 Jan 2013 12:38:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.584
X-Spam-Level: 
X-Spam-Status: No, score=-3.584 tagged_above=-999 required=5 tests=[AWL=0.015,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 svAA5lHwEzNG for <ietf@ietfa.amsl.com>; Sat, 19 Jan 2013 12:38:09 -0800 (PST)
Received: from mail-vb0-f48.google.com (mail-vb0-f48.google.com [209.85.212.48]) by ietfa.amsl.com (Postfix) with ESMTP id ED2D021F879E for <ietf@ietf.org>; Sat, 19 Jan 2013 12:38:08 -0800 (PST)
Received: by mail-vb0-f48.google.com with SMTP id fc21so4621992vbb.7 for <ietf@ietf.org>; Sat, 19 Jan 2013 12:38:08 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to:cc :content-type; bh=S8aSEzm3Qjp13uMPyyJLBRvyfOBKzlKTd71tmJu96Y8=; b=HC4oiEbaFVLXlxKXZdERJFu9Zu5IZDpoSFK1idf1K1tozpIWz95RM2m7kNQ5UAv4Xl F3E5JO6tbv9rtXNCmkEMPzxJXIedKmaBjiTi207nPexDsSpentbjS5ebX4h3A06R5qyW 39bJAHm4ARw4N+CSEA5KibIXXSsrmrEpIQrC3crsIEi7r5eOtxy2pMOwGLd2rHavtD/y OZnD0QPAOxkbhMLNgD0VfVWx3VgJkOOzffyMtbWKHvr0iCzCxKgcU6NuNqe0b00GsZ2e p2xqJnsYeUKhiR/x8XkBqno8N1ouHYhtsVogkYRZmrfjweM3RL8zsBfTHnOyN5O0RG8d 5u1Q==
MIME-Version: 1.0
X-Received: by 10.52.21.179 with SMTP id w19mr12716977vde.55.1358627888193; Sat, 19 Jan 2013 12:38:08 -0800 (PST)
Received: by 10.220.145.5 with HTTP; Sat, 19 Jan 2013 12:38:08 -0800 (PST)
Date: Sat, 19 Jan 2013 21:38:08 +0100
Message-ID: <CADnDZ88Gv_9iSNCoyAESH-tj3h86d+Q=Z0WDW9euPHj8+FDXmA@mail.gmail.com>
Subject: Re: Discussion of BCP79 on the IPR-WG List
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: cntreras@gmail.com
Content-Type: text/plain; charset=ISO-8859-1
Cc: ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 19 Jan 2013 20:38:09 -0000

Hi Jorge,

I never heard of this WG, is it a IETF WG, why it is not under the
General Area. This is very strange, when checking the WGs there is no
WG under General Area, is there explaination, please advise,

It is not active maybe because not represented well, or the management
of IETF was not interested in such WG, I am not sure :-( . IMO, I am
not encouraged to participate only if this WG is IETF WG under an IETF
Area, but I will read to see WG progress and/or future,

Regards

AB
++++
All - I wanted to bring to your attention that a new I-D relating to
the IETF's patent policy (BCP79) has been released and is being
discussed on the IPR-WG mailing list.  I am taking the liberty of
letting everyone know, since the IPR-WG list hasn't been particularly
active over the past few years, and this is an important policy
document that the community should be aware of.


I look forward to the discussion!


Jorge Contreras

From smb@cs.columbia.edu  Sat Jan 19 14:00:22 2013
Return-Path: <smb@cs.columbia.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2D4CE21F86D3 for <ietf@ietfa.amsl.com>; Sat, 19 Jan 2013 14:00:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[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 I4kfbsT70y2D for <ietf@ietfa.amsl.com>; Sat, 19 Jan 2013 14:00:16 -0800 (PST)
Received: from paneer.cc.columbia.edu (paneer.cc.columbia.edu [128.59.29.4]) by ietfa.amsl.com (Postfix) with ESMTP id CDC8321F862D for <ietf@ietf.org>; Sat, 19 Jan 2013 14:00:15 -0800 (PST)
Received: from [10.9.0.186] (fireball.cs.columbia.edu [128.59.13.10]) (user=smb2132 mech=PLAIN bits=0) by paneer.cc.columbia.edu (8.14.4/8.14.3) with ESMTP id r0JM0DeB017280 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Sat, 19 Jan 2013 17:00:14 -0500 (EST)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Subject: Re: Discussion of BCP79 on the IPR-WG List
From: Steven Bellovin <smb@cs.columbia.edu>
In-Reply-To: <CADnDZ88Gv_9iSNCoyAESH-tj3h86d+Q=Z0WDW9euPHj8+FDXmA@mail.gmail.com>
Date: Sat, 19 Jan 2013 17:00:12 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <ECF91269-8551-4DA4-8BF8-644F3AEF8BEF@cs.columbia.edu>
References: <CADnDZ88Gv_9iSNCoyAESH-tj3h86d+Q=Z0WDW9euPHj8+FDXmA@mail.gmail.com>
To: Abdussalam Baryun <abdussalambaryun@gmail.com>
X-Mailer: Apple Mail (2.1499)
X-No-Spam-Score: Local
X-Scanned-By: MIMEDefang 2.68 on 128.59.29.4
Cc: ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 19 Jan 2013 22:00:22 -0000

It's not listed under the General area because the working group =
disbanded
when its RFCs were finished.  IETF working groups do not last forever;
when their work is done, they're shut down.  The last charter is at
https://www.ietf.org/wg/concluded/ipr.html

As for IETF management support -- Rob Austein and I were the original
chairs.  At the time, I was on the IESG and he was on the IAB.  Rob
was succeed as co-chair by Harald Alvestrand, the immediate past chair
of the IETF.  So yes, it did have full support.

On Jan 19, 2013, at 3:38 PM, Abdussalam Baryun =
<abdussalambaryun@gmail.com> wrote:

> Hi Jorge,
>=20
> I never heard of this WG, is it a IETF WG, why it is not under the
> General Area. This is very strange, when checking the WGs there is no
> WG under General Area, is there explaination, please advise,
>=20
> It is not active maybe because not represented well, or the management
> of IETF was not interested in such WG, I am not sure :-( . IMO, I am
> not encouraged to participate only if this WG is IETF WG under an IETF
> Area, but I will read to see WG progress and/or future,
>=20
> Regards
>=20
> AB
> ++++
> All - I wanted to bring to your attention that a new I-D relating to
> the IETF's patent policy (BCP79) has been released and is being
> discussed on the IPR-WG mailing list.  I am taking the liberty of
> letting everyone know, since the IPR-WG list hasn't been particularly
> active over the past few years, and this is an important policy
> document that the community should be aware of.
>=20
>=20
> I look forward to the discussion!
>=20
>=20
> Jorge Contreras
>=20


		--Steve Bellovin, https://www.cs.columbia.edu/~smb






From abdussalambaryun@gmail.com  Sun Jan 20 04:03:08 2013
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8432921F8512 for <ietf@ietfa.amsl.com>; Sun, 20 Jan 2013 04:03:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.584
X-Spam-Level: 
X-Spam-Status: No, score=-3.584 tagged_above=-999 required=5 tests=[AWL=0.015,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 ksJ2UcSibLOr for <ietf@ietfa.amsl.com>; Sun, 20 Jan 2013 04:03:07 -0800 (PST)
Received: from mail-vc0-f179.google.com (mail-vc0-f179.google.com [209.85.220.179]) by ietfa.amsl.com (Postfix) with ESMTP id C3DD521F8506 for <ietf@ietf.org>; Sun, 20 Jan 2013 04:03:03 -0800 (PST)
Received: by mail-vc0-f179.google.com with SMTP id fl15so162016vcb.10 for <ietf@ietf.org>; Sun, 20 Jan 2013 04:03:03 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=0h4Qng/NKLprYBYNhStpqiDb2JXyrQUuiUOATdI37Wc=; b=bXF/bInxV4VmFTZGrZYYnfZ0pFAqBcqvPGfWZVxD0qBhyndjXvCz5mzverXmeSw1+S 9w0pqHYmf3TN4CR7ucoEy+VkJ5MHA9Psk4wzt51gxfNZ1nl6CcsvD32vhJw3Yl0/z1V6 Gf6Ug3fB84Or9nyhM6kNB1aznSkIiJVRS6Ry8nUxO67NmVb37mo4hPhr9A8NyWGbnkoe KuUYsbEFmcJBJyYLsiu4hVmBAXWNbVN3HUbTX+HefdJd+nAlVW0SDGCrErWEjuYhuEmZ vs3HDxqZQhMiUaWxjNv5GEQNmmR1f75A1afyChMOJVbvKAP5p/nvR2fd8kSIq4O+/D2W w1Yw==
MIME-Version: 1.0
X-Received: by 10.220.149.69 with SMTP id s5mr16076871vcv.23.1358683383151; Sun, 20 Jan 2013 04:03:03 -0800 (PST)
Received: by 10.220.145.5 with HTTP; Sun, 20 Jan 2013 04:03:03 -0800 (PST)
In-Reply-To: <ECF91269-8551-4DA4-8BF8-644F3AEF8BEF@cs.columbia.edu>
References: <CADnDZ88Gv_9iSNCoyAESH-tj3h86d+Q=Z0WDW9euPHj8+FDXmA@mail.gmail.com> <ECF91269-8551-4DA4-8BF8-644F3AEF8BEF@cs.columbia.edu>
Date: Sun, 20 Jan 2013 13:03:03 +0100
Message-ID: <CADnDZ88+sSt=VuUJMDc_L5wxQsbWQust1nBc0b=y_C3SLYk_Rw@mail.gmail.com>
Subject: Re: Discussion of BCP79 on the IPR-WG List
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: Steven Bellovin <smb@cs.columbia.edu>
Content-Type: text/plain; charset=ISO-8859-1
Cc: ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 20 Jan 2013 12:03:08 -0000

Hi Steven,

Thanks, I am learning :)

AB

On 1/19/13, Steven Bellovin <smb@cs.columbia.edu> wrote:
> It's not listed under the General area because the working group disbanded
> when its RFCs were finished.  IETF working groups do not last forever;
> when their work is done, they're shut down.  The last charter is at
> https://www.ietf.org/wg/concluded/ipr.html
>
> As for IETF management support -- Rob Austein and I were the original
> chairs.  At the time, I was on the IESG and he was on the IAB.  Rob
> was succeed as co-chair by Harald Alvestrand, the immediate past chair
> of the IETF.  So yes, it did have full support.
>
> On Jan 19, 2013, at 3:38 PM, Abdussalam Baryun <abdussalambaryun@gmail.com>
> wrote:
>
>> Hi Jorge,
>>
>> I never heard of this WG, is it a IETF WG, why it is not under the
>> General Area. This is very strange, when checking the WGs there is no
>> WG under General Area, is there explaination, please advise,
>>
>> It is not active maybe because not represented well, or the management
>> of IETF was not interested in such WG, I am not sure :-( . IMO, I am
>> not encouraged to participate only if this WG is IETF WG under an IETF
>> Area, but I will read to see WG progress and/or future,
>>
>> Regards
>>
>> AB
>> ++++
>> All - I wanted to bring to your attention that a new I-D relating to
>> the IETF's patent policy (BCP79) has been released and is being
>> discussed on the IPR-WG mailing list.  I am taking the liberty of
>> letting everyone know, since the IPR-WG list hasn't been particularly
>> active over the past few years, and this is an important policy
>> document that the community should be aware of.
>>
>>
>> I look forward to the discussion!
>>
>>
>> Jorge Contreras
>>
>
>
> 		--Steve Bellovin, https://www.cs.columbia.edu/~smb
>
>
>
>
>
>

From agmalis@gmail.com  Sun Jan 20 06:53:41 2013
Return-Path: <agmalis@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 169C421F84BA; Sun, 20 Jan 2013 06:53:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.182
X-Spam-Level: 
X-Spam-Status: No, score=-3.182 tagged_above=-999 required=5 tests=[AWL=0.416,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
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 YUZi9Ue2OMRO; Sun, 20 Jan 2013 06:53:40 -0800 (PST)
Received: from mail-qa0-f51.google.com (mail-qa0-f51.google.com [209.85.216.51]) by ietfa.amsl.com (Postfix) with ESMTP id CD56321F8421; Sun, 20 Jan 2013 06:53:39 -0800 (PST)
Received: by mail-qa0-f51.google.com with SMTP id i20so4081949qad.17 for <multiple recipients>; Sun, 20 Jan 2013 06:53:39 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:mime-version:in-reply-to:references:from:date:message-id :subject:to:cc:content-type; bh=2gvNs3Bbq+36I3ypkhmJC+kKtDvuxcCaJsiUK1Bo0c8=; b=jXRVb4fPkjDIuLBkJYcnwwa1qW+FOSq/n8GoMitB+BcNLxJTzlC5NMrSpgTuStLILv wF9Q6S9pkikB6t6QngAhq2YIefamUFYKOZ+6l1rsDyzbNy66vcpoOmI9is3ZWpDT4jfJ L4tbSQTJ4xBOO9oKJ6oAs/wSAXhgwmsUZmX1tJPNoUU6T9F4SSOATgurKzQa/OAmZBUI Sat43/itpPA0NvorDLx8a70aLZH6fEvfAxU3/8H4Mnu02/jAsADrSc6iWEzkzdjWvFSz RmnnEtlqNzxTh47Tcdw7RAJlCsfYm+n18ccgPKzICpOlKGEl3My828N/bG9RG2JDktgA 6bVg==
X-Received: by 10.224.100.130 with SMTP id y2mr16341066qan.40.1358693619143; Sun, 20 Jan 2013 06:53:39 -0800 (PST)
MIME-Version: 1.0
Received: by 10.229.78.72 with HTTP; Sun, 20 Jan 2013 06:53:18 -0800 (PST)
In-Reply-To: <20130118194608.726.21941.idtracker@ietfa.amsl.com>
References: <20130118194608.726.21941.idtracker@ietfa.amsl.com>
From: "Andrew G. Malis" <agmalis@gmail.com>
Date: Sun, 20 Jan 2013 09:53:18 -0500
Message-ID: <CAA=duU2M_47tmR6YFCtfWtRgjYQ=y3Tya_tDD=yBAj9pJ=yY3w@mail.gmail.com>
Subject: Re: IETF Meeting Hotels for 2013
To: IETF Administrative Director <iad@ietf.org>
Content-Type: multipart/alternative; boundary=20cf306f750487123204d3b98213
Cc: "iaoc@ietf.org" <iaoc@ietf.org>, IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 20 Jan 2013 14:53:41 -0000

--20cf306f750487123204d3b98213
Content-Type: text/plain; charset=ISO-8859-1

Ray,

I haven't seen much (any?) discussion of this announcement, perhaps a first
for this group. Anyway, I think it's an excellent idea, it gives people a
chance to plan their travel further out especially if they're thinking of
bringing companions, families, etc. Please continue this!

Thanks,
Andy

On Fri, Jan 18, 2013 at 2:46 PM, IETF Administrative Director
<iad@ietf.org>wrote:

> The IAOC has approved giving advance notice of the IETF Meeting hotel
> venues for 2013 as an experiment.
> Customarily such information has not been provided prior to registration
> opening for that meeting, however
> the IAOC is persuaded that it may be advantageous to attendees and wants
> to determine whether there are any
> unintended consequences.
>
> IETF 88 March 10 - 15
> Location: Orlando, FL
> Venue:  Caribe Royale
>                 Registration now open:  <
> https://www.ietf.org/meeting/86/index.html>
>
> IETF 87         July 28 - August 2
> Location: Berlin, Germany
> Venue:          InterContinental Berlin
>                 (Note: Reservations to open approximately 12 weeks before
> the meeting.)
>
> IETF 88 November 3-8
> Location:       Vancouver, BC, Canada
> Venue:          Hyatt Regency Vancouver
>                 (Note: Reservations to open approximately 12 weeks before
> the meeting.)
>
> Providing Venue information for 2013 is an experiment to determine impacts
> to participants, Secretariat,
> contracts, venue, and budget.  A decision will be made whether to continue
> to provide Venue information
> for 2014 after IETF 88.
>
> Ray
> IETF Administrative Director
>

--20cf306f750487123204d3b98213
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>Ray,<br><br>I haven&#39;t seen much (any?) discussion=
 of this announcement, perhaps a first for this group. Anyway, I think it&#=
39;s an excellent idea, it gives people a chance to plan their travel furth=
er out especially if they&#39;re thinking of bringing companions, families,=
 etc. Please continue this!<br>

<br>Thanks,<br></div>Andy<br><div><div class=3D"gmail_extra"><br><div class=
=3D"gmail_quote">On Fri, Jan 18, 2013 at 2:46 PM, IETF Administrative Direc=
tor <span dir=3D"ltr">&lt;<a href=3D"mailto:iad@ietf.org" target=3D"_blank"=
>iad@ietf.org</a>&gt;</span> wrote:<br>


<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">The IAOC has approved giving advance notice =
of the IETF Meeting hotel venues for 2013 as an experiment.<br>
Customarily such information has not been provided prior to registration op=
ening for that meeting, however<br>
the IAOC is persuaded that it may be advantageous to attendees and wants to=
 determine whether there are any<br>
unintended consequences.<br>
<br>
IETF 88 March 10 - 15<br>
Location: Orlando, FL<br>
Venue: =A0Caribe Royale<br>
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 Registration now open: =A0&lt;<a href=3D"ht=
tps://www.ietf.org/meeting/86/index.html" target=3D"_blank">https://www.iet=
f.org/meeting/86/index.html</a>&gt;<br>
<br>
IETF 87 =A0 =A0 =A0 =A0 July 28 - August 2<br>
Location: Berlin, Germany<br>
Venue: =A0 =A0 =A0 =A0 =A0InterContinental Berlin<br>
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 (Note: Reservations to open approximately 1=
2 weeks before the meeting.)<br>
<br>
IETF 88 November 3-8<br>
Location: =A0 =A0 =A0 Vancouver, BC, Canada<br>
Venue: =A0 =A0 =A0 =A0 =A0Hyatt Regency Vancouver<br>
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 (Note: Reservations to open approximately 1=
2 weeks before the meeting.)<br>
<br>
Providing Venue information for 2013 is an experiment to determine impacts =
to participants, Secretariat,<br>
contracts, venue, and budget. =A0A decision will be made whether to continu=
e to provide Venue information<br>
for 2014 after IETF 88.<br>
<br>
Ray<br>
<span><font color=3D"#888888">IETF Administrative Director<br>
</font></span></blockquote></div><br></div></div></div>

--20cf306f750487123204d3b98213--

From akatlas@gmail.com  Sun Jan 20 07:53:51 2013
Return-Path: <akatlas@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8157721F84EA; Sun, 20 Jan 2013 07:53:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.598
X-Spam-Level: 
X-Spam-Status: No, score=-3.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
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 GYCvK7xf6K7v; Sun, 20 Jan 2013 07:53:50 -0800 (PST)
Received: from mail-ie0-f170.google.com (mail-ie0-f170.google.com [209.85.223.170]) by ietfa.amsl.com (Postfix) with ESMTP id 9B94921F84E9; Sun, 20 Jan 2013 07:53:50 -0800 (PST)
Received: by mail-ie0-f170.google.com with SMTP id k10so8778571iea.29 for <multiple recipients>; Sun, 20 Jan 2013 07:53:50 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=HpGjQoDx9ysdL4Ncs4F5gJ2o1YH9ylO4gb/GDabKTZY=; b=Iuz1ecpwkLWOjvcCkYHqsNz4tDXVV8xk1MNXrSipjE16erPaA3N+Sz5J2leL0RGWAn zM++YPNqrxV9LlCIO0VDh8E23JYNLw3rcjN3XYMuRIO1PbRPC45+E6zLTmKBCV9FSmd7 go1ZT4uSyqhY9eIs80kXP5tY5e12teqRRshptDYaxeSkglyciBnWouhQuZ2ASklH4wOb ew8wMdVPBwfywVKlG1e9E0SzgPDXS3qy1NvDY3kAMxBiYQuFtf1dnA100RJ7TA8vDdEk QI2QQAITIhHq8nbhPVNz5TEvh7D3LijPNfKacOjpzromQrxPV0AmDA4FSjWd+sLs14x9 97tw==
MIME-Version: 1.0
X-Received: by 10.50.6.169 with SMTP id c9mr7377565iga.24.1358697230202; Sun, 20 Jan 2013 07:53:50 -0800 (PST)
Received: by 10.64.23.144 with HTTP; Sun, 20 Jan 2013 07:53:50 -0800 (PST)
Received: by 10.64.23.144 with HTTP; Sun, 20 Jan 2013 07:53:50 -0800 (PST)
In-Reply-To: <CAA=duU2M_47tmR6YFCtfWtRgjYQ=y3Tya_tDD=yBAj9pJ=yY3w@mail.gmail.com>
References: <20130118194608.726.21941.idtracker@ietfa.amsl.com> <CAA=duU2M_47tmR6YFCtfWtRgjYQ=y3Tya_tDD=yBAj9pJ=yY3w@mail.gmail.com>
Date: Sun, 20 Jan 2013 10:53:50 -0500
Message-ID: <CAG4d1rfaxz1U3yNxcjGPu-LbpcWZ2Gip-S3zuuNNaDODpLOMBQ@mail.gmail.com>
Subject: Re: IETF Meeting Hotels for 2013
From: Alia Atlas <akatlas@gmail.com>
To: "Andrew G. Malis" <agmalis@gmail.com>
Content-Type: multipart/alternative; boundary=e89a8f646717c377b904d3ba5931
Cc: "iaoc@ietf.org" <iaoc@ietf.org>, IETF Discussion Mailing List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 20 Jan 2013 15:53:51 -0000

--e89a8f646717c377b904d3ba5931
Content-Type: text/plain; charset=ISO-8859-1

I agree.  What a great idea for those of us trying to plan bringing family
along or for after/before.

Alia
On Jan 20, 2013 9:53 AM, "Andrew G. Malis" <agmalis@gmail.com> wrote:

> Ray,
>
> I haven't seen much (any?) discussion of this announcement, perhaps a
> first for this group. Anyway, I think it's an excellent idea, it gives
> people a chance to plan their travel further out especially if they're
> thinking of bringing companions, families, etc. Please continue this!
>
> Thanks,
> Andy
>
> On Fri, Jan 18, 2013 at 2:46 PM, IETF Administrative Director <
> iad@ietf.org> wrote:
>
>> The IAOC has approved giving advance notice of the IETF Meeting hotel
>> venues for 2013 as an experiment.
>> Customarily such information has not been provided prior to registration
>> opening for that meeting, however
>> the IAOC is persuaded that it may be advantageous to attendees and wants
>> to determine whether there are any
>> unintended consequences.
>>
>> IETF 88 March 10 - 15
>> Location: Orlando, FL
>> Venue:  Caribe Royale
>>                 Registration now open:  <
>> https://www.ietf.org/meeting/86/index.html>
>>
>> IETF 87         July 28 - August 2
>> Location: Berlin, Germany
>> Venue:          InterContinental Berlin
>>                 (Note: Reservations to open approximately 12 weeks before
>> the meeting.)
>>
>> IETF 88 November 3-8
>> Location:       Vancouver, BC, Canada
>> Venue:          Hyatt Regency Vancouver
>>                 (Note: Reservations to open approximately 12 weeks before
>> the meeting.)
>>
>> Providing Venue information for 2013 is an experiment to determine
>> impacts to participants, Secretariat,
>> contracts, venue, and budget.  A decision will be made whether to
>> continue to provide Venue information
>> for 2014 after IETF 88.
>>
>> Ray
>> IETF Administrative Director
>>
>
>

--e89a8f646717c377b904d3ba5931
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<p dir=3D"ltr">I agree.=A0 What a great idea for those of us trying to plan=
 bringing family along or for after/before.</p>
<p dir=3D"ltr">Alia</p>
<div class=3D"gmail_quote">On Jan 20, 2013 9:53 AM, &quot;Andrew G. Malis&q=
uot; &lt;<a href=3D"mailto:agmalis@gmail.com">agmalis@gmail.com</a>&gt; wro=
te:<br type=3D"attribution"><blockquote class=3D"gmail_quote" style=3D"marg=
in:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir=3D"ltr"><div>Ray,<br><br>I haven&#39;t seen much (any?) discussion=
 of this announcement, perhaps a first for this group. Anyway, I think it&#=
39;s an excellent idea, it gives people a chance to plan their travel furth=
er out especially if they&#39;re thinking of bringing companions, families,=
 etc. Please continue this!<br>


<br>Thanks,<br></div>Andy<br><div><div class=3D"gmail_extra"><br><div class=
=3D"gmail_quote">On Fri, Jan 18, 2013 at 2:46 PM, IETF Administrative Direc=
tor <span dir=3D"ltr">&lt;<a href=3D"mailto:iad@ietf.org" target=3D"_blank"=
>iad@ietf.org</a>&gt;</span> wrote:<br>



<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">The IAOC has approved giving advance notice =
of the IETF Meeting hotel venues for 2013 as an experiment.<br>
Customarily such information has not been provided prior to registration op=
ening for that meeting, however<br>
the IAOC is persuaded that it may be advantageous to attendees and wants to=
 determine whether there are any<br>
unintended consequences.<br>
<br>
IETF 88 March 10 - 15<br>
Location: Orlando, FL<br>
Venue: =A0Caribe Royale<br>
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 Registration now open: =A0&lt;<a href=3D"ht=
tps://www.ietf.org/meeting/86/index.html" target=3D"_blank">https://www.iet=
f.org/meeting/86/index.html</a>&gt;<br>
<br>
IETF 87 =A0 =A0 =A0 =A0 July 28 - August 2<br>
Location: Berlin, Germany<br>
Venue: =A0 =A0 =A0 =A0 =A0InterContinental Berlin<br>
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 (Note: Reservations to open approximately 1=
2 weeks before the meeting.)<br>
<br>
IETF 88 November 3-8<br>
Location: =A0 =A0 =A0 Vancouver, BC, Canada<br>
Venue: =A0 =A0 =A0 =A0 =A0Hyatt Regency Vancouver<br>
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 (Note: Reservations to open approximately 1=
2 weeks before the meeting.)<br>
<br>
Providing Venue information for 2013 is an experiment to determine impacts =
to participants, Secretariat,<br>
contracts, venue, and budget. =A0A decision will be made whether to continu=
e to provide Venue information<br>
for 2014 after IETF 88.<br>
<br>
Ray<br>
<span><font color=3D"#888888">IETF Administrative Director<br>
</font></span></blockquote></div><br></div></div></div>
</blockquote></div>

--e89a8f646717c377b904d3ba5931--

From huubatwork@gmail.com  Sun Jan 20 14:50:08 2013
Return-Path: <huubatwork@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F098F21F84B9; Sun, 20 Jan 2013 14:50:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.374
X-Spam-Level: *
X-Spam-Status: No, score=1.374 tagged_above=-999 required=5 tests=[FH_HOST_EQ_D_D_D_D=0.765, RCVD_IN_PBL=0.509, RDNS_DYNAMIC=0.1]
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 NhBmQb2lhlQY; Sun, 20 Jan 2013 14:50:07 -0800 (PST)
Received: from mail-we0-x22a.google.com (mail-we0-x22a.google.com [IPv6:2a00:1450:400c:c03::22a]) by ietfa.amsl.com (Postfix) with ESMTP id BCCA221F84B2; Sun, 20 Jan 2013 14:49:59 -0800 (PST)
Received: by mail-we0-f170.google.com with SMTP id r1so1488843wey.29 for <multiple recipients>; Sun, 20 Jan 2013 14:49:59 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:disposition-notification-to:date:from :reply-to:user-agent:mime-version:to:cc:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=hLl5zhR7qvgLnbO3JNGmPAGnXGYd9lAHAd/JlDKjb4A=; b=HCjoYZz/4khq1RfN9egpCc7xoGzqz5/+IPXMVHelK0PSN91rHOnmd8EKmABdMpJTig XXOhKqHGcGwaQIPBOLJd/j2ptPj2iyen5eVhr/RJE9CeijGdQk5tBCzeLl7/TnmBNja/ RihMQOCWubFuRc9m4y5kVkzF+f56xnWllxCVmeue0Y9VxGw1yYAUaoLfz5U6fdPOyPv6 afrQoFb2Nazw3pNh5rmD4cVPCZQ7XYufrPmkDRYhJeIV6gISImR8wsWmplSLH33cg2m3 KBttHLAv7ScBvMntvRrAzZTTVmGZnffXNUfqzIuvkhAkDLElhZZIMg3GCsnTArn+t4Ta lB1g==
X-Received: by 10.194.174.196 with SMTP id bu4mr23172440wjc.35.1358722198979;  Sun, 20 Jan 2013 14:49:58 -0800 (PST)
Received: from McAsterix.local (dhcp-077-250-051-060.chello.nl. [77.250.51.60]) by mx.google.com with ESMTPS id u6sm15873728wif.2.2013.01.20.14.49.57 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 20 Jan 2013 14:49:58 -0800 (PST)
Message-ID: <50FC7495.7030202@gmail.com>
Date: Sun, 20 Jan 2013 23:49:57 +0100
From: Huub van Helvoort <huubatwork@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130107 Thunderbird/17.0.2
MIME-Version: 1.0
To: "Bitar, Nabil N" <nabil.n.bitar@verizon.com>
Subject: Re: [PWE3] Gen-ART review of draft-ietf-pwe3-mpls-eth-oam-iwk-06
References: <CD1C6C1E.75AFC%nabil.n.bitar@verizon.com>
In-Reply-To: <CD1C6C1E.75AFC%nabil.n.bitar@verizon.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Greg Mirsky <gregimirsky@gmail.com>, "sajassi@cisco.com" <sajassi@cisco.com>, "ietf@ietf.org" <ietf@ietf.org>, "gen-art@ietf.org" <gen-art@ietf.org>, "dinmohan@hotmail.com" <dinmohan@hotmail.com>, "pwe3@ietf.org" <pwe3@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: huubatwork@gmail.com
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 20 Jan 2013 22:50:08 -0000

Hello Nabil,

Considering your response:

> <NB> Please, see above. There are different contexts per above where the
> expanded terminology is applied. Are you suggesting still using Reverse
> Defect Indication per above where needed but not to abbreviate it? RDI as
> Remote Defect Indication part of Ethernet CFM is already there.

Would it be possible to remove the dependency on the context by
prepending the PW defect notifications by "P-". I.e.:

P-RDI  PW Reverse Defect Indication
P-FDI  PW Forward Defect Indication

And usinf RDI  Remote Defect Indication.

Regards, Huub.



From ron.even.tlv@gmail.com  Mon Jan 21 03:33:51 2013
Return-Path: <ron.even.tlv@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E4DE421F86D5; Mon, 21 Jan 2013 03:33:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.598
X-Spam-Level: 
X-Spam-Status: No, score=-3.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
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 7s3sSSK7Ikl5; Mon, 21 Jan 2013 03:33:50 -0800 (PST)
Received: from mail-ee0-f46.google.com (mail-ee0-f46.google.com [74.125.83.46]) by ietfa.amsl.com (Postfix) with ESMTP id A111221F84B2; Mon, 21 Jan 2013 03:33:49 -0800 (PST)
Received: by mail-ee0-f46.google.com with SMTP id e49so2758412eek.5 for <multiple recipients>; Mon, 21 Jan 2013 03:33:48 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:from:to:cc:subject:date:message-id:mime-version :content-type:x-mailer:thread-index:content-language; bh=NyTy95GvQ2FLA7tW+1rFuB1W0e6jvVhUs0b8SVRUHaI=; b=UzkSKPfGn8J3AUtFp+o+BBFMfQJdZTWU+CYtIxklW3aDLkgQTKfbOmvGLnbrJZOT3h 7Z9RhDYyBueCrlANeG3mZSrav3aGrhKlbE6D0cUBHbBpcs9azRgN2FBpRdNVev4lI3Jr TbvVijMheNxQPQPBrf/BZlt5H0fjqBazSPMixrvrvFktgLjsd3wIB9uGMm3ZaNj8pXCH ZpS1FZVrB0415zibQgKRKQ7AJfDR2CvZ9tT73bvyMBgcCNZmGhRP8TlYh5NDcNvQpnba Ya6FgUAIO2R4OMWWEtgVJ6zACF+tU6bX/YL11M8KZ+96THfnEyqGObsPc2zOrH8YFr1w No5A==
X-Received: by 10.14.223.131 with SMTP id v3mr2865696eep.28.1358768028536; Mon, 21 Jan 2013 03:33:48 -0800 (PST)
Received: from RoniE (bzq-79-181-179-229.red.bezeqint.net. [79.181.179.229]) by mx.google.com with ESMTPS id t44sm21899046eeo.2.2013.01.21.03.33.46 (version=TLSv1 cipher=RC4-SHA bits=128/128); Mon, 21 Jan 2013 03:33:47 -0800 (PST)
From: "Roni Even" <ron.even.tlv@gmail.com>
To: <draft-gp-obsolete-icmp-types-iana.all@tools.ietf.org>
Subject: Gen-ART LC review of draft-gp-obsolete-icmp-types-iana-01
Date: Mon, 21 Jan 2013 13:30:55 +0200
Message-ID: <015601cdf7ca$c8e2be90$5aa83bb0$@gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0157_01CDF7DB.8C6C2AD0"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: Ac33ysanZOhiFxAcTVKJ89I2PnxK7A==
Content-Language: en-us
Cc: gen-art@ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 21 Jan 2013 11:33:51 -0000

This is a multipart message in MIME format.

------=_NextPart_000_0157_01CDF7DB.8C6C2AD0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

I am the assigned Gen-ART reviewer for this draft. For background on
Gen-ART, please see the FAQ at
<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

Please resolve these comments along with any other Last Call comments you
may receive.

Document: draft-gp-obsolete-icmp-types-iana-01

Reviewer: Roni Even

Review Date:2013-1-21

IETF LC End Date: 2013-2-14

IESG Telechat date: 

 

Summary: This draft is ready for publication as Standard track RFC.

 

 

Major issues:

 

Minor issues:

 

 

Nits/editorial comments:

 


------=_NextPart_000_0157_01CDF7DB.8C6C2AD0
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><META =
HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 14 =
(filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin-top:0in;
	margin-right:0in;
	margin-bottom:10.0pt;
	margin-left:0in;
	line-height:115%;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.5pt;
	font-family:Consolas;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:Consolas;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><a =
name=3D"OLE_LINK1"></a><a name=3D"OLE_LINK2">I am the assigned Gen-ART =
reviewer for this draft. For background on Gen-ART, please see the FAQ =
at &lt;</a><a =
href=3D"http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq" =
target=3D"_blank">http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq=
</a>&gt;.<o:p></o:p></p><p class=3DMsoNormal>Please resolve these =
comments along with any other Last Call comments you may =
receive.<o:p></o:p></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Document: =
</span><span style=3D'font-family:"Courier =
New"'>draft-gp-obsolete-icmp-types-iana-01</span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p></o:p>=
</span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Reviewer: =
Roni Even<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Review =
Date:2013&#8211;1&#8211;21<o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>IETF LC =
End Date: 2013-2&#8211;14<o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>IESG =
Telechat date: <o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Summary: =
This draft is ready for publication as Standard track RFC</span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>.<o:p></o:p=
></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Major =
issues:<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Minor =
issues:<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoNormal>Nits/editorial =
comments:<o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></body></html>
------=_NextPart_000_0157_01CDF7DB.8C6C2AD0--


From Jeff.Hodges@KingsMountain.com  Mon Jan 21 19:12:02 2013
Return-Path: <Jeff.Hodges@KingsMountain.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7C35521F8588 for <ietf@ietfa.amsl.com>; Mon, 21 Jan 2013 19:12:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.265
X-Spam-Level: 
X-Spam-Status: No, score=-102.265 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, USER_IN_WHITELIST=-100]
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 EeygjaoGuLlh for <ietf@ietfa.amsl.com>; Mon, 21 Jan 2013 19:11:59 -0800 (PST)
Received: from oproxy5-pub.bluehost.com (oproxy5-pub.bluehost.com [67.222.38.55]) by ietfa.amsl.com (Postfix) with SMTP id C7B7921F85A2 for <ietf@ietf.org>; Mon, 21 Jan 2013 19:11:51 -0800 (PST)
Received: (qmail 27349 invoked by uid 0); 22 Jan 2013 03:11:27 -0000
Received: from unknown (HELO box514.bluehost.com) (74.220.219.114) by cpoproxy2.bluehost.com with SMTP; 22 Jan 2013 03:11:26 -0000
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=kingsmountain.com; s=default;  h=Content-Transfer-Encoding:Content-Type:Subject:CC:To:MIME-Version:From:Date:Message-ID; bh=yoBVQjVkIn6KnMFBJ7sv9gF6m0/KqEfO9qov+J5ANWQ=;  b=HB2hMVNSqDNBPY9m04qaCrxdjsPdzf5OPOIAI6jZ3VNBJ5whKH8OyuSl5NlbE/cRxQ8BXkbOG1OWSJzgxlIuCfrmmHWvvHT7RA6xnnOvHIMWyOBaAmjuy3y+F0GWFN+D;
Received: from [24.4.122.173] (port=35782 helo=[192.168.11.12]) by box514.bluehost.com with esmtpsa (TLSv1:CAMELLIA256-SHA:256) (Exim 4.80) (envelope-from <Jeff.Hodges@KingsMountain.com>) id 1TxUGj-0008Uo-JY; Mon, 21 Jan 2013 20:11:25 -0700
Message-ID: <50FE035C.4010808@KingsMountain.com>
Date: Mon, 21 Jan 2013 19:11:24 -0800
From: =JeffH <Jeff.Hodges@KingsMountain.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130106 Thunderbird/17.0.2
MIME-Version: 1.0
To: Ben Laurie <benl@google.com>
Subject: Re: LC comments on draft-laurie-pki-sunlight-05
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Identified-User: {11025:box514.bluehost.com:kingsmou:kingsmountain.com} {sentby:smtp auth 24.4.122.173 authed with jeff.hodges+kingsmountain.com}
Cc: Emilia Kasper <ekasper@google.com>, "therightkey@ietf.org" <therightkey@ietf.org>, IETF Discussion List <ietf@ietf.org>, Adam Langley <agl@google.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 22 Jan 2013 03:12:02 -0000

apologies for latency, many meetings and a conference in the last couple of weeks.

BenL replied:
 > On 1 January 2013 21:50, =JeffH <Jeff.Hodges@kingsmountain.com> wrote:

[ in the below discussion:

  "the spec", "this spec" refers to draft-laurie-pki-sunlight-05.

"TLS-CT client"  refers to a TLS client capable of processing CT information 
that is included in the TLS handshake in any of the specified manners.

"ok" means in general: "ok, will check this in next rev of the spec..".

]

<snip>
 >>
 >> comments on draft-laurie-pki-sunlight-05
 >>
 >> substantive comments (in somewhat arbitrary order)
 >> --------------------------------------------------
 >>

[ I demoted the comments wrt "JSON object" terminology and put them down at the 
end of this msg ]


 >> Also, the syntax for GETS isn't fully specified. Are the URL parameters to
 >> be encoded as (order independent) key-value pairs, or just as
 >> order-dependent values?  Which separator character is to be used between
 >> parameters? RFC3986 should be cited.
 >
 > RFC 3986 says nothing about parameter format, though

correct, it doesn't, and I wasn't trying to imply that it did, sorry.  I was 
just trying to say that RFC3986 should be cited in this spec because this spec 
normatively employs URLs, but perhaps referencing RFC2616 HTTP is better because 
it defines "http_URL".

 >  - is there a
 > standard reference for that? I've refereced HTML 4.01, but perhaps
 > there's a better one?

hm, AFAICT, there is not a standard for URI query component formating and thus 
parameter encoding, so this spec will have to explicitly specify something. 
Section 3.4 of RFC3986 gives allowed chars for the query component, but that's 
about it.

Have you mocked up code that parses the log client messages? If so, what query 
component syntax does it handle?


<snip>
 >> 2. "4. Client Messages" doesn't define error handling, i.e., responses to
 >> inputs the log service doesn't understand and/or is unable to parse, and/or
 >> have other errors. If the log service is to simply return a 4xx or 5xx error
 >> code, this should at least be mentioned.
 >
 > For now, I will specify 4xx/5xx. We may have more to say once we've
 > gained some experience.

Ok.


 >> 3. There appear to be three defined methods for TLS servers to provide TLS
 >> clients with CT data, in S3.2.  For this experiment, which approach is
 >> mandatory to implement for servers and clients?  Or, is it the case that
 >> participating TLS clients (ie web browsers etc) implement all three methods,
 >> and TLS servers can choose any of them?
 >
 > The latter.

That should be made very clear. Is the reason for doing so to obtain operational 
experience wrt the three defined methods such that they perhaps can be narrowed 
down in the future, or is the expectation that TLS-CT clients will need to 
support all three methods in perpetuity?

 >> 4. "Leaf Hash" as used in S4.5 appears to be formally undefined. It
 >> apparently would be:
 >>
 >>       SHA-256(0x00 || MerkleTreeLeaf)
 >>
 >> ..it should also be noted in S3.3.
 >
 > You are right.

:)


 >> 5. The recursive equations in S2.1 describe how to calculate a Merkle Tree
 >> Hash (MTH) (aka "root hash"), and thus as a side effect generate a Merkle
 >> Tree, for a given set of input data. However, there doesn't seem to be a
 >> defined algorithm (or even hints, really) for adding further inputs to an
 >> existing tree. Even though this may be reasonably left as an exercise for
 >> implementers, it should probably be discussed to some degree in the spec.
 >> E.g., note that leaf hashes are "frozen" and various interior tree node
 >> hashes become "frozen" as the tree grows. Is it not sub-optimal to employ
 >> the obvious default brute-force mechanism of rebuilding a tree entirely from
 >> scratch when new inputs are available?  Would not a recursive algorithm for
 >> adding new inputs to an existing tree be straightforward to provide?
 >
 > I dunno about straightforward.

yeah, agreed.


 > I'll think about it.

ok. At least providing some hints would be useful it seems.



 >> 6. Signed tree heads (STHs) are denoted in terms of "tree size" (number of
 >> entries), but SCTs are denoted in terms of a timestamp.  Should there be a
 >> log client message supporting the return of the nearest STH (and thus tree
 >> size) to a given timestamp?
 >
 > I'm not sure why? Any STH (that includes that SCT) will do.

Hm, it was sort of a gut feel that it might be useful, but perhaps not.

S5.2. Auditor says..

    A certificate accompanied by an SCT can be verified against any STH
    dated after the SCT timestamp + the Maximum Merge Delay by requesting
    a Merkle Audit Proof using Section 4.5.

S4.5 get-proof-by-hash stipulates tree_size as an input,  but
if a log auditor doesn't already have tree_size, then I suppose it first calls 
S4.3 get-sth, which will return a timestamp and a tree_size, which if generated 
max merge delay (MMD) after the SCT was gen'd, ought to be sufficient, yes?

I don't see in the spec where/how MMD is published.  Does MMD vary per log 
service?  The latter isn't stipulated in the spec it seems AFAICT ?



 >> 7. S3 paragraph 2 states that "TLS clients MUST reject certificates that do
 >> not have a valid SCT for the end-entity certificate" (i.e., hard-fail).
 >> Presummably this requirement is only for TLS clients participating in the CT
 >> experiment and that understand this protocol.
 >
 > Of course - what other way could it be? In other words, all RFCs can
 > only say what implementations that conform with them do.
 >
 >> This, or whatever the
 >> requirement actually is, should be further explained.

I guess what I was getting at is that CT-conformant TLS clients should be 
differentiated from non-CT-conformant ones. Stipulating a name for CT-conformant 
TLS clients would clarify this (seems to me), e.g. "TLS-CT client" or something 
similar.


 >> For example, does the simple presence of SCT(s) in the TLS handshake serve
 >> to signal to participating TLS clients that hard-fail is expected if there
 >> are any issues with CT validation?
 >
 > We are not saying what action a client should take when it rejects a
 > certificate, as is, I believe the usual practice.

Ok.



 >> 8. The spec implies, but doesn't clearly describe, especially in S3.1, that
 >> the hashes are "labels" for tree entries, and that given a leaf hash, the
 >> log implementation should be able to look up and present the LogEntry data
 >> defined in that section.
 >
 > We actually only require an entry to be retrievable by hash (in
 > effect) for the message in 4.7, which we (at least currently) label as
 > a debugging message - so I am not sure that logs really are required
 > to be able to do that - certainly the system would work fine if they
 > couldn't, I believe (other than being unable to provide the debugging
 > data).

I think what I was getting at was that this is stated at the end of S3.2..

    The leaves of the Merkle Tree are the hashes of the corresponding
    "MerkleTreeLeaf" structures.

..but it is somewhat confusing because (abstractly) each leaf also contains (or 
has a reference to) the LogEntry data (that's defined back in S3.1)  ...if I 
understand this correctly.



<snip>
 >>
 >> Various overall comments:
 >> --------------------------
 >>
 >> O-1. The phrase "this experiment" is used in S2.1 -- should describing this
 >> as an experiment be more explicitly done in the abstract and introduction
 >> sections?  What about the document title?
 >
 > The plan is this will be an Experimental RFC, which seems clear enough to me?

well, lots of people don't perceive the difference between the various RFC 
tracks, and I'd be inclined to make it abundantly pedantically clear that this 
spec is documenting a particular actual experiment (modulo what the sponsoring 
AD thinks/advises (hi Stephen :) )


<snip>
 >> O-3. The bare term "client" is used in various places where either the term
 >> "log client" or "TLS client" is being implied -- these should be made
 >> explicit. Also the roles of log clients and TLS clients should be more
 >> thoroughly presented/explored, in part because they can intersect.
 >
 > Section 5 "Clients" is an attempt to document the various client
 > roles, one or more of which may be embodied by any particular client
 > implementation, rather than try to deal with this intersection.
 >
 > I have gone over mentions of "client" elsewhere to try to deal with
 > your point, though. Sometimes it just means "any client" so not all
 > instances have been changed.

ok.


 >> O-4. These things seem to be duplicate names:
 >>
 >>      "root hash" and "Merkle Tree Hash (MTH)"
 >
 > Yes,
 >
 >>
 >>      "Tree Head Signature" and "Signed Tree Head (STH)"
 >
 > These are not the same - you are probably confused by the
 > digitally-signed struct, which is only used as input for a signature
 > and never appears in its own right. However, we haven't been super
 > clear about what's going on here and I've tried to clean that up.

ok.



<snip>
 >> O-6. I found the "history tree" paper (aka "[1]", cited here as
 >> [CrosbyWallach]) helpful in understanding how such trees are constructed,
 >> perhaps it should be more prominently mentioned. Plus the differences
 >> between the two algorithms should perhaps be more explicitly mentioned. E.g.
 >> in [CrosbyWallach] version-n tree stores n+1 inputs, while in CT a version-n
 >> tree (D[n]) stores n inputs.
 >>
 >> [CrosbyWallach]  <http://tamperevident.cs.rice.edu/Logging.html>
 >>
 >>
 >> O-7. The note mentioning "dummy leaves" in [CrosbyWallach] seems misleading.
 >> The difference is AFAICT that in [CrosbyWallach] all nodes at layer 1 and
 >> above (leaf entries are at layer 0), are "interior nodes", and have hashes
 >> created using 0x01. Thus in a tree with an odd number of entries (ie leaf
 >> nodes at layer 0), there will be one leaf node under an interior node having
 >> only that one child. It's not that there is a "dummy leaf", it's that such
 >> an interior node's hash is constructed from just one child rather than two.
 >
 > Not sure I really agree with this, but in any case I have reworded it
 > slightly. I've also changed the reference to be a "proper" one, shown
 > at the end of the I-D.

ok.


 >> While in CT, if the input set is an odd number of entries, then the hash of
 >> the final single leaf is at layer 1, and is calculated as a leaf hash using
 >> 0x00. Thus CT "interior nodes" always have two children, but if the tree has
 >> an odd number of entries, the rightmost hash at layer 1 ("j" in the "binary
 >> Merkle tree with 7 leaves" figure) is a leaf node hash rather than an
 >> interior node hash.
 >>
 >>
 >> O-8. [CrosbyWallach] discusses auditing and gossiping and could be cited as
 >> a source for further discussion on those topics.
 >>
 >>
 >> O-9. The notion of "commitments" isn't well defined, and where "add a
 >> commitment to D[k:n]"  couldn't  "add an interior/intermediate node to
 >> D[k:n}"  be used?
 >>
 >> Is not the term "commitment" used in [CrosbyWallach] equivalent to the
 >> sha256_root_hash (an STH component) in the spec?
 >>
 >> [CrosbyWallach] uses the term "interior node(s)" while the spec uses
 >> "intermediate nodes" (in one place).
 >
 > CT is not actually derived from [CrosbyWallach], we just mention it as
 > a useful reference.

yeah, it is useful, it would've been much harder to figure out the spec without 
it. Is there an existing paper that the spec is based more closely on?

The differences between the spec and [CrosbyWallach] doesn't seem to be that 
large, and so if there aren't more closely matching paper(s) to cite (?), it may 
be worth summarizing the differences between the spec and  [CrosbyWallach] e.g. 
in an appendix.


 > "commitment" is a term of cryptographic art.

so it is, but its definitions in the literature seem to vary somewhat depending 
on context.  IIUC, the spec uses "commitment" to refer to the hash labels of 
intermediate nodes ('interior nodes' in [CrosbyWallach]) as well as the root 
hash, yes?

In S2.1.1, where it says..

          We prove that the left subtree entries D[0:k] are consistent
    and add a commitment to D[k:n]:

..it's not clear just what "add a commitment" means. add it (an 
intermediate-node hash?) to the list of hashes that the recursive algorthm is 
constructing?

Overall, I'm finding S2.1.1 pretty difficult to parse and sort out.

E.g., it isn't clear to me how/why/when the apparently boolean 3d parameter of 
SUBPROOF is either true or false, and whether there's an implied "if b then ... 
else ..."  in there somewhere.



 >> O-10. The recursive algorithms in S2 are dense and take effort to work
 >> through, perhaps adding simplistic example code (in an appendix) which
 >> implements, and/or actually working through the algorithms to arrive at some
 >> of the audit paths and consistency proofs in S2.1.3, would be helpful.
 >
 > We have actual working code - would a reference to that be better?

I don't know if it would be better (I've compiled it and am poking through the 
code). I sorta think pseudo code in an appendix that would generate the trees in 
S2.1.3. would be helpful.


 >> I desk-checked S2.1, and it seems correct, but didn't do S2.1.1 or S2.1.2.
 >> The examples in S2.1.3 appear nominally correct but I didn't desk check
 >> them.
 >>
 >> Should there be a reference to
 >> <https://code.google.com/p/certificate-transparency/> ?   And/or a note
 >> regarding available code and to contact the authors for more information?
 >> (as is done in RFC 2154)
 >
 > I couldn't find such a thing in RFC 2154.

see end of S2 on page 4 of RFC2154.


 >  My only concern about such a
 > reference is whether it would live as long as the RFC does :-)

hence the desire to have pseudo code in spec :)


 >> O-11. S3.3 should mention the Maximum Merge Delay MMD where it says
 >> "periodically append". Also, in S3.3, "Signed Merkle Tree Update" should be
 >> a "Tree Head Signature" aka "signed tree head (STH)"?
 >
 > I just removed that, as it is immediately repeated in the next section.

Ok.


 >> O-12. S3.3, S3.4, S4.4, S4.5, and S4.7 mention the notion of logs
 >> "publishing" STHs, but no mechanism is described for explicitly
 >> "publishing". Is this meant to mean only that a "published" STH is available
 >> for retrieval by clients using the "Retrieve Latest Signed Tree Head" log
 >> client message?
 >>
 >> Or, would there be a use case, eg introducing an existing log service to a
 >> log monitor, for requesting (or being able to enumerate) all published STHs
 >> from the log?
 >
 > I don't believe there is: the latest STH tells you everything you need
 > to know at that point. I have removed mention of publishing.

ok.



<snip>
 >>
 >>
 >> O-14. Detailed comments on S2...
 >> ------------------------------
 >>
 >>> 2. Cryptographic components
 >>>
 >>>
 >>> 2.1. Merkle Hash Trees
 >>>
 >>>
 >>>    Logs use a binary Merkle hash tree for efficient auditing.  The
 >>>    hashing algorithm is SHA-256 (note that this is fixed for this
 >>>    experiment but it is anticipated that each log would be able to
 >>>    specify a hash algorithm).  The input to the Merkle tree hash is a
 >>>    list of data entries; these entries will be hashed to form the leaves
 >>>    of the Merkle hash tree.  The output is a single 32-byte root hash.
 >>>    Given an ordered list of n inputs, D[n] = {d(0), d(1), ..., d(n-1)},
 >>>    the Merkle Tree Hash (MTH) is thus defined as follows:
 >>>
 >>>    The hash of an empty list is the hash of an empty string:
 >>>
 >>>    MTH({}) = SHA-256().
 >>
 >>
 >> This MTH({}) construct doesn't appear to be used anywhere else in the spec
 >> (yes?), and so does it really need mentioning?
 >
 > If it is not defined, then we cannot represent an empty tree.

yeah, I agree from a mathematical completeness perspective.  but I still found 
it sort of distracting in that I don't know that it's actually germane from an 
implementor's perspective. maybe it is because


 >>>    The hash of a list with one entry is:
 >>>
 >>>    MTH({d(0)}) = SHA-256(0x00 || d(0)).
 >>
 >>
 >> The immediately above equation is for leaf entries (yes?),
 >
 > Yes.
 >
 >> where in this
 >> notation n = 1, perhaps it should be stated explicitly:
 >>
 >>     When n = 1, a leaf entry is denoted, and D[1] = {d(0)}. The leaf hash
 >>     (LH) for a leaf entry is calculated as:
 >>
 >>     MTH(D[1]) = LH(D[1]) = SHA-256( 0x00 || d(0) )
 >
 > Ugh. LH(D[1]) seems meaningless to me. A leaf hash is always of a "1
 > entry tree".

yeah, for those who have grokked this stuff. for others it isn't immediately 
obvious. also,  the above comment was motivated in part due to the missing 
formal definition for "Leaf Hash" noted in item (4) above. even if the LH(D[1]) 
notation isn't used, some additional prose along the lines suggested above would 
be helpful to less initiated readers imv.



 >>>    For n > 1, let k be the largest power of two smaller than n.
 >>
 >>
 >> The unqualified "power of two" phrase is arguably ambiguous.
 >
 > It is?

uh, yeah.

but "let k be a number which is the largest power of two such that..." isn't.


 >> Suggested rephrase for this where it occurs throughout section 2..
 >>
 >>     For n > 1, let k be a number which is the largest power of two
 >>     such that k = 2^i, 0 <= i < n, and k < n.
 >
 > If we're going to go down that path, then it should say:
 >
 > For n > 1, let k be the largest number such that k = 2^i and k < n.
 >
 > or
 >
 > For n > 1, let k = 2^i s.t. k < n and 2k >= n.
 >
 > surely?

well, yes (i prefer the former), but i think it's also important to explicitly 
state 0 <= i < n


 >
 >>>    The Merkle Tree Hash of an n-element list D[n] is then defined
 >>>    recursively as
 >>
 >>
 >> The above statement applies to the combination of the n = 1 equation above
 >> and the equation below, and so should perhaps be moved up above the n = 1
 >> equation.
 >
 > ? It says n > 1, so doesn't apply to n = 1?

oh yeah huh.

in any case, I found the prose separation of the "list with one entry" and the 
"n > 1" case to be confusing because the former is part of the recursive 
definition of MTH(), yes?


 >>>    MTH(D[n]) = SHA-256(0x01 || MTH(D[0:k]) || MTH(D[k:n])),
 >>>
 >>>    where || is concatenation and D[k1:k2] denotes the length (k2 - k1)
 >>>    list {d(k1), d(k1+1),..., d(k2-1)}.
 >>
 >>
 >> The above phrase doesn't parse well and is somewhat ambiguous, here it is
 >> extracted for clarity:
 >>
 >>  "D[k1:k2] denotes the length (k2 - k1) list {d(k1), d(k1+1),..., d(k2-1)}"
 >>
 >>
 >> How about rephrasing it along the lines of this:
 >>
 >>     D[k1:k2] denotes a sublist {d(k1), d(k1+1),..., d(k2-1)}, having
 >>     (k2 - k1) elements, of the original input list D[n]. When (k2 - k1)
 >>     is 1, a leaf hash is calculated.
 >
 > We tried lots of different ways of saying this and they were all a
 > little messy. Yours mixes concerns and is rather verbose, so not
 > convinced it is actually an improvement.

well, the way it's presently said in the spec is (to me) pretty darn hard to 
understand.

which concerns are missed in the suggested reformulation?  I tend to think 
concocting something not so terse would be a service to the reader/implementer.

 >
 >>
 >>
 >>                                          (Note that the hash calculation
 >>>
 >>>    for leaves and nodes differ.  This domain separation is required to
 >>>    give second preimage resistance.)
 >>>
 >>>    Note that we do not require the length of the input list to be a
 >>>    power of two.  The resulting Merkle tree may thus not be balanced,
 >>>    however, its shape is uniquely determined by the number of leaves.
 >>>    [This Merkle tree is essentially the same as the history tree [1]
 >>>    proposal, except our definition omits dummy leaves.]
 >>
 >>
 >> I suggest re-writing the first above Note along with the next paragraph in
 >> light of all above comments on S2 and [CrosbyWallach].
 >
 > It was already partly rewritten as a result of above comments, so
 > let's see how you like the next version?

ok.



 >
 >> O-15.  Some comments on S3:
 >> ------------------------------------
 >>
 >>> 3. Log Format
 >>
 >>
 >> this section isn't just about "format" of log - it's also about log
 >> behavior/operation
 >
 > Good point.
 >
 >>
 >>
 >>>    Anyone can submit certificates to certificate logs for public
 >>>    auditing, however, since certificates will not be accepted by clients
 >>>    unless logged, it is expected that certificate owners or their CAs
 >>>    will usually submit them.  A log is a single, ever-growing, append-
 >>>    only Merkle Tree of such certificates.
 >>>
 >>>    When a valid certificate is submitted to a log, the log MUST
 >>>    immediately return a Signed Certificate Timestamp (SCT).  The SCT is
 >>>    the log's promise to incorporate the certificate in the Merkle Tree
 >>>    within a fixed amount of time known as the Maximum Merge Delay (MMD).
 >>>    If the log has previously seen the certificate, it MAY return the
 >>>    same SCT as it returned before.
 >>
 >>
 >> What if the submitted end entity cert is the same, but the certificate chain
 >> is different (yet valid)?
 >
 > The purpose of the chain is to:
 >
 > a) Prevent spam, and
 >
 > b) Identify who to blame in the event of a misissue.
 >
 > Alternate chains presumably don't actually change the direct blame,
 > and so I see no reason to do other than what the I-D says - i.e.
 > return the same SCT as before.

ok. tho i wonder if there's any value in caching the alternate chain or the new 
portions thereof.



 >>>                                     TLS servers MUST present an SCT from
 >>>    one or more logs to the client together with the certificate.  TLS
 >>>    clients MUST reject certificates that do not have a valid SCT for the
 >>>    end-entity certificate.
 >>
 >>
 >> [ see comment (7) above ]
 >>
 >>
 >>>    Periodically, each log appends all its new entries to the Merkle
 >>>    Tree, and signs the root of the tree.  Clients and auditors can thus
 >>
 >>
 >> Should "Clients and auditors" actually be "TLS Clients, log monitors, and
 >> log auditors" ?
 >
 > Bearing in mind that these are actually roles rather than distinct
 > entities, it should probably just say "auditors".

I dunno, that may loose some readers.  in any case, the distinction between 
roles and distinct entities should probably be mentioned/discussed e.g. in the 
Introduction or thereabouts.


<snip>

 >>> 3.1. Log Entries
 >>>
 >>>
 >>>    Anyone can submit a certificate to any log.  In order to enable
 >>>    attribution of each logged certificate to its issuer, the log SHALL
 >>>    publish a list of acceptable root certificates (this list might
 >>>    usefully be the union of root certificates trusted by major browser
 >>>    vendors).  Each submitted certificate MUST be accompanied by all
 >>>    additional certificates required to verify the certificate chain up
 >>>    to an accepted root certificate.  The root certificate itself MAY be
 >>>    omitted from this list.
 >>>
 >>>    Alternatively, (root as well as intermediate) Certificate Authorities
 >>
 >>
 >> Additionally?  which manner is the experiment going to operate, or is it TBD
 >> ?
 >
 > Not sure what you mean? The log will accept either type of submission.

oh, sorry, I meant s/Alternatively/Additionally/



 >>>    may submit a certificate to logs prior to issuance.  To do so, a
 >>>    Certificate Authority constructs a Precertificate by adding a special
 >>>    critical poison extension (OID 1.3.6.1.4.1.11129.2.4.3, whose
 >>>    extnValue OCTET STRING contains ASN.1 NULL data (0x05 0x00)) to the
 >>>    leaf TBSCertificate (this extension is to ensure that the
 >>
 >>
 >> leaf == end entity ?
 >>
 >> s/leaf certificate/end entity certificate/g   ?
 >
 > Yes.
 >
 >>>    Precertificate cannot be validated by a standard X.509v3 client), and
 >>>    signing the resulting TBSCertificate [RFC5280] with either
 >>
 >>
 >>
 >>>    o  a special-purpose (Extended Key Usage: Certificate Transparency,
 >>>       OID 1.3.6.1.4.1.11129.2.4.4) Precertificate Signing Certificate.
 >>>       The Precertificate Signing Certificate MUST be certified by the CA
 >>>       certificate that will ultimately sign the leaf TBSCertificate
 >>
 >>
 >> "sign the leaf TBSCertificate"  means to say "sign the actual
 >> issued-to-the-customer TBSCertificate component of the End Entity
 >> certificate" ?
 >
 > Well, it means something like that, I have added some words.

ok


 >>>       (note that the log may relax standard validation rules to allow
 >>>       this, so long as the final signed certificate will be valid),
 >>>
 >>>    o  or, the CA certificate that will sign the final certificate.
 >>
 >>
 >> "final certificate" is the "issued-to-the-customer End Entity certificate" ?
 >
 > I have changed this to "issued certificate".

ok, tho should it be "issued end entity certificate" ?



 >>>    Structure of the Signed Certificate Timestamp:
 >>
 >>
 >> The SCT discussion here should probably be its own subsection.
 >
 > OK.
 >
 >>
 >>
 >>>
 >>>        enum { certificate_timestamp(0), tree_hash(1), 255 }
 >>>          SignatureType;
 >>>
 >>>        enum { v1(0), 255 }
 >>>          Version;
 >>
 >>>
 >>>
 >>>          struct {
 >>>              opaque key_id[32];
 >>>          } LogID;
 >>>
 >>>          opaque CtExtensions<0..2^16-1>;
 >>>
 >>>    "key_id" is the SHA-256 hash of the log's public key, calculated over
 >>>    the DER encoding of the key represented as SubjectPublicKeyInfo.
 >>
 >>
 >> I'd place the above paragraph regarding "key_id" down below the
 >> SignedCertificateTimestamp definition.
 >>
 >>
 >>>        struct {
 >>>            Version sct_version;
 >>>            LogID id;
 >>>            uint64 timestamp;
 >>>            CtExtensions extensions;
 >>>            digitally-signed struct {
 >>>                Version sct_version;
 >>>                SignatureType signature_type = certificate_timestamp;
 >>>                uint64 timestamp;
 >>>                LogEntryType entry_type;
 >>>                select(entry_type) {
 >>>                    case x509_entry: ASN.1Cert;
 >>>                    case precert_entry: ASN.1Cert;
 >>>                } signed_entry;
 >>>               CtExtensions extensions;
 >>>            };
 >>>        } SignedCertificateTimestamp;
 >>>
 >>>    The encoding of the digitally-signed element is defined in [RFC5246].
 >>
 >>
 >> I would add a few words here summarizing that what happens here is that the
 >> digitally-signed struct here is replaced in the actual serialized binary
 >> structure by a struct DigitallySigned and cross-ref to S4.7 of RFC5246.
 >
 > Except it isn't :-)

ok, then I don't understand what's going on here.  RFC5246 S4.7 sez...

    A digitally-signed element is encoded as a struct DigitallySigned:

       struct {
          SignatureAndHashAlgorithm algorithm;
          opaque signature<0..2^16-1>;
       } DigitallySigned;


..and I take the "digitally-signed struct" within SignedCertificateTimestamp to 
be a "digitally-signed element".  Please help me understand what am I missing?


 >
 > And we already reference RFC5246.

we (IETF spec editors/authors) reasonably often reference particular sections of 
other RFCs in order to aid the reader. this is a sufficiently subtle construct 
to merit such an explicit ref (to S4.7 of RFC5246 if I'm correct) in my view.


<snip>

 >> O-15.  Some comments on S4:
 >> ---------------------------
 >>
 >>
 >>> 4. Client Messages
 >>
 >>
 >> title should be "Log Client Messages" ?
 >
 > Yes.
 >
 >>>    Messages are sent as HTTPS GET or POST requests.  Parameters for
 >>>    POSTs and all responses are encoded as JSON objects.  Parameters for
 >>
 >>
 >> s/JSON objects/JSON texts/
 >
 > I don't agree with this. See above.

see below.


<snip>


 >>>       inclusion in the TLS handshake are not required to verify it, we
 >>
 >>
 >> s/the TLS handshake/subsequent TLS handshakes/   ?



 >>>       do not assume they know the ID of the log.
 >>>
 >>>    timestamp  The SCT timestamp, in decimal.
 >>>
 >>>    extensions  An opaque type for future expansion.  It is likely that
 >>>       not all participants will need to understand data in this field.
 >>>       Logs should set this to the empty string.  Clients should decode
 >>>       the base64 encoded data and include it in the SCT.
 >>>
 >>>    signature  The SCT signature, base64 encoded.
 >>
 >>
 >> "The SCT signature" means a SignedCertificateTimestamp structure ?
 >
 > No, the signature that is a component of the structure.

Oh, you mean this..

            digitally-signed struct {
                Version sct_version;
                SignatureType signature_type = certificate_timestamp;
                uint64 timestamp;
                LogEntryType entry_type;
                select(entry_type) {
                    case x509_entry: ASN.1Cert;
                    case precert_entry: ASN.1Cert;
                } signed_entry;
               CtExtensions extensions;
            };

..which automagically transforms to

       struct {
          SignatureAndHashAlgorithm algorithm;
          opaque signature<0..2^16-1>;
       } DigitallySigned;

..if I understand RFC5246 correctly?  If not, please direct us to the correct 
formulation :)


 >>>    If the "sct_version" is not v1, then a v1 client may be unable to
 >>>    verify the signature.  It MUST NOT construe this as an error.  [Note:
 >>>    log clients don't need to be able to verify this structure, only TLS
 >>>    clients do - if we were to serve the structure binary, then we could
 >>>    completely change it without requiring an upgrade to v1 clients].
 >>
 >>
 >> Does this "if we were to serve the structure binary...."  statement mean to
 >> say that since v1 log clients don't need to be able to verify the SCT
 >> signature over the various returned data items, that this operation could
 >> instead return an opaque binary blob?
 >
 > Indeed.

Ok, then perhaps it could use some added text to more explicitly state that?



 >
 >> O-16.  Some comments on S5:
 >> ---------------------------
 >>
 >>
 >>> 5. Clients
 >>>
 >>>
 >>>    There are various different functions clients of logs might perform.
 >>
 >>
 >> Perhaps this section should be entitled "Log Client Roles" ?
 >
 > Since you persuaded me to include TLS clients, no :-)

ok.


 >
 >> this section doesn't mention the role of a (CA) log client that submits
 >> "certs and cert chains" to logs. Even though the latter role is mentioned
 >> elsewhere in the spec it should perhaps be mentioned here also.
 >
 > OK.

ok :)



 >>> 5.1. Monitor
 >>>
 >>>
 >>>    Monitors watch logs and check that they behave correctly.  They also
 >>>    watch for certificates of interest.
 >>
 >>
 >> "Monitor" should be "Log Monitor" ?
 >
 > There's no other kind of monitor :-)

in the explicit context of this spec, agreed.  but in general I favor/advocate 
creation and use of more fully descriptive words/phrases so at least one is more 
likely to find them with a search when you're wondering what sort of "monitor" 
someone down the road is yammering on about.

[ I would add a terminology section to the spec ]

 >>> 5.2. Auditor
 >>>
 >>>
 >>>    Auditors take partial information about a log as input and verify
 >>>    that this information is consistent with other partial information
 >>>    they have.  An auditor might be an integral component of a TLS
 >>>    client, it might be a standalone service or it might be a secondary
 >>>    function of a monitor.
 >>
 >>
 >> "Auditor" should be "Log Auditor" ?
 >
 > And there's no other kind of auditor.

see above :)

e.g. in the overall webpki world, there /are/ other forms of auditors (e.g. the 
ones noted here <http://wiki.cacert.org/Audit/CriteriaAlphabetSoup>) and so it's 
worth using a more descriptive term, imv.


 >>> 8. Efficiency Considerations
 >>>
 >>>
 >>>    The Merkle tree design serves the purpose of keeping communication
 >>>    overhead low.
 >>>
 >>>    Auditing logs for integrity does not require third parties to
 >>>    maintain a copy of each entire log.  The Signed Tree Heads can be
 >>>    updated as new entries become available, without recomputing entire
 >>>    trees.  Third party auditors need only fetch the Merkle consistency
 >>>    proofs against a log's existing STH to efficiently verify the append-
 >>>    only property of updates to their Merkle Trees, without auditing the
 >>>    entire tree.
 >>
 >>
 >> The above could be explained in more detail, and S5.1 should be
 >> cross-referenced. Is the last sentence above essentially a summary of step
 >> #8 in S5.1? Or are there differences?
 >
 > It is a summary of 5.1

ok, but it'd be helpful to state that and crossref S5.1.


wrt he JSON stuff...

 >> 1. The client messages S4 don't explicitly lay out the syntax for request
 >> messages or responses. E.g., for S4.1 "Add Chain to Log", is the input a
 >> stand-alone JSON text array, or a JSON text object containing a JSON text
 >> array?
 >>
 >> The term "JSON object" as used in the first paragraph is ambiguous and
 >> perhaps what is mean is simply "JSON texts" or "JSON text objects or JSON
 >> text arrays". RFC4627 clearly defines "JSON text", and should be cited. But
 >> RFC4627 is a little ambiguous itself regarding "JSON object" and so I
 >> suggest these definitions:
 >>
 >>     JSON text object:   A JSON text matching the "object" ABNF production
 >>        in Section 2.2 of [RFC4627].
 >>
 >>     JSON text array:   A JSON text matching the "array" ABNF production
 >>        in Section 2.3 of [RFC4627].
 >
 > I agree that RFC 4627 should be cited and I will correct that.

ok.

 > The
 > rest of this confuses me: JSON is a textual representation of
 > structured data, as it states in the RFC. It defines an object quite
 > clearly
 >
 > " An object is an unordered collection of zero or more name/value
 >    pairs, where a name is a string and a value is a string, number,
 >    boolean, null, object, or array."

well, yes, but that's in just the introduction of RFC 4627.

 > Defining a "JSON text object" seems pointless to me - clearly a JSON
 > object is an object as defined by JSON, surely? Introducing another
 > term seems like to add confusion rather than remove it.

note that "JSON text" is very explicitly defined in RFC4627 at the beginning of 
S2 as..

    A JSON text is a sequence of tokens.  The set of tokens includes six
    structural characters, strings, numbers, and three literal names.

    A JSON text is a serialized object or array.

       JSON-text = object / array

the reason I flagged this issue is that I just recently reviewed a different 
internet-draft where they'd confused a JSON object -- in the sense of a JSON 
text matching the object production of S2.2 RFC4627 -- and a "JSON object" in 
the sense of an abstract programming construct, and they didn't understand that 
in the protocol on-the-wire world a JSON object /is a string/  (i.e. it is 
string-serialized according to the grammar of RFC4627).

It seems the term "JSON object" is ambiguous depending on whether you're looking 
at it from a programming perspective or an on-the-wire protocol perspective (eg 
see <http://www.json.org/javadoc/org/json/JSONObject.html> which talks about 
"internal form" and "external form" (ugh)), hence my (perhaps feeble) attempt to 
invent a more explicit term for the on-the-wire protocol form.

So maybe a more palatable definition would be..

   JSON object: A JSON text matching the "object" ABNF production
                in Section 2.2 of [RFC4627].

?


---
end









From wjordan129@gmail.com  Mon Jan 21 20:57:27 2013
Return-Path: <wjordan129@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3CBC711E80A5 for <ietf@ietfa.amsl.com>; Mon, 21 Jan 2013 20:57:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.598
X-Spam-Level: 
X-Spam-Status: No, score=-3.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
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 S+JjEYfmm-hB for <ietf@ietfa.amsl.com>; Mon, 21 Jan 2013 20:57:26 -0800 (PST)
Received: from mail-ob0-f174.google.com (mail-ob0-f174.google.com [209.85.214.174]) by ietfa.amsl.com (Postfix) with ESMTP id 8336D11E8097 for <ietf@ietf.org>; Mon, 21 Jan 2013 20:57:23 -0800 (PST)
Received: by mail-ob0-f174.google.com with SMTP id 16so719249obc.5 for <ietf@ietf.org>; Mon, 21 Jan 2013 20:57:23 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type; bh=RbqsEscOanRZmmkpTcw954D7jJy4m7QGoSPDDVy5C+8=; b=PSAIotA4khAJ7cGKfWspIHzVwfQ+slrJaP6kufp4xlkq3KEH6b6oj7e19YAVngApiM EmkZCX+JXoxPLe5AFH/34rKxKtSG3o0+hjoH4qFhdUJJKp35WQlEg9PdhgqtFCjfk+2/ z01O1iQ7+Hlmzzes/cicTwuXyOu4Lb2ikNXxVdkYtjK8HD7A+IrpMI9V/Zcm+dnj24Jy uQttyJ6nb9wMMIV4mFvlCc4LIdBiNcejmpz3hF8DfdTPpdVE1F7F1NghJuBRs1QRI4WK fNDjbQyL2iQrb+1SQAQDYZMqAONc51swBpI2dubbgcinBEPsfYmnAFwZhUXbgOU8e+10 /TIw==
MIME-Version: 1.0
X-Received: by 10.60.20.167 with SMTP id o7mr15664343oee.126.1358830643060; Mon, 21 Jan 2013 20:57:23 -0800 (PST)
Received: by 10.76.154.234 with HTTP; Mon, 21 Jan 2013 20:57:22 -0800 (PST)
Date: Mon, 21 Jan 2013 23:57:22 -0500
Message-ID: <CAPJ9He0dOttM+DmpUt9MzfWEXcs+tbpJJy4Z+usoRroyAdzJbA@mail.gmail.com>
Subject: A modest proposal
From: William Jordan <wjordan129@gmail.com>
To: ietf@ietf.org
Content-Type: multipart/alternative; boundary=e89a8ff1c6eeca209804d3d969ad
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 22 Jan 2013 05:01:38 -0000

--e89a8ff1c6eeca209804d3d969ad
Content-Type: text/plain; charset=ISO-8859-1

I've recent had to write a program to interface with a SIP lync server and
in doing so have had to code to several rfcs.  After reading and dealing
with implementation of the various rfcs I have read I have come up with
what I consider "A modest proposal" to fix some of the problems I've seen
with implementing a rfc.  I think anyone who writes a rfc should have to
provide a working ANSI/C or GNU/C implementation of the rfc in question.
 Specifically, I have worked with the SIP rfc (rfc 3261) and have come to
the conclusion that whoever wrote the rfc has never coded a day in their
life.  Whoever thought it was a good idea to allow multiple ways of doing
the same exact thing would hopefully be deterred by actually writing code
to do it.  I think a suitable punishment for those people would be to write
each way of writing a from header on a blackboard 100 times... this would
actually be less of the pain they've cause by making each writer of a SIP
stack handle each possible way of doing things.

Anyways, that is my modest proposal, please respond or I will be forced to
reply every day to this mailing list on each and every way the SIP spec
sucks one email at a time.  FYI I'm not sure if GNU/C is the correct
acronym, maybe its POSIX/C.

Regards,
Bill

--e89a8ff1c6eeca209804d3d969ad
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

I&#39;ve recent had to write a program to interface with a SIP lync server =
and in doing so have had to code to several rfcs. =A0After reading and deal=
ing with implementation of the various rfcs I have read I have come up with=
 what I consider &quot;A modest proposal&quot; to fix some of the problems =
I&#39;ve seen with implementing a rfc. =A0I think anyone who writes a rfc s=
hould have to provide a working ANSI/C or GNU/C implementation of the rfc i=
n question. =A0Specifically, I have worked with the SIP rfc (rfc 3261) and =
have come to the conclusion that whoever wrote the rfc has never coded a da=
y in their life. =A0Whoever thought it was a good idea to allow multiple wa=
ys of doing the same exact thing would hopefully be deterred by actually wr=
iting code to do it. =A0I think a suitable punishment for those people woul=
d be to write each way of writing a from header on a blackboard 100 times..=
. this would actually be less of the pain they&#39;ve cause by making each =
writer of a SIP stack handle each possible way of doing things.<div>
<br></div><div>Anyways, that is my modest proposal, please respond or I wil=
l be forced to reply every day to this mailing list on each and every way t=
he SIP spec sucks one email at a time. =A0FYI I&#39;m not sure if GNU/C is =
the correct acronym, maybe its POSIX/C.<div>
<br></div><div>Regards,</div><div>Bill</div></div>

--e89a8ff1c6eeca209804d3d969ad--

From melinda.shore@gmail.com  Mon Jan 21 23:05:33 2013
Return-Path: <melinda.shore@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 16E2321F84C7 for <ietf@ietfa.amsl.com>; Mon, 21 Jan 2013 23:05:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 u0XhBZVG3MB1 for <ietf@ietfa.amsl.com>; Mon, 21 Jan 2013 23:05:32 -0800 (PST)
Received: from mail-da0-f47.google.com (mail-da0-f47.google.com [209.85.210.47]) by ietfa.amsl.com (Postfix) with ESMTP id A3B5521F84B9 for <ietf@ietf.org>; Mon, 21 Jan 2013 23:05:32 -0800 (PST)
Received: by mail-da0-f47.google.com with SMTP id s35so3088088dak.34 for <ietf@ietf.org>; Mon, 21 Jan 2013 23:05:32 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=T7/zGkfFpWY6zX7kc48XK7AJcJvAbh1RQwBko34ZTAk=; b=lWcE09A5SwuVFuq+R7aRcLWRTGXODiKOJgnRMyb/rIG3WAa1dITZwMTqQJLldOKOJA 6iSiRZE5d9XmldDQI18+xQiGRMM5lse7sIS/HGVHQHs6+NoeiIK9Y/2HbrfQyuEW//QX GR/YTX+Jgnn4MK+Ojcv45jcq6hy2Tj5ukVJYpBA+3D7CFDGCoY+Qbf6ZplJvdjHqSZrs D17vm3gTEEEcy7vh+A6PmFwVhGTSUZ70C+PgEy61Rh8wVVwC1p2JHvP5c3hfCK+NRxsZ CyguOlCT3f94yf4HVkgvGxh68N2Yr8Xo0QhS3IySaNfkgZzIOXRr2BRUwZAf156BCKeh GKbQ==
X-Received: by 10.68.235.200 with SMTP id uo8mr36540385pbc.29.1358838332426; Mon, 21 Jan 2013 23:05:32 -0800 (PST)
Received: from spandex.local (66-230-112-168-rb1.fai.dsl.dynamic.acsalaska.net. [66.230.112.168]) by mx.google.com with ESMTPS id i1sm10837484pav.35.2013.01.21.23.05.30 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 21 Jan 2013 23:05:31 -0800 (PST)
Message-ID: <50FE3A37.7040402@gmail.com>
Date: Mon, 21 Jan 2013 22:05:27 -0900
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130107 Thunderbird/17.0.2
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: A modest proposal
References: <CAPJ9He0dOttM+DmpUt9MzfWEXcs+tbpJJy4Z+usoRroyAdzJbA@mail.gmail.com>
In-Reply-To: <CAPJ9He0dOttM+DmpUt9MzfWEXcs+tbpJJy4Z+usoRroyAdzJbA@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 22 Jan 2013 07:05:33 -0000

On 1/21/13 7:57 PM, William Jordan wrote:
> Whoever thought it was a good idea to
> allow multiple ways of doing the same exact thing would hopefully be
> deterred by actually writing code to do it.  

I think there's general agreement that options are not a good thing and
a pretty decent understanding of the issues around complexity, but
there's many a slip, etc.  I'm sympathetic to your complaints.  At the
time that SIP came along there was much happiness that there was a less
complex alternative to H.323, but for better or worse complicated
problems sometimes have complicated solutions, and SIP ended up a
hairball. I don't think your proposal is likely to go anywhere but I'm
curious about why you're specifically requesting implementations in C.

Melinda


From cabo@tzi.org  Mon Jan 21 23:21:05 2013
Return-Path: <cabo@tzi.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5EAB621F882E for <ietf@ietfa.amsl.com>; Mon, 21 Jan 2013 23:21:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.249
X-Spam-Level: 
X-Spam-Status: No, score=-106.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 meu1haoTvj6W for <ietf@ietfa.amsl.com>; Mon, 21 Jan 2013 23:21:04 -0800 (PST)
Received: from informatik.uni-bremen.de (mailhost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::12]) by ietfa.amsl.com (Postfix) with ESMTP id 262E321F8831 for <ietf@ietf.org>; Mon, 21 Jan 2013 23:21:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from smtp-fb3.informatik.uni-bremen.de (smtp-fb3.informatik.uni-bremen.de [134.102.224.120]) by informatik.uni-bremen.de (8.14.3/8.14.3) with ESMTP id r0M7Kiu5022834; Tue, 22 Jan 2013 08:20:44 +0100 (CET)
Received: from [192.168.217.105] (p548919DD.dip.t-dialin.net [84.137.25.221]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp-fb3.informatik.uni-bremen.de (Postfix) with ESMTPSA id ED4CE310; Tue, 22 Jan 2013 08:20:43 +0100 (CET)
Subject: Re: A modest proposal
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Content-Type: text/plain; charset=iso-8859-1
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <50FE3A37.7040402@gmail.com>
Date: Tue, 22 Jan 2013 08:20:42 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <78CC8F41-E266-4191-9DF5-A4E20FABD675@tzi.org>
References: <CAPJ9He0dOttM+DmpUt9MzfWEXcs+tbpJJy4Z+usoRroyAdzJbA@mail.gmail.com> <50FE3A37.7040402@gmail.com>
To: Melinda Shore <melinda.shore@gmail.com>
X-Mailer: Apple Mail (2.1499)
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 22 Jan 2013 07:21:05 -0000

On Jan 22, 2013, at 08:05, Melinda Shore <melinda.shore@gmail.com> =
wrote:

> why you're specifically requesting implementations in C

I think his argument is that the spec author should be punished for each =
piece of fluff in the spec.
A sentiment that I can relate to.

Having to write C code probably does qualify as the appropriate =
punishment :-)

Gr=FC=DFe, Carsten

PS.: The underlying hypothesis that the authors of RFC 3261 don't code =
can be easily refuted.
But a spec writer who has to code things at the specific instant a new =
feature is being put into the spec will be in a different, more =
desirable mindset than someone who can just drop the English and leave =
implementation as an exercise to the reader.
And too bad we can't have the IESG implement it while reviewing it.
Both would be really useful to curb the "political" fluff that tends to =
accumulate in our specs.


From melinda.shore@gmail.com  Mon Jan 21 23:24:35 2013
Return-Path: <melinda.shore@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 29C8221F8831 for <ietf@ietfa.amsl.com>; Mon, 21 Jan 2013 23:24:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 6S6D-4UUGZdX for <ietf@ietfa.amsl.com>; Mon, 21 Jan 2013 23:24:34 -0800 (PST)
Received: from mail-pb0-f44.google.com (mail-pb0-f44.google.com [209.85.160.44]) by ietfa.amsl.com (Postfix) with ESMTP id B6AA621F8444 for <ietf@ietf.org>; Mon, 21 Jan 2013 23:24:34 -0800 (PST)
Received: by mail-pb0-f44.google.com with SMTP id uo1so3799112pbc.3 for <ietf@ietf.org>; Mon, 21 Jan 2013 23:24:34 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=Xhm85QH15wKyHfTIYxyT8a7KGe8MLyv3PygTDRHMzG4=; b=xgGVVElC5H+Af1nza/QvGvrLVdM6WlCqMFWkhB3qBU6JgXXwMFzq5LzPcBRFUMgpPP lIJ61STTEU1y4+ahC0i1rPCnu8KEjgweJzjmzKRfsnfrGUQXkctltDL2Ku+lH99Yf3ny LCTDv038dLDEvnwM6llUTxpZ6I53ykoieCYCkp4zUT11L9RgdFduGqmLajz7v5S5QZxC QNA4ZyPpzRfbFF3IJHvtIY6Bi/3pe0hbk+w+lZQgtecTTCnudtLT7Qo+kZEGtICTkHwY umA58Mxjfe5Umz/OBhswu9gc1tVTvM0VAsFNUzryC4BM90GM3zzE7CbwqvdNfubPw3Vi 8pow==
X-Received: by 10.66.89.132 with SMTP id bo4mr53778604pab.62.1358839474490; Mon, 21 Jan 2013 23:24:34 -0800 (PST)
Received: from spandex.local (66-230-112-168-rb1.fai.dsl.dynamic.acsalaska.net. [66.230.112.168]) by mx.google.com with ESMTPS id ue7sm10225177pbc.53.2013.01.21.23.24.32 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 21 Jan 2013 23:24:33 -0800 (PST)
Message-ID: <50FE3EAF.3050604@gmail.com>
Date: Mon, 21 Jan 2013 22:24:31 -0900
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130107 Thunderbird/17.0.2
MIME-Version: 1.0
To: Carsten Bormann <cabo@tzi.org>
Subject: Re: A modest proposal
References: <CAPJ9He0dOttM+DmpUt9MzfWEXcs+tbpJJy4Z+usoRroyAdzJbA@mail.gmail.com> <50FE3A37.7040402@gmail.com> <78CC8F41-E266-4191-9DF5-A4E20FABD675@tzi.org>
In-Reply-To: <78CC8F41-E266-4191-9DF5-A4E20FABD675@tzi.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 22 Jan 2013 07:24:35 -0000

On 1/21/13 10:20 PM, Carsten Bormann wrote:
> Having to write C code probably does qualify as the appropriate
> punishment :-)

I guess that depends on your background ...

> And too bad we can't have the IESG implement it while
> reviewing it. 

There we go.  That would cut down on the "I'll support your
awful idea if you support my awful idea" horse trading.

Melinda

From dwm@xpasc.com  Mon Jan 21 23:39:12 2013
Return-Path: <dwm@xpasc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E3C1A21F8839 for <ietf@ietfa.amsl.com>; Mon, 21 Jan 2013 23:39:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.654
X-Spam-Level: 
X-Spam-Status: No, score=-4.654 tagged_above=-999 required=5 tests=[AWL=-3.346, BAYES_00=-2.599, MISSING_HEADERS=1.292]
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 4K2ZY1Uwof18 for <ietf@ietfa.amsl.com>; Mon, 21 Jan 2013 23:39:12 -0800 (PST)
Received: from c2w3p-2.abacamail.com (c2w3p-2.abacamail.com [209.133.53.32]) by ietfa.amsl.com (Postfix) with ESMTP id 851B021F8837 for <ietf@ietf.org>; Mon, 21 Jan 2013 23:39:12 -0800 (PST)
Received: from xpasc.com (unknown [68.164.244.188]) by c2w3p-2.abacamail.com (Postfix) with ESMTP id 293A940377 for <ietf@ietf.org>; Tue, 22 Jan 2013 07:39:09 +0000 (UTC)
Received: from egate.xpasc.com (egate.xpasc.com [10.1.2.49]) by xpasc.com (8.13.8/8.13.8) with ESMTP id r0M7d8Lm030199 for <ietf@ietf.org>; Mon, 21 Jan 2013 23:39:08 -0800
Date: Mon, 21 Jan 2013 23:39:08 -0800 (PST)
From: David Morris <dwm@xpasc.com>
cc: ietf@ietf.org
Subject: Re: A modest proposal
In-Reply-To: <50FE3EAF.3050604@gmail.com>
Message-ID: <alpine.LRH.2.01.1301212334160.29369@egate.xpasc.com>
References: <CAPJ9He0dOttM+DmpUt9MzfWEXcs+tbpJJy4Z+usoRroyAdzJbA@mail.gmail.com> <50FE3A37.7040402@gmail.com> <78CC8F41-E266-4191-9DF5-A4E20FABD675@tzi.org> <50FE3EAF.3050604@gmail.com>
User-Agent: Alpine 2.01 (LRH 1266 2009-07-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Milter-Version: master.1+13-gbab1945
X-AV-Type: clean
X-AV-Accuracy: exact
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: ietf@ietf.org
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 22 Jan 2013 07:39:13 -0000

On Mon, 21 Jan 2013, Melinda Shore wrote:

> > And too bad we can't have the IESG implement it while
> > reviewing it. 
> 
> There we go.  That would cut down on the "I'll support your
> awful idea if you support my awful idea" horse trading.

No, it just means that I have to implement my awful idea and
you have to implement yours and then we agree to cross license
the source.

The thing that is easy to forget when viewing a specification
outside of the context of when it was written is that many/most
IETF specs are written to imporve the interoperability of
existing implementations. Part of improving the interoperability
is to incorporate features and/or extensibility to avoid
future hacking. AND we tend to need to grandfather existing
features which we then have to work-around for ever.

And our most popular specifications are the hardest to improve
because of the weight of existing usage.

From hannes.tschofenig@gmx.net  Tue Jan 22 00:34:35 2013
Return-Path: <hannes.tschofenig@gmx.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D4B0B21F85D9 for <ietf@ietfa.amsl.com>; Tue, 22 Jan 2013 00:34:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.98
X-Spam-Level: 
X-Spam-Status: No, score=-101.98 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_SORBS_WEB=0.619, USER_IN_WHITELIST=-100]
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 zHCwRh1i6ndB for <ietf@ietfa.amsl.com>; Tue, 22 Jan 2013 00:34:35 -0800 (PST)
Received: from mout.gmx.net (mout.gmx.net [212.227.15.18]) by ietfa.amsl.com (Postfix) with ESMTP id 090D321F85D7 for <ietf@ietf.org>; Tue, 22 Jan 2013 00:34:34 -0800 (PST)
Received: from mailout-de.gmx.net ([10.1.76.17]) by mrigmx.server.lan (mrigmx002) with ESMTP (Nemesis) id 0MOVLv-1TsM722dEb-005sp8 for <ietf@ietf.org>; Tue, 22 Jan 2013 09:34:33 +0100
Received: (qmail invoked by alias); 22 Jan 2013 08:34:33 -0000
Received: from unknown (EHLO [10.255.135.234]) [194.251.119.201] by mail.gmx.net (mp017) with SMTP; 22 Jan 2013 09:34:33 +0100
X-Authenticated: #29516787
X-Provags-ID: V01U2FsdGVkX18dRH5rjHAdzMWfymnA45dfmH+iStUn/B1DmfREr5 HVdmvPt99dWl1Q
Subject: Re: A modest proposal
Mime-Version: 1.0 (Apple Message framework v1085)
Content-Type: text/plain; charset=us-ascii
From: Hannes Tschofenig <hannes.tschofenig@gmx.net>
In-Reply-To: <50FE3A37.7040402@gmail.com>
Date: Tue, 22 Jan 2013 10:34:31 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <691CE879-B639-4C69-8B8D-0FC2DCB909A8@gmx.net>
References: <CAPJ9He0dOttM+DmpUt9MzfWEXcs+tbpJJy4Z+usoRroyAdzJbA@mail.gmail.com> <50FE3A37.7040402@gmail.com>
To: Melinda Shore <melinda.shore@gmail.com>
X-Mailer: Apple Mail (2.1085)
X-Y-GMX-Trusted: 0
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 22 Jan 2013 08:34:36 -0000

Hi Melinda,

On Jan 22, 2013, at 9:05 AM, Melinda Shore wrote:

> there's general agreement that options are not a good thing and
> a pretty decent understanding of the issues around complexity, but
> there's many a slip, etc.=20
It may seem to be very easy to agree with you on that point. However, =
the story isn't that simple as it first seems to be.=20

For example: For SIP there are many different key distribution protocols =
being specified (see http://tools.ietf.org/html/rfc5479 and =
http://tools.ietf.org/html/draft-ietf-avtcore-rtp-security-options-01).
Why are there so many different ways to distribute keys for usage with =
SRTP? Why cannot we just have one solution and always use it? It turns =
out that there are many reasons, including different properties of =
individual solutions, designed by other organizations (e.g., 3GPP) and =
nobody wanted to upset them, IPRs, different architectural assumptions =
(e.g., regarding regulatory requirements), etc. Even the question =
whether SRTP should be mandated is already complicated as discussed in =
http://datatracker.ietf.org/doc/draft-ietf-avt-srtp-not-mandatory/

Another example from a different area: Why do we need so many transition =
technologies for the migration from IPv4 to IPv6? Wouldn't it be less =
complex to just have one transition mechanism?

Yet another example: Diameter supports TCP and SCTP. RADIUS initially =
supported UDP only and later added support for TCP. Couldn't the RADIUS =
guys just have used Diameter if they want to use a reliable transport?=20=


Ciao
Hannes


From melinda.shore@gmail.com  Tue Jan 22 01:49:21 2013
Return-Path: <melinda.shore@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 389E221F8801 for <ietf@ietfa.amsl.com>; Tue, 22 Jan 2013 01:49:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 sifb4AmWpft5 for <ietf@ietfa.amsl.com>; Tue, 22 Jan 2013 01:49:20 -0800 (PST)
Received: from mail-pa0-f49.google.com (mail-pa0-f49.google.com [209.85.220.49]) by ietfa.amsl.com (Postfix) with ESMTP id 5C2A821F85AD for <ietf@ietf.org>; Tue, 22 Jan 2013 01:49:20 -0800 (PST)
Received: by mail-pa0-f49.google.com with SMTP id bi1so3935476pad.22 for <ietf@ietf.org>; Tue, 22 Jan 2013 01:49:20 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=JrfNh5p88C2QxQrbpgUj9/3Yw9aPcqxIcOYXwmoC1eM=; b=sZpwMIKM6JokF0gu/JtMJHSf3SMfQLCWM5qpwLYbAO+Vzac4N+JXFZntIu9qCExpai /sPtHDSPSX3BR0YAu7Eac/Jj8vgPHD4WIU7xBhYbEymhpn2SEff4tKPke7Ae9YabfLxV 9sQXePR0wwKFKwV9fQnqfNsy9i8cYkfJYA3JsxMU3Ejm+Ae/FOmuITL6MI15bEVPVMpq Nzfd2bL7YGoV3T2F7+eqsbqiTDcHzPqWnzZJ2KJ5+got7Ot9dfvRAbzccKaDzaVmhqQ8 5ZyjpjxvKQbruSD/yJh+njf10XscpAqqR4rYGkXLW0CXxuprOp1QnBWoZLnD4IbmLY6V cZPA==
X-Received: by 10.66.87.67 with SMTP id v3mr54707414paz.63.1358848159915; Tue, 22 Jan 2013 01:49:19 -0800 (PST)
Received: from spandex.local (66-230-112-168-rb1.fai.dsl.dynamic.acsalaska.net. [66.230.112.168]) by mx.google.com with ESMTPS id bg6sm11098533pab.33.2013.01.22.01.49.17 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 22 Jan 2013 01:49:18 -0800 (PST)
Message-ID: <50FE609C.7090000@gmail.com>
Date: Tue, 22 Jan 2013 00:49:16 -0900
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130107 Thunderbird/17.0.2
MIME-Version: 1.0
To: Hannes Tschofenig <hannes.tschofenig@gmx.net>
Subject: Re: A modest proposal
References: <CAPJ9He0dOttM+DmpUt9MzfWEXcs+tbpJJy4Z+usoRroyAdzJbA@mail.gmail.com> <50FE3A37.7040402@gmail.com> <691CE879-B639-4C69-8B8D-0FC2DCB909A8@gmx.net>
In-Reply-To: <691CE879-B639-4C69-8B8D-0FC2DCB909A8@gmx.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 22 Jan 2013 09:49:21 -0000

On 1/21/13 11:34 PM, Hannes Tschofenig wrote:
> It may seem to be very easy to agree with you on that point. However,
> the story isn't that simple as it first seems to be.

Complex problems often have complex solutions.  I think a lot of
people look at sendmail, for example, and go "GAH!" without
knowing much of the history of gatewaying between networks and
the rewrite rules that facilitated that.  But I also wonder how
hard we've worked at trying to reduce complexity in some cases.

The SIP thing is a little painful because at the time it was
brought to the IETF it was touted as a much simpler technology
than H.323.  And, of course, it turned out that ... complex problems
often have complex solutions and there's a reason why H.323 is
as complicated as it is (mostly).  Still, I wonder if we're just
tending to accept complex solutions a bit readily.

Melinda

From daedulus@btconnect.com  Tue Jan 22 02:00:23 2013
Return-Path: <daedulus@btconnect.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B196A21F86D8 for <ietf@ietfa.amsl.com>; Tue, 22 Jan 2013 02:00:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 H9Z3iixhREsj for <ietf@ietfa.amsl.com>; Tue, 22 Jan 2013 02:00:22 -0800 (PST)
Received: from co1outboundpool.messaging.microsoft.com (co1ehsobe005.messaging.microsoft.com [216.32.180.188]) by ietfa.amsl.com (Postfix) with ESMTP id 9031621F86AB for <ietf@ietf.org>; Tue, 22 Jan 2013 02:00:22 -0800 (PST)
Received: from mail150-co1-R.bigfish.com (10.243.78.215) by CO1EHSOBE016.bigfish.com (10.243.66.79) with Microsoft SMTP Server id 14.1.225.23; Tue, 22 Jan 2013 10:00:21 +0000
Received: from mail150-co1 (localhost [127.0.0.1])	by mail150-co1-R.bigfish.com (Postfix) with ESMTP id 391B8D01064; Tue, 22 Jan 2013 10:00:21 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.254.181; KIP:(null); UIP:(null); IPV:NLI; H:DBXPRD0711HT004.eurprd07.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: -21
X-BigFish: PS-21(zz9371I1b0bI542I1432I1418Izz1ee6h1de0h1202h1e76h1d1ah1d2ahzz1033IL8275bh8275dhz2dh2a8h5a9h668h839h947hd24hf0ah1177h1179h1288h12a5h12a9h12bdh137ah139eh13b6h1441h1504h1537h162dh1631h1758h17f1h184fh1898h18e1h304l1155h)
Received: from mail150-co1 (localhost.localdomain [127.0.0.1]) by mail150-co1 (MessageSwitch) id 135884881955294_20443; Tue, 22 Jan 2013 10:00:19 +0000 (UTC)
Received: from CO1EHSMHS017.bigfish.com (unknown [10.243.78.224])	by mail150-co1.bigfish.com (Postfix) with ESMTP id 006C894005F; Tue, 22 Jan 2013 10:00:19 +0000 (UTC)
Received: from DBXPRD0711HT004.eurprd07.prod.outlook.com (157.56.254.181) by CO1EHSMHS017.bigfish.com (10.243.66.27) with Microsoft SMTP Server (TLS) id 14.1.225.23; Tue, 22 Jan 2013 10:00:17 +0000
Received: from AMXPRD0111HT003.eurprd01.prod.exchangelabs.com (157.56.250.117) by pod51017.outlook.com (10.255.178.37) with Microsoft SMTP Server (TLS) id 14.16.257.4; Tue, 22 Jan 2013 10:00:12 +0000
Message-ID: <005601cdf886$e6f16be0$4001a8c0@gateway.2wire.net>
From: t.p. <daedulus@btconnect.com>
To: William Jordan <wjordan129@gmail.com>, <ietf@ietf.org>
References: <CAPJ9He0dOttM+DmpUt9MzfWEXcs+tbpJJy4Z+usoRroyAdzJbA@mail.gmail.com>
Subject: Re: A modest proposal
Date: Tue, 22 Jan 2013 09:57:27 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Originating-IP: [157.56.250.117]
X-OriginatorOrg: btconnect.com
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 22 Jan 2013 10:00:23 -0000

----- Original Message -----
From: "William Jordan" <wjordan129@gmail.com>
To: <ietf@ietf.org>
Sent: Tuesday, January 22, 2013 4:57 AM
> I've recent had to write a program to interface with a SIP lync server
and
> in doing so have had to code to several rfcs.  After reading and
dealing
> with implementation of the various rfcs I have read I have come up
with
> what I consider "A modest proposal" to fix some of the problems I've
seen
> with implementing a rfc.  I think anyone who writes a rfc should have
to
> provide a working ANSI/C or GNU/C implementation of the rfc in
question.
>  Specifically, I have worked with the SIP rfc (rfc 3261) and have come
to
> the conclusion that whoever wrote the rfc has never coded a day in
their
> life.  Whoever thought it was a good idea to allow multiple ways of
doing
> the same exact thing would hopefully be deterred by actually writing
code
> to do it.  I think a suitable punishment for those people would be to
write
> each way of writing a from header on a blackboard 100 times... this
would
> actually be less of the pain they've cause by making each writer of a
SIP
> stack handle each possible way of doing things.

I find your proposal puzzling as many of those involved in the creation
of an RFC are experienced coders and do turn out implementations in
short order.  They know, they do not have to write the code, what is
easy to code and what is not.  If a choice is made, to have many
alternatives, which increases the complexity of implementation, then
that choice is made knowingly, in order to produce a protocol that will
better meet the requirements.

Code you write once, a successful implementation will execute a
countless number of times; what matters is that the protocol works every
time, not the length of the one off exercise to implement it beforehand.

If you had said that you had found flaws in the logic of the protocol
which could have been found by coding - and that does happen - then I
think that your argument would carry more weight.

Tom Petch

> Anyways, that is my modest proposal, please respond or I will be
forced to
> reply every day to this mailing list on each and every way the SIP
spec
> sucks one email at a time.  FYI I'm not sure if GNU/C is the correct
> acronym, maybe its POSIX/C.
>
> Regards,
> Bill
>



From abdussalambaryun@gmail.com  Tue Jan 22 02:05:23 2013
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9032321F8826 for <ietf@ietfa.amsl.com>; Tue, 22 Jan 2013 02:05:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 oGJNUyhSIhvD for <ietf@ietfa.amsl.com>; Tue, 22 Jan 2013 02:05:23 -0800 (PST)
Received: from mail-pa0-f46.google.com (mail-pa0-f46.google.com [209.85.220.46]) by ietfa.amsl.com (Postfix) with ESMTP id 4371C21F86D8 for <ietf@ietf.org>; Tue, 22 Jan 2013 02:05:22 -0800 (PST)
Received: by mail-pa0-f46.google.com with SMTP id kp14so2566852pab.5 for <ietf@ietf.org>; Tue, 22 Jan 2013 02:05:22 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to:cc :content-type; bh=lFvBkPxeO3ihptA2ul62RgrqpOz8jxdqZrYWu7yJsvI=; b=bZ70Qok+pBQ41d2cxAazpprSo3SH0jf/p44GqqHkpvz4kTD6e3cHlqm3OA6So5tT30 6uVh4K2PD2z4ugWDtWyqbrutgvVps6kBg9OENkM1vczRhreoDGPWNRG4deCzsH94DhMU 9siV+qqD+7LhV/fGc7MHQI4zIOlMFNNQpYOzcMnz6sj5fiGHe+PyerulE8mDsYiYjAVp ej5G0tmPvs6Ss3NkUu88mQsKe7OKQI3jaKd3PRhziydNP2c6ZZcfR6mCVQo9Mt9WAP8r eRlCQuOCN9HHc+krZm5QveG0bKjVHBRB8tCmS+SqQWk2x7y531lhJ5Q6Pm1rX4CJLnPl 0WRg==
MIME-Version: 1.0
X-Received: by 10.68.234.167 with SMTP id uf7mr37646109pbc.20.1358849122015; Tue, 22 Jan 2013 02:05:22 -0800 (PST)
Received: by 10.68.218.134 with HTTP; Tue, 22 Jan 2013 02:05:21 -0800 (PST)
Date: Tue, 22 Jan 2013 11:05:21 +0100
Message-ID: <CADnDZ8_uoNb+vP1aO3T_yondwiN0tnmL-sroEt6SCgyDfPmcsA@mail.gmail.com>
Subject: Re: A modest proposal
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: wjordan129@gmail.com
Content-Type: text/plain; charset=ISO-8859-1
Cc: ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 22 Jan 2013 10:05:23 -0000

Hi Bill,

I agree that we need to look into this issue of writting RFCs that had
difficulties in understanding and implementations. I mentioned before
some comment regarding 2119 to help. Please suggest your comments on
the RFC3261 and post them on this list, I RECOMMEND to update this RFC
if you see it is not suitable for well implementation. If you don't
want to update the RFC some will like to but we need to see your
specific comments that should be updated on the RFC3261. I like the
choice of implementing in C and don't think the coding language makes
much difference if you got difficulties to understand the RFC authors.
However, don't blaim the authors to punish they were doing their best,
but blaim the current AD or IETF management if they don't do nothing
after reading your input.

 I RECOMMEND that participant SHOULD report in IETF the interop tests
if any done and/or report problems of implementation as informational
I-Ds. Thanks for your information,

AB

+++++++++
On Mon, 21 Jan 2013 23:57:22 -0500

I've recent had to write a program to interface with a SIP lync server
and in doing so have had to code to several rfcs.  After reading and
dealing with implementation of the various rfcs I have read I have
come up with what I consider "A modest proposal" to fix some of the
problems I've seen with implementing a rfc.  I think anyone who writes
a rfc should have to provide a working ANSI/C or GNU/C implementation
of the rfc in question.  Specifically, I have worked with the SIP rfc
(rfc 3261) and have come to the conclusion that whoever wrote the rfc
has never coded a day in their life.  Whoever thought it was a good
idea to allow multiple ways of doing the same exact thing would
hopefully be deterred by actually writing code to do it.  I think a
suitable punishment for those people would be to write each way of
writing a from header on a blackboard 100 times... this would actually
be less of the pain they've cause by making each writer of a SIP stack
handle each possible way of doing things.


Anyways, that is my modest proposal, please respond or I will be
forced to reply every day to this mailing list on each and every way
the SIP spec sucks one email at a time.  FYI I'm not sure if GNU/C is
the correct acronym, maybe its POSIX/C.


Regards,
Bill

From wjordan129@gmail.com  Tue Jan 22 02:11:10 2013
Return-Path: <wjordan129@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6674921F86D8 for <ietf@ietfa.amsl.com>; Tue, 22 Jan 2013 02:11:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.293
X-Spam-Level: 
X-Spam-Status: No, score=-3.293 tagged_above=-999 required=5 tests=[AWL=0.305,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
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 gMEWVVQS5KUh for <ietf@ietfa.amsl.com>; Tue, 22 Jan 2013 02:11:10 -0800 (PST)
Received: from mail-oa0-f49.google.com (mail-oa0-f49.google.com [209.85.219.49]) by ietfa.amsl.com (Postfix) with ESMTP id D754421F8644 for <ietf@ietf.org>; Tue, 22 Jan 2013 02:11:09 -0800 (PST)
Received: by mail-oa0-f49.google.com with SMTP id l10so6895683oag.8 for <ietf@ietf.org>; Tue, 22 Jan 2013 02:11:09 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type; bh=m6vvJ0MTzr3zUmHzTkWeCVUbadgyURd+t5J2trKrtqE=; b=UQrIcrL37GFDXbtQBC9ucxIBfjA631I0WeFpvFA5C1cUwMgEkmOulJgbHXL+h1wbLK QuaUshUdk64ef+D71HJsbPnzL4cn3+jfVgU3cqB7+Slv10l5C0zgl0VhWzIkXtJX6kVl JABfapRJUvLTOQZY1txrxnfyd93qGDWXunYygI2v1YW8MQEEE6nlJSy/B7Yk2JWrjr1j eIaGtDRnSQzZpFeK1A8/8goln32hamovRy75bDWX90dbI/y6oRXqIZnhhgJxu3ICfCAB wzqJyRa9/vZAb2b7Ou+eetqy4G+klRLeBPrsE7/59kyuK5smRa+Py/zIi44dx8+mLiYc Mekw==
MIME-Version: 1.0
X-Received: by 10.60.28.129 with SMTP id b1mr16816400oeh.106.1358849469370; Tue, 22 Jan 2013 02:11:09 -0800 (PST)
Received: by 10.76.154.234 with HTTP; Tue, 22 Jan 2013 02:11:09 -0800 (PST)
Date: Tue, 22 Jan 2013 05:11:09 -0500
Message-ID: <CAPJ9He36PgOdwocyB0EnEqWruNGc4zzMW6ETW2im2azy7Kg0rw@mail.gmail.com>
Subject: Re: A modest proposal
From: William Jordan <wjordan129@gmail.com>
To: ietf@ietf.org
Content-Type: multipart/alternative; boundary=e89a8ff1c2e0ecd1ce04d3ddcb25
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 22 Jan 2013 10:11:10 -0000

--e89a8ff1c2e0ecd1ce04d3ddcb25
Content-Type: text/plain; charset=ISO-8859-1

In response to Melinda's first reply, the reason I specifically requested
an implementation in C is because I think its the language that a developer
is the least likely to hang himself with.  I've seen plenty of examples of
bad code and I think c gives the least opportunity for a developer to make
an unreadable mess.  It also is a language that is in line with my general
idea of coding, i.e. KISS (keep it simple stupid).

Continuing my discussion about how badly SIP is designed, I'm gonna talk
about the via line.  First of all each via line can be expressed as via: OR
v: OR you can have multiple via entries on the same line separated by a
comma where random whitespaces are allowed.  Additionally, I can't
understand why each line is terminated with <CR><LF>, why use two
characters when one will do.  I could also go into a design argument about
how the same specification is used for udp as for tcp and why the idea for
a stateless SIP proxy wasn't thrown out completely when writing the draft,
but I'll wait on those.

Bill

--e89a8ff1c2e0ecd1ce04d3ddcb25
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div>In response to Melinda&#39;s first reply, the reason I specifically re=
quested an implementation in C is because I think its the language that a d=
eveloper is the least likely to hang himself with. =A0I&#39;ve seen plenty =
of examples of bad code and I think c gives the least opportunity for a dev=
eloper to make an unreadable mess. =A0It also is a language that is in line=
 with my general idea of coding, i.e. KISS (keep it simple stupid).</div>
<div><br></div><div>Continuing my discussion about how badly SIP is designe=
d, I&#39;m gonna talk about the via line. =A0First of all each via line can=
 be expressed as via: OR v: OR you can have multiple via entries on the sam=
e line separated by a comma where random whitespaces are allowed. =A0Additi=
onally, I can&#39;t understand why each line is terminated with &lt;CR&gt;&=
lt;LF&gt;, why use two characters when one will do. =A0I could also go into=
 a design argument about how the same specification is used for udp as for =
tcp and why the idea for a stateless SIP proxy wasn&#39;t thrown out comple=
tely when writing the draft, but I&#39;ll wait on those.</div>
<div><br></div><div>Bill=A0</div>

--e89a8ff1c2e0ecd1ce04d3ddcb25--

From wjordan129@gmail.com  Tue Jan 22 02:19:18 2013
Return-Path: <wjordan129@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 26AE421F8644 for <ietf@ietfa.amsl.com>; Tue, 22 Jan 2013 02:19:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.395
X-Spam-Level: 
X-Spam-Status: No, score=-3.395 tagged_above=-999 required=5 tests=[AWL=0.203,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
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 43AicXiLPKRG for <ietf@ietfa.amsl.com>; Tue, 22 Jan 2013 02:19:17 -0800 (PST)
Received: from mail-ob0-f178.google.com (mail-ob0-f178.google.com [209.85.214.178]) by ietfa.amsl.com (Postfix) with ESMTP id A0E0021F8622 for <ietf@ietf.org>; Tue, 22 Jan 2013 02:19:17 -0800 (PST)
Received: by mail-ob0-f178.google.com with SMTP id eh20so6821970obb.37 for <ietf@ietf.org>; Tue, 22 Jan 2013 02:19:17 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type; bh=6xECEnKJ5yLUBbD6iC7kAlNbVQaYly82EOkkGa/HvXY=; b=v1xCV7By8zoIJFcUddOZnaPjUcdW6/+6YJx2ttsVrTOq3nKspzs05EcCC+qeSIPSH9 u5kzTyfB4uVhgcVEcICefw4+MYpbakaJRT8hBqTGYXSDTbYM7TN0ZEnsGEVkVrMUGpyt xOsIEorGz+a01GZSpLjyDieXa/5sRcOSU/gOAJYiXcd4kYI5VJ5+YCK++ho/xInGpl2w vYM/dakmkP3yniOZldMGYgASdA5RJmK4an3xLXVU3n2fUmGd2HjjqaRihf4csd/z+fh8 pSzBwzf+3dfU72PSocu3h5sK8EUW0b6w4fy8kp+JQ26t3R6CeY+xKZQSvPFRfxW6YXto cgZw==
MIME-Version: 1.0
X-Received: by 10.182.77.169 with SMTP id t9mr2463743obw.13.1358849957224; Tue, 22 Jan 2013 02:19:17 -0800 (PST)
Received: by 10.76.154.234 with HTTP; Tue, 22 Jan 2013 02:19:17 -0800 (PST)
Date: Tue, 22 Jan 2013 05:19:17 -0500
Message-ID: <CAPJ9He3aUGMS4W6Xfjes2Thbh65iUOFiY8oSpRbZp_UmfTPt7Q@mail.gmail.com>
Subject: Re: A modest proposal
From: William Jordan <wjordan129@gmail.com>
To: ietf@ietf.org
Content-Type: multipart/alternative; boundary=f46d04447ee900e0f804d3dde92f
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 22 Jan 2013 10:19:18 -0000

--f46d04447ee900e0f804d3dde92f
Content-Type: text/plain; charset=ISO-8859-1

Another reason I believe a code implementation of a rfc would be good is
understanding.  For me, it is sometimes easier to read an example of code
than to try to read through a rfc description of it.

Bill

--f46d04447ee900e0f804d3dde92f
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Another reason I believe a code implementation of a rfc would be good is un=
derstanding. =A0For me, it is sometimes easier to read an example of code t=
han to try to read through a rfc description of it.<div><br></div><div>Bill=
</div>

--f46d04447ee900e0f804d3dde92f--

From abdussalambaryun@gmail.com  Tue Jan 22 03:08:15 2013
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C769321F87E7 for <ietf@ietfa.amsl.com>; Tue, 22 Jan 2013 03:08:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 HszzGwiuJhxt for <ietf@ietfa.amsl.com>; Tue, 22 Jan 2013 03:08:15 -0800 (PST)
Received: from mail-pb0-f44.google.com (mail-pb0-f44.google.com [209.85.160.44]) by ietfa.amsl.com (Postfix) with ESMTP id 3E08F21F87DC for <ietf@ietf.org>; Tue, 22 Jan 2013 03:08:15 -0800 (PST)
Received: by mail-pb0-f44.google.com with SMTP id uo1so3910725pbc.3 for <ietf@ietf.org>; Tue, 22 Jan 2013 03:08:15 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type; bh=IJfIX9yUFK9fi75hJ2jmvkNtAszi/J3BUUVoQUOwnEQ=; b=MBRD5gLLi1JfbRQxfM9UEDE5BBKuIIJtzbLk3MXemEl4Xy9Es2EBkcHIj8hHl8QEQI oEETzskV97Avi+S/tlT7ses1YmqBAYFwL2qaHVoYCOZOFLVczzQ79DZjRNXYLc2DbEgu auixpAnrxhi3srQRNNDNWbUip0EZ7jmsJKkyknUXSkPyaS3MBLN+TfdjqVoEzxcNn9wp 4Jo2q5ANOpUEXa7IJRI9Xw1GTs0BWh8sUH5KGYYpOh+fAk59PBFWdcnbiL7mWtnXCykm 6N3aalHxkqC/Y0SQWpK49itg8iO8cRnldR38L2HTv5B/GmRsQX89tar89yxcHQGY2mS3 MgBA==
MIME-Version: 1.0
X-Received: by 10.68.232.195 with SMTP id tq3mr38044453pbc.70.1358852894967; Tue, 22 Jan 2013 03:08:14 -0800 (PST)
Received: by 10.68.218.134 with HTTP; Tue, 22 Jan 2013 03:08:14 -0800 (PST)
Date: Tue, 22 Jan 2013 12:08:14 +0100
Message-ID: <CADnDZ88+Q0yqgX+evJzL_8TRSFq7O0zv_8r1p1ebn7GXkCKLTg@mail.gmail.com>
Subject: The Implemetation and Running Code MAY be tested [RFC2026]
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: ietf <ietf@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 22 Jan 2013 11:08:15 -0000

It is generally expected that "independent implementations" will
interoperate.  In particular, see RFC 2026, "Internet Standards
Process", which includes the following:

2026>
    Thus, a candidate specification must be implemented and tested for
    correct operation and interoperability by multiple independent
    parties and utilized in increasingly demanding environments, before
    it can be adopted as an Internet Standard.

AB> Does this make specifications recommended or required to interop
test, the must was not capital?

2026>
    In general, an Internet Standard is a specification that is stable
    and well-understood, is technically competent, has multiple,
    independent, and interoperable implementations with substantial
    operational experience, enjoys significant public support, and is
    recognizably useful in some or all parts of the Internet.

AB> I was told that independent implementation = independent and
different implementation, is that true?

AB>Does independent mean, that number of implementors read the
specification separately and implemented without contact or
dependance? or that the implementation does not have to work with
other implementation of same spec?

AB> Does independent mean separately or jointly each of the following
were implemented;
       - implemented in different languages but same implementor,
       - implemented by different implementors and same code langauge,
       - the number of implementations (with same implementor) were
then modified but does not contradict the specification.

Please advise,

AB

From bygg@mail.cafax.se  Tue Jan 22 03:08:11 2013
Return-Path: <bygg@mail.cafax.se>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CF74721F87E7 for <ietf@ietfa.amsl.com>; Tue, 22 Jan 2013 03:08:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 8t6j4WhAM05j for <ietf@ietfa.amsl.com>; Tue, 22 Jan 2013 03:08:11 -0800 (PST)
Received: from mail.cafax.se (mail.cafax.se [IPv6:2a00:801:11:53::4]) by ietfa.amsl.com (Postfix) with ESMTP id 263FD21F87CC for <ietf@ietf.org>; Tue, 22 Jan 2013 03:08:10 -0800 (PST)
Received: from mail.cafax.se (localhost [127.0.0.1]) by mail.cafax.se (8.14.6/8.14.6) with ESMTP id r0MB88P3028782 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Tue, 22 Jan 2013 12:08:08 +0100 (MET)
Received: (from bygg@localhost) by mail.cafax.se (8.14.6/8.14.6/Submit) id r0MB88T3025760 for ietf@ietf.org; Tue, 22 Jan 2013 12:08:08 +0100 (MET)
Sender: Johnny Eriksson <bygg@cafax.se>
Date: Tue, 22 Jan 2013 12:08:08 WET
From: Johnny Eriksson <bygg@cafax.se>
To: ietf@ietf.org
Subject: Re: A modest proposal
In-Reply-To: Your message of Tue, 22 Jan 2013 05:11:09 -0500
Message-ID: <CMM.0.91.0.1358852888.bygg@mail.cafax.se>
X-Scanned-By: MIMEDefang 2.71 on 192.71.228.4
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: Johnny Eriksson <bygg@cafax.se>
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 22 Jan 2013 11:09:49 -0000

William Jordan <wjordan129@gmail.com> wrote:

> comma where random whitespaces are allowed.  Additionally, I can't
> understand why each line is terminated with <CR><LF>, why use two
> characters when one will do.

It is called NETASCII, and is the norm for text-based protocols.

It is a canonical end-of-line representation.

> Bill

--Johnny

From elwynd@dial.pipex.com  Tue Jan 22 06:12:41 2013
Return-Path: <elwynd@dial.pipex.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7BB5821F85BC; Tue, 22 Jan 2013 06:12:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 uzMJvQmeIhvF; Tue, 22 Jan 2013 06:12:40 -0800 (PST)
Received: from auth.a.painless.aa.net.uk (a.painless.aa.net.uk [IPv6:2001:8b0:0:30::51bb:1e33]) by ietfa.amsl.com (Postfix) with ESMTP id 4403B21F85B2; Tue, 22 Jan 2013 06:12:40 -0800 (PST)
Received: from mightyatom.folly.org.uk ([81.187.254.250]) by a.painless.aa.net.uk with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.77) (envelope-from <elwynd@dial.pipex.com>) id 1TxeaU-0003aK-Pc; Tue, 22 Jan 2013 14:12:34 +0000
Subject: Gen-art last call review of draft-ietf-opsawg-oam-overview-08.txt
From: Elwyn Davies <elwynd@dial.pipex.com>
To: General Area Review Team <gen-art@ietf.org>
Content-Type: text/plain
Date: Tue, 22 Jan 2013 14:10:45 +0000
Message-Id: <1358863845.28723.19076.camel@mightyatom>
Mime-Version: 1.0
X-Mailer: Evolution 2.26.3 
Content-Transfer-Encoding: 7bit
X-Spam-Score-a.painless.aa.net.uk: -4.0
Cc: IETF discussion <ietf@ietf.org>, draft-ietf-opsawg-oam-overview.all@tools.ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 22 Jan 2013 14:12:41 -0000

I am the assigned Gen-ART reviewer for this draft. For background on
Gen-ART, please see the FAQ at

<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

Please resolve these comments along with any other Last Call comments
you may receive.

Document: draft-ietf-opsawg-oam-overview-08.txt
Reviewer: Elwyn Davies
Review Date: 22 Jan 2013
IETF LC End Date:25 Jan 2013
IESG Telechat date: (if known) -

Summary: In my opinion, this draft has serious issues as described
below.

Major issues:
General 1: Title vs Abstract vs Section 1 vs actual content:

Here in the UK a well-known brand of varnishes and wood preservative
paints uses the slogan 'Does what it says on the tin!'.  If my
understanding and the write-up in RFC 6491, OAM covers a whole lot more
than the coverage of the specific mechanisms discussed in this
document .. and there are various other mechanisms such as SNMP and
Netconf that support the OAM constellation.  I would take the view that
this document certainly does not 'do what it says on the tin'.
Accordingly I take issue with the title as it doesn't provide a total
overview of OAM mechanisms; the abstract closes down the scope of OAM as
compared with RFC 6491 and s1 restricts it even more - and certainly
does not summarize all the OAM tools and mechanisms defined in the IETF.
The last para of s1 claims that 'management aspects are outside the
scope of this document' - if this is really saying that this 'overview'
of OAM skips the whole M aspect of OAM then I'm afraid the document is
badly misnamed.  And it significantly reduces the value of the work.

General (2): The intended purpose of this document: Back in 2011 Stewart
Bryant summarized a review of a previous version of this document from
the routing directorate
(https://datatracker.ietf.org/doc/draft-ietf-opsawg-oam-overview/history/ entry dated 2011-08-10 referring to version 05 of the document).  IMO the initial section of that review regarding the audience of this document was well targeted and *has not been fixed*.  If this is intended as an introductory overview for people wishing to see what OAM is about in the IETF then it needs further introductory text and some background.  It should also state what its target audience actually is.

General (3): I don't know if Scott Bradner has actually produced a proto
shpeherd write up, but I would be intrigued to know the level of
concensus behind this document.  In particular the tool classification
in s1.1 and terminology in s2 (particularly s2.2.2) is that used
exclusively in the MPLS-TP work in the IETF which is derived from the
802.1ag terminology.  The terminology is presented as if it is common to
OAM work across the IETF. Does the IETF management community at large
concur with this expansion of the applicability of the terminology set
based on 'Management Domains' etc?

General (4): As an overview, I think it would be advisable to point out
that one reason for the multiplicity of tools is that they support at
least four different data plane technologies (native IP, vanilla MPLS,
MPLS-TP and PWE) and note that in several cases the data plane
technologies rely on distinct (IP-based) management channels to allow
the information gleaned by the operations in the the data plane to be
reported back to the application that originated the operation. 


Minor (or at least less major) issues:

s1, para1: For consistency with  the abstract, s1.1 .. and because I'd 
expect OAM to handle it as well ... OAM deals with performance 
monitoring and statistics gathering as well as dealing with degradation.

s1.1: The section is entitled building blocks but actually only mentions 
one block, i.e., the OAM protocol.  Presumably this section really ought 
to say something about the applications and device drivers that have to 
instantiated in the MPs.  In particular as introduction to the text in 
the following section it should say something about classifying 
applications into continuously running or proactive monitoring and 
on-demand applications (since the latter are introduced without any 
definition in the next section.)


s2.2.2/3: I am not familiar with 802.1 management issues and I was 
rather confused by the logical status of MIPs .  The text here seems to 
indicate that they are intermediate and generally don't terminate 
messages but then says in s2.2.3 that messages are 'destined to' MIPs.  
Looking for some additional understanding, I fetched up at Wikipedia 
(now there's a surprise) http://en.wikipedia.org/wiki/IEEE_802.1ag.  
This page mentions the concept of maintenance domains and the 
explanation of MIPs as internal points in the domain that generally 
forward messages within the domain whereas end points (MEPs) are 
effectively on the domain boundary. This makes a whole lot more sense
and seemed to be a rather better set of term definitions than we have in
this draft.  
I noticed eventually that the term Management Domain (MD) had appeared
in the first line of s1.1 but does not appear in s2 at all. If we are
going to accept the Management Domain terminology set, then MD certainly
ought to be defined and discussed here.   


s2.2.3, para1, sentence 1:
>   either initiates or reacts to OAM messages.
The following sentences contradict this.  Should be 'initiates and/or 
reacts to OAM messages'.  See comment above.

s3, general: The level of detail regarding the various toolsets is not
very even.  In particular, the MPLS-TP toolset gets significantly more
attention than others and the detail in OWAMP/TWAMP may be more than is
desirable for an overview.

s3.1: A few words about the likely suppression of pings and traceroute 
messages due to ICMP filtering is probably desirable as these limit
their usefulness in the wider Internet.

s3.3: What about RFC6374 (MPLS packet loss measurement)? It appears in
the list in s1.4 but is not mentioned here.

s3.4.1: Talking about what the MPLS working group 'is currently doing' 
will not be helpful for an archival document.

s3.4.3.1: The OnDemand-CV reference is for non-TP MPLS... do you mean 
RFC 6426 which appears to be the TP variant?

Nits/editorial comments:
General: For a reader who wants to go on and look at the RFCs that 
define the various tools, it would probably be helpful to use reference 
tags that  either are or include the RFC number.
s1.3, para 2: s/in several fronts/covering several different approaches/

s2.2.2, last para: Need to expand 'p2mp'.

s3.4.3.8: Should this section reference RFC6375?

s3.5.1: It appears that the basic AC acronym (associated channel) is not 
defined.


From lars@netapp.com  Tue Jan 22 06:53:59 2013
Return-Path: <lars@netapp.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CE45E21F895B; Tue, 22 Jan 2013 06:53:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.799
X-Spam-Level: 
X-Spam-Status: No, score=-9.799 tagged_above=-999 required=5 tests=[AWL=-0.599, BAYES_00=-2.599, J_CHICKENPOX_21=0.6, RCVD_IN_DNSWL_HI=-8, SARE_SUB_RAND_LETTRS4=0.799]
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 lx3GF2uKGk-s; Tue, 22 Jan 2013 06:53:52 -0800 (PST)
Received: from mx12.netapp.com (mx12.netapp.com [216.240.18.77]) by ietfa.amsl.com (Postfix) with ESMTP id 2846E21F8933; Tue, 22 Jan 2013 06:53:42 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.84,514,1355126400"; d="scan'208";a="10399519"
Received: from smtp2.corp.netapp.com ([10.57.159.114]) by mx12-out.netapp.com with ESMTP; 22 Jan 2013 06:53:41 -0800
Received: from vmwexceht04-prd.hq.netapp.com (vmwexceht04-prd.hq.netapp.com [10.106.77.34]) by smtp2.corp.netapp.com (8.13.1/8.13.1/NTAP-1.6) with ESMTP id r0MErfHU026894; Tue, 22 Jan 2013 06:53:41 -0800 (PST)
Received: from SACEXCMBX01-PRD.hq.netapp.com ([169.254.2.51]) by vmwexceht04-prd.hq.netapp.com ([10.106.77.34]) with mapi id 14.02.0328.009; Tue, 22 Jan 2013 06:53:41 -0800
From: "Eggert, Lars" <lars@netapp.com>
To: "ietf@ietf.org list" <ietf@ietf.org>, "86attendees@ietf.org" <86attendees@ietf.org>
Subject: Fwd: [irtf-discuss] Applied Networking Research Prize 2013 presentation		at IETF-86
Thread-Topic: [irtf-discuss] Applied Networking Research Prize 2013 presentation		at IETF-86
Thread-Index: AQHN+LBETvvak6ltu0emYbYjMDVwcA==
Date: Tue, 22 Jan 2013 14:53:40 +0000
Message-ID: <D4D47BCFFE5A004F95D707546AC0D7E91F64E43A@SACEXCMBX01-PRD.hq.netapp.com>
References: <D4D47BCFFE5A004F95D707546AC0D7E91F64E368@SACEXCMBX01-PRD.hq.netapp.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.106.53.51]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <95C2C2F4C4AF8D47BB62BCC8329B6AD2@tahoe.netapp.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: "anrp@irtf.org <anrp@irtf.org" <anrp@irtf.org>
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 22 Jan 2013 14:54:00 -0000

Begin forwarded message:

> From: "Eggert, Lars" <lars@netapp.com>
> Subject: [irtf-discuss] Applied Networking Research Prize 2013 presentati=
on	 at IETF-86
> Date: January 22, 2013 15:51:13 GMT+01:00
> To: "irtf-announce@irtf.org" <irtf-announce@irtf.org>, "irtf-discuss@irtf=
.org" <irtf-discuss@irtf.org>
> Reply-To: "anrp@irtf.org" <anrp@irtf.org>
>=20
>=20
> Hi,
>=20
> we are extremely pleased to report that for the 2013 award period of
> the Applied Networking Research Prize (ANRP), 36 eligible nominations
> were received. Each submission was reviewed by eight members of the
> selection committee according to a diverse set of criteria, including
> scientific excellence and substance, timeliness, relevance, and
> potential impact on the Internet.
>=20
> Based on this review, four submissions will be awarded an ANRP in 2013.
> The first of these awards will happen at IETF-86 in Orlando, FL, USA.
> It goes to:
>=20
>  *** Gonca G=FCrsun *** for defining a metric that allows an analysis
>  of BGP routing policies:
>=20
>    Gonca G=FCrsun, Natali Ruchansky, Evimaria Terzi and Mark Crovella.
>    Routing State Distance: A Path-based Metric For Network Analysis.
>    Proc. ACM IMC, Boston, MA, USA, Nov. 2012.
>    http://cs-people.bu.edu/goncag/papers/imc12-rsd.pdf
>=20
> Gonca has been invited to present her findings in the IRTF Open Meeting
> during IETF-86, March 10-15, 2013 in Orlando, FL, USA. Join her there!
>=20
> The other three ANRP winners of 2013 will be announced before IETF-87
> and IETF-88, respectively.
>=20
> The call for ANRP nominations for the 2014 awards cycle will open in the
> fall of 2013. Read more about the ANRP at http://irtf.org/anrp.
>=20
> Please subscribe to the IRTF-Announce mailing list in order to receive
> future calls for ANRP nominations and join ISOC to stay informed of
> other networking research initiatives:
>=20
> http://irtf.org/mailman/listinfo/irtf-announce
> http://isoc.org/join
>=20
> Regards,
>=20
> Lars Eggert, IRTF Chair            http://irtf.org/anrp
> Mat Ford, Internet Society         http://isoc.org/research
>=20
> --
>=20
> 2013 ANRP Selection Committee
>=20
> Mark Allman, ICIR
> Marcelo Bagnulo, UC3M
> Lou Berger, LabN
> Olivier Bonaventure, UCL Louvain
> Ross Callon, Juniper
> Lars Eggert, NetApp
> Olivier Festor, INRIA
> Mat Ford, ISOC
> Lisandro Granville, UFRGS
> Volker Hilt, Bell Labs
> Suresh Krishnan, Ericsson
> Dan Massey, Colorado State
> Al Morton, AT&T Laboratories
> J=F6rg Ott, Aalto University
> Colin Perkins, University of Glasgow
> Stefano Previdi, Cisco
> J=FCrgen Sch=F6nw=E4lder, Jacobs University Bremen
> Yang Richard Yang, Yale
> Lixia Zhang, UCLA


From petithug@acm.org  Tue Jan 22 08:02:53 2013
Return-Path: <petithug@acm.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DC24721F89A3 for <ietf@ietfa.amsl.com>; Tue, 22 Jan 2013 08:02:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.6
X-Spam-Level: 
X-Spam-Status: No, score=-102.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
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 NCq4Ga2S8Il3 for <ietf@ietfa.amsl.com>; Tue, 22 Jan 2013 08:02:53 -0800 (PST)
Received: from implementers.org (implementers.org [IPv6:2604:3400:dc1:41:216:3eff:fe5b:8240]) by ietfa.amsl.com (Postfix) with ESMTP id 03DCC21F8960 for <ietf@ietf.org>; Tue, 22 Jan 2013 08:02:53 -0800 (PST)
Received: from [IPv6:2601:9:4b80:32:4d92:4f6a:39f2:445d] (unknown [IPv6:2601:9:4b80:32:4d92:4f6a:39f2:445d]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (Client CN "Marc Petit-Huguenin", Issuer "implementers.org" (verified OK)) by implementers.org (Postfix) with ESMTPS id 484C320416; Tue, 22 Jan 2013 16:02:51 +0000 (UTC)
Message-ID: <50FEB838.400@acm.org>
Date: Tue, 22 Jan 2013 08:03:04 -0800
From: Marc Petit-Huguenin <petithug@acm.org>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.12) Gecko/20130116 Icedove/10.0.12
MIME-Version: 1.0
To: William Jordan <wjordan129@gmail.com>
Subject: Re: A modest proposal
References: <CAPJ9He0dOttM+DmpUt9MzfWEXcs+tbpJJy4Z+usoRroyAdzJbA@mail.gmail.com>
In-Reply-To: <CAPJ9He0dOttM+DmpUt9MzfWEXcs+tbpJJy4Z+usoRroyAdzJbA@mail.gmail.com>
X-Enigmail-Version: 1.4.1
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 22 Jan 2013 16:02:54 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On 01/21/2013 08:57 PM, William Jordan wrote:
> I've recent had to write a program to interface with a SIP lync server and
> in doing so have had to code to several rfcs.  After reading and dealing
> with implementation of the various rfcs I have read I have come up with
> what I consider "A modest proposal" to fix some of the problems I've seen
> with implementing a rfc.  I think anyone who writes a rfc should have to
> provide a working ANSI/C or GNU/C implementation of the rfc in question.
> Specifically, I have worked with the SIP rfc (rfc 3261) and have come to
> the conclusion that whoever wrote the rfc has never coded a day in their
> life.  Whoever thought it was a good idea to allow multiple ways of doing
> the same exact thing would hopefully be deterred by actually writing code
> to do it.  I think a suitable punishment for those people would be to write
> each way of writing a from header on a blackboard 100 times... this would
> actually be less of the pain they've cause by making each writer of a SIP
> stack handle each possible way of doing things.
> 
> Anyways, that is my modest proposal, please respond or I will be forced to
> reply every day to this mailing list on each and every way the SIP spec
> sucks one email at a time.  FYI I'm not sure if GNU/C is the correct
> acronym, maybe its POSIX/C.
> 

SIP is an RFC so there is nothing that can be done here.  If you want to help,
choose one or more Internet-Drafts, *fully* implement them and report the
problems you find to the Working Group.  I also went through the full 5 steps
of grief over the death of my hope of having a good time implementing IETF
protocols and that's the best way I found of ensuring that RFCs do not suck at
implementation time.

- -- 
Marc Petit-Huguenin
Email: marc@petit-huguenin.org
Blog: http://blog.marc.petit-huguenin.org
Profile: http://www.linkedin.com/in/petithug
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iQIcBAEBCAAGBQJQ/rg2AAoJECnERZXWan7EDoAP/1R5eEvy+RRACs5FfQ6ZzS4y
33FuGscGOQn+1D3vftUPTrQA5CyyFBqHbahYIJ4xODVkgyRM4U2OExMxcAZJ/b5t
YB7M+rpMxxozcwhBUrP+OgTiMHqh0b8sVzcDrb3bQ7mdkgyYXXcEvwEd+hzeQm58
vyaivz7WW5U9Y4dXev1/nsEaN4Wm2gGCHsxtk4rZAT6IHouTF0gDTRSLGKZbiZ0q
0wuMg9WjnlEH8qIqOEIA+6cIUQLvC7tQD8TXVxEC9BsUs7kHFcs7jMpcrfxALnfc
pDg4KtoyCbKzWhxVNJm+6Rgu4goEkX3Gx/Piptjs6jG4gwzdRYVWzIu0MYSZ1EM3
87bSUaf4lKlcn6kedfYuCAwAlkvdQYzelciGgP/hekhi4UZ7uf7G3rMPqJPdqsU0
l1vT+9liE8I5F7KrKo7jrUiTnGL1poSgwBFme5CAZXp9Z4nDQeQSAB3RVYPYWxbV
3ndmycW5OSSqpmNqno1BKWXF2UdYPVgKl4i7yVz4GWQiyK+XIftm4mQm4UYmSNbW
pJGi44w5lU0Ky8sjatOr/c0pkwqw0v4s6vx8SuTUO5uhRCHUKAvXFg0SHPJgZvYY
IrMXBEz2vRN91YbjhEqtZm2XhGTHIn7ZtR1JaKxq8ZGT1Y2D0fvgd0DIYyjmMt0R
8zIycA3AnZIy+nM4gsfo
=1GcK
-----END PGP SIGNATURE-----

From jgunn6@csc.com  Tue Jan 22 08:29:14 2013
Return-Path: <jgunn6@csc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8A1C021F8AC8; Tue, 22 Jan 2013 08:29:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.598
X-Spam-Level: 
X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, 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 3Sn0JbXoW-Wd; Tue, 22 Jan 2013 08:29:13 -0800 (PST)
Received: from mail85.messagelabs.com (mail85.messagelabs.com [216.82.241.211]) by ietfa.amsl.com (Postfix) with ESMTP id 9B81821F8A71; Tue, 22 Jan 2013 08:29:13 -0800 (PST)
X-Env-Sender: jgunn6@csc.com
X-Msg-Ref: server-2.tower-85.messagelabs.com!1358872150!17739627!1
X-Originating-IP: [20.137.2.88]
X-StarScan-Received: 
X-StarScan-Version: 6.7; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 9334 invoked from network); 22 Jan 2013 16:29:12 -0000
Received: from amer-mta102.csc.com (HELO amer-mta102.csc.com) (20.137.2.88) by server-2.tower-85.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 22 Jan 2013 16:29:12 -0000
Received: from amer-gw09.amer.csc.com (amer-gw09.amer.csc.com [20.6.39.245]) by amer-mta102.csc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id r0MGT63W011928; Tue, 22 Jan 2013 11:29:09 -0500
In-Reply-To: <CAPJ9He0dOttM+DmpUt9MzfWEXcs+tbpJJy4Z+usoRroyAdzJbA@mail.gmail.com>
References: <CAPJ9He0dOttM+DmpUt9MzfWEXcs+tbpJJy4Z+usoRroyAdzJbA@mail.gmail.com>
To: William Jordan <wjordan129@gmail.com>
MIME-Version: 1.0
Subject: Re: A modest proposal
X-KeepSent: 6AC84813:FB0E6206-85257AFB:005A7979; type=4; name=$KeepSent
X-Mailer: Lotus Notes Release 8.5.2FP4 SHF97 March 26, 2012
From: Janet P Gunn <jgunn6@csc.com>
Message-ID: <OF6AC84813.FB0E6206-ON85257AFB.005A7979-85257AFB.005A8E39@csc.com>
Date: Tue, 22 Jan 2013 11:29:04 -0500
X-MIMETrack: Serialize by Router on AMER-GW09/SRV/CSC(Release 8.5.2FP3 HF204|September 20, 2011) at 01/22/2013 11:24:07 AM, Serialize complete at 01/22/2013 11:24:07 AM
Content-Type: multipart/alternative; boundary="=_alternative 005A8E1C85257AFB_="
Cc: ietf-bounces@ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 22 Jan 2013 16:29:14 -0000

This is a multipart message in MIME format.
--=_alternative 005A8E1C85257AFB_=
Content-Type: text/plain; charset="US-ASCII"

Do none of you know what the phrase "a modest proposal" refers to?

Try googling it.

Janet


ietf-bounces@ietf.org wrote on 01/21/2013 11:57:22 PM:

> From: William Jordan <wjordan129@gmail.com>
> To: ietf@ietf.org
> Date: 01/22/2013 12:01 AM
> Subject: A modest proposal
> Sent by: ietf-bounces@ietf.org
> 
> I've recent had to write a program to interface with a SIP lync 
> server and in doing so have had to code to several rfcs.  After 
> reading and dealing with implementation of the various rfcs I have 
> read I have come up with what I consider "A modest proposal" to fix 
> some of the problems I've seen with implementing a rfc.  I think 
> anyone who writes a rfc should have to provide a working ANSI/C or 
> GNU/C implementation of the rfc in question.  Specifically, I have 
> worked with the SIP rfc (rfc 3261) and have come to the conclusion 
> that whoever wrote the rfc has never coded a day in their life. 
>  Whoever thought it was a good idea to allow multiple ways of doing 
> the same exact thing would hopefully be deterred by actually writing
> code to do it.  I think a suitable punishment for those people would
> be to write each way of writing a from header on a blackboard 100 
> times... this would actually be less of the pain they've cause by 
> making each writer of a SIP stack handle each possible way of doing 
things.
> 
> Anyways, that is my modest proposal, please respond or I will be 
> forced to reply every day to this mailing list on each and every way
> the SIP spec sucks one email at a time.  FYI I'm not sure if GNU/C 
> is the correct acronym, maybe its POSIX/C.
> 
> Regards,
> Bill
--=_alternative 005A8E1C85257AFB_=
Content-Type: text/html; charset="US-ASCII"

<font size=2 face="sans-serif"><br>
Do none of you know what the phrase &quot;a modest proposal&quot; refers
to?</font>
<br>
<br><font size=2 face="sans-serif">Try googling it.</font>
<br>
<br><font size=2 face="sans-serif">Janet</font>
<br>
<br>
<br><tt><font size=2>ietf-bounces@ietf.org wrote on 01/21/2013 11:57:22
PM:<br>
<br>
&gt; From: William Jordan &lt;wjordan129@gmail.com&gt;</font></tt>
<br><tt><font size=2>&gt; To: ietf@ietf.org</font></tt>
<br><tt><font size=2>&gt; Date: 01/22/2013 12:01 AM</font></tt>
<br><tt><font size=2>&gt; Subject: A modest proposal</font></tt>
<br><tt><font size=2>&gt; Sent by: ietf-bounces@ietf.org</font></tt>
<br><tt><font size=2>&gt; <br>
&gt; I've recent had to write a program to interface with a SIP lync <br>
&gt; server and in doing so have had to code to several rfcs. &nbsp;After
<br>
&gt; reading and dealing with implementation of the various rfcs I have
<br>
&gt; read I have come up with what I consider &quot;A modest proposal&quot;
to fix <br>
&gt; some of the problems I've seen with implementing a rfc. &nbsp;I think
<br>
&gt; anyone who writes a rfc should have to provide a working ANSI/C or
<br>
&gt; GNU/C implementation of the rfc in question. &nbsp;Specifically, I
have <br>
&gt; worked with the SIP rfc (rfc 3261) and have come to the conclusion
<br>
&gt; that whoever wrote the rfc has never coded a day in their life. <br>
&gt; &nbsp;Whoever thought it was a good idea to allow multiple ways of
doing <br>
&gt; the same exact thing would hopefully be deterred by actually writing<br>
&gt; code to do it. &nbsp;I think a suitable punishment for those people
would<br>
&gt; be to write each way of writing a from header on a blackboard 100
<br>
&gt; times... this would actually be less of the pain they've cause by
<br>
&gt; making each writer of a SIP stack handle each possible way of doing
things.</font></tt>
<br><tt><font size=2>&gt; <br>
&gt; Anyways, that is my modest proposal, please respond or I will be <br>
&gt; forced to reply every day to this mailing list on each and every way<br>
&gt; the SIP spec sucks one email at a time. &nbsp;FYI I'm not sure if
GNU/C <br>
&gt; is the correct acronym, maybe its POSIX/C.</font></tt>
<br><tt><font size=2>&gt; <br>
&gt; Regards,</font></tt>
<br><tt><font size=2>&gt; Bill</font></tt>
--=_alternative 005A8E1C85257AFB_=--

From touch@isi.edu  Tue Jan 22 08:40:14 2013
Return-Path: <touch@isi.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CEDE821F894E for <ietf@ietfa.amsl.com>; Tue, 22 Jan 2013 08:40:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 bsiRu2Ws6E7j for <ietf@ietfa.amsl.com>; Tue, 22 Jan 2013 08:40:14 -0800 (PST)
Received: from vapor.isi.edu (vapor.isi.edu [128.9.64.64]) by ietfa.amsl.com (Postfix) with ESMTP id 5202021F8863 for <ietf@ietf.org>; Tue, 22 Jan 2013 08:40:14 -0800 (PST)
Received: from [192.168.1.81] (pool-71-105-87-221.lsanca.dsl-w.verizon.net [71.105.87.221]) (authenticated bits=0) by vapor.isi.edu (8.13.8/8.13.8) with ESMTP id r0MGdIZG003666 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 22 Jan 2013 08:39:30 -0800 (PST)
Message-ID: <50FEC0B8.8060905@isi.edu>
Date: Tue, 22 Jan 2013 08:39:20 -0800
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:17.0) Gecko/20130107 Thunderbird/17.0.2
MIME-Version: 1.0
To: adrian@olddog.co.uk
Subject: Re: FW: Last Call: <draft-farrell-ft-03.txt> (A Fast-Track way to RFC with Running Code) to Experimental RFC
References: <017001cdf017$c394df00$4abe9d00$@olddog.co.uk>
In-Reply-To: <017001cdf017$c394df00$4abe9d00$@olddog.co.uk>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 22 Jan 2013 16:40:14 -0000

Hi, all,

On 1/11/2013 8:21 AM, Adrian Farrel wrote:
> Hi Alexa,
>
> Please be aware of this document that has just entered a four-week IETF last
> call. The document describes a proposed IETF process experiment under the rules
> of RFC 3933.
>
> The proposed experiment calls on the IETF Secretariat to take specific actions
> under certain circumstances in corner cases of the experiment. C

This is a silly idea.

First, running code should already be considered as part of the context 
of review.

Second, running code is not correlated to correctness, appropriateness, 
or safety. See Linux for numerous examples.

Third, running code doesn't mean the doc is sufficient that multiple 
parties can generate interoperable instances. It's merely the sound of 
one hand clapping ;-)

Finally, NOTHING should circumvent the multi-tiered review process. That 
process helps reduce the burden on the community at large via the 
presumption that smaller groups with more context have already reviewed 
proposals before they get to the broader community.

This is a bad idea even as an experiment.

Joe

From stephen.farrell@cs.tcd.ie  Tue Jan 22 09:01:07 2013
Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4E5E721F84F2 for <ietf@ietfa.amsl.com>; Tue, 22 Jan 2013 09:01:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 knad+p37CZGo for <ietf@ietfa.amsl.com>; Tue, 22 Jan 2013 09:01:06 -0800 (PST)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) by ietfa.amsl.com (Postfix) with ESMTP id B6F3821F8A27 for <ietf@ietf.org>; Tue, 22 Jan 2013 09:01:06 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id 032E0BE56; Tue, 22 Jan 2013 17:00:45 +0000 (GMT)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id B3rXZjp2O8ah; Tue, 22 Jan 2013 17:00:43 +0000 (GMT)
Received: from [IPv6:2001:770:10:203:f478:ae35:d564:74e7] (unknown [IPv6:2001:770:10:203:f478:ae35:d564:74e7]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id D603ABDDC; Tue, 22 Jan 2013 17:00:43 +0000 (GMT)
Message-ID: <50FEC5BC.7030405@cs.tcd.ie>
Date: Tue, 22 Jan 2013 17:00:44 +0000
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130106 Thunderbird/17.0.2
MIME-Version: 1.0
To: Joe Touch <touch@isi.edu>
Subject: Re: FW: Last Call: <draft-farrell-ft-03.txt> (A Fast-Track way to RFC with Running Code) to Experimental RFC
References: <017001cdf017$c394df00$4abe9d00$@olddog.co.uk> <50FEC0B8.8060905@isi.edu>
In-Reply-To: <50FEC0B8.8060905@isi.edu>
X-Enigmail-Version: 1.5
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: adrian@olddog.co.uk, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 22 Jan 2013 17:01:07 -0000

Hi Joe,

On 01/22/2013 04:39 PM, Joe Touch wrote:
> Hi, all,
> 
> On 1/11/2013 8:21 AM, Adrian Farrel wrote:
>> Hi Alexa,
>>
>> Please be aware of this document that has just entered a four-week
>> IETF last
>> call. The document describes a proposed IETF process experiment under
>> the rules
>> of RFC 3933.
>>
>> The proposed experiment calls on the IETF Secretariat to take specific
>> actions
>> under certain circumstances in corner cases of the experiment. C
> 
> This is a silly idea.

So you're in two minds about it eh:-)

> 
> First, running code should already be considered as part of the context
> of review.
> 
> Second, running code is not correlated to correctness, appropriateness,
> or safety. See Linux for numerous examples.
> 
> Third, running code doesn't mean the doc is sufficient that multiple
> parties can generate interoperable instances. It's merely the sound of
> one hand clapping ;-)

Your second and third and points seem opposed to your first.
The latter ones imply that running code is useless, the first
one says its not.

I don't believe any of us have any quantitative basis on which to
base assertions that this will improve or dis-improve our processes
or output, or be neutral. (Hence proposing it as an experiment.)

> Finally, NOTHING should circumvent the multi-tiered review process. That
> process helps reduce the burden on the community at large via the
> presumption that smaller groups with more context have already reviewed
> proposals before they get to the broader community.

I disagree with the shouted "NOTHING" - if there are non-silly
ways in which we figure we can improve our processes then we
ought be open to trying 'em out. You may or may not be right
that this is silly, but merely asserting that it is doesn't
make it so.

Being stuck with current processes or only ever adding more
review tiers would IMO be sillier than this proposal. But
that seems to be where we're mostly at.

> This is a bad idea even as an experiment.

Sorry, I don't get the "bad" aspect - rhetoric aside, in what
way do you see running this experiment doing harm?

S.

> 
> Joe
> 
> 

From touch@isi.edu  Tue Jan 22 09:15:08 2013
Return-Path: <touch@isi.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F2F0E21F8956 for <ietf@ietfa.amsl.com>; Tue, 22 Jan 2013 09:15:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 FPjtCFncjiqA for <ietf@ietfa.amsl.com>; Tue, 22 Jan 2013 09:15:07 -0800 (PST)
Received: from vapor.isi.edu (vapor.isi.edu [128.9.64.64]) by ietfa.amsl.com (Postfix) with ESMTP id EF3BA21F895B for <ietf@ietf.org>; Tue, 22 Jan 2013 09:15:01 -0800 (PST)
Received: from [192.168.1.81] (pool-71-105-87-221.lsanca.dsl-w.verizon.net [71.105.87.221]) (authenticated bits=0) by vapor.isi.edu (8.13.8/8.13.8) with ESMTP id r0MHE7QU011895 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 22 Jan 2013 09:14:17 -0800 (PST)
Message-ID: <50FEC8E2.1060007@isi.edu>
Date: Tue, 22 Jan 2013 09:14:10 -0800
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:17.0) Gecko/20130107 Thunderbird/17.0.2
MIME-Version: 1.0
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Subject: Re: FW: Last Call: <draft-farrell-ft-03.txt> (A Fast-Track way to RFC with Running Code) to Experimental RFC
References: <017001cdf017$c394df00$4abe9d00$@olddog.co.uk> <50FEC0B8.8060905@isi.edu> <50FEC5BC.7030405@cs.tcd.ie>
In-Reply-To: <50FEC5BC.7030405@cs.tcd.ie>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: adrian@olddog.co.uk, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 22 Jan 2013 17:15:08 -0000

On 1/22/2013 9:00 AM, Stephen Farrell wrote:
>
> Hi Joe,
>
> On 01/22/2013 04:39 PM, Joe Touch wrote:
...
>> This is a silly idea.
>
> So you're in two minds about it eh:-)
>
>>
>> First, running code should already be considered as part of the context
>> of review.
>>
>> Second, running code is not correlated to correctness, appropriateness,
>> or safety. See Linux for numerous examples.
>>
>> Third, running code doesn't mean the doc is sufficient that multiple
>> parties can generate interoperable instances. It's merely the sound of
>> one hand clapping ;-)
>
> Your second and third and points seem opposed to your first.
> The latter ones imply that running code is useless, the first
> one says its not.

I never said "useless"; I explained several ways in which it alone is 
correlated to any of the issues relevant to speeding up the review process.

Multiple interoperable implementations helps ensure a doc sufficiently 
describes a protocol - nothing less, but also NOTHING MORE.

> I don't believe any of us have any quantitative basis on which to
> base assertions that this will improve or dis-improve our processes
> or output, or be neutral. (Hence proposing it as an experiment.)

It takes more than an "unknown" to make an experiment. There has to be 
an hypothesis. Near as I can tell, yours is "running code means it's OK 
to run concurrent review at multiple levels".

Please explain why you think that is true. I gave multiple reasons why 
it is not.

>> Finally, NOTHING should circumvent the multi-tiered review process. That
>> process helps reduce the burden on the community at large via the
>> presumption that smaller groups with more context have already reviewed
>> proposals before they get to the broader community.
>
> I disagree with the shouted "NOTHING" - if there are non-silly
> ways in which we figure we can improve our processes then we
> ought be open to trying 'em out. You may or may not be right
> that this is silly, but merely asserting that it is doesn't
> make it so.
>
> Being stuck with current processes or only ever adding more
> review tiers would IMO be sillier than this proposal. But
> that seems to be where we're mostly at.

OK, so let's try an experiment where authors with the first name 
"Stephen" pay everyone $1,000 to review their docs. It certainly hasn't 
been tried, so - by your metric - it's worth considering?

Some things are simply not.

>> This is a bad idea even as an experiment.
>
> Sorry, I don't get the "bad" aspect - rhetoric aside, in what
> way do you see running this experiment doing harm?

It puts more work on the community at large to review an idea that could 
have been either rejected or significantly improved in a smaller 
community before wasting the larger communities time.

This document is a prime example of such.

Joe

From stephen.farrell@cs.tcd.ie  Tue Jan 22 09:40:18 2013
Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6EE7921F8A4A for <ietf@ietfa.amsl.com>; Tue, 22 Jan 2013 09:40:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 ylNKNoFCHYhV for <ietf@ietfa.amsl.com>; Tue, 22 Jan 2013 09:40:17 -0800 (PST)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) by ietfa.amsl.com (Postfix) with ESMTP id 8625121F8A1E for <ietf@ietf.org>; Tue, 22 Jan 2013 09:40:17 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id 9E46ABE35; Tue, 22 Jan 2013 17:39:55 +0000 (GMT)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8WAndmTV2C1t; Tue, 22 Jan 2013 17:39:50 +0000 (GMT)
Received: from [IPv6:2001:770:10:203:f478:ae35:d564:74e7] (unknown [IPv6:2001:770:10:203:f478:ae35:d564:74e7]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 5A785BE38; Tue, 22 Jan 2013 17:39:50 +0000 (GMT)
Message-ID: <50FECEE6.2070804@cs.tcd.ie>
Date: Tue, 22 Jan 2013 17:39:50 +0000
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130106 Thunderbird/17.0.2
MIME-Version: 1.0
To: Joe Touch <touch@isi.edu>
Subject: Re: FW: Last Call: <draft-farrell-ft-03.txt> (A Fast-Track way to RFC with Running Code) to Experimental RFC
References: <017001cdf017$c394df00$4abe9d00$@olddog.co.uk> <50FEC0B8.8060905@isi.edu> <50FEC5BC.7030405@cs.tcd.ie> <50FEC8E2.1060007@isi.edu>
In-Reply-To: <50FEC8E2.1060007@isi.edu>
X-Enigmail-Version: 1.5
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: adrian@olddog.co.uk, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 22 Jan 2013 17:40:18 -0000

On 01/22/2013 05:14 PM, Joe Touch wrote:
> 
> 
> On 1/22/2013 9:00 AM, Stephen Farrell wrote:
>>
>> Hi Joe,
>>
>> On 01/22/2013 04:39 PM, Joe Touch wrote:
> ...
>>> This is a silly idea.
>>
>> So you're in two minds about it eh:-)
>>
>>>
>>> First, running code should already be considered as part of the context
>>> of review.
>>>
>>> Second, running code is not correlated to correctness, appropriateness,
>>> or safety. See Linux for numerous examples.
>>>
>>> Third, running code doesn't mean the doc is sufficient that multiple
>>> parties can generate interoperable instances. It's merely the sound of
>>> one hand clapping ;-)
>>
>> Your second and third and points seem opposed to your first.
>> The latter ones imply that running code is useless, the first
>> one says its not.
> 
> I never said "useless"; 

That's how I interpreted one hand clapping.

> I explained several ways in which it alone is
> correlated to any of the issues relevant to speeding up the review process.

I can't parse the above. But sure, there are many things
that running code does not do, and for which running code
is insufficient. Some of those are noted in the draft.

> 
> Multiple interoperable implementations helps ensure a doc sufficiently
> describes a protocol - nothing less, but also NOTHING MORE.

Multiple interoperable implementations are not required for
PS or experimental RFCs. Perhaps you've misread something.
Or perhaps there is some other process-experiment that you'd
prefer we try that's not this one? If so, writing a draft
would be the way to go.

>> I don't believe any of us have any quantitative basis on which to
>> base assertions that this will improve or dis-improve our processes
>> or output, or be neutral. (Hence proposing it as an experiment.)
> 
> It takes more than an "unknown" to make an experiment. There has to be
> an hypothesis. Near as I can tell, yours is "running code means it's OK
> to run concurrent review at multiple levels".
> 
> Please explain why you think that is true. I gave multiple reasons why
> it is not.

The above is an oversimplification of what the draft proposes
but see below.

> 
>>> Finally, NOTHING should circumvent the multi-tiered review process. That
>>> process helps reduce the burden on the community at large via the
>>> presumption that smaller groups with more context have already reviewed
>>> proposals before they get to the broader community.
>>
>> I disagree with the shouted "NOTHING" - if there are non-silly
>> ways in which we figure we can improve our processes then we
>> ought be open to trying 'em out. You may or may not be right
>> that this is silly, but merely asserting that it is doesn't
>> make it so.
>>
>> Being stuck with current processes or only ever adding more
>> review tiers would IMO be sillier than this proposal. But
>> that seems to be where we're mostly at.
> 
> OK, so let's try an experiment where authors with the first name
> "Stephen" pay everyone $1,000 to review their docs. It certainly hasn't
> been tried, so - by your metric - it's worth considering?
> 
> Some things are simply not.

Rhetoric to the fore then.

Feel free to cut the text above this line if responding;-)

>>> This is a bad idea even as an experiment.
>>
>> Sorry, I don't get the "bad" aspect - rhetoric aside, in what
>> way do you see running this experiment doing harm?
> 
> It puts more work on the community at large to review an idea that could
> have been either rejected or significantly improved in a smaller
> community before wasting the larger communities time.

The proposal actually doesn't formally change what's required
of a WG before a publication request. So I think you're just
incorrect there.

You would perhaps have been correct had you argued that the
proposal might speed things up and hence give the community
less time for review. But seeing if such a speed-up happens
and whether that has other good or bad impacts under these
conditions is an explicit goal of the experiment.

I'm guessing we just disagree about the likelihood that
going faster under these conditions might improve or
dis-improve things. But that's ok. If we get to run the
experiment we might find out. If the draft doesn't become
an RFC, then we won't.

S.

> 
> This document is a prime example of such.
> 
> Joe
> 
> 

From joelja@bogus.com  Tue Jan 22 10:01:35 2013
Return-Path: <joelja@bogus.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 241DB21F8A05; Tue, 22 Jan 2013 10:01:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 5h7gyp9jYDZ4; Tue, 22 Jan 2013 10:01:34 -0800 (PST)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id 8AF7A21F8A03; Tue, 22 Jan 2013 10:01:34 -0800 (PST)
Received: from joels-MacBook-Air.local (host-64-47-153-50.masergy.com [64.47.153.50]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id r0MI1RJY058536 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT); Tue, 22 Jan 2013 18:01:28 GMT (envelope-from joelja@bogus.com)
Message-ID: <50FED3F2.9030407@bogus.com>
Date: Tue, 22 Jan 2013 10:01:22 -0800
From: joel jaeggli <joelja@bogus.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:18.0) Gecko/20121128 Thunderbird/18.0
MIME-Version: 1.0
To: Janet P Gunn <jgunn6@csc.com>
Subject: Re: A modest proposal
References: <CAPJ9He0dOttM+DmpUt9MzfWEXcs+tbpJJy4Z+usoRroyAdzJbA@mail.gmail.com> <OF6AC84813.FB0E6206-ON85257AFB.005A7979-85257AFB.005A8E39@csc.com>
In-Reply-To: <OF6AC84813.FB0E6206-ON85257AFB.005A7979-85257AFB.005A8E39@csc.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (nagasaki.bogus.com [147.28.0.81]); Tue, 22 Jan 2013 18:01:28 +0000 (UTC)
Cc: ietf-bounces@ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 22 Jan 2013 18:01:35 -0000

On 1/22/13 8:29 AM, Janet P Gunn wrote:
>
> Do none of you know what the phrase "a modest proposal" refers to?
>
We should kill and eat more internet drafts before they  reach one year 
of age.
> Try googling it.
>
> Janet
>
>
> ietf-bounces@ietf.org wrote on 01/21/2013 11:57:22 PM:
>
> > From: William Jordan <wjordan129@gmail.com>
> > To: ietf@ietf.org
> > Date: 01/22/2013 12:01 AM
> > Subject: A modest proposal
> > Sent by: ietf-bounces@ietf.org
> >
> > I've recent had to write a program to interface with a SIP lync
> > server and in doing so have had to code to several rfcs.  After
> > reading and dealing with implementation of the various rfcs I have
> > read I have come up with what I consider "A modest proposal" to fix
> > some of the problems I've seen with implementing a rfc.  I think
> > anyone who writes a rfc should have to provide a working ANSI/C or
> > GNU/C implementation of the rfc in question.  Specifically, I have
> > worked with the SIP rfc (rfc 3261) and have come to the conclusion
> > that whoever wrote the rfc has never coded a day in their life.
> >  Whoever thought it was a good idea to allow multiple ways of doing
> > the same exact thing would hopefully be deterred by actually writing
> > code to do it.  I think a suitable punishment for those people would
> > be to write each way of writing a from header on a blackboard 100
> > times... this would actually be less of the pain they've cause by
> > making each writer of a SIP stack handle each possible way of doing 
> things.
> >
> > Anyways, that is my modest proposal, please respond or I will be
> > forced to reply every day to this mailing list on each and every way
> > the SIP spec sucks one email at a time.  FYI I'm not sure if GNU/C
> > is the correct acronym, maybe its POSIX/C.
> >
> > Regards,
> > Bill 


From daedulus@btconnect.com  Tue Jan 22 10:05:51 2013
Return-Path: <daedulus@btconnect.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6F5F421F8A64 for <ietf@ietfa.amsl.com>; Tue, 22 Jan 2013 10:05:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.099
X-Spam-Level: 
X-Spam-Status: No, score=-5.099 tagged_above=-999 required=5 tests=[AWL=1.500,  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 zZhzSWoGkhPP for <ietf@ietfa.amsl.com>; Tue, 22 Jan 2013 10:05:50 -0800 (PST)
Received: from tx2outboundpool.messaging.microsoft.com (tx2ehsobe005.messaging.microsoft.com [65.55.88.15]) by ietfa.amsl.com (Postfix) with ESMTP id A1E7921F8A61 for <ietf@ietf.org>; Tue, 22 Jan 2013 10:05:50 -0800 (PST)
Received: from mail69-tx2-R.bigfish.com (10.9.14.242) by TX2EHSOBE011.bigfish.com (10.9.40.31) with Microsoft SMTP Server id 14.1.225.23; Tue, 22 Jan 2013 18:05:49 +0000
Received: from mail69-tx2 (localhost [127.0.0.1])	by mail69-tx2-R.bigfish.com (Postfix) with ESMTP id 5A02B200183; Tue, 22 Jan 2013 18:05:49 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.249.85; KIP:(null); UIP:(null); IPV:NLI; H:AMSPRD0710HT002.eurprd07.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: -21
X-BigFish: PS-21(zzbb2dI9371I1b0bI542I1432Izz1ee6h1de0h1202h1e76h1d1ah1d2ahzz1033IL8275bh8275dhz2dh2a8h5a9h668h839h947hd24hf0ah1177h1179h1288h12a5h12a9h12bdh137ah139eh13b6h1441h1504h1537h162dh1631h1758h17f1h184fh1898h18e1h304l1155h)
Received: from mail69-tx2 (localhost.localdomain [127.0.0.1]) by mail69-tx2 (MessageSwitch) id 1358877946898402_28040; Tue, 22 Jan 2013 18:05:46 +0000 (UTC)
Received: from TX2EHSMHS014.bigfish.com (unknown [10.9.14.254])	by mail69-tx2.bigfish.com (Postfix) with ESMTP id D4D6A48005B; Tue, 22 Jan 2013 18:05:46 +0000 (UTC)
Received: from AMSPRD0710HT002.eurprd07.prod.outlook.com (157.56.249.85) by TX2EHSMHS014.bigfish.com (10.9.99.114) with Microsoft SMTP Server (TLS) id 14.1.225.23; Tue, 22 Jan 2013 18:05:46 +0000
Received: from AMXPRD0111HT004.eurprd01.prod.exchangelabs.com (157.56.250.117) by pod51017.outlook.com (10.255.160.165) with Microsoft SMTP Server (TLS) id 14.16.257.4; Tue, 22 Jan 2013 18:05:44 +0000
Message-ID: <00fc01cdf8ca$bb17e500$4001a8c0@gateway.2wire.net>
From: t.p. <daedulus@btconnect.com>
To: Janet P Gunn <jgunn6@csc.com>
References: <CAPJ9He0dOttM+DmpUt9MzfWEXcs+tbpJJy4Z+usoRroyAdzJbA@mail.gmail.com> <OF6AC84813.FB0E6206-ON85257AFB.005A7979-85257AFB.005A8E39@csc.com>
Subject: Re: A modest proposal
Date: Tue, 22 Jan 2013 18:02:56 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Originating-IP: [157.56.250.117]
X-OriginatorOrg: btconnect.com
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 22 Jan 2013 18:05:51 -0000

----- Original Message -----
From: "Janet P Gunn" <jgunn6@csc.com>
To: "William Jordan" <wjordan129@gmail.com>
Cc: <ietf-bounces@ietf.org>; <ietf@ietf.org>
Sent: Tuesday, January 22, 2013 4:29 PM
Subject: Re: A modest proposal


> Do none of you know what the phrase "a modest proposal" refers to?
>
> Try googling it.

Or else look through the archives; Margaret explained it very clearly on
August 1st, 2011.

Tom Petch

>
> Janet
>
>
> ietf-bounces@ietf.org wrote on 01/21/2013 11:57:22 PM:
>
> > From: William Jordan <wjordan129@gmail.com>
> > To: ietf@ietf.org
> > Date: 01/22/2013 12:01 AM
> > Subject: A modest proposal
> > Sent by: ietf-bounces@ietf.org
> >
> > I've recent had to write a program to interface with a SIP lync
> > server and in doing so have had to code to several rfcs.  After
> > reading and dealing with implementation of the various rfcs I have
> > read I have come up with what I consider "A modest proposal" to fix
> > some of the problems I've seen with implementing a rfc.  I think
> > anyone who writes a rfc should have to provide a working ANSI/C or
> > GNU/C implementation of the rfc in question.  Specifically, I have
> > worked with the SIP rfc (rfc 3261) and have come to the conclusion
> > that whoever wrote the rfc has never coded a day in their life.
> >  Whoever thought it was a good idea to allow multiple ways of doing
> > the same exact thing would hopefully be deterred by actually writing
> > code to do it.  I think a suitable punishment for those people would
> > be to write each way of writing a from header on a blackboard 100
> > times... this would actually be less of the pain they've cause by
> > making each writer of a SIP stack handle each possible way of doing
> things.
> >
> > Anyways, that is my modest proposal, please respond or I will be
> > forced to reply every day to this mailing list on each and every way
> > the SIP spec sucks one email at a time.  FYI I'm not sure if GNU/C
> > is the correct acronym, maybe its POSIX/C.
> >
> > Regards,
> > Bill



From john@jlc.net  Tue Jan 22 11:04:14 2013
Return-Path: <john@jlc.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EE63C21F8A7B for <ietf@ietfa.amsl.com>; Tue, 22 Jan 2013 11:04:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 4a1WXhAHTATk for <ietf@ietfa.amsl.com>; Tue, 22 Jan 2013 11:04:14 -0800 (PST)
Received: from mailhost.jlc.net (mailhost.jlc.net [199.201.159.4]) by ietfa.amsl.com (Postfix) with ESMTP id CC3DA21F8A45 for <ietf@ietf.org>; Tue, 22 Jan 2013 11:04:13 -0800 (PST)
Received: by mailhost.jlc.net (Postfix, from userid 104) id D504833D57; Tue, 22 Jan 2013 14:04:13 -0500 (EST)
Date: Tue, 22 Jan 2013 14:04:13 -0500
From: John Leslie <john@jlc.net>
To: Joe Touch <touch@isi.edu>
Subject: Re: FW: Last Call: <draft-farrell-ft-03.txt> (A Fast-Track way to RFC with Running Code) to Experimental RFC
Message-ID: <20130122190413.GD92335@verdi>
References: <017001cdf017$c394df00$4abe9d00$@olddog.co.uk> <50FEC0B8.8060905@isi.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <50FEC0B8.8060905@isi.edu>
User-Agent: Mutt/1.4.1i
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 22 Jan 2013 19:04:15 -0000

Joe Touch <touch@isi.edu> wrote:
> On 1/11/2013 8:21 AM, Adrian Farrel wrote:
>>
>> The proposed experiment calls on the IETF Secretariat to take specific 
>> actions under certain circumstances in corner cases of the experiment.

   Specifically:
] 
] 8. If at any point in the fast-track process the responsbile AD does 
]    not act in a timely fashion then the IESG Secretary should ensure 
]    that the draft enters IESG evaluation and is scheduled for the 
]    the soonest IESG telechat that is more than one week after the 
]    end of the two-week post-IETF LC period.  That is, if the 
]    responsible AD does not act, then the default action applies 
]    which is that the draft enters IESG evaluation and is placed on 
]    the earliest IESG telechat. 

   I honestly don't know who or what the "IESG Secretary" might be:
several of us have assumed this is a typo, and "Secretariat" was
intended.

   (There is one mention of "Secretariat" in the draft, but it speaks
of what WG Chairs must do, not what the Secretariat should do.)

> This is a silly idea.

   Assuming that Joe refers to the item quoted above, I find myself
forced to agree with Joe (which is scary ;^)...

   (There is, BTW, an email address <iesg-secretary@ietf.org>, which
feeds into an automated ticket-generation system. I have been asked
not to respond to it because it tends to get overloaded.)

   If we actually wanted the Secretariat to take the actions listed
above, they would need an automated tool to "discover" the inaction
of the AD involved. From the paragraph above, I frankly have no idea
how to program such a tool.

   "Enters IESG evaluation" is a simple state variable, mostly harmless.
"Scheduled" for an IESG telechat is a little vague. Usually this means
creating a "ballot" where each IESG member can enter a "position," but
there are other ways to get on the agenda.

   Who gets to decide whether this paragraph calls upon the Secretariat
to create that ballot?

   What time-limit applies between adding the item to the agenda and
the actual start of the telechat? I have seen items appear _after_
the "FINAL Agenda" is posted the afternoon before (and have done my
best to discourage such a practice).

> First, running code should already be considered as part of the context 
> of review.

   Considered how?

> Second, running code is not correlated to correctness, appropriateness, 
> or safety. See Linux for numerous examples.

   Exactly! Evaluating the correlation of running code to the printed
standard-to-be is a long-winded process.

> Third, running code doesn't mean the doc is sufficient that multiple 
> parties can generate interoperable instances. It's merely the sound of 
> one hand clapping ;-)

   Here I disagree with Joe (familiar territory!) -- the existence of
one open-source implementation decidely helps other implementors to
produce interoperable instances.

   (Alas, at the same time it tends to hide ambiguities of the spec.)

> Finally, NOTHING should circumvent the multi-tiered review process.
> That process helps reduce the burden on the community at large via
> the presumption that smaller groups with more context have already
> reviewed proposals before they get to the broader community.

   This "multi-tiered review process" is somewhat mythical. To the
extent it actually exists, I believe it benefits us; but accomplishing
it in limited time is iffy at best.

> This is a bad idea even as an experiment.

   I'd like to call folks' attention to one paragraph in the Introduction:
] 
] In summary, this experiment collapses three stages of the publication 
] process to run concurrently: working group last call, AD review, and 
] IETF last call.  Additionally, the experiment will only require 
] issues raised during these three stages to be addressed if they meet 
] the IESG's Discuss criteria.  The former is not formally a process 
] change, although it is a change to the normal conventions.  The 
] latter is a process change and requires this experiment to be run 
] under the auspices of [RFC3933].

   All the other verbiage aside, _this_ is the point of the experiment:
to remove any implied requirement to respond to LastCall comments that
don't meet (current?) IESG Discuss criteria. (There is, fortunately,
a normative reference to these, but being a web-page, one wonders if
it will be entirely stable...)

   It is unreasonable to expect every commenter to read that web-page;
and I can testify that IESG members sometimes disagree on how it should
be interpreted. In practice, I believe this change will mean that the
effort now spent responding to comments from respected IETFers will
tend to be replaced by justifying why no response is needed. :^(

   To me, it seems unfortunate we should even be "experimenting" with
paying less attention to comments from the more-experienced IETFers.
The existence of "running code" doesn't make evaluation simpler. :^(

   I wonder if we might do better to encourage the "Experimental"
status for potential standards _with_ running code, and distribute
the evaluation during the period of experiment (rather than try to
squeeze "enough" evaluation into IETF-wide LastCall).

====
   Quoting from RFC 2026:
] 
] A Proposed Standard specification is generally stable, has resolved
] known design choices, is believed to be well-understood, has received
] significant community review, and appears to enjoy enough community
] interest to be considered valuable...

   Will this still be true under this proposed experiment?

] A Proposed Standard should have no known technical omissions with
] respect to the requirements placed upon it. However, the IESG may
] waive this requirement in order to allow a specification to advance
] to the Proposed Standard state when it is considered to be useful and
] necessary (and timely) even with known technical omissions.

   I would feel less nervous about this experiment were it to include
a specific IESG action to waive the "no known technical omissions"
clause.

--
John Leslie <john@jlc.net>

From johnl@iecc.com  Tue Jan 22 11:21:11 2013
Return-Path: <johnl@iecc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BF4BA21F8A91 for <ietf@ietfa.amsl.com>; Tue, 22 Jan 2013 11:21:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -108.785
X-Spam-Level: 
X-Spam-Status: No, score=-108.785 tagged_above=-999 required=5 tests=[BAYES_40=-0.185, HABEAS_ACCREDITED_SOI=-4.3, RCVD_IN_BSP_TRUSTED=-4.3, USER_IN_WHITELIST=-100]
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 asdZSmnHHlVX for <ietf@ietfa.amsl.com>; Tue, 22 Jan 2013 11:21:11 -0800 (PST)
Received: from leila.iecc.com (leila6.iecc.com [IPv6:2001:470:1f07:1126:0:4c:6569:6c61]) by ietfa.amsl.com (Postfix) with ESMTP id E20B621F8A8F for <ietf@ietf.org>; Tue, 22 Jan 2013 11:21:10 -0800 (PST)
Received: (qmail 52576 invoked from network); 22 Jan 2013 19:21:09 -0000
Received: from leila.iecc.com (64.57.183.34) by mail1.iecc.com with QMQP; 22 Jan 2013 19:21:09 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:vbr-info; s=50fee6a5.xn--yuvv84g.k1301; i=johnl@user.iecc.com; bh=zEXGOQ4p9ZrVD7syquvo9jUHhwRVl7x4kKZW9YXUpTo=; b=JGILu4nGkbiSG8b4yr0PlnTR3aVGDA+UE8TZV/SvhbQFc4Q3ERsf8TjtDn+6UROitWRz72iTiyAfYPjKj2Bb8pVJ06CrqGdM8cGAvvO8b9646eODJwD77MPzSiykVLvD475Qy7Z5Rg7Ez2WBgtdLF6Ob0HkU8B0Sf24d3Tyrkx4=
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:vbr-info; s=50fee6a5.xn--yuvv84g.k1301; olt=johnl@user.iecc.com; bh=zEXGOQ4p9ZrVD7syquvo9jUHhwRVl7x4kKZW9YXUpTo=; b=X13hXZ4qvhXS6EtglkNmUwbJ1etRjq3jMdH2KdaDsNRJo6UY5Yg9gmn7ry8j13XDudPP/uma9P8WaB8PihErUh2NxlUeDNEtCPrP9kpAU10DmVkAsuRJc5YSx1R7ijRlkETPje0sPdXBWsA3gP+r5zo/uEqPmi+4BIw2t6Gx1jQ=
VBR-Info: md=iecc.com; mc=all; mv=dwl.spamhaus.org
Date: 22 Jan 2013 19:20:47 -0000
Message-ID: <20130122192047.82541.qmail@joyce.lan>
From: "John Levine" <johnl@taugh.com>
To: ietf@ietf.org
Subject: Re: A modest proposal
In-Reply-To: <OF6AC84813.FB0E6206-ON85257AFB.005A7979-85257AFB.005A8E39@csc.com>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 22 Jan 2013 19:21:12 -0000

>Do none of you know what the phrase "a modest proposal" refers to?

No, but I'm sure that this will be a Great Leap Forward.


From narten@us.ibm.com  Tue Jan 22 13:31:28 2013
Return-Path: <narten@us.ibm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ADB1521F8956 for <ietf@ietfa.amsl.com>; Tue, 22 Jan 2013 13:31:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.599
X-Spam-Level: 
X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
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 DjCTGOPr-Ke9 for <ietf@ietfa.amsl.com>; Tue, 22 Jan 2013 13:31:28 -0800 (PST)
Received: from e9.ny.us.ibm.com (e9.ny.us.ibm.com [32.97.182.139]) by ietfa.amsl.com (Postfix) with ESMTP id B956B21F8942 for <ietf@ietf.org>; Tue, 22 Jan 2013 13:31:27 -0800 (PST)
Received: from /spool/local by e9.ny.us.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for <ietf@ietf.org> from <narten@us.ibm.com>; Tue, 22 Jan 2013 16:31:26 -0500
Received: from d01dlp03.pok.ibm.com (9.56.250.168) by e9.ny.us.ibm.com (192.168.1.109) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted;  Tue, 22 Jan 2013 16:31:25 -0500
Received: from d01relay03.pok.ibm.com (d01relay03.pok.ibm.com [9.56.227.235]) by d01dlp03.pok.ibm.com (Postfix) with ESMTP id E917CC90026 for <ietf@ietf.org>; Tue, 22 Jan 2013 16:31:23 -0500 (EST)
Received: from d01av02.pok.ibm.com (d01av02.pok.ibm.com [9.56.224.216]) by d01relay03.pok.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id r0MLVNlg296130 for <ietf@ietf.org>; Tue, 22 Jan 2013 16:31:23 -0500
Received: from d01av02.pok.ibm.com (loopback [127.0.0.1]) by d01av02.pok.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP id r0MLVN9b029545 for <ietf@ietf.org>; Tue, 22 Jan 2013 19:31:23 -0200
Received: from cichlid.raleigh.ibm.com (sig-9-65-237-235.mts.ibm.com [9.65.237.235]) by d01av02.pok.ibm.com (8.14.4/8.13.1/NCO v10.0 AVin) with ESMTP id r0MLVMm2029435 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 22 Jan 2013 19:31:23 -0200
Received: from cichlid.raleigh.ibm.com (localhost.localdomain [127.0.0.1]) by cichlid.raleigh.ibm.com (8.14.5/8.12.5) with ESMTP id r0MLVK8C015116; Tue, 22 Jan 2013 16:31:20 -0500
Message-Id: <201301222131.r0MLVK8C015116@cichlid.raleigh.ibm.com>
To: Joe Touch <touch@isi.edu>
Subject: Re: FW: Last Call: <draft-farrell-ft-03.txt> (A Fast-Track way to RFC with Running Code) to Experimental RFC
In-reply-to: <50FEC0B8.8060905@isi.edu>
References: <017001cdf017$c394df00$4abe9d00$@olddog.co.uk> <50FEC0B8.8060905@isi.edu>
Comments: In-reply-to Joe Touch <touch@isi.edu> message dated "Tue, 22 Jan 2013 08:39:20 -0800."
Date: Tue, 22 Jan 2013 16:31:20 -0500
From: Thomas Narten <narten@us.ibm.com>
X-Content-Scanned: Fidelis XPS MAILER
x-cbid: 13012221-7182-0000-0000-000004A1A454
Cc: adrian@olddog.co.uk, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 22 Jan 2013 21:31:28 -0000

FWIW, I share Joe's concerns. And Stephen's responses don't really
change my mind.

This document seems to have a bit of missing the forest for the
trees. In the overall scheme of things, I don't believe the draft will
materially help, and is at best a distraction from dealing with
meaningful problems.

The crux of the issue is that any attempt at "fast tracking" is
fundamentally about short-circuiting some aspect of our review
processes. We should only do that very carefully. In almost all cases,
individual judgement is needed as to when it is appropriate to do
that. ADs/WG chairs already have some flexibility here. e.g., a WG can
skip WG LC if they think its not needed.  And nothing stops an AD from
going to WGLC before doing a careful review. But I'd rather that be
done because the case at hand justifies such an optimization, not
because there is some "running code" checkmark that allows a special
case to be fast tracked..

This document risks substituting process for judgement. I'd rather see
more of the latter and less of the former.

Some specifics from the doc:

>    In summary this experiment collapses three stages of the publication
>    process to run concurrently: working group last call, AD review, and
>    IETF last call.  Additionally, the experiment will only require

IMO, it is almost never appropriate to collapse WG LC and IETF LC. In
cases where it is appropriate to do so, there presumably isn't a need
for a WG LC to start with.  And an AD has always been able to start an
IETF LC without doing a detailed review. The point, is judgement is
needed, and all such cases are best handled on a case-by-case
basis. 

Surely, we don't need a document to justify doing this in those cases
where it makes sense...

>    IETF last call.  Additionally, the experiment will only require
>    issues raised during these three stages to be addressed if they meet
>    the IESG's Discuss criteria.  The former is not formally a
>    process

and later:

>    4.  Only comments that would be "DISCUSS-worthy" according to the
>        IESG Discuss Criteria [DCRIT] need be handled during last call.
>        Other comments can be handled or not, at the authors/editors
>        discretion.

The above can easily become a way to dismiss legitimate review
comments. No doubt, when a AD or reviewer suggests "this needs
fixing", the proponents will hold up this document and say "you
shouldn't do this, per the RFC -- you're violating the spirit of this
document, only really really critical stuff needs to get addressed..."
No thanks. That is not what the IETF is about.

If it is really urgent to get a document done, it is far better to
take steps to make sure the editors are engaged and responsive. That
is more likely the real issue!!!

>    It is understood that the savings in time for the end-to-end delivery
>    of a proposed standard or experimental RFC may be modest, however,
>    the modifications to normal IETF process will also serve as an
>    indication of the importance that the IETF places in running code.

Running code is valuable. Always has been, always will be. But we need
to resist the temptation of making "running code" more equal than
other criteria or putting it on a pedestal as some sort of holy
grail. Running code by itself is just a sound bite. The importance of
running code is what it tells us about a protocol specification. Just
the mere fact that there is running code doesn't mean there is
anything particularly enlightening to learn from an
implementation. For example, "running code" of a router function in
software doesn't necessarily say anything as to whether the code can
be implemented efficiently using ASICs, which may be the real
requirement.

> 
>    5.  The responsible AD for the WG concerned makes the decision as to
>        whether changes are required as a result of review comments, and
>        determines whether or not those have been completed.  If
>        significant change or extended discussion is required, or if
>        changes are not complete within two weeks after the end of fast-
>        track last call, then the draft is returned to the WG by the
>        responsible AD and the document is withdrawn from the experiment.

The two week figure is too stringent. The above is too prescriptive to
be practical. For starters, how will the IESG telechat align with the
ending of LC? Or what if an IESG member issues a defer (or will those
be disallowed?).

Section 4 has a bit too much detail and process in it. I'm sure it has
both too much and too little actually. I.e., it probably misses some
corner cases, and then what do you do given how prescriptive the rest
of the section is?

But overall, I see this document at best as a no-op. However, I fear
that it can be used to short-circuit our review processes in a way
that doesn't help the IETF and that won't really speed things up
enough to justify the downsides.

Thomas


From Jeff.Hodges@KingsMountain.com  Tue Jan 22 13:45:08 2013
Return-Path: <Jeff.Hodges@KingsMountain.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3644621F8818 for <ietf@ietfa.amsl.com>; Tue, 22 Jan 2013 13:45:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.321
X-Spam-Level: 
X-Spam-Status: No, score=-102.321 tagged_above=-999 required=5 tests=[AWL=-0.056, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, USER_IN_WHITELIST=-100]
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 eC9yJyyitNgf for <ietf@ietfa.amsl.com>; Tue, 22 Jan 2013 13:45:07 -0800 (PST)
Received: from oproxy9.bluehost.com (oproxy9.bluehost.com [69.89.24.6]) by ietfa.amsl.com (Postfix) with SMTP id 8614A21F86BE for <ietf@ietf.org>; Tue, 22 Jan 2013 13:45:06 -0800 (PST)
Received: (qmail 29779 invoked by uid 0); 22 Jan 2013 21:44:44 -0000
Received: from unknown (HELO box514.bluehost.com) (74.220.219.114) by oproxy9.bluehost.com with SMTP; 22 Jan 2013 21:44:44 -0000
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=kingsmountain.com; s=default;  h=Content-Transfer-Encoding:Content-Type:Subject:CC:To:MIME-Version:From:Date:Message-ID; bh=lwSoGqHLxupsI90ovAAsHrAfEGeCuidxYDle7sxcHCs=;  b=pd4sLwgQ4tDxn7GNmWoMwmHb3QQZjClIufO96kqe0VlMeC/lITVTMIy6V3HJUULc7AVcFcdNEwg9tDwl/92DVwl4hMzEmm6wdgn35RPiufTIjnZTTHb/3iUE2P2OKNzi;
Received: from [216.113.168.128] (port=45136 helo=[10.244.137.234]) by box514.bluehost.com with esmtpsa (TLSv1:CAMELLIA256-SHA:256) (Exim 4.80) (envelope-from <Jeff.Hodges@KingsMountain.com>) id 1Txle7-0007BP-NF; Tue, 22 Jan 2013 14:44:43 -0700
Message-ID: <50FF084B.5040508@KingsMountain.com>
Date: Tue, 22 Jan 2013 13:44:43 -0800
From: =JeffH <Jeff.Hodges@KingsMountain.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130106 Thunderbird/17.0.2
MIME-Version: 1.0
To: Ben Laurie <benl@google.com>
Subject: Re: LC comments on draft-laurie-pki-sunlight-05 - "acceptable root certificates" ?
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Identified-User: {11025:box514.bluehost.com:kingsmou:kingsmountain.com} {sentby:smtp auth 216.113.168.128 authed with jeff.hodges+kingsmountain.com}
Cc: Emilia Kasper <ekasper@google.com>, "therightkey@ietf.org" <therightkey@ietf.org>, IETF Discussion List <ietf@ietf.org>, Adam Langley <agl@google.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 22 Jan 2013 21:45:08 -0000

<snip>

 >>> 3.1. Log Entries
 >>>
 >>>    Anyone can submit a certificate to any log.  In order to enable
 >>>    attribution of each logged certificate to its issuer, the log SHALL
 >>>    publish a list of acceptable root certificates (this list might
 >>>    usefully be the union of root certificates trusted by major browser
 >>>    vendors).  Each submitted certificate MUST be accompanied by all
 >>>    additional certificates required to verify the certificate chain up
 >>>    to an accepted root certificate.  The root certificate itself MAY be
 >>>    omitted from this list.

a question I neglected to add here is: how do log services publish their lists 
of "acceptable root certificates" ?


=JeffH



From stephen.farrell@cs.tcd.ie  Tue Jan 22 14:12:05 2013
Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 400B021F89DC for <ietf@ietfa.amsl.com>; Tue, 22 Jan 2013 14:12:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.524
X-Spam-Level: 
X-Spam-Status: No, score=-102.524 tagged_above=-999 required=5 tests=[AWL=0.075, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 56KXH9FAMsrd for <ietf@ietfa.amsl.com>; Tue, 22 Jan 2013 14:12:04 -0800 (PST)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) by ietfa.amsl.com (Postfix) with ESMTP id 80EAE21F89CE for <ietf@ietf.org>; Tue, 22 Jan 2013 14:12:04 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id 804B6BE57; Tue, 22 Jan 2013 22:11:41 +0000 (GMT)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 99Dcdp2X-av9; Tue, 22 Jan 2013 22:11:40 +0000 (GMT)
Received: from [10.87.48.12] (unknown [86.42.26.104]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 92ECEBE3C; Tue, 22 Jan 2013 22:11:40 +0000 (GMT)
Message-ID: <50FF0E9C.1010808@cs.tcd.ie>
Date: Tue, 22 Jan 2013 22:11:40 +0000
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130106 Thunderbird/17.0.2
MIME-Version: 1.0
To: Joe Touch <touch@isi.edu>
Subject: Re: FW: Last Call: <draft-farrell-ft-03.txt> (A Fast-Track way to RFC with Running Code) to Experimental RFC
References: <017001cdf017$c394df00$4abe9d00$@olddog.co.uk> <50FEC0B8.8060905@isi.edu> <50FEC5BC.7030405@cs.tcd.ie> <50FEC8E2.1060007@isi.edu>
In-Reply-To: <50FEC8E2.1060007@isi.edu>
X-Enigmail-Version: 1.5
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: adrian@olddog.co.uk, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 22 Jan 2013 22:12:05 -0000

Hiya,

On 01/22/2013 05:14 PM, Joe Touch wrote:
> 
> It puts more work on the community at large to review an idea that could
> have been either rejected or significantly improved in a smaller
> community before wasting the larger communities time.

Actually it occurs to me that there might be something
here of note (while continuing to disagree with you about
the overall idea)...

If we do the experiment and a draft changes significantly
during last-call based on new comments from someone active
in the relevant WG then that would imply that either that
draft wasn't suited for fast-tracking or perhaps that
the experiment indicates a problem with fast-tracking.

I'd be surprised if that happens at all to be honest,
unless lots of WGs choose to try the experiment, but it
could.

I don't think there's really a high probability that a
draft from a WG will be "rejected" - almost all docs
that get to the start of WGLC tend to arrive at the IESG
as far as I can see, though I'm sure there'll be some WG
that operates differently.

S.

From stephen.farrell@cs.tcd.ie  Tue Jan 22 14:36:14 2013
Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B7F7E21F875C for <ietf@ietfa.amsl.com>; Tue, 22 Jan 2013 14:36:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.539
X-Spam-Level: 
X-Spam-Status: No, score=-102.539 tagged_above=-999 required=5 tests=[AWL=0.060, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 3xtajGkDC4qX for <ietf@ietfa.amsl.com>; Tue, 22 Jan 2013 14:36:13 -0800 (PST)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) by ietfa.amsl.com (Postfix) with ESMTP id 6264821F874B for <ietf@ietf.org>; Tue, 22 Jan 2013 14:36:13 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id 85E49BE50; Tue, 22 Jan 2013 22:35:51 +0000 (GMT)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YVl2gN7rsxlu; Tue, 22 Jan 2013 22:35:50 +0000 (GMT)
Received: from [10.87.48.12] (unknown [86.42.26.104]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id D5DA2BE4D; Tue, 22 Jan 2013 22:35:49 +0000 (GMT)
Message-ID: <50FF1445.4010809@cs.tcd.ie>
Date: Tue, 22 Jan 2013 22:35:49 +0000
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130106 Thunderbird/17.0.2
MIME-Version: 1.0
To: Thomas Narten <narten@us.ibm.com>
Subject: Re: FW: Last Call: <draft-farrell-ft-03.txt> (A Fast-Track way to RFC with Running Code) to Experimental RFC
References: <017001cdf017$c394df00$4abe9d00$@olddog.co.uk> <50FEC0B8.8060905@isi.edu> <201301222131.r0MLVK8C015116@cichlid.raleigh.ibm.com>
In-Reply-To: <201301222131.r0MLVK8C015116@cichlid.raleigh.ibm.com>
X-Enigmail-Version: 1.5
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: adrian@olddog.co.uk, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 22 Jan 2013 22:36:14 -0000

Hi Thomas,

On 01/22/2013 09:31 PM, Thomas Narten wrote:
> FWIW, I share Joe's concerns. And Stephen's responses don't really
> change my mind.

Ah well. I'm willing to keep trying:-)

> This document seems to have a bit of missing the forest for the
> trees. In the overall scheme of things, I don't believe the draft will
> materially help, and is at best a distraction from dealing with
> meaningful problems.

Do you mean the experiment or if this became a permanent
part of the process? Your comments read as if you're concerned
mostly about the latter, and you make no mention of the
former.

As it happens, I agree that this is not going to produce
a huge improvement. But its not intended to, and modest
improvements (as opposed to modest proposals:-) should also
be ok. If not then we're in a worse process-rut than even I
think.

> The crux of the issue is that any attempt at "fast tracking" is
> fundamentally about short-circuiting some aspect of our review
> processes. 

I'd prefer s/short-circuiting/speeding-up/

> We should only do that very carefully. 

For example as an experiment? I think we are being careful.

> In almost all cases,
> individual judgement is needed as to when it is appropriate to do
> that. ADs/WG chairs already have some flexibility here. e.g., a WG can
> skip WG LC if they think its not needed.  And nothing stops an AD from
> going to WGLC before doing a careful review. But I'd rather that be
> done because the case at hand justifies such an optimization, not
> because there is some "running code" checkmark that allows a special
> case to be fast tracked..
> 
> This document risks substituting process for judgement. I'd rather see
> more of the latter and less of the former.

Disagree. The WG chairs exercise judgement to kick off the
process. The IESG exercise judgement as usual with no changes.

> 
> Some specifics from the doc:
> 
>>    In summary this experiment collapses three stages of the publication
>>    process to run concurrently: working group last call, AD review, and
>>    IETF last call.  Additionally, the experiment will only require
> 
> IMO, it is almost never appropriate to collapse WG LC and IETF LC. In
> cases where it is appropriate to do so, there presumably isn't a need
> for a WG LC to start with.  And an AD has always been able to start an
> IETF LC without doing a detailed review. The point, is judgement is
> needed, and all such cases are best handled on a case-by-case
> basis. 

What's wrong with the judgement of a set of WG chairs? AFAIK, ADs
are no wiser in general and this one is certainly dumber than a
lot of WG chairs.

> Surely, we don't need a document to justify doing this in those cases
> where it makes sense...
> 
>>    IETF last call.  Additionally, the experiment will only require
>>    issues raised during these three stages to be addressed if they meet
>>    the IESG's Discuss criteria.  The former is not formally a
>>    process
> 
> and later:
> 
>>    4.  Only comments that would be "DISCUSS-worthy" according to the
>>        IESG Discuss Criteria [DCRIT] need be handled during last call.
>>        Other comments can be handled or not, at the authors/editors
>>        discretion.
> 
> The above can easily become a way to dismiss legitimate review
> comments. 

Equally, gratuitous nit-picking can be used to try kill something
with a thousand cuts. Neither are at all common that I can see,
during IETF LC.

I think incorporating the discuss criteria should be an interesting
part of the experiment. (I've found them really helpful in reviewing
documents these last couple of years.)

> No doubt, when a AD or reviewer suggests "this needs
> fixing", the proponents will hold up this document and say "you
> shouldn't do this, per the RFC -- you're violating the spirit of this
> document, only really really critical stuff needs to get addressed..."
> No thanks. That is not what the IETF is about.

I don't see how you get to "No doubt..." I do entirely doubt that'll
happen for most all editors.

> If it is really urgent to get a document done, it is far better to
> take steps to make sure the editors are engaged and responsive. That
> is more likely the real issue!!!

Urgency isn't a part of this. Going faster doesn't imply urgency.

> 
>>    It is understood that the savings in time for the end-to-end delivery
>>    of a proposed standard or experimental RFC may be modest, however,
>>    the modifications to normal IETF process will also serve as an
>>    indication of the importance that the IETF places in running code.
> 
> Running code is valuable. Always has been, always will be. But we need
> to resist the temptation of making "running code" more equal than
> other criteria or putting it on a pedestal as some sort of holy
> grail. 

I agree. And this draft doesn't do that. Or are you saying it does?

> Running code by itself is just a sound bite. The importance of
> running code is what it tells us about a protocol specification. Just
> the mere fact that there is running code doesn't mean there is
> anything particularly enlightening to learn from an
> implementation. For example, "running code" of a router function in
> software doesn't necessarily say anything as to whether the code can
> be implemented efficiently using ASICs, which may be the real
> requirement.

Sure. The proposal says that this won't be suitable for all drafts.
In response to other comments we had the idea of building up text
about that as part of a wiki.

>>    5.  The responsible AD for the WG concerned makes the decision as to
>>        whether changes are required as a result of review comments, and
>>        determines whether or not those have been completed.  If
>>        significant change or extended discussion is required, or if
>>        changes are not complete within two weeks after the end of fast-
>>        track last call, then the draft is returned to the WG by the
>>        responsible AD and the document is withdrawn from the experiment.
> 
> The two week figure is too stringent. 

Possibly. But I think its a useful quid-pro-quo - if the authors
want fast track review but aren't willing to do fast edits then I
think they ought not get fast-track review.

I think the timers in general are something that an experiment
may show to be ok or not. And if not, then changing 'em would
be easy if we wanted to continue this after the experiment.

> The above is too prescriptive to
> be practical. For starters, how will the IESG telechat align with the
> ending of LC? 

That's covered in the draft. Could be it needs to be better
stated. (Basically, next telechat that's more than one week
after the authors have done their changes, if they got those
done within the two weeks after the end of LC.)

> Or what if an IESG member issues a defer (or will those
> be disallowed?).

No change there. IESG evaluation is entirely unaffected by this.
The draft says that.

> Section 4 has a bit too much detail and process in it. I'm sure it has
> both too much and too little actually. I.e., it probably misses some
> corner cases, and then what do you do given how prescriptive the rest
> of the section is?

That's fair. Its hard to get the right balance there. I think
some of that text could be better on a wiki, as discussed in
response to some earlier comments.

> But overall, I see this document at best as a no-op. However, I fear
> that it can be used to short-circuit our review processes in a way
> that doesn't help the IETF and that won't really speed things up
> enough to justify the downsides.

I think the worst case is nothing happens but that if this
does get tried, we'll learn something about our processes and
(of course:-) I reckon we ought do the experiment.

Cheers,
S.

> 
> Thomas
> 
> 
> 

From stephen.farrell@cs.tcd.ie  Tue Jan 22 14:46:39 2013
Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 279A221F892B for <ietf@ietfa.amsl.com>; Tue, 22 Jan 2013 14:46:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.549
X-Spam-Level: 
X-Spam-Status: No, score=-102.549 tagged_above=-999 required=5 tests=[AWL=0.050, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 4a4dqZ67rOzd for <ietf@ietfa.amsl.com>; Tue, 22 Jan 2013 14:46:37 -0800 (PST)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) by ietfa.amsl.com (Postfix) with ESMTP id 3B2F221F8937 for <ietf@ietf.org>; Tue, 22 Jan 2013 14:46:32 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id D57E2BE55; Tue, 22 Jan 2013 22:46:08 +0000 (GMT)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UFx-rLl59tgn; Tue, 22 Jan 2013 22:46:06 +0000 (GMT)
Received: from [10.87.48.12] (unknown [86.42.26.104]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 0DB3EBE50; Tue, 22 Jan 2013 22:46:06 +0000 (GMT)
Message-ID: <50FF16AD.4040901@cs.tcd.ie>
Date: Tue, 22 Jan 2013 22:46:05 +0000
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130106 Thunderbird/17.0.2
MIME-Version: 1.0
To: John Leslie <john@jlc.net>
Subject: Re: FW: Last Call: <draft-farrell-ft-03.txt> (A Fast-Track way to RFC with Running Code) to Experimental RFC
References: <017001cdf017$c394df00$4abe9d00$@olddog.co.uk> <50FEC0B8.8060905@isi.edu> <20130122190413.GD92335@verdi>
In-Reply-To: <20130122190413.GD92335@verdi>
X-Enigmail-Version: 1.5
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 22 Jan 2013 22:46:39 -0000

Hi John,

Bits and pieces below...

On 01/22/2013 07:04 PM, John Leslie wrote:
> Joe Touch <touch@isi.edu> wrote:
>> On 1/11/2013 8:21 AM, Adrian Farrel wrote:
>>>
>>> The proposed experiment calls on the IETF Secretariat to take specific 
>>> actions under certain circumstances in corner cases of the experiment.
> 
>    Specifically:
> ] 
> ] 8. If at any point in the fast-track process the responsbile AD does 
> ]    not act in a timely fashion then the IESG Secretary should ensure 
> ]    that the draft enters IESG evaluation and is scheduled for the 
> ]    the soonest IESG telechat that is more than one week after the 
> ]    end of the two-week post-IETF LC period.  That is, if the 
> ]    responsible AD does not act, then the default action applies 
> ]    which is that the draft enters IESG evaluation and is placed on 
> ]    the earliest IESG telechat. 
> 
>    I honestly don't know who or what the "IESG Secretary" might be:
> several of us have assumed this is a typo, and "Secretariat" was
> intended.
> 
>    (There is one mention of "Secretariat" in the draft, but it speaks
> of what WG Chairs must do, not what the Secretariat should do.)

Fair enough. I think the terms effectively mean the same set of
folks though.

> 
>> This is a silly idea.
> 
>    Assuming that Joe refers to the item quoted above, I find myself
> forced to agree with Joe (which is scary ;^)...
> 
>    (There is, BTW, an email address <iesg-secretary@ietf.org>, which
> feeds into an automated ticket-generation system. I have been asked
> not to respond to it because it tends to get overloaded.)
> 
>    If we actually wanted the Secretariat to take the actions listed
> above, they would need an automated tool to "discover" the inaction
> of the AD involved. 

Perhaps ultimately, were this to be a part of our permanent process.

> From the paragraph above, I frankly have no idea
> how to program such a tool.

"AD didn't hit button to move forward or backward"? Absent a tool,
my guess is a WG chair would complain and some other AD would tell
'em to talk to their AD or ask the secretariat to push the button.
This is very much a corner case.

>    "Enters IESG evaluation" is a simple state variable, mostly harmless.
> "Scheduled" for an IESG telechat is a little vague. Usually this means
> creating a "ballot" where each IESG member can enter a "position," but
> there are other ways to get on the agenda.
> 
>    Who gets to decide whether this paragraph calls upon the Secretariat
> to create that ballot?
> 
>    What time-limit applies between adding the item to the agenda and
> the actual start of the telechat? I have seen items appear _after_
> the "FINAL Agenda" is posted the afternoon before (and have done my
> best to discourage such a practice).

I'm not seeing the vagueness there sorry.

> 
>> First, running code should already be considered as part of the context 
>> of review.
> 
>    Considered how?
> 
>> Second, running code is not correlated to correctness, appropriateness, 
>> or safety. See Linux for numerous examples.
> 
>    Exactly! Evaluating the correlation of running code to the printed
> standard-to-be is a long-winded process.
> 
>> Third, running code doesn't mean the doc is sufficient that multiple 
>> parties can generate interoperable instances. It's merely the sound of 
>> one hand clapping ;-)
> 
>    Here I disagree with Joe (familiar territory!) -- the existence of
> one open-source implementation decidely helps other implementors to
> produce interoperable instances.
> 
>    (Alas, at the same time it tends to hide ambiguities of the spec.)
> 
>> Finally, NOTHING should circumvent the multi-tiered review process.
>> That process helps reduce the burden on the community at large via
>> the presumption that smaller groups with more context have already
>> reviewed proposals before they get to the broader community.
> 
>    This "multi-tiered review process" is somewhat mythical. To the
> extent it actually exists, I believe it benefits us; but accomplishing
> it in limited time is iffy at best.
> 
>> This is a bad idea even as an experiment.
> 
>    I'd like to call folks' attention to one paragraph in the Introduction:
> ] 
> ] In summary, this experiment collapses three stages of the publication 
> ] process to run concurrently: working group last call, AD review, and 
> ] IETF last call.  Additionally, the experiment will only require 
> ] issues raised during these three stages to be addressed if they meet 
> ] the IESG's Discuss criteria.  The former is not formally a process 
> ] change, although it is a change to the normal conventions.  The 
> ] latter is a process change and requires this experiment to be run 
> ] under the auspices of [RFC3933].
> 
>    All the other verbiage aside, _this_ is the point of the experiment:
> to remove any implied requirement to respond to LastCall comments that
> don't meet (current?) IESG Discuss criteria. (There is, fortunately,
> a normative reference to these, but being a web-page, one wonders if
> it will be entirely stable...)

Stable enough for an experiment I think. That might be something that
would need attention should we want to adopt this permanently after
the experiment I agree.

> 
>    It is unreasonable to expect every commenter to read that web-page;
> and I can testify that IESG members sometimes disagree on how it should
> be interpreted. In practice, I believe this change will mean that the
> effort now spent responding to comments from respected IETFers will
> tend to be replaced by justifying why no response is needed. :^(

I don't think that'll happen much. Maybe a little though.

>    To me, it seems unfortunate we should even be "experimenting" with
> paying less attention to comments from the more-experienced IETFers.
> The existence of "running code" doesn't make evaluation simpler. :^(

Yet, we have found these criteria valuable in IESG review, right?
I think they could be equally valuable here too.

> 
>    I wonder if we might do better to encourage the "Experimental"
> status for potential standards _with_ running code, and distribute
> the evaluation during the period of experiment (rather than try to
> squeeze "enough" evaluation into IETF-wide LastCall).
> 
> ====
>    Quoting from RFC 2026:
> ] 
> ] A Proposed Standard specification is generally stable, has resolved
> ] known design choices, is believed to be well-understood, has received
> ] significant community review, and appears to enjoy enough community
> ] interest to be considered valuable...
> 
>    Will this still be true under this proposed experiment?

I think it'll be no less true than today for documents as they
arrive at the start of IESG review.

> 
> ] A Proposed Standard should have no known technical omissions with
> ] respect to the requirements placed upon it. However, the IESG may
> ] waive this requirement in order to allow a specification to advance
> ] to the Proposed Standard state when it is considered to be useful and
> ] necessary (and timely) even with known technical omissions.
> 
>    I would feel less nervous about this experiment were it to include
> a specific IESG action to waive the "no known technical omissions"
> clause.

But IESG evaluation is unchanged.

Cheers,
S.

> 
> --
> John Leslie <john@jlc.net>
> 

From dean.willis@softarmor.com  Tue Jan 22 20:01:31 2013
Return-Path: <dean.willis@softarmor.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5199D21F8804 for <ietf@ietfa.amsl.com>; Tue, 22 Jan 2013 20:01:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.977
X-Spam-Level: 
X-Spam-Status: No, score=-102.977 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
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 2IgQKMo8BHKa for <ietf@ietfa.amsl.com>; Tue, 22 Jan 2013 20:01:30 -0800 (PST)
Received: from mail-vc0-f172.google.com (mail-vc0-f172.google.com [209.85.220.172]) by ietfa.amsl.com (Postfix) with ESMTP id 552C121F8800 for <ietf@ietf.org>; Tue, 22 Jan 2013 20:01:30 -0800 (PST)
Received: by mail-vc0-f172.google.com with SMTP id l6so6179490vcl.17 for <ietf@ietf.org>; Tue, 22 Jan 2013 20:01:29 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=softarmor.com; s=google; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=/HMmnvLQdn/bXtAOD87dAOaxB5HNUrMEpiqcld+ZsN0=; b=NMG+YaPVMZbEL4AOP+ad3oUt8rLSiF0s0opZeYqgnfDJt1EdKADiPvXddlq+m9KMhT rNHE1i4ZA5zSFGKDqbhjpy+Jo+mAqSqdFk3j0rnEu6M4/ArlMuEuvQKY/bCqaw0rMkha yzWCJd7n/++/ZeKmSuSt5bPzVv1jPWAiz0Yhs=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type:x-gm-message-state; bh=/HMmnvLQdn/bXtAOD87dAOaxB5HNUrMEpiqcld+ZsN0=; b=Zu/DQfQpdG54BaJP/wFe61X1Chv6MfVP7j08oJT4226L/GKrE/gOpjaEHMKqUAg3jP Zz2uc26XaGcVmIIcfuoG+J0k7h2tQrVzAlM/ysRbP6+KiuZ0/bGCsl3uhnZehRH/fRdf +DULgKlDUF18gkQaQDnUsH1OfQ/YUgQx023qcC8LSqpyWZZ161jMp8DJjtr+ez0C2Nfq 7p1U+NjqR0NpcvJcrK43fAh1zWlUJEY7CF6wRgBbsHIkf1cK0V5h7X7Af7+N0PAVPWdg w9NurCnqlHT00vIjFHtIyt3ny9v1J0AXqPj9hqxNEPLoljdTsxJ8xt99cYb3LLZuEdNA iwcw==
MIME-Version: 1.0
X-Received: by 10.221.10.72 with SMTP id oz8mr26365854vcb.36.1358913689422; Tue, 22 Jan 2013 20:01:29 -0800 (PST)
Received: by 10.58.152.234 with HTTP; Tue, 22 Jan 2013 20:01:29 -0800 (PST)
In-Reply-To: <CAPJ9He0dOttM+DmpUt9MzfWEXcs+tbpJJy4Z+usoRroyAdzJbA@mail.gmail.com>
References: <CAPJ9He0dOttM+DmpUt9MzfWEXcs+tbpJJy4Z+usoRroyAdzJbA@mail.gmail.com>
Date: Tue, 22 Jan 2013 22:01:29 -0600
Message-ID: <CAOHm=4txFTVM_Pm9Hi4sv=ptY7d6C+ah9uYFH6gu_9VWRoRM6Q@mail.gmail.com>
Subject: Re: A modest proposal
From: Dean Willis <dean.willis@softarmor.com>
To: William Jordan <wjordan129@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
X-Gm-Message-State: ALoCoQlTQyWjILWans2T4tH63u8VEBhbI8weZfPTJVZJ06eUN4WuUwDFPnKY427IJDpICkpwMw93
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 23 Jan 2013 04:01:31 -0000

On Mon, Jan 21, 2013 at 10:57 PM, William Jordan <wjordan129@gmail.com> wrote:

> Whoever thought it was a good idea to allow multiple ways of doing the same
> exact thing would hopefully be deterred by actually writing code to do it.
> I think a suitable punishment for those people would be to write each way of
> writing a from header on a blackboard 100 times... this would actually be
> less of the pain they've cause by making each writer of a SIP stack handle
> each possible way of doing things.

I know this because I chaired the meetings for the RFC 2543 to RFC
3261 re-write. It's even worse than you think; half of the
participants were hard-core coders, each of whom had done an
implementation (or two). The other half were philosophy or art
students, who wanted the spec to be beautiful and meaningful and true
and formally correct and all those good things. And EVERYBODY had a
conflicting understanding for what they wrote, mostly based on
fondling a different part of the elephant. I was just lazy and tried
to keep from having to rewrite too much code due to spec changes,
except of course for that parts that were totally bogus (like strict
routing).

It's called a "committee" for a reason. That's where one gets
two-headed llamas and the US federal budget. Oh wait, we don't have a
budget yet, going on three years.

--
Dean

From joelja@bogus.com  Tue Jan 22 20:14:52 2013
Return-Path: <joelja@bogus.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E944421F867D for <ietf@ietfa.amsl.com>; Tue, 22 Jan 2013 20:14:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 JXrg+u4m0oql for <ietf@ietfa.amsl.com>; Tue, 22 Jan 2013 20:14:52 -0800 (PST)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id 7860521F85D2 for <ietf@ietf.org>; Tue, 22 Jan 2013 20:14:52 -0800 (PST)
Received: from joels-MacBook-Air.local (c-24-5-127-59.hsd1.ca.comcast.net [24.5.127.59]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id r0N4EktR064907 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT); Wed, 23 Jan 2013 04:14:47 GMT (envelope-from joelja@bogus.com)
Message-ID: <50FF63B1.8080509@bogus.com>
Date: Tue, 22 Jan 2013 20:14:41 -0800
From: joel jaeggli <joelja@bogus.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:19.0) Gecko/20130117 Thunderbird/19.0
MIME-Version: 1.0
To: Hannes Tschofenig <hannes.tschofenig@gmx.net>, Melinda Shore <melinda.shore@gmail.com>
Subject: Re: A modest proposal
References: <CAPJ9He0dOttM+DmpUt9MzfWEXcs+tbpJJy4Z+usoRroyAdzJbA@mail.gmail.com> <50FE3A37.7040402@gmail.com> <691CE879-B639-4C69-8B8D-0FC2DCB909A8@gmx.net>
In-Reply-To: <691CE879-B639-4C69-8B8D-0FC2DCB909A8@gmx.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (nagasaki.bogus.com [147.28.0.81]); Wed, 23 Jan 2013 04:14:47 +0000 (UTC)
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 23 Jan 2013 04:14:53 -0000

On 1/22/13 12:34 AM, Hannes Tschofenig wrote:
> Another example from a different area: Why do we need so many 
> transition technologies for the migration from IPv4 to IPv6? Wouldn't 
> it be less complex to just have one transition mechanism?

You mean no transition mechanisms...

From dean.willis@softarmor.com  Tue Jan 22 20:16:21 2013
Return-Path: <dean.willis@softarmor.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 82FFA21F86AF for <ietf@ietfa.amsl.com>; Tue, 22 Jan 2013 20:16:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.977
X-Spam-Level: 
X-Spam-Status: No, score=-102.977 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
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 Js3OVK29I7NF for <ietf@ietfa.amsl.com>; Tue, 22 Jan 2013 20:16:20 -0800 (PST)
Received: from mail-vc0-f180.google.com (mail-vc0-f180.google.com [209.85.220.180]) by ietfa.amsl.com (Postfix) with ESMTP id B788021F867D for <ietf@ietf.org>; Tue, 22 Jan 2013 20:16:20 -0800 (PST)
Received: by mail-vc0-f180.google.com with SMTP id fo13so2505083vcb.25 for <ietf@ietf.org>; Tue, 22 Jan 2013 20:16:20 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=softarmor.com; s=google; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=eH4b1mtPiBup5WobWT97bScPj3Gax0ftLCA4erNjT9Y=; b=Xc7TxDIWkOBJI3eHFqzmnk1/dXE+8AA0AQIXPjgU3gje4/al7c6STUFAYOKjhzTs+p W9y6K6sTZzqweO6bU2lfmwxCECFdt+bbwhjOsLGbkUp9mS1Fd1DwK2dm/aPVLC76AnDW V7gy3KTKyr7caTYcYe735BAPmFv+Bonrv1QVI=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type:x-gm-message-state; bh=eH4b1mtPiBup5WobWT97bScPj3Gax0ftLCA4erNjT9Y=; b=S+v0Ak7GXHwXrmslWZOFsvZ3OOdErGXOQZ8wOyYD5yEDYueqgHv745kOWWTCQKqZV5 q0FY+cuJHDzCbEHZ+mFo2vPASsJwhaW0WNgoEaDQ4tL3uoaF+Zvb6MbKojG1tCNzO0+D S0PzyeQVz8iUUvEGmnMsA0qKzAoqN4h3sa80akKjeCtXBHkBJDRcGXxQdBjLAe1lpbSf zJVVHf5h5XrI7nPZgat5cyOnpyiCUoYqB7iRpVwm+OW9BN/yp9oUVuzH3buxlyNePl3B wlgrfGko6oJS0KqngZ0ALFfHQ4Z2p8zQ9Stt80NIyPTqW7cADj1KaNKLPTAUqxHJsk+B XPXg==
MIME-Version: 1.0
X-Received: by 10.52.177.103 with SMTP id cp7mr23208184vdc.113.1358914580241;  Tue, 22 Jan 2013 20:16:20 -0800 (PST)
Received: by 10.58.152.234 with HTTP; Tue, 22 Jan 2013 20:16:20 -0800 (PST)
In-Reply-To: <CAPJ9He36PgOdwocyB0EnEqWruNGc4zzMW6ETW2im2azy7Kg0rw@mail.gmail.com>
References: <CAPJ9He36PgOdwocyB0EnEqWruNGc4zzMW6ETW2im2azy7Kg0rw@mail.gmail.com>
Date: Tue, 22 Jan 2013 22:16:20 -0600
Message-ID: <CAOHm=4tEGOeYcfp5yWD0VvhCq3Rj=cnvzynG9J6uORHqZHXcNw@mail.gmail.com>
Subject: Re: A modest proposal
From: Dean Willis <dean.willis@softarmor.com>
To: William Jordan <wjordan129@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
X-Gm-Message-State: ALoCoQm1uhcfXoynQpQhUDamjiY8ZJKcuL7q4aP/qmo9jr+INyl6ml4kFw6fvSYFHzRLGclWPlQl
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 23 Jan 2013 04:16:21 -0000

On Tue, Jan 22, 2013 at 4:11 AM, William Jordan <wjordan129@gmail.com> wrote:

> Continuing my discussion about how badly SIP is designed, I'm gonna talk
> about the via line.  First of all each via line can be expressed as via: OR
> v: OR you can have multiple via entries on the same line separated by a
> comma where random whitespaces are allowed.

Hey, we stole that stuff from HTTP. We're not smart enough to invent
something that broken. I think HTTP stole it from RFC 822.

> Additionally, I can't
> understand why each line is terminated with <CR><LF>, why use two characters
> when one will do.

Microsoft-OS text editors. Seriously. People wanted to be able to
write correct SIP messages using text editors, and there were more
Microsoft users than Linux users on the list. And we agreed because
that's the way it works in HTTP, which got it from RFC 822 (there's a
reference in the spec, so we KNOW where that came from!)

> I could also go into a design argument about how the same
> specification is used for udp as for tcp and why the idea for a stateless
> SIP proxy wasn't thrown out completely when writing the draft, but I'll wait
> on those.

Yeah, keeping both UDP and TCP was stupid. We should've just specified
TLS, but there were all these 8-bit processors out there ... and
countries where TLS was illegal. In fact, we couldn't export a TLS
stack from the US at the time without special paperwork. So, allowing
for both protocols got us "exportable" product, and "passing the IESG
security police" at the same time.

Stateless proxies were seen as key performance enablers. Our high-end
super-performant proxy running on a $40,000 quad-core Sun box could
only get like 8 transactions a second, so every CPU optimization was
sacred.

But hey, live and learn ...

From melinda.shore@gmail.com  Tue Jan 22 20:45:05 2013
Return-Path: <melinda.shore@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3F59F21F8800 for <ietf@ietfa.amsl.com>; Tue, 22 Jan 2013 20:45:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 mVw8Aoe8-ySy for <ietf@ietfa.amsl.com>; Tue, 22 Jan 2013 20:45:04 -0800 (PST)
Received: from mail-pa0-f43.google.com (mail-pa0-f43.google.com [209.85.220.43]) by ietfa.amsl.com (Postfix) with ESMTP id 49D5021F859A for <ietf@ietf.org>; Tue, 22 Jan 2013 20:45:04 -0800 (PST)
Received: by mail-pa0-f43.google.com with SMTP id fb10so4493326pad.2 for <ietf@ietf.org>; Tue, 22 Jan 2013 20:45:04 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=XgaXOpi0Rv0X4W9YbjLO09jlQQ/MUmC0JqvFbukNK2o=; b=jNShrtMsW0miwCtu+puMi/o4bF/g3VIW7AyJBCat6Q8t+CUnpJk8Wn1NmeJefakLLi cpBgxh9eWyTMn/bgM9XE+UI7FYsf15mTaXviIK8VBrUitk9ISK+sb2JkxMzRL2NcAFew y716gHas64M3FRM6rXfX49Sxg4QPVVmByIp91beH76zZeVz7tirjP5NMyNl3c2grNOoe GgKNkTqgowVbzjhhJ2jA4fvN6e35iY8lRwjSL2LwYliZrqYZOvyLSKMaOs11dm65oUps fkQCbgNQKt09qqzBYN1fcvwwR6VoGxCQBDrTEVvrauvtXl4YEEr05PBWMHFg4BOJ2hg2 5VEw==
X-Received: by 10.68.252.69 with SMTP id zq5mr46159575pbc.104.1358916303992; Tue, 22 Jan 2013 20:45:03 -0800 (PST)
Received: from spandex.local (66-230-112-168-rb1.fai.dsl.dynamic.acsalaska.net. [66.230.112.168]) by mx.google.com with ESMTPS id gl5sm12029309pbc.51.2013.01.22.20.45.02 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 22 Jan 2013 20:45:03 -0800 (PST)
Message-ID: <50FF6ACC.1050508@gmail.com>
Date: Tue, 22 Jan 2013 19:45:00 -0900
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130107 Thunderbird/17.0.2
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: A modest proposal
References: <CAPJ9He36PgOdwocyB0EnEqWruNGc4zzMW6ETW2im2azy7Kg0rw@mail.gmail.com> <CAOHm=4tEGOeYcfp5yWD0VvhCq3Rj=cnvzynG9J6uORHqZHXcNw@mail.gmail.com>
In-Reply-To: <CAOHm=4tEGOeYcfp5yWD0VvhCq3Rj=cnvzynG9J6uORHqZHXcNw@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 23 Jan 2013 04:45:05 -0000

On 1/22/13 7:16 PM, Dean Willis wrote:
> Microsoft-OS text editors. Seriously. People wanted to be able to
> write correct SIP messages using text editors, and there were more
> Microsoft users than Linux users on the list. 

Oh, c'mon.  MS products and MacOS at the time used CRLF for newlines
generally, not just in Word.  The fact that it was specified that way
in HTTP, SMTP, FTP, and others matters a bit, as well.

Melinda


From johnl@iecc.com  Tue Jan 22 22:16:20 2013
Return-Path: <johnl@iecc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C452021F8800 for <ietf@ietfa.amsl.com>; Tue, 22 Jan 2013 22:16:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -109.992
X-Spam-Level: 
X-Spam-Status: No, score=-109.992 tagged_above=-999 required=5 tests=[AWL=1.207, BAYES_00=-2.599, HABEAS_ACCREDITED_SOI=-4.3, RCVD_IN_BSP_TRUSTED=-4.3, USER_IN_WHITELIST=-100]
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 fMIliV8TJh1t for <ietf@ietfa.amsl.com>; Tue, 22 Jan 2013 22:16:20 -0800 (PST)
Received: from leila.iecc.com (leila6.iecc.com [IPv6:2001:470:1f07:1126:0:4c:6569:6c61]) by ietfa.amsl.com (Postfix) with ESMTP id EC73221F87FF for <ietf@ietf.org>; Tue, 22 Jan 2013 22:16:19 -0800 (PST)
Received: (qmail 15428 invoked from network); 23 Jan 2013 06:16:17 -0000
Received: from leila.iecc.com (64.57.183.34) by mail1.iecc.com with QMQP; 23 Jan 2013 06:16:17 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:vbr-info; s=50ff8031.xn--3zv.k1301; i=johnl@user.iecc.com; bh=9WujynRqMVwPZw48TLKsRwbwZkjj3+lqN10OR+LkBds=; b=WXAN4Odlotxtja349mf+xS+ONpg/deO1kBPk3FO3/yP5zhxK6YW/xlBaZ5Tes/hO1+RxeetyjP2B9j+q3RICpCRR/YxwBgLxfngnmPxRhb1dvySWlJjFchQ4fjvqntCtkQcwAcullZA3VxlrqmGQn5ZopcQXAH1L3SsI56BNEEc=
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:vbr-info; s=50ff8031.xn--3zv.k1301; olt=johnl@user.iecc.com; bh=9WujynRqMVwPZw48TLKsRwbwZkjj3+lqN10OR+LkBds=; b=CCl0j2JQAO5LSOJOQ9vNMoPX7TAeMv8FHkHMLEHigXVoZ6MvXHUHQiGAOBiFmG6Dg/62xBXOHdxuVnZd9jeoMyt18o5GlQT+U7L/0mbbeFQ5uhZqDq+FI/qNij9tY9aJs40RfU7qZUmzUBJEnk9LX5whYHgZD+jEk228S8JkpHo=
VBR-Info: md=iecc.com; mc=all; mv=dwl.spamhaus.org
Date: 23 Jan 2013 06:15:54 -0000
Message-ID: <20130123061554.85592.qmail@joyce.lan>
From: "John Levine" <johnl@taugh.com>
To: ietf@ietf.org
Subject: Re: A modest proposal
In-Reply-To: <CAOHm=4tEGOeYcfp5yWD0VvhCq3Rj=cnvzynG9J6uORHqZHXcNw@mail.gmail.com>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 7bit
Cc: dean.willis@softarmor.com
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 23 Jan 2013 06:16:20 -0000

>> Additionally, I can't understand why each line is terminated with
>> <CR><LF>, why use two characters when one will do.
>
>Microsoft-OS text editors. Seriously.

My, what a bunch of parvenus.  SIP got it from SMTP, SMTP got it from
Telnet.  Back in the 1960s we all used <CR><LF> because on a
mechanical model 33 or 35 Teletype, CR really returned the carriage,
LF really advanced the platen, and you needed both.  I first ran into
CR/LF on a PDP-6 in about 1968, but I know it wasn't new then.

A single LF to start a new line arrived with the model 37 Teletype,
and Unix was, as far as I know, the first system to use just \n as the
line terminator starting in the early 1970s.  But by then the Arpanet
protocols were designed, and the hassle of changing wasn't (and still
isn't) worth it.


From peter@akayla.com  Tue Jan 22 22:52:08 2013
Return-Path: <peter@akayla.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 13CE421F8804 for <ietf@ietfa.amsl.com>; Tue, 22 Jan 2013 22:52:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.299
X-Spam-Level: 
X-Spam-Status: No, score=-0.299 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MANGLED_LIST=2.3]
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 O7pJCH4sqCds for <ietf@ietfa.amsl.com>; Tue, 22 Jan 2013 22:52:07 -0800 (PST)
Received: from p3plsmtpa01-02.prod.phx3.secureserver.net (p3plsmtpa01-02.prod.phx3.secureserver.net [72.167.82.82]) by ietfa.amsl.com (Postfix) with SMTP id 022CC21F87FE for <ietf@ietf.org>; Tue, 22 Jan 2013 22:52:06 -0800 (PST)
Received: (qmail 7172 invoked from network); 23 Jan 2013 06:52:06 -0000
Received: from unknown (173.8.184.78) by p3plsmtpa01-02.prod.phx3.secureserver.net (72.167.82.82) with ESMTP; 23 Jan 2013 06:52:05 -0000
From: "Peter Yee" <peter@akayla.com>
To: <draft-ietf-roll-security-threats.all@tools.ietf.org>
Subject: Gen-ART review of draft-ietf-roll-security-threats-00
Date: Tue, 22 Jan 2013 22:52:09 -0800
Message-ID: <005701cdf936$2a8434f0$7f8c9ed0$@akayla.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: Ac35Nf5BRz1aBjIsRWKCRRx50QtVgQ==
Content-Language: en-us
Cc: gen-art@ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 23 Jan 2013 06:52:08 -0000

I am the assigned Gen-ART reviewer for this draft. For background on
Gen-ART, please see the FAQ at
<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>

Please resolve these comments along with any other Last Call comments you
may receive.  (My apologies for submitting these a day late.)

Document: draft-ietf-roll-security-threats-00
Reviewer: Peter Yee
Review Date: Jan-22-2012
IETF LC End Date: Jan-21-2012
IESG Telechat date: Unknown

Summary: This draft is basically ready for publication, but has nits that
should be fixed before publication. [Ready with nits.]

This document analyzes security threats for routing in a low-power and lossy
networks.  It discusses countermeasures and operational considerations for
dealing with the threats in the design of ROLL protocols.

Major issues:

Minor issues:

Nits/editorial comments:

General: replace "low power" with "low-power" throughout the document to
match usage in other ROLL RFCs

General: replace "a LLN" with "an LLN" throughout the document.

General: there are quite a few really long, dense sentences in this
document.  They make parsing and comprehension more difficult.  I realize
that's not something terribly concrete on which you can act.

Section 1, 1st paragraph, 2nd sentence: insert "a" before "user access
interface" or consider making "interface" plural.

Section 2, definition of Node: place a comma after "power".

Section 3, 1st paragraph, 2nd sentence: since you're going to use CIA later
in the document, perhaps you would like to include integrity in this
sentence.

Section 3.1, 1st paragraph, 3rd sentence: an adjective such as "improper" or
"unauthorized" before "access" would be helpful.

Section 3.3, 5th paragraph, last sentence: make "damages" singular.

Section 4.1.1, second sentence: add a period after "etc".

Section 4.3.2, Figure 2: I'm not sure why "Falsify as Good Link to Node_5"
appears twice.  Perhaps delete one? 

Section 4.3.4, 1st paragraph, 1st sentence: add a serial comma after
"memory".

Section 5.1.4, 3rd paragraph, last sentence: add a serial comma after
"integrity".

Section 5.1.4, 6th paragraph, 1st sentence: consider mentioning FIPS 140-2
not just for device hardening but for other tamper-resistance mechanisms and
for correctness of cryptographic operations (including random number
generation).

Section 5.2.3, 2nd paragraph, 2nd sentence: consider changing "explicit and
implicit" to "explicitly and implicitly".  If not, rewrite the sentence so
it parses.

Section 5.2.3, 3rd paragraph, 2nd sentence: replace "shared key or public
key based" with "a shared key- or public key-based".

Section 5.2.4, 2nd sentence: add an "s" after "need"

Section 5.2.5, 5th paragraph: You might also wish to consider an intrusion
detection system (within the node and/or in conjunction with other nodes) as
an alternative to external audit entity.  The literature for MANETs has much
to offer in this regard.  The seminal paper is:

	Zhang, Y. & Lee, W. (2000). Intrusion detection in wireless ad-hoc
networks. Proceedings of the 6th International Conference on Mobile
Computing and Networking (MobiCom 2000), 275-283. doi:10.1145/345910.345958

Also consider:

	Liu, Y., Comaniciu, C., & Man, H. (2006).  A Bayesian game approach
for intrusion detection in wireless ad hoc networks.  Proceedings of the
2006 Workshop on Game Theory for Communications and Networks (GAMENET06).
doi:0.1145/1190195.1190198

	Li, W., Parker, J., & Joshi, A. (2012). Security through
collaboration and trust in MANETs. Mobile Networks & Applications, 17(3),
342-352. doi:10.1007/s11036-010-0243-9

Section 5.3, 1st sentence: Drop "a" before "proper".

Section 5.3.2, 1st paragraph, 1st sentence: replace "battery or energy
scavenging" with "batteries or energy scavenging".

Section 5.3.2, 1st paragraph, 2nd sentence: replace "battery" with
"energy-constrained".

Section 5.3.3, 2nd bullet item: add "ing" to "select".

Section 5.3.3, last paragraph, 2nd sentence: add "a" before "method".

Section 5.3.3, last paragraph, 2nd sentence: it's also suboptimal from a
network utilization perspective.

Section 6, 2nd paragraph, 3rd sentence: delete "that" before "do not of".

Section 6, last paragraph, last sentence: add a serial comma after
"integrity".

Section 6.1., 1st paragraph after bullet items: change "accordance of" to
"accordance with".

Section 6.2, 4th bullet item: add a comma after "increments".

Section 6.2, 1st paragraph after bullet items, 2nd sentence: add "be" before
"used".

Section 6.2, 1st paragraph after bullet items, last sentence: insert
"counting" between "as" and "against".

Section 6.4, 5th paragraph, 3rd sentence: add "ly" after "separate".

Section 6.4, 5th paragraph, 3rd sentence: remove the space in "IETF-
standard".

Section 6.4, 5th paragraph, 4th sentence: change "IKE" to "IKEv2".

Section 6.4, 5th paragraph, 4th sentence: consider changing "private" to
"secret" to avoid confusion between symmetric and asymmetric cryptograph
concepts.

Section 6.5.1, 3rd paragraph, 1st sentence: add "ly" after "independent".

Section 6.5.1, 8th paragraph, 2nd sentence: add a comma after "LLNs" for
ease of parsing.

Section 6.5.1, 9th paragraph, 1st sentence: change "extends" to "extend".

Section 6.5.2, 1st paragraph, 2nd sentence: delete ", as listed in the last
subsection," since it isn't listed there.


From peter@akayla.com  Tue Jan 22 23:10:20 2013
Return-Path: <peter@akayla.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 883F421F86C5; Tue, 22 Jan 2013 23:10:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.449
X-Spam-Level: 
X-Spam-Status: No, score=-1.449 tagged_above=-999 required=5 tests=[AWL=1.150,  BAYES_00=-2.599]
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 N+Zf23N5UfwE; Tue, 22 Jan 2013 23:10:20 -0800 (PST)
Received: from p3plsmtpa07-06.prod.phx3.secureserver.net (p3plsmtpa07-06.prod.phx3.secureserver.net [173.201.192.235]) by ietfa.amsl.com (Postfix) with ESMTP id C3F1721F868F; Tue, 22 Jan 2013 23:10:19 -0800 (PST)
Received: from spectre ([173.8.184.78]) by p3plsmtpa07-06.prod.phx3.secureserver.net with  id rKAJ1k00C1huGat01KAJ1y; Wed, 23 Jan 2013 00:10:19 -0700
From: "Peter Yee" <peter@akayla.com>
To: "'Magnus Westerlund'" <magnus.westerlund@ericsson.com>
References: <000701cde358$da44c6a0$8ece53e0$@akayla.com> <50F7D97D.2030508@ericsson.com>
In-Reply-To: <50F7D97D.2030508@ericsson.com>
Subject: RE: Gen-ART review of draft-ietf-6man-udpchecksums-06
Date: Tue, 22 Jan 2013 23:10:23 -0800
Message-ID: <005801cdf938$b6704bf0$2350e3d0$@akayla.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQEvFQgBJNYMpW9GbpA7KwYG22ColQMdPAJemXtdQYA=
Content-Language: en-us
Cc: draft-ietf-6man-udpchecksums.all@tools.ietf.org, gen-art@ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 23 Jan 2013 07:10:20 -0000

Magnus,

	Looks good to me.  My summary is now "Ready for publication".

		Kind regards,
		-Peter

-----Original Message-----
From: Magnus Westerlund [mailto:magnus.westerlund@ericsson.com]=20
Sent: Thursday, January 17, 2013 2:59 AM
To: Peter Yee
Cc: draft-ietf-6man-udpchecksums.all@tools.ietf.org; gen-art@ietf.org;
ietf@ietf.org
Subject: Re: Gen-ART review of draft-ietf-6man-udpchecksums-06

Hi Peter,

Thanks for your detailed review. An updated version has just been =
submitted
the includes fixes to your comments.

Thanks

Magnus

On 2012-12-26 12:05, Peter Yee wrote:
> I am the assigned Gen-ART reviewer for this draft. For background on=20
> Gen-ART, please see the FAQ at=20
> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>
>=20
> Please wait for direction from your document shepherd or AD before=20
> posting a new version of the draft.
>=20
> Document: draft-ietf-6man-udpchecksums-06
> Reviewer: Peter Yee
> Review Date: Dec-25-2012
> IETF LC End Date: Dec-25-2012
> IESG Telechat date: Unknown
>=20
> Summary: This draft is basically ready for publication, but has nits=20
> that should be fixed before publication. [Ready with nits.]
>=20
> This document provides an update to 2460 to allow the use of zero=20
> checksum UDP packets over IPv6 in certain cases involving protocols=20
> tunneled inside of UDP packets.
>=20
> Nits:
>=20
> General: a comma after "i.e." is preferred in American English.
>=20
> General: it is not necessary to hyphenate "misdelivered" or =
"misdelivery".
>=20
> General: put quotes around "Applicability Statement for the use of=20
> IPv6 UDP Datagrams with Zero  Checksums"
>=20
> Abstract, first sentence: "when" -> "where"
>=20
> Abstract, second sentence: "protocol" -> "protocols"
>=20
> Section 1, second paragraph, first sentence: delete the comma after=20
> "packet".
>=20
> Section 1, fourth paragraph, first sentence: move the comma in "AMT,"=20
> to after the reference.
>=20
> Section 1, fourth paragraph, last sentence: insert "the" after=20
> "applicable in".
>=20
> Section 3, second sentence: delete the first occurrence of "where".
> Consider revising the sentence for clarity.
>=20
> Section 4, second sentence: "Section" -> "Sections"
>=20
> Section 4.1, it would be nice, but not necessary to have an=20
> enumeration of the corruption modes.
>=20
> Section 4.1, third bullet item, first sentence: a verb is missing here =

> making the sentence difficult to parse.
>=20
> Section 4.1, third bullet item, first sentence: "packets" -> "packet"
>=20
> Section 4.1, third bullet item, third sub-bullet: put commas around=20
> "for example".
>=20
> Section 4.2, first bullet item, last sentence: this sentence is hard=20
> to understand; consider revising.  (See next comment)
>=20
> Section 4.2, first bullet item, last sentence: "an" -> "a" and "are"=20
> -> "is"; also not general comment about "misdelivered".
>=20
> Section 4.2, third bullet item, third sentence: "effect" -> "affect"
>=20
> Section 4.2, first paragraph after bullet items, first sentence:=20
> delete "this".
>=20
> Section 4.2, first paragraph after bullet items, third sentence:
> "mis-delievery" -> "misdelivery".
>=20
> Section 4.2, first paragraph after bullet items, third sentence:=20
> delete "that".
>=20
> Section 4.3, first sentence: "middlebox devices" -> "middleboxes"=20
> unless this a specific usage from I-D.ietf-6man-udpzero.
>=20
> Section 4.3, second sentence: "needs" -> "need"
>=20
> Section 5, first paragraph, second sentence: insert "in" after "node=20
> requirements".
>=20
> Section 5, first paragraph of replacement text, second sentence:=20
> delete "usage for", replace "some" with "certain", and replace second
"protocols"
> with "those".
>=20
> Section 5, last paragraph: delete first instance of "the".
>=20
> Section 6, first bullet item, first sentence: "corruptions" ->
"corruption"
>=20
> Section 6, second bullet item, last sentence: change "This" to =
"UDP-Lite".
>=20
> Section 8, first sentence: delete redundant "required".
>=20
>=20


--=20

Magnus Westerlund

----------------------------------------------------------------------
Multimedia Technologies, Ericsson Research EAB/TVM
----------------------------------------------------------------------
Ericsson AB                | Phone  +46 10 7148287
F=E4r=F6gatan 6                | Mobile +46 73 0949079
SE-164 80 Stockholm, Sweden| mailto: magnus.westerlund@ericsson.com
----------------------------------------------------------------------



From brian.e.carpenter@gmail.com  Tue Jan 22 23:58:39 2013
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 862EC21F8877 for <ietf@ietfa.amsl.com>; Tue, 22 Jan 2013 23:58:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.691
X-Spam-Level: 
X-Spam-Status: No, score=-101.691 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, RCVD_ILLEGAL_IP=1.908, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
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 e5s+Wt+WTpAu for <ietf@ietfa.amsl.com>; Tue, 22 Jan 2013 23:58:39 -0800 (PST)
Received: from mail-wg0-f48.google.com (mail-wg0-f48.google.com [74.125.82.48]) by ietfa.amsl.com (Postfix) with ESMTP id 5567121F86F4 for <ietf@ietf.org>; Tue, 22 Jan 2013 23:58:38 -0800 (PST)
Received: by mail-wg0-f48.google.com with SMTP id 16so1711627wgi.27 for <ietf@ietf.org>; Tue, 22 Jan 2013 23:58:37 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:organization:user-agent :mime-version:to:cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=28Wd94SF1iIpoDH9hXkLHVatE0NTCiROYK/f+njNPXU=; b=cRaHmwRHxE85oNsJAXD7RilOZrsTJGNd3dtB2w6eQkvMmZEGGITWGaBg6N0f1MmCiG 94p5WJlR+omxMGAhwZD1d7tyU50NpHG9k1L0VRtReWYAY2JJ0fIhHHC8wJhUnZ957zvx sOjs5ViyBb5tks88UBfZZK2F0YqwUw/WlOE25eLIUgBjOiRGDYXScrFJYG3dnYrMM1dB CyDsJRSmWQaix2EMJAmoXqGGf2hHL8tyeN1YAPcZbTrXY2oBzZCB3Wg/v8CiCgiw8Dj3 IReYaBWzeOk8YTZYcm5IqzR+r+DszHtVYXvVHVKuS3OilH+UyHp54/Rs6Yxw313shNBX gRJw==
X-Received: by 10.180.79.194 with SMTP id l2mr620804wix.22.1358927917446; Tue, 22 Jan 2013 23:58:37 -0800 (PST)
Received: from [192.168.1.65] (host-2-102-217-31.as13285.net. [2.102.217.31]) by mx.google.com with ESMTPS id e6sm28212226wiz.1.2013.01.22.23.58.35 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 22 Jan 2013 23:58:36 -0800 (PST)
Message-ID: <50FF9830.6010403@gmail.com>
Date: Wed, 23 Jan 2013 07:58:40 +0000
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: joel jaeggli <joelja@bogus.com>
Subject: Re: A modest proposal
References: <CAPJ9He0dOttM+DmpUt9MzfWEXcs+tbpJJy4Z+usoRroyAdzJbA@mail.gmail.com>	<50FE3A37.7040402@gmail.com>	<691CE879-B639-4C69-8B8D-0FC2DCB909A8@gmx.net> <50FF63B1.8080509@bogus.com>
In-Reply-To: <50FF63B1.8080509@bogus.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 23 Jan 2013 07:58:39 -0000

On 23/01/2013 04:14, joel jaeggli wrote:
> On 1/22/13 12:34 AM, Hannes Tschofenig wrote:
>> Another example from a different area: Why do we need so many
>> transition technologies for the migration from IPv4 to IPv6? Wouldn't
>> it be less complex to just have one transition mechanism?
> 
> You mean no transition mechanisms...

That was, in fact, the plan (dual stack during coexistence).
It went wrong.

  Brian

From hannes.tschofenig@gmx.net  Wed Jan 23 01:27:22 2013
Return-Path: <hannes.tschofenig@gmx.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B7F7121F85B3 for <ietf@ietfa.amsl.com>; Wed, 23 Jan 2013 01:27:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.98
X-Spam-Level: 
X-Spam-Status: No, score=-101.98 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_SORBS_WEB=0.619, USER_IN_WHITELIST=-100]
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 cuuxJ-4stI1S for <ietf@ietfa.amsl.com>; Wed, 23 Jan 2013 01:27:22 -0800 (PST)
Received: from mout.gmx.net (mout.gmx.net [212.227.17.21]) by ietfa.amsl.com (Postfix) with ESMTP id 0492221F86A3 for <ietf@ietf.org>; Wed, 23 Jan 2013 01:27:21 -0800 (PST)
Received: from mailout-de.gmx.net ([10.1.76.34]) by mrigmx.server.lan (mrigmx002) with ESMTP (Nemesis) id 0M7WSv-1T0lmZ3SlT-00xIuk for <ietf@ietf.org>; Wed, 23 Jan 2013 10:27:20 +0100
Received: (qmail invoked by alias); 23 Jan 2013 09:27:20 -0000
Received: from unknown (EHLO [10.255.131.154]) [194.251.119.201] by mail.gmx.net (mp034) with SMTP; 23 Jan 2013 10:27:20 +0100
X-Authenticated: #29516787
X-Provags-ID: V01U2FsdGVkX1/n3w42N5PnI667ayJKpyDKZVMG5BmsZBaJQNyAse 6z2O/8Dttc0ufB
Subject: Re: A modest proposal
Mime-Version: 1.0 (Apple Message framework v1085)
Content-Type: text/plain; charset=us-ascii
From: Hannes Tschofenig <hannes.tschofenig@gmx.net>
In-Reply-To: <50FF9830.6010403@gmail.com>
Date: Wed, 23 Jan 2013 11:27:17 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <23F5A1DB-357E-4133-A01E-2608D47D34C9@gmx.net>
References: <CAPJ9He0dOttM+DmpUt9MzfWEXcs+tbpJJy4Z+usoRroyAdzJbA@mail.gmail.com>	<50FE3A37.7040402@gmail.com>	<691CE879-B639-4C69-8B8D-0FC2DCB909A8@gmx.net> <50FF63B1.8080509@bogus.com> <50FF9830.6010403@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-Mailer: Apple Mail (2.1085)
X-Y-GMX-Trusted: 0
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 23 Jan 2013 09:27:22 -0000

Hi Brian, Hi Joel,=20

the point of my mail was not to start a discussion about the examples I =
provided but to note that the suggested "let's reduce complexity by =
reducing options" is not as easy as it sounds in practice.

In the context of the document Stephen wrote and the proposal that was =
made on the list I was wondering whether a bit more analysis about what =
the problems we are trying to solve would be helpful. As some folks had =
raised implementing specifications is not a sufficient condition for =
interoperability, or successful deployment. I personally believe that =
IETF working groups are a fine job in writing code along with their =
specification work.=20

Ciao
Hannes

On Jan 23, 2013, at 9:58 AM, Brian E Carpenter wrote:

> On 23/01/2013 04:14, joel jaeggli wrote:
>> On 1/22/13 12:34 AM, Hannes Tschofenig wrote:
>>> Another example from a different area: Why do we need so many
>>> transition technologies for the migration from IPv4 to IPv6? =
Wouldn't
>>> it be less complex to just have one transition mechanism?
>>=20
>> You mean no transition mechanisms...
>=20
> That was, in fact, the plan (dual stack during coexistence).
> It went wrong.
>=20
>  Brian


From narten@us.ibm.com  Wed Jan 23 06:11:52 2013
Return-Path: <narten@us.ibm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BB3B521F8650 for <ietf@ietfa.amsl.com>; Wed, 23 Jan 2013 06:11:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.599
X-Spam-Level: 
X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
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 bAku2G8zA5t9 for <ietf@ietfa.amsl.com>; Wed, 23 Jan 2013 06:11:52 -0800 (PST)
Received: from e31.co.us.ibm.com (e31.co.us.ibm.com [32.97.110.149]) by ietfa.amsl.com (Postfix) with ESMTP id E3EFF21F8549 for <ietf@ietf.org>; Wed, 23 Jan 2013 06:11:51 -0800 (PST)
Received: from /spool/local by e31.co.us.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for <ietf@ietf.org> from <narten@us.ibm.com>; Wed, 23 Jan 2013 07:11:50 -0700
Received: from d03dlp03.boulder.ibm.com (9.17.202.179) by e31.co.us.ibm.com (192.168.1.131) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted;  Wed, 23 Jan 2013 07:11:49 -0700
Received: from d03relay03.boulder.ibm.com (d03relay03.boulder.ibm.com [9.17.195.228]) by d03dlp03.boulder.ibm.com (Postfix) with ESMTP id 0C96F19D803C for <ietf@ietf.org>; Wed, 23 Jan 2013 07:11:48 -0700 (MST)
Received: from d03av03.boulder.ibm.com (d03av03.boulder.ibm.com [9.17.195.169]) by d03relay03.boulder.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id r0NEBWbw179616 for <ietf@ietf.org>; Wed, 23 Jan 2013 07:11:34 -0700
Received: from d03av03.boulder.ibm.com (loopback [127.0.0.1]) by d03av03.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP id r0NEApqQ002270 for <ietf@ietf.org>; Wed, 23 Jan 2013 07:10:51 -0700
Received: from cichlid.raleigh.ibm.com (sig-9-65-210-85.mts.ibm.com [9.65.210.85]) by d03av03.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVin) with ESMTP id r0NE9ejP023942 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 23 Jan 2013 07:09:41 -0700
Received: from cichlid.raleigh.ibm.com (localhost.localdomain [127.0.0.1]) by cichlid.raleigh.ibm.com (8.14.5/8.12.5) with ESMTP id r0NE2Pi2030108; Wed, 23 Jan 2013 09:02:25 -0500
Message-Id: <201301231402.r0NE2Pi2030108@cichlid.raleigh.ibm.com>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Subject: Re: FW: Last Call: <draft-farrell-ft-03.txt> (A Fast-Track way to RFC with Running Code) to Experimental RFC
In-reply-to: <50FF1445.4010809@cs.tcd.ie>
References: <017001cdf017$c394df00$4abe9d00$@olddog.co.uk> <50FEC0B8.8060905@isi.edu> <201301222131.r0MLVK8C015116@cichlid.raleigh.ibm.com> <50FF1445.4010809@cs.tcd.ie>
Comments: In-reply-to Stephen Farrell <stephen.farrell@cs.tcd.ie> message dated "Tue, 22 Jan 2013 22:35:49 +0000."
Date: Wed, 23 Jan 2013 09:02:25 -0500
From: Thomas Narten <narten@us.ibm.com>
X-Content-Scanned: Fidelis XPS MAILER
x-cbid: 13012314-7282-0000-0000-0000136F73CC
Cc: adrian@olddog.co.uk, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 23 Jan 2013 14:11:52 -0000

I do not really have time or desire to enter an extended discussion on
this document. It's pretty clear to me we just disagree. But I did
want to be on record as not supporting this document so that silence
wouldn't be taken as agreement or support.

A few specific followups below.

> > This document seems to have a bit of missing the forest for the
> > trees. In the overall scheme of things, I don't believe the draft will
> > materially help, and is at best a distraction from dealing with
> > meaningful problems.

> Do you mean the experiment or if this became a permanent
> part of the process? Your comments read as if you're concerned
> mostly about the latter, and you make no mention of the
> former.

Mostly the latter. But given I don't see this experiment being
successful, I think the community has better ways of spending its
limited resources.

> As it happens, I agree that this is not going to produce
> a huge improvement. But its not intended to, and modest
> improvements (as opposed to modest proposals:-) should also
> be ok. If not then we're in a worse process-rut than even I
> think.

If there is an improvement, I expect it will be too small to be worth
bothering with. And given the community's limited resources (a not
insubstantial amount of collective cycles has already gone into this
document), it seems better to use those resources where there is some
hope of making a real difference.

> > The crux of the issue is that any attempt at "fast tracking" is
> > fundamentally about short-circuiting some aspect of our review
> > processes. 

> I'd prefer s/short-circuiting/speeding-up/

Sorry, I think short-circuiting is the right term. Saying you are just
speeding things up is just spin.

The reality is that it takes time to do quality standards/technical
work. And, it takes iteration. The only kind of iteration that makes
sense is sequential. Get some review, revise, then review the new
version. When one tries to overlap sequential reviews, the result is
almost always a poorer quality document.  It is important that the
revisions get reviewed by a fresh set of eyes. If you short-circuit
such iteration, you inevitably get poorer quality documents. Also,
it's really unfair to reviewers to have all of them stumble across the
same issues.

> > This document risks substituting process for judgement. I'd rather see
> > more of the latter and less of the former.

> Disagree. The WG chairs exercise judgement to kick off the
> process. The IESG exercise judgement as usual with no changes.

This document would use a different kind of judgement. One that is
more formulaic. The kind of judgement I'd rather see is the WG/WG
chairs/ADs getting together and making the case for a particular
document being so important/urgent that it needs to be
accelerated. And then have them work out a plan to actually get
reviews in a more timely manner, etc. E.g., get committments from folk
to review and revise quickly. Have a realistic workplan that folk
commit to. If its not possible to get folk to commit to being
responsive, doesn't that implicitely say something about the overall
urgency of the document?  But make that case on a number of factors
(importance of having the RFC in place, etc.) rather than just on the
fact that there was some sort of running code associated with it.

> I think incorporating the discuss criteria should be an interesting
> part of the experiment. (I've found them really helpful in reviewing
> documents these last couple of years.)

Discuss criteria are an IESG-level construct, developed to find
balance between "nit picking" by the IESG very late in the process
vs. correcting real problems. That same criteria is not appropriate to
apply to a document that hasn't gone through WG LC, which is at a much
earlier stage of the process. 

> > No doubt, when a AD or reviewer suggests "this needs
> > fixing", the proponents will hold up this document and say "you
> > shouldn't do this, per the RFC -- you're violating the spirit of this
> > document, only really really critical stuff needs to get addressed..."
> > No thanks. That is not what the IETF is about.

> I don't see how you get to "No doubt..." I do entirely doubt that'll
> happen for most all editors.

This community is really good at citing process to justify whatever
action (or inaction) they would like to see. Like it or not, this
could become another such tool.

Thomas


From joelja@bogus.com  Wed Jan 23 09:01:11 2013
Return-Path: <joelja@bogus.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BD00521F8686 for <ietf@ietfa.amsl.com>; Wed, 23 Jan 2013 09:01:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 Ty-sRyeLs+yh for <ietf@ietfa.amsl.com>; Wed, 23 Jan 2013 09:01:09 -0800 (PST)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id 10BC221F8694 for <ietf@ietf.org>; Wed, 23 Jan 2013 09:01:08 -0800 (PST)
Received: from joels-MacBook-Air.local (host-64-47-153-50.masergy.com [64.47.153.50]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id r0NH11LE073465 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT); Wed, 23 Jan 2013 17:01:02 GMT (envelope-from joelja@bogus.com)
Message-ID: <51001748.90702@bogus.com>
Date: Wed, 23 Jan 2013 09:00:56 -0800
From: joel jaeggli <joelja@bogus.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:19.0) Gecko/20130117 Thunderbird/19.0
MIME-Version: 1.0
To: Hannes Tschofenig <hannes.tschofenig@gmx.net>, Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: A modest proposal
References: <CAPJ9He0dOttM+DmpUt9MzfWEXcs+tbpJJy4Z+usoRroyAdzJbA@mail.gmail.com>	<50FE3A37.7040402@gmail.com>	<691CE879-B639-4C69-8B8D-0FC2DCB909A8@gmx.net> <50FF63B1.8080509@bogus.com> <50FF9830.6010403@gmail.com> <23F5A1DB-357E-4133-A01E-2608D47D34C9@gmx.net>
In-Reply-To: <23F5A1DB-357E-4133-A01E-2608D47D34C9@gmx.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (nagasaki.bogus.com [147.28.0.81]); Wed, 23 Jan 2013 17:01:02 +0000 (UTC)
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 23 Jan 2013 17:01:11 -0000

On 1/23/13 1:27 AM, Hannes Tschofenig wrote:
> Hi Brian, Hi Joel,
>
> the point of my mail was not to start a discussion about the examples I provided but to note that the suggested "let's reduce complexity by reducing options" is not as easy as it sounds in practice.
The prototypical human enterprise has need to innovate which means 
finding a way to bring products and services which people want buy to 
market. This process is both one of discovery and failure (market 
signals). Part of the process which respond(s) in an inverse fashion to 
market signals is effort required for standardization (e.g. increased 
demand and therefore resources makes it harder not easier). It is is 
relativity easy at the margins to wing documents for things which nobody 
really cares about through the IETF (one can contrast this with other 
standardization processes if you like), the result being that you have a 
record of a diversity of lightly used but possibly important to someone 
or potentially no-one solutions. When you have a great number of groups 
involved in the development of what is currently a hot area of work, the 
amount of effort associated with getting those drafts through a  process 
is dramatically larger, they are subject to evolutionary pressure, and 
they have to satisfy the needs of a great number of constituents, that 
probably if not always produces a better outcome as far as utility, and 
interoperability as concerned but the efforts at the margins don't stop 
because of it.
> In the context of the document Stephen wrote and the proposal that was made on the list I was wondering whether a bit more analysis about what the problems we are trying to solve would be helpful. As some folks had raised implementing specifications is not a sufficient condition for interoperability, or successful deployment. I personally believe that IETF working groups are a fine job in writing code along with their specification work.
>
> Ciao
> Hannes
>
> On Jan 23, 2013, at 9:58 AM, Brian E Carpenter wrote:
>
>> On 23/01/2013 04:14, joel jaeggli wrote:
>>> On 1/22/13 12:34 AM, Hannes Tschofenig wrote:
>>>> Another example from a different area: Why do we need so many
>>>> transition technologies for the migration from IPv4 to IPv6? Wouldn't
>>>> it be less complex to just have one transition mechanism?
>>> You mean no transition mechanisms...
>> That was, in fact, the plan (dual stack during coexistence).
>> It went wrong.
>>
>>   Brian
>


From fanf2@hermes.cam.ac.uk  Wed Jan 23 09:40:09 2013
Return-Path: <fanf2@hermes.cam.ac.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 39F7D21F85AC for <ietf@ietfa.amsl.com>; Wed, 23 Jan 2013 09:40:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.299
X-Spam-Level: 
X-Spam-Status: No, score=-5.299 tagged_above=-999 required=5 tests=[AWL=1.300,  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 4tnj1xIoSzdR for <ietf@ietfa.amsl.com>; Wed, 23 Jan 2013 09:40:08 -0800 (PST)
Received: from ppsw-41.csi.cam.ac.uk (ppsw-41.csi.cam.ac.uk [131.111.8.141]) by ietfa.amsl.com (Postfix) with ESMTP id 7A88021F859A for <ietf@ietf.org>; Wed, 23 Jan 2013 09:40:08 -0800 (PST)
X-Cam-AntiVirus: no malware found
X-Cam-SpamDetails: not scanned
X-Cam-ScannerInfo: http://www.ucs.cam.ac.uk/email/scanner/
Received: from hermes-1.csi.cam.ac.uk ([131.111.8.51]:42248) by ppsw-41.csi.cam.ac.uk (smtp.hermes.cam.ac.uk [131.111.8.156]:25) with esmtpa (EXTERNAL:fanf2) id 1Ty4Iw-0008Or-SU (Exim 4.72) (return-path <fanf2@hermes.cam.ac.uk>); Wed, 23 Jan 2013 17:40:06 +0000
Received: from fanf2 by hermes-1.csi.cam.ac.uk (hermes.cam.ac.uk) with local id 1Ty4Iw-0006JR-Pf (Exim 4.72) (return-path <fanf2@hermes.cam.ac.uk>); Wed, 23 Jan 2013 17:40:06 +0000
Date: Wed, 23 Jan 2013 17:40:06 +0000
From: Tony Finch <dot@dotat.at>
X-X-Sender: fanf2@hermes-1.csi.cam.ac.uk
To: John Levine <johnl@taugh.com>
Subject: Re: A modest proposal
In-Reply-To: <20130123061554.85592.qmail@joyce.lan>
Message-ID: <alpine.LSU.2.00.1301231739060.27013@hermes-1.csi.cam.ac.uk>
References: <20130123061554.85592.qmail@joyce.lan>
User-Agent: Alpine 2.00 (LSU 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: Tony Finch <fanf2@hermes.cam.ac.uk>
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 23 Jan 2013 17:40:09 -0000

John Levine <johnl@taugh.com> wrote:
>
> My, what a bunch of parvenus.  SIP got it from SMTP, SMTP got it from
> Telnet.  Back in the 1960s we all used <CR><LF> because on a
> mechanical model 33 or 35 Teletype, CR really returned the carriage,
> LF really advanced the platen, and you needed both.  I first ran into
> CR/LF on a PDP-6 in about 1968, but I know it wasn't new then.

Dates back to 1930s teleprinters, I think.

Tony.
-- 
f.anthony.n.finch  <dot@dotat.at>  http://dotat.at/
Forties, Cromarty: East, veering southeast, 4 or 5, occasionally 6 at first.
Rough, becoming slight or moderate. Showers, rain at first. Moderate or good,
occasionally poor at first.

From mcr@sandelman.ca  Wed Jan 23 10:14:53 2013
Return-Path: <mcr@sandelman.ca>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 460B321F84F8 for <ietf@ietfa.amsl.com>; Wed, 23 Jan 2013 10:14:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.499
X-Spam-Level: 
X-Spam-Status: No, score=-2.499 tagged_above=-999 required=5 tests=[AWL=0.100,  BAYES_00=-2.599]
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 Yh7ovpy3qvjP for <ietf@ietfa.amsl.com>; Wed, 23 Jan 2013 10:14:52 -0800 (PST)
Received: from tuna.sandelman.ca (unknown [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) by ietfa.amsl.com (Postfix) with ESMTP id F220F21F87FB for <ietf@ietf.org>; Wed, 23 Jan 2013 10:14:51 -0800 (PST)
Received: from sandelman.ca (desk.marajade.sandelman.ca [209.87.252.247]) by tuna.sandelman.ca (Postfix) with ESMTP id 2100020168; Wed, 23 Jan 2013 13:19:55 -0500 (EST)
Received: by sandelman.ca (Postfix, from userid 179) id D8D0A63765; Wed, 23 Jan 2013 13:13:52 -0500 (EST)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id C81A8636C4; Wed, 23 Jan 2013 13:13:52 -0500 (EST)
From: Michael Richardson <mcr@sandelman.ca>
To: Tony Finch <dot@dotat.at>
Subject: Re: A modest proposal
In-Reply-To: <alpine.LSU.2.00.1301231739060.27013@hermes-1.csi.cam.ac.uk>
References: <20130123061554.85592.qmail@joyce.lan> <alpine.LSU.2.00.1301231739060.27013@hermes-1.csi.cam.ac.uk>
X-Mailer: MH-E 8.3; nmh 1.3-dev; XEmacs 21.4 (patch 22)
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
Date: Wed, 23 Jan 2013 13:13:52 -0500
Message-ID: <25837.1358964832@sandelman.ca>
Sender: mcr@sandelman.ca
Cc: John Levine <johnl@taugh.com>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 23 Jan 2013 18:14:53 -0000

>>>>> "Tony" == Tony Finch <dot@dotat.at> writes:
    >> My, what a bunch of parvenus.  SIP got it from SMTP, SMTP got it from
    >> Telnet.  Back in the 1960s we all used <CR><LF> because on a
    >> mechanical model 33 or 35 Teletype, CR really returned the carriage,
    >> LF really advanced the platen, and you needed both.  I first ran into
    >> CR/LF on a PDP-6 in about 1968, but I know it wasn't new then.

    Tony> Dates back to 1930s teleprinters, I think.

Since they were "tele"-printers, it seems obvious why *SIP* must retain
it for "tele"-phony :-) 




From warren@kumari.net  Wed Jan 23 10:45:17 2013
Return-Path: <warren@kumari.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 843A421F87AC for <ietf@ietfa.amsl.com>; Wed, 23 Jan 2013 10:45:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.399
X-Spam-Level: 
X-Spam-Status: No, score=-101.399 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_54=0.6, J_CHICKENPOX_64=0.6, USER_IN_WHITELIST=-100]
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 Pfr6fMwLqjjf for <ietf@ietfa.amsl.com>; Wed, 23 Jan 2013 10:45:17 -0800 (PST)
Received: from vimes.kumari.net (smtp1.kumari.net [204.194.22.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2017421F85D9 for <ietf@ietf.org>; Wed, 23 Jan 2013 10:45:17 -0800 (PST)
Received: from [192.168.0.187] (unknown [64.13.52.115]) by vimes.kumari.net (Postfix) with ESMTPSA id 406121B401C6; Wed, 23 Jan 2013 13:45:16 -0500 (EST)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Subject: Re: [IETF] A modest proposal
From: Warren Kumari <warren@kumari.net>
In-Reply-To: <50FF6ACC.1050508@gmail.com>
Date: Wed, 23 Jan 2013 13:45:14 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <C92E19A6-3DDA-4020-ACC4-67DC1A525B1D@kumari.net>
References: <CAPJ9He36PgOdwocyB0EnEqWruNGc4zzMW6ETW2im2azy7Kg0rw@mail.gmail.com> <CAOHm=4tEGOeYcfp5yWD0VvhCq3Rj=cnvzynG9J6uORHqZHXcNw@mail.gmail.com> <50FF6ACC.1050508@gmail.com>
To: Melinda Shore <melinda.shore@gmail.com>
X-Mailer: Apple Mail (2.1499)
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 23 Jan 2013 18:45:17 -0000

On Jan 22, 2013, at 11:45 PM, Melinda Shore <melinda.shore@gmail.com> =
wrote:

> On 1/22/13 7:16 PM, Dean Willis wrote:
>> Microsoft-OS text editors. Seriously. People wanted to be able to
>> write correct SIP messages using text editors, and there were more
>> Microsoft users than Linux users on the list.=20
>=20
> Oh, c'mon.  MS products and MacOS at the time used CRLF for newlines
> generally, not just in Word.  The fact that it was specified that way
> in HTTP, SMTP, FTP, and others matters a bit, as well.

Yup, and Unix users have the ability to choose line endings:
Emacs -
M-x set-buffer-file-coding-system RET undecided-dos

VI -=20
: Set fileformat =3D dos : W=20

If you are using anything else, a: don't or b:=20

tr -d '\r' < input.file > output.file

or=20

perl -pi -e 's/\r\n/\n/g' input.file

or=20

sed 's/$'"/`echo \\\r`/" input.txt > output.txt

or=85.=20

W



>=20
> Melinda
>=20

--
The duke had a mind that ticked like a clock and, like a clock, it =
regularly went cuckoo.

    -- (Terry Pratchett, Wyrd Sisters)



From john-ietf@jck.com  Wed Jan 23 11:56:36 2013
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8053021F8770 for <ietf@ietfa.amsl.com>; Wed, 23 Jan 2013 11:56:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.932
X-Spam-Level: 
X-Spam-Status: No, score=-102.932 tagged_above=-999 required=5 tests=[AWL=-0.333, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 VXeSP4pZ7v6G for <ietf@ietfa.amsl.com>; Wed, 23 Jan 2013 11:56:36 -0800 (PST)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id E01EA21F85D4 for <ietf@ietf.org>; Wed, 23 Jan 2013 11:56:35 -0800 (PST)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1Ty6Qu-000Bzx-2e; Wed, 23 Jan 2013 14:56:28 -0500
Date: Wed, 23 Jan 2013 14:56:23 -0500
From: John C Klensin <john-ietf@jck.com>
To: John Levine <johnl@taugh.com>, ietf@ietf.org
Subject: CRLF (was: Re: A modest proposal)
Message-ID: <C3CD7DDBD81323BD17837BCE@JcK-HP8200.jck.com>
In-Reply-To: <20130123061554.85592.qmail@joyce.lan>
References: <20130123061554.85592.qmail@joyce.lan>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Cc: dean.willis@softarmor.com
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 23 Jan 2013 19:56:36 -0000

--On Wednesday, January 23, 2013 06:15 +0000 John Levine
<johnl@taugh.com> wrote:

>>> Additionally, I can't understand why each line is terminated
>>> with <CR><LF>, why use two characters when one will do.
>> 
>> Microsoft-OS text editors. Seriously.
> 
> My, what a bunch of parvenus.  SIP got it from SMTP, SMTP got
> it from Telnet.  Back in the 1960s we all used <CR><LF>
> because on a mechanical model 33 or 35 Teletype, CR really
> returned the carriage, LF really advanced the platen, and you
> needed both.  I first ran into CR/LF on a PDP-6 in about 1968,
> but I know it wasn't new then.
>...

Right.  And the relationships between the standards and the
equipment was a little obscure (at least to me) in terms of what
came first.  But having CR as an unambiguous "return to first
character position on line" was important for overstriking
(especially underlining) on a number of devices including line
printers as well as TTY equipment.   A number of systems of the
mid-1960s even had device drivers that would canonicalize lines
with non-destructive backspaces into lines with CR or vice
versa, depending on the needs of the particular device.

The first version of ASCII was very specific that CR was "move
to first character position on current line" and LF was a
vertical index function.  Then the confusion began with some
company (where I was at the time, the finger was pointed at
Digital Equipment, but I have no first hand information or
documentation) who started using CR as "new line".  That left us
with systems in the wild that used LF (only) internally, ones
that used CR (only), ones that used CRLF (always the safe choice
because it worked whether LF was an index function or a new line
one), and equipment that often required the latter.  Subsequent
versions of ASCII solved the incompatibility the same way the
FORTRAN standard (this was a bit before _that_ standards
committee decided the language was named "Fortran") solved
zero-iteration loops -- by fuzzy language that made both
one-traversal and zero-traversal valid in the FORTRAN case and
that made either interpretation of LF valid.

> A single LF to start a new line arrived with the model 37
> Teletype, and Unix was, as far as I know, the first system to
> use just \n as the line terminator starting in the early
> 1970s.

IIR, Multics from several years earlier.  I'd have to dig
through old manuals to remember what CTSS did, but that system
(and the IBM Model 1050 and 2741 devices often used as terminals
with it) were somewhat pre-ASCII (and long before ECMA-48/ ANSI
X3.64 and the VT100 and friends)  and, IIR, sent and received
shift and rotate codes rather than what we would normally
consider character codes today.  The character codes were just
input to device drivers that dealt with device characteristics

>  But by then the Arpanet protocols were designed, and
> the hassle of changing wasn't (and still isn't) worth it.

Again, the key useful property of CRLF on the wire is that the
combination is fairly insensitive to the various interpretations
of CR and LF.

    john


From fanf2@hermes.cam.ac.uk  Wed Jan 23 12:08:21 2013
Return-Path: <fanf2@hermes.cam.ac.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 55F3D21F882E for <ietf@ietfa.amsl.com>; Wed, 23 Jan 2013 12:08:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.303
X-Spam-Level: 
X-Spam-Status: No, score=-3.303 tagged_above=-999 required=5 tests=[AWL=-1.996, BAYES_00=-2.599, MISSING_HEADERS=1.292]
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 vJ06hYuO4SZE for <ietf@ietfa.amsl.com>; Wed, 23 Jan 2013 12:08:20 -0800 (PST)
Received: from ppsw-43.csi.cam.ac.uk (ppsw-43.csi.cam.ac.uk [131.111.8.143]) by ietfa.amsl.com (Postfix) with ESMTP id B3F9621F87ED for <ietf@ietf.org>; Wed, 23 Jan 2013 12:08:20 -0800 (PST)
X-Cam-AntiVirus: no malware found
X-Cam-SpamDetails: not scanned
X-Cam-ScannerInfo: http://www.ucs.cam.ac.uk/email/scanner/
Received: from hermes-1.csi.cam.ac.uk ([131.111.8.51]:40398) by ppsw-43.csi.cam.ac.uk (smtp.hermes.cam.ac.uk [131.111.8.159]:25) with esmtpa (EXTERNAL:fanf2) id 1Ty6cN-0002ws-oZ (Exim 4.72) (return-path <fanf2@hermes.cam.ac.uk>); Wed, 23 Jan 2013 20:08:19 +0000
Received: from fanf2 by hermes-1.csi.cam.ac.uk (hermes.cam.ac.uk) with local id 1Ty6cN-0006kd-LE (Exim 4.72) (return-path <fanf2@hermes.cam.ac.uk>); Wed, 23 Jan 2013 20:08:19 +0000
Date: Wed, 23 Jan 2013 20:08:19 +0000
From: Tony Finch <dot@dotat.at>
X-X-Sender: fanf2@hermes-1.csi.cam.ac.uk
Subject: Re: [IETF] A modest proposal
In-Reply-To: <C92E19A6-3DDA-4020-ACC4-67DC1A525B1D@kumari.net>
Message-ID: <alpine.LSU.2.00.1301232005300.27013@hermes-1.csi.cam.ac.uk>
References: <CAPJ9He36PgOdwocyB0EnEqWruNGc4zzMW6ETW2im2azy7Kg0rw@mail.gmail.com> <CAOHm=4tEGOeYcfp5yWD0VvhCq3Rj=cnvzynG9J6uORHqZHXcNw@mail.gmail.com> <50FF6ACC.1050508@gmail.com> <C92E19A6-3DDA-4020-ACC4-67DC1A525B1D@kumari.net>
User-Agent: Alpine 2.00 (LSU 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: Tony Finch <fanf2@hermes.cam.ac.uk>
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 23 Jan 2013 20:08:21 -0000

Melinda Shore <melinda.shore@gmail.com> wrote:
>
> Oh, c'mon.  MS products and MacOS at the time used CRLF for newlines
> generally, not just in Word.

Classic Mac OS used bare CR for newlines, as did a number of 8 bit micros.

Tony.
-- 
f.anthony.n.finch  <dot@dotat.at>  http://dotat.at/
Forties, Cromarty: East, veering southeast, 4 or 5, occasionally 6 at first.
Rough, becoming slight or moderate. Showers, rain at first. Moderate or good,
occasionally poor at first.

From derhoermi@gmx.net  Wed Jan 23 12:49:28 2013
Return-Path: <derhoermi@gmx.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1D95621F87AC for <ietf@ietfa.amsl.com>; Wed, 23 Jan 2013 12:49:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 WYNJ3OehwJTh for <ietf@ietfa.amsl.com>; Wed, 23 Jan 2013 12:49:27 -0800 (PST)
Received: from mout.gmx.net (mout.gmx.net [212.227.15.18]) by ietfa.amsl.com (Postfix) with ESMTP id E2FB421F87AA for <ietf@ietf.org>; Wed, 23 Jan 2013 12:49:26 -0800 (PST)
Received: from mailout-de.gmx.net ([10.1.76.17]) by mrigmx.server.lan (mrigmx002) with ESMTP (Nemesis) id 0Lur0x-1Uy5gN0Q1x-0102EY for <ietf@ietf.org>; Wed, 23 Jan 2013 21:49:26 +0100
Received: (qmail invoked by alias); 23 Jan 2013 20:49:25 -0000
Received: from pD9538B97.dip.t-dialin.net (EHLO netb.Speedport_W_700V) [217.83.139.151] by mail.gmx.net (mp017) with SMTP; 23 Jan 2013 21:49:25 +0100
X-Authenticated: #723575
X-Provags-ID: V01U2FsdGVkX1+n9H9keOanKOLNcOO7fHfekJV4/BduYP9r+u6teO ljBh3IQmCzBzil
From: Bjoern Hoehrmann <derhoermi@gmx.net>
To: ietf@ietf.org
Subject: Comments on draft-shafranovich-mime-sql-03
Date: Wed, 23 Jan 2013 21:49:27 +0100
Message-ID: <1ah0g8p99e7rljhvndsmqi7qp8ujoj4ije@hive.bjoern.hoehrmann.de>
X-Mailer: Forte Agent 3.3/32.846
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-Y-GMX-Trusted: 0
Cc: draft-shafranovich-mime-sql@tools.ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 23 Jan 2013 20:49:28 -0000

Hi,

  Regarding <http://tools.ietf.org/html/draft-shafranovich-mime-sql-03>,
I think the document should be more clear that there are many variants
of the SQL format and the media type is intended as "umbrella type" for
them all, for instance, the Abstract should refer to, say, "variants of
the Structured Query Language" and not "the Structured Query Language".
The "Published specification" field in the registration template should
also note that there exist individual specifications for individual de-
rived formats (like "SQL As Understood By SQLite").

The proposed type has an optional 'charset' parameter. As I understand
it, SQL formats typically indicate character encoding, if at all, in
proprietary ways inline in SQL resources, or entirely out of band, and
for exchange, everybody seems to be settling on UTF-* encodings, so the
parameter is unlikely to serve a useful purpose, but does create some
problems, like how implementations should handle HTTP responses where
the HTTP header says `Content-Type: application/sql;charset=iso-8859-1`
while UTF-8 is specified inline. I think the type would do better with-
out this parameter.

Whether it is kept or not, the media type registration should not de-
fine a default. If the character encoding is not explicitly specified,
then it is unknown, and it should be up to individual applications and
their conventions for their SQL variants how to handle that case.

regards,
-- 
Björn Höhrmann · mailto:bjoern@hoehrmann.de · http://bjoern.hoehrmann.de
Am Badedeich 7 · Telefon: +49(0)160/4415681 · http://www.bjoernsworld.de
25899 Dagebüll · PGP Pub. KeyID: 0xA4357E78 · http://www.websitedev.de/ 

From hsantos@isdg.net  Wed Jan 23 13:37:19 2013
Return-Path: <hsantos@isdg.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6457621F8620 for <ietf@ietfa.amsl.com>; Wed, 23 Jan 2013 13:37:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.599
X-Spam-Level: 
X-Spam-Status: No, score=-101.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, SARE_OEM_OBFU=1, USER_IN_WHITELIST=-100]
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 kSCKjs7jO+25 for <ietf@ietfa.amsl.com>; Wed, 23 Jan 2013 13:37:15 -0800 (PST)
Received: from listserv.winserver.com (news.winserver.com [208.247.131.9]) by ietfa.amsl.com (Postfix) with ESMTP id BB1ED21F85FD for <ietf@ietf.org>; Wed, 23 Jan 2013 13:37:14 -0800 (PST)
DKIM-Signature: v=1; d=isdg.net; s=tms1; a=rsa-sha1; c=simple/relaxed; l=4974; t=1358977026; h=Received:Received: Message-ID:From:To:Subject:Date:Organization:List-ID; bh=1JXatog E7SAX2i399O8/45JGJfo=; b=Z1U9A/9z1H46flgde01eHK+WZ/bxySXPn/M1v1J ArROFfMj4oSS4mkeIJlS3XApJEr3d15989MeeHgDp0pNzNZQ7qfWlRK3DDlUycSH dwFxFRrHqxm27TSer75HH5zIY4RtmyOZ7IMdd96SBgITWd+FUH5fybEor4WoF9/G gO3Y=
Received: by winserver.com (Wildcat! SMTP Router v7.0.454.4) for ietf@ietf.org; Wed, 23 Jan 2013 16:37:06 -0500
Received: from main2 ([208.247.131.8]) by winserver.com (Wildcat! SMTP v7.0.454.4) with ESMTP id 2113770911.12291.4444; Wed, 23 Jan 2013 16:37:05 -0500
Message-ID: <1BB31081E0DF469386AC5D6A89DCE160@addom.santronics.com>
From: "Hector Santos" <hsantos@isdg.net>
To: "John C Klensin" <john-ietf@jck.com>
References: <20130123061554.85592.qmail@joyce.lan> <C3CD7DDBD81323BD17837BCE@JcK-HP8200.jck.com>
Subject: Re: CRLF (was: Re: A modest proposal)
Date: Wed, 23 Jan 2013 16:35:55 -0500
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.3790.4657
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.4721
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 23 Jan 2013 21:37:19 -0000

There was a mechancal reason for both and not just an EOL (End of Line) =
concept. As you point out, it was the original way to get an emulation =
of BOLD characters on print devices.  You control the print head and =
when this emulation moved to 80x25 screens, the cursor was the carriage =
head.  Some "Smart" terminals had a 132 columns mode to help with the =
emulation of Punch Cards which has 132 columns.

But to me, overall, it would of been difficult to design the interactive =
I/O spftware and both modem and internet hosting protocols, overall =
telecommunications applications without the proper translations of CR/LF =
simply for proper visual operations.  It was either hardware or software =
driven.  For example, hitting the Carriage Return key <CR>, either the =
device was set to also send the <LF> or the receiver did the translation =
and with an echo back of <LF>, the sender (now the receiver) will react =
to the control character.  All to make sure the visual (or print) was =
correct.

I'm sure with SIP the same interactive I/O translation, telecomputing, =
full versus half duples issues are present.  It would be been very =
difficult for SIP developers to do all this (text based Command/Response =
protocol ) in the blind and in an <LF> EOL world - something would have =
to be doing the translation, the device, the sender and/or receiver =
simply visual/print effects.

--
HLS


----- Original Message -----=20
From: "John C Klensin" <john-ietf@jck.com>
To: "John Levine" <johnl@taugh.com>; <ietf@ietf.org>
Cc: <dean.willis@softarmor.com>
Sent: Wednesday, January 23, 2013 2:56 PM
Subject: CRLF (was: Re: A modest proposal)


>=20
>=20
> --On Wednesday, January 23, 2013 06:15 +0000 John Levine
> <johnl@taugh.com> wrote:
>=20
>>>> Additionally, I can't understand why each line is terminated
>>>> with <CR><LF>, why use two characters when one will do.
>>>=20
>>> Microsoft-OS text editors. Seriously.
>>=20
>> My, what a bunch of parvenus.  SIP got it from SMTP, SMTP got
>> it from Telnet.  Back in the 1960s we all used <CR><LF>
>> because on a mechanical model 33 or 35 Teletype, CR really
>> returned the carriage, LF really advanced the platen, and you
>> needed both.  I first ran into CR/LF on a PDP-6 in about 1968,
>> but I know it wasn't new then.
>>...
>=20
> Right.  And the relationships between the standards and the
> equipment was a little obscure (at least to me) in terms of what
> came first.  But having CR as an unambiguous "return to first
> character position on line" was important for overstriking
> (especially underlining) on a number of devices including line
> printers as well as TTY equipment.   A number of systems of the
> mid-1960s even had device drivers that would canonicalize lines
> with non-destructive backspaces into lines with CR or vice
> versa, depending on the needs of the particular device.
>=20
> The first version of ASCII was very specific that CR was "move
> to first character position on current line" and LF was a
> vertical index function.  Then the confusion began with some
> company (where I was at the time, the finger was pointed at
> Digital Equipment, but I have no first hand information or
> documentation) who started using CR as "new line".  That left us
> with systems in the wild that used LF (only) internally, ones
> that used CR (only), ones that used CRLF (always the safe choice
> because it worked whether LF was an index function or a new line
> one), and equipment that often required the latter.  Subsequent
> versions of ASCII solved the incompatibility the same way the
> FORTRAN standard (this was a bit before _that_ standards
> committee decided the language was named "Fortran") solved
> zero-iteration loops -- by fuzzy language that made both
> one-traversal and zero-traversal valid in the FORTRAN case and
> that made either interpretation of LF valid.
>=20
>> A single LF to start a new line arrived with the model 37
>> Teletype, and Unix was, as far as I know, the first system to
>> use just \n as the line terminator starting in the early
>> 1970s.
>=20
> IIR, Multics from several years earlier.  I'd have to dig
> through old manuals to remember what CTSS did, but that system
> (and the IBM Model 1050 and 2741 devices often used as terminals
> with it) were somewhat pre-ASCII (and long before ECMA-48/ ANSI
> X3.64 and the VT100 and friends)  and, IIR, sent and received
> shift and rotate codes rather than what we would normally
> consider character codes today.  The character codes were just
> input to device drivers that dealt with device characteristics
>=20
>>  But by then the Arpanet protocols were designed, and
>> the hassle of changing wasn't (and still isn't) worth it.
>=20
> Again, the key useful property of CRLF on the wire is that the
> combination is fairly insensitive to the various interpretations
> of CR and LF.
>=20
>    john
>=20
>


From john@jck.com  Wed Jan 23 14:18:26 2013
Return-Path: <john@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D135721F85E0 for <ietf@ietfa.amsl.com>; Wed, 23 Jan 2013 14:18:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 4YQ6nQgktgmH for <ietf@ietfa.amsl.com>; Wed, 23 Jan 2013 14:18:25 -0800 (PST)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 5FC1E21F84E4 for <ietf@ietf.org>; Wed, 23 Jan 2013 14:18:25 -0800 (PST)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john@jck.com>) id 1Ty8eF-000C8g-BZ; Wed, 23 Jan 2013 17:18:23 -0500
Date: Wed, 23 Jan 2013 17:18:18 -0500
From: John C Klensin <john@jck.com>
To: Warren Kumari <warren@kumari.net>, Melinda Shore <melinda.shore@gmail.com>
Subject: Re: [IETF] A modest proposal
Message-ID: <E30D6DC466D58F7F5D3CF0BB@JcK-HP8200.jck.com>
In-Reply-To: <C92E19A6-3DDA-4020-ACC4-67DC1A525B1D@kumari.net>
References: <CAPJ9He36PgOdwocyB0EnEqWruNGc4zzMW6ETW2im2azy7Kg0rw@mail.gmail.com> <CAOHm=4tEGOeYcfp5yWD0VvhCq3Rj=cnvzynG9J6uORHqZHXcNw@mail.gmail.com> <50FF6ACC.1050508@gmail.com> <C92E19A6-3DDA-4020-ACC4-67DC1A525B1D@kumari.net>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 23 Jan 2013 22:18:26 -0000

--On Wednesday, January 23, 2013 13:45 -0500 Warren Kumari
<warren@kumari.net> wrote:

>...
> Yup, and Unix users have the ability to choose line endings:
> Emacs -
> M-x set-buffer-file-coding-system RET undecided-dos
>...

Not exactly.  Depending on the particular version/
implementation, most version of Emacs (which, unlike VI, are
distinctly not limited to Unix and were actually around before
Unix was) keep the lines in a buffer as an threaded list.  That
makes certain operations, like moving a region from one buffer
to another or inserting text in a buffer, really fast because
they don't require moving the rest of the file up or down.  How
a buffer is written to an external medium then becomes another
issue, with emacs internally being indifferent to CR, LF, CRLF,
strings delimited in other ways such as by record markers,
length-delimited lines or records, and so on.

It does make Emacs and its clones pretty convenient as a format
converter, but...

best,
   john





From jeanjour@comcast.net  Wed Jan 23 14:18:27 2013
Return-Path: <jeanjour@comcast.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0BE3B21F84E4 for <ietf@ietfa.amsl.com>; Wed, 23 Jan 2013 14:18:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.437
X-Spam-Level: 
X-Spam-Status: No, score=-100.437 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_NET=0.611,  RDNS_NONE=0.1, USER_IN_WHITELIST=-100]
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 tZGA5PSmYnUk for <ietf@ietfa.amsl.com>; Wed, 23 Jan 2013 14:18:25 -0800 (PST)
Received: from qmta15.emeryville.ca.mail.comcast.net (qmta15.emeryville.ca.mail.comcast.net [IPv6:2001:558:fe2d:44:76:96:27:228]) by ietfa.amsl.com (Postfix) with ESMTP id B6BEF21F85D7 for <ietf@ietf.org>; Wed, 23 Jan 2013 14:18:25 -0800 (PST)
Received: from omta16.emeryville.ca.mail.comcast.net ([76.96.30.72]) by qmta15.emeryville.ca.mail.comcast.net with comcast id rTZr1k0061ZMdJ4AFaJRzY; Wed, 23 Jan 2013 22:18:25 +0000
Received: from [10.0.1.3] ([79.145.202.255]) by omta16.emeryville.ca.mail.comcast.net with comcast id raHb1k00A5X7tlr8caHnPX; Wed, 23 Jan 2013 22:18:20 +0000
Mime-Version: 1.0
Message-Id: <a062408f3cd2610b7f0fc@[10.0.1.3]>
In-Reply-To: <C3CD7DDBD81323BD17837BCE@JcK-HP8200.jck.com>
References: <20130123061554.85592.qmail@joyce.lan> <C3CD7DDBD81323BD17837BCE@JcK-HP8200.jck.com>
Date: Wed, 23 Jan 2013 17:16:30 -0500
To: John C Klensin <john-ietf@jck.com>, John Levine <johnl@taugh.com>, ietf@ietf.org
From: John Day <jeanjour@comcast.net>
Subject: Re: CRLF (was: Re: A modest proposal)
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20121106; t=1358979505; bh=SY/a9yReQ3ltgVmQoFON5D6umXIbCUQh1TmRz0PeXr8=; h=Received:Received:Mime-Version:Message-Id:Date:To:From:Subject: Content-Type; b=L9ggSmVz/pf8zXumgYjGKFJHKSjcuLYgECni0Jl9M8FP9qRK7uhAy2t3Qa3kInfLG OV9eK/2LnZkWsH/Oz85zB5k5cKZug+rmgmWwW0yDR4vImQ2jmH4LfXLsUA7bA07l/3 vD1i3jGifSOXjQs7qF0EaBbT/v7m/GGTDi4WM0+na7KWcI+spu06/l7CHGr82HzV8W WGigctHz8gWy/g/eloYaxqPxroQe3jWy1U8jWOFkJd1fZKWTpQMUCxWegrMDChUzAg T2HLF85G3OtqtuDWfKaopg25ShnYCRX8m62kekVK9tEjIUW5kyHktLk5FoXpMRhgcq J9KaAyAEXUzzg==
Cc: dean.willis@softarmor.com
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 23 Jan 2013 22:18:27 -0000

>
>IIR, Multics from several years earlier.  I'd have to dig
>through old manuals to remember what CTSS did, but that system
>(and the IBM Model 1050 and 2741 devices often used as terminals
>with it) were somewhat pre-ASCII (and long before ECMA-48/ ANSI
>X3.64 and the VT100 and friends)  and, IIR, sent and received
>shift and rotate codes rather than what we would normally
>consider character codes today.  The character codes were just
>input to device drivers that dealt with device characteristics

Multics was based on EBCDIC which had a New Line (NL) character but 
no CR or LF.  The ARPANET went with the ASCII standard.  But I never 
forgave the ANSI committee for taking left arrow out of the character 
set (as a replacement operator).

Then there was the day that BBN loaded ASCII to EBCDIC tables into 
the TIPs that would not generate the line delete or character delete 
characters for Multics.  They said it was an accident.  ;-)

Take care,
John

From cabo@tzi.org  Wed Jan 23 14:29:41 2013
Return-Path: <cabo@tzi.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DF72E21F8793 for <ietf@ietfa.amsl.com>; Wed, 23 Jan 2013 14:29:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.174
X-Spam-Level: 
X-Spam-Status: No, score=-106.174 tagged_above=-999 required=5 tests=[AWL=0.075, BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 PLwMcV0Y4bmp for <ietf@ietfa.amsl.com>; Wed, 23 Jan 2013 14:29:41 -0800 (PST)
Received: from informatik.uni-bremen.de (mailhost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::12]) by ietfa.amsl.com (Postfix) with ESMTP id 24C7421F8790 for <ietf@ietf.org>; Wed, 23 Jan 2013 14:29:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from smtp-fb3.informatik.uni-bremen.de (smtp-fb3.informatik.uni-bremen.de [134.102.224.120]) by informatik.uni-bremen.de (8.14.3/8.14.3) with ESMTP id r0NMTXu8006452; Wed, 23 Jan 2013 23:29:33 +0100 (CET)
Received: from [192.168.217.105] (p5489396F.dip.t-dialin.net [84.137.57.111]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp-fb3.informatik.uni-bremen.de (Postfix) with ESMTPSA id 2D0B3170; Wed, 23 Jan 2013 23:29:33 +0100 (CET)
Subject: Vestigial Features (was Re: CRLF (was: Re: A modest proposal))
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Content-Type: text/plain; charset=iso-8859-1
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <C3CD7DDBD81323BD17837BCE@JcK-HP8200.jck.com>
Date: Wed, 23 Jan 2013 23:29:32 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <8EFA8168-7F05-4010-975C-CE601361501C@tzi.org>
References: <20130123061554.85592.qmail@joyce.lan> <C3CD7DDBD81323BD17837BCE@JcK-HP8200.jck.com>
To: John C Klensin <john-ietf@jck.com>
X-Mailer: Apple Mail (2.1499)
Cc: John Levine <johnl@taugh.com>, ietf@ietf.org, dean.willis@softarmor.com
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 23 Jan 2013 22:29:42 -0000

On Jan 23, 2013, at 20:56, John C Klensin <john-ietf@jck.com> wrote:

> But having CR as an unambiguous "return to first
> character position on line" was important for overstriking
> (especially underlining) on a number of devices including line
> printers as well as TTY equipment.

But John, on a TTY, you have to send CR NUL, or the first character will =
smudge.
The carriage is still in flight when the next byte after it is =
processed, so it better not be a printing character.

(This is actually the real reason for CR LF:
CR needs 200 ms to execute because it takes time to move the carriage, =
so you have to fill in a character to waste 100 ms.
So you might as well separate the CR and LF function, which is what =
happened.
Multiple newlines are sent as CR LF LF LF to a real TTY because LF =
*does* execute in 100 ms -- moving the paper is quicker.)

Now the reason I'm writing this:

SIP has CRLF because TTY carriages smudged. =20

Really.

Please let that sink in a minute.

I think in protocol evolution (as well as computer system evolution in =
general) we are missing triggers to get rid of vestigial features.

CRLF was quite reasonable for Telnet, as this really was about TTYs.
FTP grew out of Telnet, so keeping it there was maybe justifiable.
For SMTP, CRLF already was vestigial; this should have been fixed when =
SMTP became separate from FTP, but maybe the separation was too gradual =
(it was too late to fix it 20 years later in 282x).
Keeping CRLF for HTTP was a travesty (enjoy RFC 2616 section 19.3 para 3 =
for added pleasure).
Keeping it in SIP was unspeakable.

Gr=FC=DFe, Carsten


From dwm@xpasc.com  Wed Jan 23 14:45:53 2013
Return-Path: <dwm@xpasc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9F1D621F8801 for <ietf@ietfa.amsl.com>; Wed, 23 Jan 2013 14:45:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.626
X-Spam-Level: 
X-Spam-Status: No, score=-3.626 tagged_above=-999 required=5 tests=[AWL=-1.027, BAYES_00=-2.599]
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 TayR-CXGIMsA for <ietf@ietfa.amsl.com>; Wed, 23 Jan 2013 14:45:53 -0800 (PST)
Received: from c2w3p-2.abacamail.com (c2w3p-2.abacamail.com [209.133.53.32]) by ietfa.amsl.com (Postfix) with ESMTP id 25A0521F85AC for <ietf@ietf.org>; Wed, 23 Jan 2013 14:45:52 -0800 (PST)
Received: from xpasc.com (unknown [68.164.244.188]) by c2w3p-2.abacamail.com (Postfix) with ESMTP id E6CEA3FD8E for <ietf@ietf.org>; Wed, 23 Jan 2013 22:45:51 +0000 (UTC)
Received: from egate.xpasc.com (egate.xpasc.com [10.1.2.49]) by xpasc.com (8.13.8/8.13.8) with ESMTP id r0NMjn0Q017136 for <ietf@ietf.org>; Wed, 23 Jan 2013 14:45:49 -0800
Date: Wed, 23 Jan 2013 14:45:49 -0800 (PST)
From: David Morris <dwm@xpasc.com>
To: ietf@ietf.org
Subject: Re: CRLF (was: Re: A modest proposal)
In-Reply-To: <a062408f3cd2610b7f0fc@[10.0.1.3]>
Message-ID: <alpine.LRH.2.01.1301231424200.16244@egate.xpasc.com>
References: <20130123061554.85592.qmail@joyce.lan> <C3CD7DDBD81323BD17837BCE@JcK-HP8200.jck.com> <a062408f3cd2610b7f0fc@[10.0.1.3]>
User-Agent: Alpine 2.01 (LRH 1266 2009-07-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Milter-Version: master.1+13-gbab1945
X-AV-Type: clean
X-AV-Accuracy: exact
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: ietf@ietf.org
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 23 Jan 2013 22:45:53 -0000

On Wed, 23 Jan 2013, John Day wrote:

> > 
> > IIR, Multics from several years earlier.  I'd have to dig
> > through old manuals to remember what CTSS did, but that system
> > (and the IBM Model 1050 and 2741 devices often used as terminals
> > with it) were somewhat pre-ASCII (and long before ECMA-48/ ANSI
> > X3.64 and the VT100 and friends)  and, IIR, sent and received
> > shift and rotate codes rather than what we would normally
> > consider character codes today.  The character codes were just
> > input to device drivers that dealt with device characteristics
> 
> Multics was based on EBCDIC which had a New Line (NL) character but no CR or
> LF.  The ARPANET went with the ASCII standard.  But I never forgave the ANSI
> committee for taking left arrow out of the character set (as a replacement
> operator).

EBCDIC has NL (new line), LF and CR characters (hex 0x15, 0x25 and 0x0d
respectively). EBCDIC was an 8 bit code easy to translate in hardware
logic from punch card codes to the 8 bit code. Earlier IBM systems
used BCD (sometimes called BCDIC) which was a 6 bit code which did
not have CR or LF but had a subset of the EBCDIC style mapping from
punched cards to computer code. IBM systems all implemented a
record based file organization rather than the character stream
of UNIX. So the BCD generation systems had a record mark charcter
(and word mark) in the pre-S/360 days with BCD and file system
level record tracking in S/360.

IBM terminal devices (e.g., 2740, 2741, 1050, etc.) of the pre VDT era
used a different character coding on the wire (not BCD). Might have
been inspired by tilt/rotate, I don't know and never worried about more
than getting the translate table right. Hardware communications
controllers and later programmable controllers recoginzed the NL
character and signaled end of line/record to the host computer.

IBM lineprinters of the era were record/line oriented devices which
printed about 132 characters per line and advanced to new like, page,
etc. based on device specific commands and not data interpretation.
ANSI line controls or IBM internal codes could be used in the first
character of the line to pre/post space 0 or more lines for each
print record.

VDTs with long lines might have been inspired by line printers or
just the idea that long lines were better. No experience there,
but I'm pretty certain there were no 132 column punch cards in
common use which would have influnced comody VDT designers. 80
and I believe 96 in S/3 days.

Dave Morris

From jeanjour@comcast.net  Wed Jan 23 14:55:58 2013
Return-Path: <jeanjour@comcast.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 80AAC21F87A9 for <ietf@ietfa.amsl.com>; Wed, 23 Jan 2013 14:55:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.739
X-Spam-Level: 
X-Spam-Status: No, score=-99.739 tagged_above=-999 required=5 tests=[AWL=-0.698, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_NET=0.611, MIME_QP_LONG_LINE=1.396, RDNS_NONE=0.1, USER_IN_WHITELIST=-100]
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 LN7McKQ2x9vW for <ietf@ietfa.amsl.com>; Wed, 23 Jan 2013 14:55:58 -0800 (PST)
Received: from qmta02.emeryville.ca.mail.comcast.net (qmta02.emeryville.ca.mail.comcast.net [IPv6:2001:558:fe2d:43:76:96:30:24]) by ietfa.amsl.com (Postfix) with ESMTP id 2996621F8786 for <ietf@ietf.org>; Wed, 23 Jan 2013 14:55:51 -0800 (PST)
Received: from omta02.emeryville.ca.mail.comcast.net ([76.96.30.19]) by qmta02.emeryville.ca.mail.comcast.net with comcast id rWTG1k0080QkzPwA2avrGy; Wed, 23 Jan 2013 22:55:51 +0000
Received: from [10.0.1.3] ([79.145.202.255]) by omta02.emeryville.ca.mail.comcast.net with comcast id rav31k00U5X7tlr8Nav9nt; Wed, 23 Jan 2013 22:55:45 +0000
Mime-Version: 1.0
Message-Id: <a062408f6cd261951f4e1@[10.0.1.3]>
In-Reply-To: <8EFA8168-7F05-4010-975C-CE601361501C@tzi.org>
References: <20130123061554.85592.qmail@joyce.lan> <C3CD7DDBD81323BD17837BCE@JcK-HP8200.jck.com> <8EFA8168-7F05-4010-975C-CE601361501C@tzi.org>
Date: Wed, 23 Jan 2013 17:55:00 -0500
To: Carsten Bormann <cabo@tzi.org>, John C Klensin <john-ietf@jck.com>
From: John Day <jeanjour@comcast.net>
Subject: Re: Vestigial Features (was Re: CRLF (was: Re: A modest proposal))
Content-Type: text/plain; charset="iso-8859-1" ; format="flowed"
Content-Transfer-Encoding: quoted-printable
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20121106; t=1358981751; bh=fmcX4ekNu83HgRPB0l+XsII5aU7ujzw4GYLYaDteHMA=; h=Received:Received:Mime-Version:Message-Id:Date:To:From:Subject: Content-Type; b=Kpiw1lifWahv6EfSbWZmpKGPs84c49/OlFAdkWfaWZkXN1X+8nqFR9x27yjz7hg1I cZOF1Cd17ueDjMwL9XDSnBVH0CJVnG1fefgUEBVGVwAp+TUuKtEWcCn+J6EFMimsqi BTiPToZO0s8iKYqBXXZWsFCp/269XwRKVyr7RE0RIVUWCvVzYUVHddt6LQVAWYOKt/ kwltysQuEIXLr6iEDDAl4phxHP8BF7ThNButGuqXAUGKTTveR+zrGIB3w+hePhknF1 oc54qNj/RXitJLE/NEdaBcHUNZF3qY6T/Jabe3Rl8um+iizfvZmYMIehDaGnXhyLx6 6QmRypZx78nBQ==
Cc: John Levine <johnl@taugh.com>, ietf@ietf.org, dean.willis@softarmor.com
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 23 Jan 2013 22:55:58 -0000

What was your source for this information?  Or=20
did you just make it up? Because it is faulty.

=46TP did not "grow out of Telnet."  The decision=20
to use Telnet was quite conscious for both FTP=20
and SMTP so that a human at a terminal on a TIP=20
could be FTP or SMTP user process and was hardly=20
vestigial in either case.  Crude, yes.  But=20
served a very distinct purpose.

John Day


At 11:29 PM +0100 1/23/13, Carsten Bormann wrote:
>On Jan 23, 2013, at 20:56, John C Klensin <john-ietf@jck.com> wrote:
>
>>  But having CR as an unambiguous "return to first
>>  character position on line" was important for overstriking
>>  (especially underlining) on a number of devices including line
>>  printers as well as TTY equipment.
>
>But John, on a TTY, you have to send CR NUL, or=20
>the first character will smudge.
>The carriage is still in flight when the next=20
>byte after it is processed, so it better not be=20
>a printing character.
>
>(This is actually the real reason for CR LF:
>CR needs 200 ms to execute because it takes time=20
>to move the carriage, so you have to fill in a=20
>character to waste 100 ms.
>So you might as well separate the CR and LF function, which is what happene=
d.
>Multiple newlines are sent as CR LF LF LF to a=20
>real TTY because LF *does* execute in 100 ms --=20
>moving the paper is quicker.)
>
>Now the reason I'm writing this:
>
>SIP has CRLF because TTY carriages smudged. 
>
>Really.
>
>Please let that sink in a minute.
>
>I think in protocol evolution (as well as=20
>computer system evolution in general) we are=20
>missing triggers to get rid of vestigial=20
>features.
>
>CRLF was quite reasonable for Telnet, as this really was about TTYs.
>FTP grew out of Telnet, so keeping it there was maybe justifiable.
>For SMTP, CRLF already was vestigial; this=20
>should have been fixed when SMTP became separate=20
>from FTP, but maybe the separation was too=20
>gradual (it was too late to fix it 20 years=20
>later in 282x).
>Keeping CRLF for HTTP was a travesty (enjoy RFC=20
>2616 section 19.3 para 3 for added pleasure).
>Keeping it in SIP was unspeakable.
>
>Gr=FC=DFe, Carsten


From worley@shell01.TheWorld.com  Wed Jan 23 14:58:28 2013
Return-Path: <worley@shell01.TheWorld.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DD82621F854F for <ietf@ietfa.amsl.com>; Wed, 23 Jan 2013 14:58:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.98
X-Spam-Level: 
X-Spam-Status: No, score=-2.98 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, RCVD_IN_SORBS_WEB=0.619]
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 9kE4mSgScSHV for <ietf@ietfa.amsl.com>; Wed, 23 Jan 2013 14:58:28 -0800 (PST)
Received: from TheWorld.com (pcls5.std.com [192.74.137.145]) by ietfa.amsl.com (Postfix) with ESMTP id A936121F8468 for <ietf@ietf.org>; Wed, 23 Jan 2013 14:58:22 -0800 (PST)
Received: from shell.TheWorld.com (svani@shell01.theworld.com [192.74.137.71]) by TheWorld.com (8.14.5/8.14.5) with ESMTP id r0NMw2xh001199; Wed, 23 Jan 2013 17:58:04 -0500
Received: from shell01.TheWorld.com (localhost.theworld.com [127.0.0.1]) by shell.TheWorld.com (8.13.6/8.12.8) with ESMTP id r0NMw2s4330662; Wed, 23 Jan 2013 17:58:02 -0500 (EST)
Received: (from worley@localhost) by shell01.TheWorld.com (8.13.6/8.13.6/Submit) id r0NMw2Y5330647; Wed, 23 Jan 2013 17:58:02 -0500 (EST)
Date: Wed, 23 Jan 2013 17:58:02 -0500 (EST)
Message-Id: <201301232258.r0NMw2Y5330647@shell01.TheWorld.com>
From: worley@ariadne.com (Dale R. Worley)
Sender: worley@ariadne.com (Dale R. Worley)
To: John Day <jeanjour@comcast.net>
In-reply-to: <a062408f3cd2610b7f0fc@[10.0.1.3]> (jeanjour@comcast.net)
Subject: Re: CRLF (was: Re: A modest proposal)
References: <20130123061554.85592.qmail@joyce.lan> <C3CD7DDBD81323BD17837BCE@JcK-HP8200.jck.com> <a062408f3cd2610b7f0fc@[10.0.1.3]>
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 23 Jan 2013 22:58:29 -0000

> From: John Day <jeanjour@comcast.net>
> 
> Multics was based on EBCDIC which had a New Line (NL) character but 
> no CR or LF.  The ARPANET went with the ASCII standard.  But I never 
> forgave the ANSI committee for taking left arrow out of the character 
> set (as a replacement operator).

Which suggests that the reason Unix used LF as newline was because
Unix was consciously based on Multics, and Multics had a newline but
no carriage return or line feed.

Dale

From worley@shell01.TheWorld.com  Wed Jan 23 15:00:03 2013
Return-Path: <worley@shell01.TheWorld.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5C59921F86EA for <ietf@ietfa.amsl.com>; Wed, 23 Jan 2013 15:00:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.98
X-Spam-Level: 
X-Spam-Status: No, score=-2.98 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, RCVD_IN_SORBS_WEB=0.619]
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 G3PEjzKiiw8v for <ietf@ietfa.amsl.com>; Wed, 23 Jan 2013 15:00:02 -0800 (PST)
Received: from TheWorld.com (pcls5.std.com [192.74.137.145]) by ietfa.amsl.com (Postfix) with ESMTP id 65BD621F88FC for <ietf@ietf.org>; Wed, 23 Jan 2013 15:00:02 -0800 (PST)
Received: from shell.TheWorld.com (svani@shell01.theworld.com [192.74.137.71]) by TheWorld.com (8.14.5/8.14.5) with ESMTP id r0NMxYUP004844 for <ietf@ietf.org>; Wed, 23 Jan 2013 17:59:36 -0500
Received: from shell01.TheWorld.com (localhost.theworld.com [127.0.0.1]) by shell.TheWorld.com (8.13.6/8.12.8) with ESMTP id r0NMxYUm330731 for <ietf@ietf.org>; Wed, 23 Jan 2013 17:59:34 -0500 (EST)
Received: (from worley@localhost) by shell01.TheWorld.com (8.13.6/8.13.6/Submit) id r0NMxYlX318315; Wed, 23 Jan 2013 17:59:34 -0500 (EST)
Date: Wed, 23 Jan 2013 17:59:34 -0500 (EST)
Message-Id: <201301232259.r0NMxYlX318315@shell01.TheWorld.com>
From: worley@ariadne.com (Dale R. Worley)
Sender: worley@ariadne.com (Dale R. Worley)
To: ietf@ietf.org
In-reply-to: <CAPJ9He0dOttM+DmpUt9MzfWEXcs+tbpJJy4Z+usoRroyAdzJbA@mail.gmail.com> (wjordan129@gmail.com)
Subject: Re: A modest proposal
References: <CAPJ9He0dOttM+DmpUt9MzfWEXcs+tbpJJy4Z+usoRroyAdzJbA@mail.gmail.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 23 Jan 2013 23:00:03 -0000

A great deal of complexity comes from the fact that standards are
rarely created in a vacuum.

In this case, RFC 3261 SIP had to be upward-compatible from RFC 2543
SIP.  And the early design of RFC 2543 SIP was influenced (I am told)
by the idea that SIP messages should be able to go through HTTP
proxies.  (That didn't work out, but the idea is less silly than it
seems, especially if you are contemplating organizations whose only
permitted outside net traffic goes through HTTP proxies...)

So, much of the SIP header formatting was taken from HTTP, which got
it from RFC 822 e-mail message formatting.  And of course, once a
variation is permitted, you *can't take it out*, because some product
with significant market share depends on it.

There is also the necessity to allow for extensibility, which favors
the use of various sorts of separators rather than a fixed sequence of
fixed-length fields.

As for CR-LF, that is conformity to the ASCII standard by RFC 822,
where "CR" stands for "carriage return" and "LF" stands for "line
feed".  Exactly why those functions were given separate control
characters I don't know, but I suspect it was to allow overstriking.
The CF-LF standard was largely followed back in 1982, especially in
Digital Equipment Corporation systems, which were the backbone of the
Arpanet.  So CR-LF remains the conventional line ending in Internet
protocols.  The use of LF alone seems to come largely from the Unix
lineage of systems.

There is also a strong tendency to favor protocols that are readable
and writable by humans as text strings (among other things, that makes
debugging easier), so formatting alternatives are added to make those
tasks easier.

Dale

From jeanjour@comcast.net  Wed Jan 23 15:05:36 2013
Return-Path: <jeanjour@comcast.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A37EA21F8831 for <ietf@ietfa.amsl.com>; Wed, 23 Jan 2013 15:05:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.088
X-Spam-Level: 
X-Spam-Status: No, score=-100.088 tagged_above=-999 required=5 tests=[AWL=0.349, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_NET=0.611, RDNS_NONE=0.1, USER_IN_WHITELIST=-100]
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 HMm2zcZTmJpg for <ietf@ietfa.amsl.com>; Wed, 23 Jan 2013 15:05:36 -0800 (PST)
Received: from qmta02.emeryville.ca.mail.comcast.net (qmta02.emeryville.ca.mail.comcast.net [IPv6:2001:558:fe2d:43:76:96:30:24]) by ietfa.amsl.com (Postfix) with ESMTP id 2335821F875A for <ietf@ietf.org>; Wed, 23 Jan 2013 15:05:36 -0800 (PST)
Received: from omta23.emeryville.ca.mail.comcast.net ([76.96.30.90]) by qmta02.emeryville.ca.mail.comcast.net with comcast id rSFa1k0041wfjNsA2b5WHa; Wed, 23 Jan 2013 23:05:30 +0000
Received: from [10.0.1.3] ([79.145.202.255]) by omta23.emeryville.ca.mail.comcast.net with comcast id rb541k00B5X7tlr8jb5B6S; Wed, 23 Jan 2013 23:05:25 +0000
Mime-Version: 1.0
Message-Id: <a062408f7cd261c209d76@[10.0.1.3]>
In-Reply-To: <alpine.LRH.2.01.1301231424200.16244@egate.xpasc.com>
References: <20130123061554.85592.qmail@joyce.lan> <C3CD7DDBD81323BD17837BCE@JcK-HP8200.jck.com> <a062408f3cd2610b7f0fc@[10.0.1.3]> <alpine.LRH.2.01.1301231424200.16244@egate.xpasc.com>
Date: Wed, 23 Jan 2013 18:05:01 -0500
To: ietf@ietf.org
From: John Day <jeanjour@comcast.net>
Subject: Re: CRLF (was: Re: A modest proposal)
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20121106; t=1358982330; bh=E63VLpVsx3OsG4Tf4K8hPjXgEbMH5c5Rri283yjN4a4=; h=Received:Received:Mime-Version:Message-Id:Date:To:From:Subject: Content-Type; b=bNoLDo/sDTCDf24OEU78TwxXW+tvveugPzO8lN8/UYY0eBD7BQQFpxlqBwyKCCAbz 6AFbiF6h8e/DIZOwbDjXIgIQqJhUSaojZai1I9JqI/BhwOkmBddQcA1cK4xOx9lrXe 5d39fpPm0aPp7SaHeJmebiEnuAVx9xe407pjjOPFlEQERE9WcM34YXA/Uc4wDimQdF 0JU4U+JqSHJfyFCyc7RjMHKzU/7/7n7UUNAQVkpl25HgOZ++WqpLqjFL8kZm1hqNcJ 2evFs1+yVpm36X6XluqeuQE+sFL13d07Ykmnu+NDC3CwSYZrm0rnfHMQ2dpBSoDCOn VP7Vrq5BBxMFA==
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 23 Jan 2013 23:05:36 -0000

Then what am I mis-remembering? ;-)  Was it that Multics didn't use 
CRLF and only NL?  I remember this as quite a point of discussion 
when we were defining Telnet and FTP.

>On Wed, 23 Jan 2013, John Day wrote:
>
>>  >
>>  > IIR, Multics from several years earlier.  I'd have to dig
>>  > through old manuals to remember what CTSS did, but that system
>>  > (and the IBM Model 1050 and 2741 devices often used as terminals
>>  > with it) were somewhat pre-ASCII (and long before ECMA-48/ ANSI
>>  > X3.64 and the VT100 and friends)  and, IIR, sent and received
>>  > shift and rotate codes rather than what we would normally
>>  > consider character codes today.  The character codes were just
>>  > input to device drivers that dealt with device characteristics
>>
>>  Multics was based on EBCDIC which had a New Line (NL) character but no CR or
>>  LF.  The ARPANET went with the ASCII standard.  But I never forgave the ANSI
>>  committee for taking left arrow out of the character set (as a replacement
>>  operator).
>
>EBCDIC has NL (new line), LF and CR characters (hex 0x15, 0x25 and 0x0d
>respectively). EBCDIC was an 8 bit code easy to translate in hardware
>logic from punch card codes to the 8 bit code. Earlier IBM systems
>used BCD (sometimes called BCDIC) which was a 6 bit code which did
>not have CR or LF but had a subset of the EBCDIC style mapping from
>punched cards to computer code. IBM systems all implemented a
>record based file organization rather than the character stream
>of UNIX. So the BCD generation systems had a record mark charcter
>(and word mark) in the pre-S/360 days with BCD and file system
>level record tracking in S/360.
>
>IBM terminal devices (e.g., 2740, 2741, 1050, etc.) of the pre VDT era
>used a different character coding on the wire (not BCD). Might have
>been inspired by tilt/rotate, I don't know and never worried about more
>than getting the translate table right. Hardware communications
>controllers and later programmable controllers recoginzed the NL
>character and signaled end of line/record to the host computer.
>
>IBM lineprinters of the era were record/line oriented devices which
>printed about 132 characters per line and advanced to new like, page,
>etc. based on device specific commands and not data interpretation.
>ANSI line controls or IBM internal codes could be used in the first
>character of the line to pre/post space 0 or more lines for each
>print record.
>
>VDTs with long lines might have been inspired by line printers or
>just the idea that long lines were better. No experience there,
>but I'm pretty certain there were no 132 column punch cards in
>common use which would have influnced comody VDT designers. 80
>and I believe 96 in S/3 days.
>
>Dave Morris


From john-ietf@jck.com  Wed Jan 23 16:08:45 2013
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E4E7121F859A for <ietf@ietfa.amsl.com>; Wed, 23 Jan 2013 16:08:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.849
X-Spam-Level: 
X-Spam-Status: No, score=-102.849 tagged_above=-999 required=5 tests=[AWL=-0.250, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 Le8voAAb5jSf for <ietf@ietfa.amsl.com>; Wed, 23 Jan 2013 16:08:44 -0800 (PST)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 2B10921F845D for <ietf@ietf.org>; Wed, 23 Jan 2013 16:08:44 -0800 (PST)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1TyAN1-000CGI-Bp; Wed, 23 Jan 2013 19:08:43 -0500
Date: Wed, 23 Jan 2013 19:08:38 -0500
From: John C Klensin <john-ietf@jck.com>
To: John Day <jeanjour@comcast.net>, ietf@ietf.org
Subject: Re: CRLF (was: Re: A modest proposal)
Message-ID: <57B220AA9F11881BDF0A7F66@JcK-HP8200.jck.com>
In-Reply-To: <a062408f7cd261c209d76@[10.0.1.3]>
References: <20130123061554.85592.qmail@joyce.lan> <C3CD7DDBD81323BD17837BCE@JcK-HP8200.jck.com> <a062408f3cd2610b7f0fc@[10.0.1.3]> <alpine.LRH.2.01.1301231424200.16244@egate.xpasc.com> <a062408f7cd261c209d76@[10.0.1.3]>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 24 Jan 2013 00:08:45 -0000

--On Wednesday, January 23, 2013 18:05 -0500 John Day
<jeanjour@comcast.net> wrote:

> Then what am I mis-remembering? ;-)  Was it that Multics
> didn't use CRLF and only NL?  I remember this as quite a point
> of discussion when we were defining Telnet and FTP.
> 
>> On Wed, 23 Jan 2013, John Day wrote:
>> 
>>>  > 
>>>  > IIR, Multics from several years earlier.  I'd have to dig
>>>  > through old manuals to remember what CTSS did, but that
>>>  > system (and the IBM Model 1050 and 2741 devices often
>>>  > used as terminals with it) were somewhat pre-ASCII (and
>>>  > long before ECMA-48/ ANSI X3.64 and the VT100 and
>>>  > friends)  and, IIR, sent and received shift and rotate
>>>  > codes rather than what we would normally consider
>>>  > character codes today.  The character codes were just
>>>  > input to device drivers that dealt with device
>>>  > characteristics
>>> 
>>>  Multics was based on EBCDIC which had a New Line (NL)
>>>  character but no CR or LF.  The ARPANET went with the ASCII
>>>  standard.  But I never forgave the ANSI committee for
>>>  taking left arrow out of the character set (as a replacement
>>>  operator).

Interesting theory, but Multics was definitely not EBCDIC-based.
The various IBM mainframes, including most importantly the UCLA
one, presumably were but Multics used a GE 645 base with (7 bit)
ASCII right justified in a 9-bit byte, four characters per 36
bit word.  That contrasted with Tenex and later TOPS-20, which
also used ASCII but as five characters in the 36 bit word with
the sign bit ignored for character purposes.

>> EBCDIC has NL (new line), LF and CR characters (hex 0x15,
>> 0x25 and 0x0d respectively). EBCDIC was an 8 bit code easy to
>> translate in hardware logic from punch card codes to the 8
>> bit code. Earlier IBM systems used BCD (sometimes called
>> BCDIC) which was a 6 bit code which did not have CR or LF but
>> had a subset of the EBCDIC style mapping from punched cards
>> to computer code. IBM systems all implemented a record based
>> file organization rather than the character stream of UNIX.
>> So the BCD generation systems had a record mark charcter (and
>> word mark) in the pre-S/360 days with BCD and file system
>> level record tracking in S/360.

IIR, parts of this aren't quite right either because the
CP/67-CMS architecture (which evolved into VM/CMS) was partially
based on CTSS and didn't follow a number of "traditional" IBM
conventions.  The S/360 mainframes also supported ASCII, but in
an odd encoding in which the spare bit was in the middle of the
byte and used, again IIR, for parity rather than being always
zero.

>...
>> VDTs with long lines might have been inspired by line
>> printers or just the idea that long lines were better. No
>> experience there, but I'm pretty certain there were no 132
>> column punch cards in common use which would have influnced
>> comody VDT designers. 80 and I believe 96 in S/3 days.

That is correct.  80, 96 (with an oddly-shaped card), and the
Univac round-holed one (don't remember how many columns it ended
up with).  The bigger VDT issue was that they tended to use
character cell architectures and made a non-destructive
backspace and composed/overstruck characters (not just simulated
boldface) impossible.

    john



From allison.mankin@gmail.com  Wed Jan 23 16:33:09 2013
Return-Path: <allison.mankin@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7BB6521F8514; Wed, 23 Jan 2013 16:33:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_21=0.6, NO_RELAYS=-0.001]
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 fUaCyM34Ilna; Wed, 23 Jan 2013 16:33:08 -0800 (PST)
Received: from mail-wg0-x229.google.com (wg-in-x0229.1e100.net [IPv6:2a00:1450:400c:c00::229]) by ietfa.amsl.com (Postfix) with ESMTP id 44A8A21F84E6; Wed, 23 Jan 2013 16:33:07 -0800 (PST)
Received: by mail-wg0-f41.google.com with SMTP id ds1so3117wgb.4 for <multiple recipients>; Wed, 23 Jan 2013 16:33:06 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to:cc :content-type; bh=oOSJIe4Zj5NhP7YIEeJskF2y/E6qqjM1SAYnfQHb0+g=; b=hp7hBPfqizDe0QCYlkQoQhJDW9t1O0eISF2NPVBCf9Zle77yvFkznAmPUVJHd8VXpY pZGVNrHnO7t9nRPDog+IViB+Gq0oUOys30IhcCrggwtTqDcqUOITG/5Foe8pYQTog/8e bKvens1f0h4GFGXQm+hfrFLlL3P/bf5lxylYq4MnmQoq6Nuzlz9tx1N2waZKyFYw6oMt cUt55DdBYrZ746C+koC4jXcYOMJJX4cer3BnJmJ9/Hh4NGAsIo6vSQEAngFhQ8Rj6Rbp PObIBgVhKauCtPMSMfyo7Tfy3HsVj7K55AAA+FIsbPz9MboVmiS9DqkcQZV6/Wpr4QRF bp9w==
MIME-Version: 1.0
X-Received: by 10.194.20.231 with SMTP id q7mr55939wje.44.1358987586383; Wed, 23 Jan 2013 16:33:06 -0800 (PST)
Received: by 10.217.80.2 with HTTP; Wed, 23 Jan 2013 16:33:06 -0800 (PST)
Date: Wed, 23 Jan 2013 19:33:06 -0500
Message-ID: <CAP8yD=tF4_2RpNZNAHRR65HTZGwSPE+Pjx8-a8H_vQHNjqfEoA@mail.gmail.com>
Subject: TSV-DIR review of draft-ietf-6man-ipv6-atomic-fragments-03
From: Allison Mankin <allison.mankin@gmail.com>
To: IETF Discuss <ietf@ietf.org>
Content-Type: multipart/alternative; boundary=047d7b451208572fd404d3fdf429
Cc: 6man@ietf.org, Transport Area <tsv-area@ietf.org>, Transport Directorate <tsv-dir@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 24 Jan 2013 00:33:09 -0000

--047d7b451208572fd404d3fdf429
Content-Type: text/plain; charset=ISO-8859-1

Transport Directorate review of
https://datatracker.ietf.org/doc/draft-ietf-6man-ipv6-atomic-fragments

I've reviewed this document as part of the transport area directorate's
ongoing effort to review key IETF documents. These comments were written
primarily for the transport area directors, but are copied to the
document's authors for their information and to allow them to address any
issues raised.  Please always CC tsv-dir@ietf.org if you reply to or
forward this review.

Summary
-------------
This draft is on the right track but has issues, described in the review,
that call for a bigger picture.

In addition to reading the draft, I read over the documents it references,
and I also read through the AD Review thread about the 02 version of the
draft, on the 6man mailing list.

It is clearly valuable to call the community's attention to the "atomic
fragment" in IPv6.  This is an IPv6 datagram that is not actually
fragmented, but has a Fragmentation Header (with an offset of 0 and the M
bit set to 0).  It seems the atomic fragment in IPv6 arose to accommodate
translation gateways with MTUs of less than 1280 (the IPv6 minimum) on the
IPv4 side [1].  The problem is that you can force a sender to generate
atomic fragments instead of normal packets from an off-path node, if the
sender doesn't filter ICMPv6 much.

I've tried to make a schematic of the problem and solution described by the
draft.

A is the IPv6 sender that either does not or cannot filter incoming ICMPv6
very well and that chooses Fragmentation IDs in a predictable way when it
must fragment.

E is a blind attacker (or collaborating blind attackers), not on path/in
the middle for A.

B is the destination for A's traffic.  B initially doesn't distinguish
between atomic fragments and normal fragments.  However, B has implemented
another solution [2], RFC 5722, which requires that IPv6 fragments be
dropped silently if they overlap (have the same IDs and carry material from
the same offset+fragment length).

ORIGINAL ATTACK
---------------------------

T0   A to B:    v6-dgram --->

T1  E to A:    ICMPv6 Too Big (MTU<1280)

T2  A to B:     switch to v6-atomic-fragment, ID=X, Offset=0

T3  E to B:     blind-inserted overlapping v6-fragment, ID=X, Offset=0

T4  B:             A's T2 data should have gotten through.  But E's T3
fragment forces silent drop.

DRAFT'S SOLUTION
-----------------------------
The draft says that B MUST process atomic fragments "in isolation", not in
relation to the fragment queue.  Further discussion in next section.

T'0-T'3:          same as T0-T3 above.

T'4 B:             receive and process A's atomic fragment, with no regard
to E's insertion.

RESIDUAL RISK?
-------------------------
In the AD Review thread, Brian Haberman asks the "WG  if the solution
actually creates an attack vector on receiving hosts." A roll-up of the
several-message exchange between Haberman and Fernando Gont, the draft
author, can be found in
http://www.ietf.org/mail-archive/web/ipv6/current/msg16807.html.   From a
Transport point of view, I agree that there could be a new attack vector on
the receivers.

Consider first that E successfully got a spoofed fragment onto B's fragment
queue.  What if E turns that fragment into an atomic fragment.
Post-mitigation, E's datagram no longer causes A's datagram to be blocked,
but does the processing of E's atomic fragment "in isolation" introduce a
greater chance than before that E's datagram can pass from B successfully
to the ULP?

It depends on what processing an atomic fragment "in isolation" means
specifically.  The draft says this:

      A host that receives an IPv6 packet which includes a Fragment
      Header with the "Fragment Offset" equal to 0 and the "M" bit equal
      to 0 MUST process such packet in isolation from any other packets/
      fragments, even if such packets/fragments contain the same set
      {IPv6 Source Address, IPv6 Destination Address, Fragment
      Identification}.  A received "atomic fragments" should be
      "reassembled" from the contents of that sole fragment.

And this:

      Additionally, if any fragments with the same set {IPV6 Source
      Address, IPv6 Destination Address, Fragment Identification} are
      present in the fragment reassembly queue when the atomic fragment
      is received, such fragments MUST NOT be discarded upon receipt of
      the "colliding" IPv6 atomic fragment, since IPv6 atomic fragments
      MUST NOT interfere with "normal" fragmented traffic.


So now a receiver is forced to process an atomic datagram even if there are
overlapping fragments already there on the fragmentation queue.

NEW ATTACK VECTOR
---------------------------------
T"0   A to B:    v6-dgram --->

T"1  E to A:    ICMPv6 Too Big (MTU<1280)

T"2  A to B:     switch to v6-atomic-fragment, ID=X, Offset=0
T"2a B:           deliver A's datagram to ULP

T"3  E to B:     blind-inserted overlapping v6-atomic-fragment, ID=X,
Offset=0
T"3a B:           deliver E's overlapping datagram to ULP

T"4:  B:           TCP attack mitigated by RFC 5722 looks possible again
[see Note 3].

Conclusion
---------------
There's an interesting table in the draft showing which sending stacks can
be tricked into switching to v6-atomic-fragments and which receiving ones
can be tricked into dropping them due to fragment overlap.  Another way of
looking at this table is that a lot of stacks need to be less predictable
and more suspicious of spoofing traffic.  The present draft is
pragmatic/empirical and is interested in fixing a problem that exists (it
can be brought on).  But I wonder if it would be better to embed the
discussion of atomic fragments and fragment overlap in a larger picture, a
collected set of best practices against spoofers (of ICMPv6, of IPv6
fragments or otherwise).  In the larger context, I agree that what's in
this draft has a part - on its own, not sure it stands.

Notes
---------
[1] (Digression) I'd love to call for a Law of Kludges that says that if
you are gatewaying two protocols, the one that is older should always be
the one that graciously accepts the kludges; I'm not deeply enough into
this all to understand why the gateway's IPv4 side needs the IPv6 side to
supply it with a Fragmentation header - why it couldn't create fragments
into IPv4 independent of the original IPv6?

[2] To a point problem...

[3] In RFC 5722, the crux of why B has to drop overlapping IPv6 fragments
is these paragraphs:

   The TCP header has the following values of the flags: S(YN)=1 and
   A(CK)=1.  This may make an inspecting stateful firewall think that it
   is a response packet for a connection request initiated from the
   trusted side of the firewall.  Hence, it will allow the fragment to
   pass.  It will also allow the following fragments with the same
   Fragment Identification value in the fragment header to pass through.

   A malicious node can form a second fragment with a TCP header that
   changes the flags and sets S(YN)=1 and A(CK)=0.  This can change the
   packet on the receiving end to consider the packet as a connection
   request instead of a response.  By doing this, the malicious node has
   bypassed the firewall's access control to initiate a connection
   request to a node protected by a firewall.

--047d7b451208572fd404d3fdf429
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Transport Directorate review of <a href=3D"https://datatracker.ietf.org/doc=
/draft-ietf-6man-ipv6-atomic-fragments" target=3D"_blank">https://datatrack=
er.ietf.org/doc/draft-ietf-6man-ipv6-atomic-fragments</a><br><br>I&#39;ve r=
eviewed this document as part of the transport area directorate&#39;s
ongoing effort to review key IETF documents. These comments were
written primarily for the transport area directors, but are copied
to the document&#39;s authors for their information and to allow them
to address any issues raised.=A0 Please always CC <a href=3D"mailto:tsv-dir=
@ietf.org" target=3D"_blank"><span></span>tsv-dir@ietf.org</a> if you=20
reply to or forward this review.
<br><br>Summary<br>-------------<br>This draft is on the right track but ha=
s issues, described in the review, that call for a bigger picture.<br><br>I=
n addition to reading the draft, I read over the documents it references, a=
nd I also read through the AD Review thread about the 02 version of the dra=
ft, on the 6man mailing list. <br>
<br>It is clearly valuable to call the community&#39;s attention to the &qu=
ot;atomic fragment&quot; in IPv6.=A0 This is an IPv6 datagram that is not a=
ctually fragmented, but has a Fragmentation Header (with an offset of 0 and=
 the M bit set to 0).=A0 It seems the atomic fragment in IPv6 arose to acco=
mmodate translation gateways with MTUs of less than 1280 (the IPv6 minimum)=
 on the IPv4 side [1].=A0 The problem is that you can force a sender to gen=
erate atomic fragments instead of normal packets from an off-path node, if =
the sender doesn&#39;t filter ICMPv6 much.=A0 <br>
<br>I&#39;ve tried to make a schematic of the problem and solution describe=
d by the draft. <br><br>A is the IPv6 sender that either does not or cannot=
 filter incoming ICMPv6 very well and that chooses Fragmentation IDs in a p=
redictable way when it must fragment.<br>
<br>E is a blind attacker (or collaborating blind attackers), not on path/i=
n the middle for A. <br><br>B is the destination for A&#39;s traffic.=A0 B =
initially doesn&#39;t distinguish between atomic fragments and normal fragm=
ents.=A0 However, B has implemented another solution [2], RFC 5722, which r=
equires that IPv6 fragments be dropped silently if they overlap (have the s=
ame IDs and carry material from the same offset+fragment length). <br>
<br>ORIGINAL ATTACK <br>---------------------------<br>=A0<br>T0=A0=A0 A to=
 B: =A0=A0 v6-dgram ---&gt; <br><br>T1=A0 E to A:=A0=A0=A0 ICMPv6 Too Big (=
MTU&lt;1280)<br><br>T2=A0 A to B:=A0=A0=A0=A0 switch to v6-atomic-fragment,=
 ID=3DX, Offset=3D0<br><br>T3=A0 E to B:=A0=A0=A0=A0 blind-inserted overlap=
ping v6-fragment, ID=3DX, Offset=3D0<br>
<br>T4=A0 B:=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 A&#39;s T2 data should hav=
e gotten through.=A0 But E&#39;s T3 fragment forces silent drop.=A0 <br><br=
>DRAFT&#39;S SOLUTION<br>-----------------------------<br>The draft says th=
at B MUST process atomic fragments &quot;in isolation&quot;, not in relatio=
n to the fragment queue.=A0 Further discussion in next section. <br>
<br>T&#39;0-T&#39;3:=A0=A0=A0=A0=A0=A0=A0=A0=A0 same as T0-T3 above.<br><br=
>T&#39;4 B:=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 receive and process A&#39;s=
 atomic fragment, with no regard to E&#39;s insertion.<br><br>RESIDUAL RISK=
?<br>-------------------------<br>In the AD Review thread, Brian Haberman a=
sks the &quot;WG=A0 if the solution actually creates an attack vector on re=
ceiving hosts.&quot; A roll-up of the several-message exchange between Habe=
rman and Fernando Gont, the draft author, can be found in <a href=3D"http:/=
/www.ietf.org/mail-archive/web/ipv6/current/msg16807.html">http://www.ietf.=
org/mail-archive/web/ipv6/current/msg16807.html</a>.=A0=A0 From a Transport=
 point of view, I agree that there could be a new attack vector on the rece=
ivers.<br>
<br>Consider first that E successfully got a spoofed fragment onto B&#39;s =
fragment queue.=A0 What if E turns that fragment into an atomic fragment. P=
ost-mitigation, E&#39;s datagram no longer causes A&#39;s datagram to be bl=
ocked, but does the processing of E&#39;s atomic fragment &quot;in isolatio=
n&quot; introduce a greater chance than before that E&#39;s datagram can pa=
ss from B successfully to the ULP?=A0 <br>
<br>It depends on what processing an atomic fragment &quot;in isolation&quo=
t; means specifically.=A0 The draft says this:<br><br><pre class=3D"newpage=
">      A host that receives an IPv6 packet which includes a Fragment
      Header with the &quot;Fragment Offset&quot; equal to 0 and the &quot;=
M&quot; bit equal
      to 0 MUST process such packet in isolation from any other packets/
      fragments, even if such packets/fragments contain the same set
      {IPv6 Source Address, IPv6 Destination Address, Fragment
      Identification}.  A received &quot;atomic fragments&quot; should be
      &quot;reassembled&quot; from the contents of that sole fragment.<br><=
/pre>And this:<br><pre class=3D"newpage">      Additionally, if any fragmen=
ts with the same set {IPV6 Source
      Address, IPv6 Destination Address, Fragment Identification} are
      present in the fragment reassembly queue when the atomic fragment
      is received, such fragments MUST NOT be discarded upon receipt of
      the &quot;colliding&quot; IPv6 atomic fragment, since IPv6 atomic fra=
gments
      MUST NOT interfere with &quot;normal&quot; fragmented traffic.</pre><=
br>So now a receiver is forced to process an atomic datagram even if there =
are overlapping fragments already there on the fragmentation queue.=A0 <br>
<br>NEW ATTACK VECTOR<br>---------------------------------<br>T&quot;0=A0=
=A0 A to B: =A0=A0 v6-dgram ---&gt; <br><br>T&quot;1=A0 E to A:=A0=A0=A0 IC=
MPv6 Too Big (MTU&lt;1280)<br><br>T&quot;2=A0 A to B:=A0=A0=A0=A0 switch to=
 v6-atomic-fragment, ID=3DX, Offset=3D0<br>
T&quot;2a B:=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 deliver A&#39;s datagram to ULP =
<br><br>T&quot;3=A0 E to B:=A0=A0=A0=A0 blind-inserted overlapping v6-atomi=
c-fragment, ID=3DX, Offset=3D0<br>T&quot;3a B: =A0 =A0 =A0 =A0 =A0 deliver =
E&#39;s overlapping datagram to ULP<br><br>
T&quot;4:=A0 B: =A0 =A0 =A0 =A0 =A0 TCP attack mitigated by RFC 5722 looks =
possible again [see Note 3].=A0 <br><br>Conclusion<br>--------------- <br>T=
here&#39;s an interesting table in the draft showing which sending stacks c=
an be tricked into switching to v6-atomic-fragments and which receiving one=
s can be tricked into dropping them due to fragment overlap.=A0 Another way=
 of looking at this table is that a lot of stacks need to be less predictab=
le and more suspicious of spoofing traffic.=A0 The present draft is pragmat=
ic/empirical and is interested in fixing a problem that exists (it can be b=
rought on).=A0 But I wonder if it would be better to embed the discussion o=
f atomic fragments and fragment overlap in a larger picture, a collected se=
t of best practices against spoofers (of ICMPv6, of IPv6 fragments or other=
wise).=A0 In the larger context, I agree that what&#39;s in this draft has =
a part - on its own, not sure it stands.=A0 <br>
<br>Notes<br>---------<br>[1] (Digression) I&#39;d love to call for a Law o=
f Kludges that says that if you are=20
gatewaying two protocols, the one that is older should always be the one
 that graciously accepts the kludges; I&#39;m not deeply enough into this=
=20
all to understand why the gateway&#39;s IPv4 side needs the IPv6 side to=20
supply it with a Fragmentation header - why it couldn&#39;t create fragment=
s into=20
IPv4 independent of the original IPv6? <br><br>[2] To a point problem...<br=
><br>[3] In RFC 5722, the crux of why B has to drop overlapping IPv6 fragme=
nts is these paragraphs:<br><pre>   The TCP header has the following values=
 of the flags: S(YN)=3D1 and
   A(CK)=3D1.  This may make an inspecting stateful firewall think that it
   is a response packet for a connection request initiated from the
   trusted side of the firewall.  Hence, it will allow the fragment to
   pass.  It will also allow the following fragments with the same
   Fragment Identification value in the fragment header to pass through.

   A malicious node can form a second fragment with a TCP header that
   changes the flags and sets S(YN)=3D1 and A(CK)=3D0.  This can change the
   packet on the receiving end to consider the packet as a connection
   request instead of a response.  By doing this, the malicious node has
   bypassed the firewall&#39;s access control to initiate a connection
   request to a node protected by a firewall.</pre><br><br>

--047d7b451208572fd404d3fdf429--

From john-ietf@jck.com  Wed Jan 23 17:21:04 2013
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E317821F8684 for <ietf@ietfa.amsl.com>; Wed, 23 Jan 2013 17:21:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.799
X-Spam-Level: 
X-Spam-Status: No, score=-102.799 tagged_above=-999 required=5 tests=[AWL=-0.200, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 yr8AauhyEVOB for <ietf@ietfa.amsl.com>; Wed, 23 Jan 2013 17:21:02 -0800 (PST)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 38B6221F867D for <ietf@ietf.org>; Wed, 23 Jan 2013 17:21:02 -0800 (PST)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1TyBUx-000CKG-98; Wed, 23 Jan 2013 20:20:59 -0500
Date: Wed, 23 Jan 2013 20:20:54 -0500
From: John C Klensin <john-ietf@jck.com>
To: Carsten Bormann <cabo@tzi.org>
Subject: Re: Vestigial Features (was Re: CRLF (was: Re: A modest proposal))
Message-ID: <B2984BB2A992EA17292A79F1@JcK-HP8200.jck.com>
In-Reply-To: <8EFA8168-7F05-4010-975C-CE601361501C@tzi.org>
References: <20130123061554.85592.qmail@joyce.lan> <C3CD7DDBD81323BD17837BCE@JcK-HP8200.jck.com> <8EFA8168-7F05-4010-975C-CE601361501C@tzi.org>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Cc: John Levine <johnl@taugh.com>, ietf@ietf.org, dean.willis@softarmor.com
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 24 Jan 2013 01:21:04 -0000

--On Wednesday, January 23, 2013 23:29 +0100 Carsten Bormann
<cabo@tzi.org> wrote:

> On Jan 23, 2013, at 20:56, John C Klensin <john-ietf@jck.com>
> wrote:
> 
>> But having CR as an unambiguous "return to first
>> character position on line" was important for overstriking
>> (especially underlining) on a number of devices including line
>> printers as well as TTY equipment.
> 
> But John, on a TTY, you have to send CR NUL, or the first
> character will smudge. The carriage is still in flight when
> the next byte after it is processed, so it better not be a
> printing character.

Oh, my.  This is getting to be interesting.  I had no direct
interaction with or insight into the ASA (later ANSI) committee
that did ASCII so, while I heard some stories, I can't do more
than speculate on why they made some of the decisions they did.
But both Multics and CTSS supported a variety of terminal
devices -- hardcopy and CRTs (storage tube and actively
refreshed), wide and narrow, character and line-oriented, and so
on.  Between the mid-60s and the mid-70s, the devices on or next
to my various MIT desks went from 1050, to 2741, to TTY 37, to
Imlac PDS-1D, with some sort of storage tube "glass TTY" in
between.  The various hardcopy devices all had timing
idiosyncrasies until they started acquiring significant local
buffering.  The Imlac was high enough resolution (2000 points
square) that I could put it into 132 character mode, but the
characters, while sharp, got pretty small.  Those devices ran at
transmission speeds from about 10cps up to 19.2kpbs and above.
It is probably also relevant that CTSS and Multics both
preferred "half-duplex" (really non-echoplex) operation in which
there was no expectation that the remote host (or controller)
would echo back the characters that the user typed and that a
few of the relevant devices transmitted line-at-a-time rather
than character-at-a-time.

All of this led, very early, to the realization that one better
have standard coding on the system so that programs that didn't
have to be specialized to the output device for some other
reason (hard to display 2000x2000 point dynamic vector graphics
on a Teletype) operated in a device-independent way with device
drivers that adapted between the standard coding to the
particular terminal.  So, yes, some TTY units needed padding
characters or other delays and sometimes it varied depending on
the relationship between current carriage position and intended
one.  But that was a device driver problem (and lots of the
device drivers ran on peripheral controllers, not the
mainframe)-- no CTSS or Multics program that used the system
device drivers ever had a NUL or character timing as part of its
application-level data stream.  Those device drivers also did a
lot of string canonicalization, eliminating problems with string
comparison that we've reinvented with Unicode (see, e.g., the
PRECIS WG for more discussion).   If the device transmitted
NULs, they would disappear before being delivered to the
application.

> (This is actually the real reason for CR LF:
> CR needs 200 ms to execute because it takes time to move the
> carriage, so you have to fill in a character to waste 100 ms.
> So you might as well separate the CR and LF function, which is
> what happened. Multiple newlines are sent as CR LF LF LF to a
> real TTY because LF *does* execute in 100 ms -- moving the
> paper is quicker.)

As I said, I wasn't part of the committee that did ASCII.   I do
know that CR was extensively used, in both our terminal
environment and in a number of ones involving line printers
without LF as a way to arrange overstriking (for bold,
underlining, and composed characters) on line-oriented devices
that couldn't handle backspacing.   Again, that was mostly in
the device drivers: an application program would see
   xxxo<BS>'yyy 
whether that was transmitted or 
   xxxoyyy<CR>   ' 
or, as mentioned earlier, whatever the first-character-of-line
printer control sequence was that would yield the same result.

I don't know the history, but have always assumed that the
experience above was one of the inputs to the development of NVT
and other terminal abstractions on the ARPANET rather that using
an "every machine needs to know the properties of every
terminal" model.  Sadly, we lost both of the people who would
have been most likely to know last year.

> Now the reason I'm writing this:
> 
> SIP has CRLF because TTY carriages smudged. 

SIP has CRLF because every single application protocol we have
that uses character-oriented commands is modeled on NVT, and NVT
uses CRLF.  You can theorize all you like about how NVT got that
way (and might be right although given what I know of the way
things unfolded, I'd be a little surprised).  But it is NVT that
is the issue. 

>...
> CRLF was quite reasonable for Telnet, as this really was about
> TTYs. FTP grew out of Telnet, so keeping it there was maybe
>...

Others have commented on the above statement, but the culprit is
NVT and the decisions were very explicit, not accidents of "we
did it that way the last time so should do it again without
thinking", _especially_ after Unix became dominant on the
network.

   john


From randy_presuhn@mindspring.com  Wed Jan 23 18:18:49 2013
Return-Path: <randy_presuhn@mindspring.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D64C921F8713 for <ietf@ietfa.amsl.com>; Wed, 23 Jan 2013 18:18:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 ay5WJKOSBze0 for <ietf@ietfa.amsl.com>; Wed, 23 Jan 2013 18:18:49 -0800 (PST)
Received: from elasmtp-mealy.atl.sa.earthlink.net (elasmtp-mealy.atl.sa.earthlink.net [209.86.89.69]) by ietfa.amsl.com (Postfix) with ESMTP id 371BC21F8518 for <ietf@ietf.org>; Wed, 23 Jan 2013 18:18:48 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=mindspring.com; b=I1vDb+RcXyz2RNnCsI9CWleo6XO2abKS/jyLYH/AZoLImCeOSdpFR4saffKW1Ie0; h=Received:Message-ID:From:To:References:Subject:Date:MIME-Version:Content-Type:Content-Transfer-Encoding:X-Priority:X-MSMail-Priority:X-Mailer:X-MimeOLE:X-ELNK-Trace:X-Originating-IP;
Received: from [99.35.225.138] (helo=oemcomputer) by elasmtp-mealy.atl.sa.earthlink.net with esmtpa (Exim 4.67) (envelope-from <randy_presuhn@mindspring.com>) id 1TyCOt-0003r6-1f for ietf@ietf.org; Wed, 23 Jan 2013 21:18:47 -0500
Message-ID: <000401cdf9d9$86882060$6b01a8c0@oemcomputer>
From: "Randy Presuhn" <randy_presuhn@mindspring.com>
To: <ietf@ietf.org>
References: <20130123061554.85592.qmail@joyce.lan><C3CD7DDBD81323BD17837BCE@JcK-HP8200.jck.com><8EFA8168-7F05-4010-975C-CE601361501C@tzi.org> <B2984BB2A992EA17292A79F1@JcK-HP8200.jck.com>
Subject: Re: Vestigial Features (was Re: CRLF (was: Re: A modest proposal))
Date: Wed, 23 Jan 2013 18:21:29 -0800
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1478
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1478
X-ELNK-Trace: 4488c18417c9426da92b9037bc8bcf44d4c20f6b8d69d88868e0cd313c0eb97e3ec4521d309de1ca47c5f88eda2a236f350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 99.35.225.138
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 24 Jan 2013 02:18:50 -0000

Hi -

> From: "John C Klensin" <john-ietf@jck.com>
> To: "Carsten Bormann" <cabo@tzi.org>
> Cc: "John Levine" <johnl@taugh.com>; <ietf@ietf.org>; <dean.willis@softarmor.com>
> Sent: Wednesday, January 23, 2013 5:20 PM
> Subject: Re: Vestigial Features (was Re: CRLF (was: Re: A modest proposal))
...
> So, yes, some TTY units needed padding
> characters or other delays and sometimes it varied depending on
> the relationship between current carriage position and intended
> one.  But that was a device driver problem (and lots of the
> device drivers ran on peripheral controllers, not the
> mainframe)-- no CTSS or Multics program that used the system
> device drivers ever had a NUL or character timing as part of its
> application-level data stream.


It was messier than that in other environments.  Yes, device drivers,
peripheral processors, or front ends commonly dealt with whether a
particular device needed CR, LF, NL, CRLF, or something else, and
how many NULs had to be sent in order to deal with device limitations
in processing those control codes.  But the more "sophisticated"
controls, such as VT, FF, and so on, also required delays on some
devices.  (I remember one device where VT would cause it to suck
paper back into the printer in order to return to the top of the current
page.)  Sequences for line insert, line delete, and region clears / fills
on some CRTs also required padding delays.  Some got seriously
confused if the padding was omitted.  However, dealing with this
issue was put painfully close to the user application in Unix-land.
Look for "padding" in the documentation for termcap and terminfo
for a glimpse into how convoluted things became.

 ....
> As I said, I wasn't part of the committee that did ASCII.   I do
> know that CR was extensively used, in both our terminal
> environment and in a number of ones involving line printers
> without LF as a way to arrange overstriking (for bold,
> underlining, and composed characters) on line-oriented devices
> that couldn't handle backspacing.   Again, that was mostly in
> the device drivers: an application program would see
>    xxxo<BS>'yyy 
> whether that was transmitted or 
>    xxxoyyy<CR>   ' 
> or, as mentioned earlier, whatever the first-character-of-line
> printer control sequence was that would yield the same result.

In our CDC shop, security was critically dependent on this.
Since the teletypes echoed everything typed locally, there needed
to be a way to prevent even a partially-typed password from
being visible.  This was accomplished by sending a sequence
that was something like:
Password:<cr><lf>[[[[[[[[<cr>]]]]]]]]<cr>########<cr>XXXXXXXX<cr> 

Randy


From worley@shell01.TheWorld.com  Wed Jan 23 19:42:12 2013
Return-Path: <worley@shell01.TheWorld.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2429A21F8517 for <ietf@ietfa.amsl.com>; Wed, 23 Jan 2013 19:42:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.98
X-Spam-Level: 
X-Spam-Status: No, score=-2.98 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, RCVD_IN_SORBS_WEB=0.619]
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 ZCfavJeEcy83 for <ietf@ietfa.amsl.com>; Wed, 23 Jan 2013 19:42:11 -0800 (PST)
Received: from TheWorld.com (pcls4.std.com [192.74.137.144]) by ietfa.amsl.com (Postfix) with ESMTP id 9558821F8506 for <ietf@ietf.org>; Wed, 23 Jan 2013 19:42:11 -0800 (PST)
Received: from shell.TheWorld.com (svani@shell01.theworld.com [192.74.137.71]) by TheWorld.com (8.14.5/8.14.5) with ESMTP id r0O3fPsm006351 for <ietf@ietf.org>; Wed, 23 Jan 2013 22:41:27 -0500
Received: from shell01.TheWorld.com (localhost.theworld.com [127.0.0.1]) by shell.TheWorld.com (8.13.6/8.12.8) with ESMTP id r0O3fOP5341017 for <ietf@ietf.org>; Wed, 23 Jan 2013 22:41:25 -0500 (EST)
Received: (from worley@localhost) by shell01.TheWorld.com (8.13.6/8.13.6/Submit) id r0O3fOui340901; Wed, 23 Jan 2013 22:41:24 -0500 (EST)
Date: Wed, 23 Jan 2013 22:41:24 -0500 (EST)
Message-Id: <201301240341.r0O3fOui340901@shell01.TheWorld.com>
From: worley@ariadne.com (Dale R. Worley)
Sender: worley@ariadne.com (Dale R. Worley)
To: ietf@ietf.org
In-reply-to: <8EFA8168-7F05-4010-975C-CE601361501C@tzi.org> (cabo@tzi.org)
Subject: Re: Vestigial Features (was Re: CRLF (was: Re: A modest proposal))
References: <20130123061554.85592.qmail@joyce.lan> <C3CD7DDBD81323BD17837BCE@JcK-HP8200.jck.com> <8EFA8168-7F05-4010-975C-CE601361501C@tzi.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 24 Jan 2013 03:42:12 -0000

> From: Carsten Bormann <cabo@tzi.org>
> 
> I think in protocol evolution (as well as computer system evolution
> in general) we are missing triggers to get rid of vestigial
> features.

That's quite true.  Let us start by rationalizing the spelling and
punctuation of written English (which is the coding system for *this
entire discussion*).  Once we've cleaned up that idiocy, we can start
in on SIP.

Dale

From presnick@qti.qualcomm.com  Wed Jan 23 19:51:09 2013
Return-Path: <presnick@qti.qualcomm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CD89A21F85B4 for <ietf@ietfa.amsl.com>; Wed, 23 Jan 2013 19:51:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.495
X-Spam-Level: 
X-Spam-Status: No, score=-102.495 tagged_above=-999 required=5 tests=[AWL=0.104, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 hHmPIHiS44E0 for <ietf@ietfa.amsl.com>; Wed, 23 Jan 2013 19:51:04 -0800 (PST)
Received: from sabertooth01.qualcomm.com (sabertooth01.qualcomm.com [65.197.215.72]) by ietfa.amsl.com (Postfix) with ESMTP id 29E1921F8514 for <ietf@ietf.org>; Wed, 23 Jan 2013 19:51:01 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qti.qualcomm.com; i=@qti.qualcomm.com; q=dns/txt; s=qcdkim; t=1358998301; x=1390534301; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=aNDflSgsQXktHbG0SL4Qzj0pz1Ru8sECNb2RwvCwyik=; b=ES5NVi16cSfj2qp4k2RRnbIzW5MtBS6t6kbW0OOKhLPdXEU7h9IcH06i Wfp6g7qKSK61tDMAqmlmn+DXX4oaSCjq2CJTzzPIcGQ5zuZiClQ00MNws iof+S/xM7gRGgjzKdgzjkitIbI4CAYixay0iHHD8GJtoCN+yHxq3x2wa3 k=;
X-IronPort-AV: E=Sophos;i="4.84,525,1355126400"; d="scan'208";a="17780608"
Received: from ironmsg03-l.qualcomm.com ([172.30.48.18]) by sabertooth01.qualcomm.com with ESMTP; 23 Jan 2013 19:31:25 -0800
X-IronPort-AV: E=Sophos;i="4.84,525,1355126400"; d="scan'208";a="408918935"
Received: from nasanexhc04.na.qualcomm.com ([172.30.48.17]) by Ironmsg03-L.qualcomm.com with ESMTP/TLS/RC4-SHA; 23 Jan 2013 19:50:43 -0800
Received: from resnick2.qualcomm.com (172.30.48.1) by qcmail1.qualcomm.com (172.30.48.17) with Microsoft SMTP Server (TLS) id 14.2.318.4; Wed, 23 Jan 2013 19:50:42 -0800
Message-ID: <5100AF90.7060202@qti.qualcomm.com>
Date: Wed, 23 Jan 2013 21:50:40 -0600
From: Pete Resnick <presnick@qti.qualcomm.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.7; en-US; rv:1.9.1.9) Gecko/20100630 Eudora/3.0.4
MIME-Version: 1.0
To: <ietf@ietf.org>
Subject: Re: CRLF
References: <20130123061554.85592.qmail@joyce.lan>	<C3CD7DDBD81323BD17837BCE@JcK-HP8200.jck.com>	<a062408f3cd2610b7f0fc@[10.0.1.3]> <alpine.LRH.2.01.1301231424200.16244@egate.xpasc.com>
In-Reply-To: <alpine.LRH.2.01.1301231424200.16244@egate.xpasc.com>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-Originating-IP: [172.30.48.1]
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 24 Jan 2013 03:51:09 -0000

On 1/23/13 4:45 PM, David Morris wrote:
> VDTs with long lines might have been inspired by line printers or
> just the idea that long lines were better.

Definitely inspired by printers. I remember when we upgraded our ancient 
VT100 terminals (which didn't have wide mode) to VT220 terminals and you 
could display your output spool file (which was 132 column wide) on the 
screen without stupid wrapping and without having to print it out on the 
green and white bar paper. Ah, the things that excited us back then.

> No experience there,
> but I'm pretty certain there were no 132 column punch cards in
> common use which would have influnced comody VDT designers. 80
> and I believe 96 in S/3 days.
>    

Yup, cards were 80 column and printouts were 132. And of course if you 
left your VT220 in 132 column mode while you were writing code and 
accidentally went over the 80 column limit on a line or two, when you 
sent your job off to VM/CMS, you'd get back an error that your job 
failed due to "Card reader jam". Gotta love it.

pr

-- 
Pete Resnick<http://www.qualcomm.com/~presnick/>
Qualcomm Technologies, Inc. - +1 (858)651-4478


From yakov@shaftek.org  Wed Jan 23 20:37:32 2013
Return-Path: <yakov@shaftek.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F1BFE21F8462 for <ietf@ietfa.amsl.com>; Wed, 23 Jan 2013 20:37:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.977
X-Spam-Level: 
X-Spam-Status: No, score=-2.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1]
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 XU9v58CZg5N2 for <ietf@ietfa.amsl.com>; Wed, 23 Jan 2013 20:37:32 -0800 (PST)
Received: from mail-ie0-f171.google.com (mail-ie0-f171.google.com [209.85.223.171]) by ietfa.amsl.com (Postfix) with ESMTP id 095F421F844F for <ietf@ietf.org>; Wed, 23 Jan 2013 20:37:31 -0800 (PST)
Received: by mail-ie0-f171.google.com with SMTP id 9so11125957iec.16 for <ietf@ietf.org>; Wed, 23 Jan 2013 20:37:31 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:mime-version:sender:x-originating-ip:in-reply-to :references:from:date:x-google-sender-auth:message-id:subject:to:cc :content-type:content-transfer-encoding:x-gm-message-state; bh=OQeEFwlqARhiNv+6pb5YZ9/H0xw1HmjsdAM/+GuGmRU=; b=TS6EcsMb+GhMDGdjPe7Y8705IIhOjVvLB/p1HJu0JGxRhr4oIWE/ZPeWkA3Fez2GhQ ztI+C9nFlHoLMGww37PVssCbojq2BPk8r4hP9XYPKIgFT5ODRhitaXWBTSst8zswOo2/ AaI70bSmXLkrSBtP3wSljmPdfLPiwxPinDDBJVDKO2Y/psGlQd7Dhphx2pajnzuUSO0d Q1nCjDgD1RgRD86+8C/TrHwv+MCt3OETf6lptMOD8ru4HG9bIaKk9QJMLPJ1ka7W2c9+ AZymGYkEBgkmOMwqlHPeNobEpEx4wDGYLQjZnbU3eTuoR24ErtFpnNhRywlMVAeooWrN F2YQ==
X-Received: by 10.50.56.232 with SMTP id d8mr353907igq.112.1359002251370; Wed, 23 Jan 2013 20:37:31 -0800 (PST)
MIME-Version: 1.0
Sender: yakov@shaftek.org
Received: by 10.64.136.33 with HTTP; Wed, 23 Jan 2013 20:37:01 -0800 (PST)
X-Originating-IP: [98.140.248.199]
In-Reply-To: <1ah0g8p99e7rljhvndsmqi7qp8ujoj4ije@hive.bjoern.hoehrmann.de>
References: <1ah0g8p99e7rljhvndsmqi7qp8ujoj4ije@hive.bjoern.hoehrmann.de>
From: Yakov Shafranovich <ietf@shaftek.org>
Date: Wed, 23 Jan 2013 23:37:01 -0500
X-Google-Sender-Auth: WWWm9l1dFe3A3OYWlUvPUQiFUnY
Message-ID: <CAPQd5oTW7w7gaNzGc1TP9C_yD2ODEec5RvzHKbt=nK04+PRzvA@mail.gmail.com>
Subject: Re: Comments on draft-shafranovich-mime-sql-03
To: Bjoern Hoehrmann <derhoermi@gmx.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
X-Gm-Message-State: ALoCoQlygZiS2JwihgFk0QSbsNsZulrBqszA9BdEXBo9fy+9zSTEGpVkFlp7hooPuOyZ8F6U6XA9
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 24 Jan 2013 04:37:33 -0000

Thanks for your comments. My understanding is that the SQL standards
as specified by ISO actually allow for variants and multiple vendor
implementations, all of which are not guaranteed to be compatible.
This is why the ISO standard specified conformance standards and
several levels of conformance. Even SQL Lite claims conformance to
SQL-92, albeit partially. I also took a quick look at several other
major DBMS, and they all have some level of conformance to the
standard.

Being that this Internet draft only registers a media type, the
details of what type of implementations there are and their
compatibilities, are best left to ISO. The interoperability
considerations section makes this clear:

      While a single standard exists ([ISO.9075.2011]), vendor
      implementations of the standard vary significantly.  Implementors
      and users should make sure that the exchanged SQL files match to
      the specific database/tool and version that they are using.

This is somewhat similar to HTML, where several specs exists, but
implementations vary greatly. One can argue that years ago
"IE-specific" HTML was not the same as "Netscape-specific" HTML, just
like various SQL dialects.

Regarding the charset issue, you are correct in that when
communicating between SQL clients and SQL servers, the encoding maybe
specified inline via a SQL command, or out of band via driver or
session parameters. HOWEVER, this media type is not intended for that
type of communication, rather it is intended for a more mundane things
like exchanging SQL files via an HTTP connection, or in an email
message. In those cases, I do not see any other way of specifying
encoding.

Going with that approach, it would seem that the draft needs slight
rewording here:

   Optional parameters:

      "charset" - indicates the character set to be used.  When not
      specified, US-ASCII should be assumed.

      Implementators should note that as per section 4.2.4, part 2 of
      [ISO.9075.2011], all SQL implementations are required to support
      US-ASCII, ISO-8859-1, UTF-8, UTF-16 and UTF-32 encodings.  Those
      should be the only valid values for the charset parameter unless
      some other agreement exists between the parties.

      When using [Unicode], the [ISO.9075.2011] standard dictates a
      preference of UTF-8 over UTF-16, and UTF-16 over UTF-32.

I would omit the last two paragraphs since we are not dealing with SQL
implementations directly, and rewrite it as follows:

   Optional parameters:

      "charset" - indicates the character set to be used.  When not
      specified, US-ASCII should be assumed.

The reason why I specify US-ASCII as the default, is because the ABNF
grammar of the SQL specification includes 88 characters that are part
of the ASCII. It seems that is the default encoding for SQL in absence
of any other information.

Yakov

On Wed, Jan 23, 2013 at 3:49 PM, Bjoern Hoehrmann <derhoermi@gmx.net> wrote=
:
> Hi,
>
>   Regarding <http://tools.ietf.org/html/draft-shafranovich-mime-sql-03>,
> I think the document should be more clear that there are many variants
> of the SQL format and the media type is intended as "umbrella type" for
> them all, for instance, the Abstract should refer to, say, "variants of
> the Structured Query Language" and not "the Structured Query Language".
> The "Published specification" field in the registration template should
> also note that there exist individual specifications for individual de-
> rived formats (like "SQL As Understood By SQLite").
>
> The proposed type has an optional 'charset' parameter. As I understand
> it, SQL formats typically indicate character encoding, if at all, in
> proprietary ways inline in SQL resources, or entirely out of band, and
> for exchange, everybody seems to be settling on UTF-* encodings, so the
> parameter is unlikely to serve a useful purpose, but does create some
> problems, like how implementations should handle HTTP responses where
> the HTTP header says `Content-Type: application/sql;charset=3Diso-8859-1`
> while UTF-8 is specified inline. I think the type would do better with-
> out this parameter.
>
> Whether it is kept or not, the media type registration should not de-
> fine a default. If the character encoding is not explicitly specified,
> then it is unknown, and it should be up to individual applications and
> their conventions for their SQL variants how to handle that case.
>
> regards,
> --
> Bj=F6rn H=F6hrmann =B7 mailto:bjoern@hoehrmann.de =B7 http://bjoern.hoehr=
mann.de
> Am Badedeich 7 =B7 Telefon: +49(0)160/4415681 =B7 http://www.bjoernsworld=
.de
> 25899 Dageb=FCll =B7 PGP Pub. KeyID: 0xA4357E78 =B7 http://www.websitedev=
.de/

From yakov@shaftek.org  Wed Jan 23 20:58:01 2013
Return-Path: <yakov@shaftek.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B536721F8858 for <ietf@ietfa.amsl.com>; Wed, 23 Jan 2013 20:58:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.977
X-Spam-Level: 
X-Spam-Status: No, score=-2.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1]
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 dnQco9QutRJN for <ietf@ietfa.amsl.com>; Wed, 23 Jan 2013 20:58:01 -0800 (PST)
Received: from mail-ie0-f169.google.com (mail-ie0-f169.google.com [209.85.223.169]) by ietfa.amsl.com (Postfix) with ESMTP id 3FF7F21F8856 for <ietf@ietf.org>; Wed, 23 Jan 2013 20:58:01 -0800 (PST)
Received: by mail-ie0-f169.google.com with SMTP id c14so15202030ieb.28 for <ietf@ietf.org>; Wed, 23 Jan 2013 20:58:01 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:mime-version:sender:x-originating-ip:in-reply-to :references:from:date:x-google-sender-auth:message-id:subject:to:cc :content-type:x-gm-message-state; bh=VnM1YlEdroz1hUNpzH8HcTBFs4Z+2MVZ1IXpHBgmfWQ=; b=IJ4zm5RlxQYXtPpg3Kkd9g1w1/E+YdohWk5p5bjgfuvsjSbtPLBRJ0xrxgZWIGCXUH 3S3zlIAL91Wd2dHxheViQstp99sw4CmU3nP/RADFkWuSvFfRAzpitzRTjcwgzLNMHVBM 7qImGbg0EgOkS1EQSs9UB3yTP596KHk0tIMl5phmjHU4E5H7EQu9cF2iCk97Ox4qCZi5 iN2z8snUL3bD7yfbymlVIxW2vmCCglBTCLUO7TnEA9ZYssQ3tvU6EmsvwGjBrMjljk/C +R9QbFYq1odh3zsSFuAphPNQUvSRkObCTYFS513FKqaNQUCyMT/iVV4H5UbWSosfu6Uq I9Hg==
X-Received: by 10.50.56.232 with SMTP id d8mr381467igq.112.1359003480448; Wed, 23 Jan 2013 20:58:00 -0800 (PST)
MIME-Version: 1.0
Sender: yakov@shaftek.org
Received: by 10.64.136.33 with HTTP; Wed, 23 Jan 2013 20:57:30 -0800 (PST)
X-Originating-IP: [98.140.248.199]
In-Reply-To: <CAPQd5oTW7w7gaNzGc1TP9C_yD2ODEec5RvzHKbt=nK04+PRzvA@mail.gmail.com>
References: <1ah0g8p99e7rljhvndsmqi7qp8ujoj4ije@hive.bjoern.hoehrmann.de> <CAPQd5oTW7w7gaNzGc1TP9C_yD2ODEec5RvzHKbt=nK04+PRzvA@mail.gmail.com>
From: Yakov Shafranovich <ietf@shaftek.org>
Date: Wed, 23 Jan 2013 23:57:30 -0500
X-Google-Sender-Auth: QJehhup4gemkfkysENWiKbA6O1Y
Message-ID: <CAPQd5oS7TEytpSe5Rq-XTdSdSD4EhHxvsxfaOGLfn5faatSEfw@mail.gmail.com>
Subject: Re: Comments on draft-shafranovich-mime-sql-03
To: Bjoern Hoehrmann <derhoermi@gmx.net>
Content-Type: text/plain; charset=ISO-8859-1
X-Gm-Message-State: ALoCoQnWMWj93Fh1rmjHhKeJ/kMH4YaSUgtbRDphHrSR9j1f0rj4wuFlk0OcRpwGAON3aSVKoNAo
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 24 Jan 2013 04:58:01 -0000

Regarding this issue in particular, the reason why I am saying that
SQL client/server communication is out of scope for this, is because
the ISO specification addresses how that is done in several different
scenarios, including embedded and direct methods. Hypothetically, if
such communication were to use HTTP with this media type, then the
charset parameter would be used instead.

Yakov

On Wed, Jan 23, 2013 at 11:37 PM, Yakov Shafranovich <ietf@shaftek.org> wrote:
>>
> Regarding the charset issue, you are correct in that when
> communicating between SQL clients and SQL servers, the encoding maybe
> specified inline via a SQL command, or out of band via driver or
> session parameters. HOWEVER, this media type is not intended for that
> type of communication, rather it is intended for a more mundane things
> like exchanging SQL files via an HTTP connection, or in an email
> message. In those cases, I do not see any other way of specifying
> encoding.
>>

From fgont@si6networks.com  Wed Jan 23 22:58:46 2013
Return-Path: <fgont@si6networks.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ABCF721F8834; Wed, 23 Jan 2013 22:58:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.051
X-Spam-Level: 
X-Spam-Status: No, score=-2.051 tagged_above=-999 required=5 tests=[AWL=-0.052, BAYES_00=-2.599, J_CHICKENPOX_21=0.6]
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 7LzeFZnAJJRJ; Wed, 23 Jan 2013 22:58:46 -0800 (PST)
Received: from web01.jbserver.net (web01.jbserver.net [93.186.182.34]) by ietfa.amsl.com (Postfix) with ESMTP id 654C521F8843; Wed, 23 Jan 2013 22:58:28 -0800 (PST)
Received: from 95-132-17-190.fibertel.com.ar ([190.17.132.95] helo=[192.168.1.113]) by web01.jbserver.net with esmtpsa (TLSv1:DHE-RSA-CAMELLIA256-SHA:256) (Exim 4.80.1) (envelope-from <fgont@si6networks.com>) id 1TyGlQ-00046C-D8; Thu, 24 Jan 2013 07:58:22 +0100
Message-ID: <5100DB84.6060000@si6networks.com>
Date: Thu, 24 Jan 2013 03:58:12 -0300
From: Fernando Gont <fgont@si6networks.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130106 Thunderbird/17.0.2
MIME-Version: 1.0
To: Allison Mankin <allison.mankin@gmail.com>
Subject: Re: TSV-DIR review of draft-ietf-6man-ipv6-atomic-fragments-03
References: <CAP8yD=tF4_2RpNZNAHRR65HTZGwSPE+Pjx8-a8H_vQHNjqfEoA@mail.gmail.com>
In-Reply-To: <CAP8yD=tF4_2RpNZNAHRR65HTZGwSPE+Pjx8-a8H_vQHNjqfEoA@mail.gmail.com>
X-Enigmail-Version: 1.4.6
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: 6man@ietf.org, Transport Area <tsv-area@ietf.org>, IETF Discuss <ietf@ietf.org>, Transport Directorate <tsv-dir@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 24 Jan 2013 06:58:46 -0000

Hi, Allison,

Thanks so much for your feedback! -- Please find my comments in-line....

On 01/23/2013 09:33 PM, Allison Mankin wrote:
> It is clearly valuable to call the community's attention to the "atomic
> fragment" in IPv6.  This is an IPv6 datagram that is not actually
> fragmented, but has a Fragmentation Header (with an offset of 0 and the
> M bit set to 0).  It seems the atomic fragment in IPv6 arose to
> accommodate translation gateways with MTUs of less than 1280 (the IPv6
> minimum) on the IPv4 side [1].  The problem is that you can force a
> sender to generate atomic fragments instead of normal packets from an
> off-path node, if the sender doesn't filter ICMPv6 much. 

Note:

1) It's not a problem at all if you process atomic fragments as indicated.

2) You cannot filter ICMPv6 as appropriate: The ICMPv6 payload can
always contain less information than needed to validate the ICMP error
messages.



> A is the IPv6 sender that either does not or cannot filter incoming
> ICMPv6 very well and that chooses Fragmentation IDs in a predictable way
> when it must fragment.
> 
> E is a blind attacker (or collaborating blind attackers), not on path/in
> the middle for A.
> 
> B is the destination for A's traffic.  B initially doesn't distinguish
> between atomic fragments and normal fragments.  However, B has
> implemented another solution [2], RFC 5722, which requires that IPv6
> fragments be dropped silently if they overlap (have the same IDs and
> carry material from the same offset+fragment length).

FWIW, RFC5722 is a solution to the "firewall evasion by overlapping
fragments", but in this case can be of help for DoS purposes.


> 
> ORIGINAL ATTACK
> ---------------------------
[....]

FWIW, the scenario you sketched is 100% correct.



> RESIDUAL RISK?
> -------------------------
[....]
> So now a receiver is forced to process an atomic datagram even if there
> are overlapping fragments already there on the fragmentation queue. 
> 
> NEW ATTACK VECTOR
> ---------------------------------
> T"0   A to B:    v6-dgram --->
> 
> T"1  E to A:    ICMPv6 Too Big (MTU<1280)
> 
> T"2  A to B:     switch to v6-atomic-fragment, ID=X, Offset=0
> T"2a B:           deliver A's datagram to ULP
> 
> T"3  E to B:     blind-inserted overlapping v6-atomic-fragment, ID=X,
> Offset=0
> T"3a B:           deliver E's overlapping datagram to ULP
> 
> T"4:  B:           TCP attack mitigated by RFC 5722 looks possible again
> [see Note 3]. 

I fail to see why this scenario could be seen as an example of an attack
RFC 5722 avoids.

Simply put, what draft-ietf-6man-ipv6-atomic-fragments-03 says is: "an
atomic fragment is not really a fragment, but rather a complete packet
that just happens to have a Frag Header -- hence, process it as such".

RFC 5722 is meant to prevent attacks in which you can fool a firewall by
sending overlapping fragments: the fragment allows the first fragment,
but then a second fragment (which looks harmless) overwrites the initial
fragment such that the reassembled packet becomes an "attack packet".

Atomic fragments do not fall in that category: A firewall has all the
knowledge it needs to decide whether to filter (or not) what's in the
atomic fragment. And if the firewall allowed the atomic fragment, that's
exactly how the fragment is going t be delivered to the ULP.



> Conclusion
> ---------------
> There's an interesting table in the draft showing which sending stacks
> can be tricked into switching to v6-atomic-fragments and which receiving
> ones can be tricked into dropping them due to fragment overlap.  Another
> way of looking at this table is that a lot of stacks need to be less
> predictable and more suspicious of spoofing traffic.  The present draft
> is pragmatic/empirical and is interested in fixing a problem that exists
> (it can be brought on).  But I wonder if it would be better to embed the
> discussion of atomic fragments and fragment overlap in a larger picture,
> a collected set of best practices against spoofers (of ICMPv6, of IPv6
> fragments or otherwise).

In this particular case, there's a specific standard that needs to be
updated, and existing software relying on the feature (atomic fragments)
that we're improving.

I'm not sure what kind of document you have in mind... but my personal
experience says that being able to tackle isolated problems separately
(rather than work on a large document that tries to address a plethora
of issues) is (by far) more doable.

Thanks!

Best regards,
-- 
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492





From dave@cridland.net  Thu Jan 24 00:15:27 2013
Return-Path: <dave@cridland.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 008D221F8468 for <ietf@ietfa.amsl.com>; Thu, 24 Jan 2013 00:15:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.976
X-Spam-Level: 
X-Spam-Status: No, score=-2.976 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
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 3qZmTYCI3nOa for <ietf@ietfa.amsl.com>; Thu, 24 Jan 2013 00:15:26 -0800 (PST)
Received: from mail-oa0-f44.google.com (mail-oa0-f44.google.com [209.85.219.44]) by ietfa.amsl.com (Postfix) with ESMTP id 6A42C21F843C for <ietf@ietf.org>; Thu, 24 Jan 2013 00:15:26 -0800 (PST)
Received: by mail-oa0-f44.google.com with SMTP id n5so9546161oag.31 for <ietf@ietf.org>; Thu, 24 Jan 2013 00:15:25 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cridland.net; s=google; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=ClkQfaK+rqOY0CoTNylZAY5onUBYWMSedeB2QfnIqxQ=; b=P2uMXH9/fC+XYV4t28EdL+hsGdLP+1PQlatIgp7qsaIDGgO76AVUQ5ODmMmUNs2YOB O0Ejvk/Y+tn50OvJxlEJX2yvW4cqu41qVFpH3a7oF6IsSoPpXNiLMEOg6Uju1xHBW0Mn APTAyja9Slo9g98KjkRfxWMISlt6kwW9Zlyu8=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type:x-gm-message-state; bh=ClkQfaK+rqOY0CoTNylZAY5onUBYWMSedeB2QfnIqxQ=; b=jCEU2rgnTp8oiAUq/EKMp1Vj6d3pcP4ODYJBIZLYBr5G+sZAFRzp1l+/katj6fHhFY pDeqLePpsMhFBi1wkFTB8yrjBb3HlogRVOqJ823ratM8rOMM93i75kMG5ou+pia52O0M udodc/0ruwDPYQ9RQDUtP0fEACeL6JidDhQ8Vy0AG4BjVWc8WEMttTsQ6cBJRtJqCc5n 0aNjhYZhRS2j9ddKh/23bWd7lY4PbM7WmGesaeZp4vB0iQ4vHXOl6X3f/UQq4ZitF7OZ r2JZHMchtZ6Q0BFdBuihH6gu6yvbvImRy+ucCRm2bOijwhcYMZkPLb409sqxmXOr/8eM GV9w==
MIME-Version: 1.0
X-Received: by 10.182.161.39 with SMTP id xp7mr793424obb.71.1359015325761; Thu, 24 Jan 2013 00:15:25 -0800 (PST)
Received: by 10.60.79.2 with HTTP; Thu, 24 Jan 2013 00:15:25 -0800 (PST)
Received: by 10.60.79.2 with HTTP; Thu, 24 Jan 2013 00:15:25 -0800 (PST)
In-Reply-To: <201301240341.r0O3fOui340901@shell01.TheWorld.com>
References: <20130123061554.85592.qmail@joyce.lan> <C3CD7DDBD81323BD17837BCE@JcK-HP8200.jck.com> <8EFA8168-7F05-4010-975C-CE601361501C@tzi.org> <201301240341.r0O3fOui340901@shell01.TheWorld.com>
Date: Thu, 24 Jan 2013 08:15:25 +0000
Message-ID: <CAKHUCzwmJEepEG9bOB41RgZzGTdLuYd1XArg5Eq-GUMspbqu6A@mail.gmail.com>
Subject: Re: Vestigial Features (was Re: CRLF (was: Re: A modest proposal))
From: Dave Cridland <dave@cridland.net>
To: "Dale R. Worley" <worley@ariadne.com>
Content-Type: multipart/alternative; boundary=f46d04428768bc80cb04d4046992
X-Gm-Message-State: ALoCoQnCTMHW1aUzOh4gQ3NRpBTA0whi8bPNuFDl942+lEdUV0PZhIQ5U8ju9NLpmgz16I4hSnVZ
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 24 Jan 2013 08:15:27 -0000

--f46d04428768bc80cb04d4046992
Content-Type: text/plain; charset=ISO-8859-1

On Jan 24, 2013 3:42 AM, "Dale R. Worley" <worley@ariadne.com> wrote:
>
> > From: Carsten Bormann <cabo@tzi.org>
> >
> > I think in protocol evolution (as well as computer system evolution
> > in general) we are missing triggers to get rid of vestigial
> > features.
>
> That's quite true.  Let us start by rationalizing the spelling and
> punctuation of written English (which is the coding system for *this
> entire discussion*).  Once we've cleaned up that idiocy, we can start
> in on SIP.
>

Noah Webster tried that once, it turns out to lead to serious interop
problems with transatlantic communications.

--f46d04428768bc80cb04d4046992
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<p><br>
On Jan 24, 2013 3:42 AM, &quot;Dale R. Worley&quot; &lt;<a href=3D"mailto:w=
orley@ariadne.com">worley@ariadne.com</a>&gt; wrote:<br>
&gt;<br>
&gt; &gt; From: Carsten Bormann &lt;<a href=3D"mailto:cabo@tzi.org">cabo@tz=
i.org</a>&gt;<br>
&gt; &gt;<br>
&gt; &gt; I think in protocol evolution (as well as computer system evoluti=
on<br>
&gt; &gt; in general) we are missing triggers to get rid of vestigial<br>
&gt; &gt; features.<br>
&gt;<br>
&gt; That&#39;s quite true. =A0Let us start by rationalizing the spelling a=
nd<br>
&gt; punctuation of written English (which is the coding system for *this<b=
r>
&gt; entire discussion*). =A0Once we&#39;ve cleaned up that idiocy, we can =
start<br>
&gt; in on SIP.<br>
&gt;</p>
<p>Noah Webster tried that once, it turns out to lead to serious interop pr=
oblems with transatlantic communications.</p>

--f46d04428768bc80cb04d4046992--

From cabo@tzi.org  Thu Jan 24 01:22:45 2013
Return-Path: <cabo@tzi.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 03D1821F843F for <ietf@ietfa.amsl.com>; Thu, 24 Jan 2013 01:22:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.249
X-Spam-Level: 
X-Spam-Status: No, score=-106.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 xE5htYSWvFJ3 for <ietf@ietfa.amsl.com>; Thu, 24 Jan 2013 01:22:44 -0800 (PST)
Received: from informatik.uni-bremen.de (mailhost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::12]) by ietfa.amsl.com (Postfix) with ESMTP id 9B37421F8481 for <ietf@ietf.org>; Thu, 24 Jan 2013 01:22:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from smtp-fb3.informatik.uni-bremen.de (smtp-fb3.informatik.uni-bremen.de [134.102.224.120]) by informatik.uni-bremen.de (8.14.3/8.14.3) with ESMTP id r0O9MHAR029111; Thu, 24 Jan 2013 10:22:17 +0100 (CET)
Received: from [10.0.1.4] (reingewinn.informatik.uni-bremen.de [134.102.218.123]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp-fb3.informatik.uni-bremen.de (Postfix) with ESMTPSA id 4894C2CD; Thu, 24 Jan 2013 10:22:17 +0100 (CET)
Subject: Re: Vestigial Features (was Re: CRLF (was: Re: A modest proposal))
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Content-Type: text/plain; charset=iso-8859-1
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <201301240341.r0O3fOui340901@shell01.TheWorld.com>
Date: Thu, 24 Jan 2013 10:22:16 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <6372D85B-041B-4FBF-B41E-7505C4B56E58@tzi.org>
References: <20130123061554.85592.qmail@joyce.lan> <C3CD7DDBD81323BD17837BCE@JcK-HP8200.jck.com> <8EFA8168-7F05-4010-975C-CE601361501C@tzi.org> <201301240341.r0O3fOui340901@shell01.TheWorld.com>
To: worley@ariadne.com (Dale R. Worley)
X-Mailer: Apple Mail (2.1499)
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 24 Jan 2013 09:22:45 -0000

On Jan 24, 2013, at 04:41, worley@ariadne.com (Dale R. Worley) wrote:

>> From: Carsten Bormann <cabo@tzi.org>
>>=20
>> I think in protocol evolution (as well as computer system evolution
>> in general) we are missing triggers to get rid of vestigial
>> features.
>=20
> That's quite true.  Let us start by rationalizing the spelling and
> punctuation of written English (which is the coding system for *this
> entire discussion*).  Once we've cleaned up that idiocy, we can start
> in on SIP.

I see I didn't make myself clear. =20
I'm not suggesting we clean up vestigials in existing spec[ie]s, such as =
HTTP or SIP.
(We might even do that, see HTTPbis, but only very carefully.)

My point was about the case when we clone new stuff off existing =
protocols.
(SIP was cloned off HTTP which was cloned off SMTP which was cloned off =
FTP which at least has had strong kinship with Telnet, hence all these =
use NVT.)

Staying in your analogy: when you design a new language based on =
English, please do fix some of this stuff.
(Maybe the analogy isn't that useful after all.)

Actually, we haven't been that bad about this.
E.g., we have been pretty good about getting rid of the madness of =
historic character coding by focusing on UTF-8 for new designs.
What I'm asking for: Apart from these big reformation projects, we also =
should occasionally fix little things.
When "inventing" new stuff by drawing analogies off of old specs.

Gr=FC=DFe, Carsten


From cabo@tzi.org  Thu Jan 24 01:37:39 2013
Return-Path: <cabo@tzi.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F308B21F8443 for <ietf@ietfa.amsl.com>; Thu, 24 Jan 2013 01:37:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.249
X-Spam-Level: 
X-Spam-Status: No, score=-106.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 MfsTXAJUwX10 for <ietf@ietfa.amsl.com>; Thu, 24 Jan 2013 01:37:38 -0800 (PST)
Received: from informatik.uni-bremen.de (mailhost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::12]) by ietfa.amsl.com (Postfix) with ESMTP id 41D6921F8442 for <ietf@ietf.org>; Thu, 24 Jan 2013 01:37:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from smtp-fb3.informatik.uni-bremen.de (smtp-fb3.informatik.uni-bremen.de [134.102.224.120]) by informatik.uni-bremen.de (8.14.3/8.14.3) with ESMTP id r0O9bU3R007217; Thu, 24 Jan 2013 10:37:30 +0100 (CET)
Received: from [10.0.1.4] (reingewinn.informatik.uni-bremen.de [134.102.218.123]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp-fb3.informatik.uni-bremen.de (Postfix) with ESMTPSA id C666B2F8; Thu, 24 Jan 2013 10:37:29 +0100 (CET)
Subject: Re: Vestigial Features (was Re: CRLF (was: Re: A modest proposal))
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Content-Type: text/plain; charset=iso-8859-1
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <B2984BB2A992EA17292A79F1@JcK-HP8200.jck.com>
Date: Thu, 24 Jan 2013 10:37:29 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <0084E7E9-405F-4DD6-8FFE-822FE6831F5E@tzi.org>
References: <20130123061554.85592.qmail@joyce.lan> <C3CD7DDBD81323BD17837BCE@JcK-HP8200.jck.com> <8EFA8168-7F05-4010-975C-CE601361501C@tzi.org> <B2984BB2A992EA17292A79F1@JcK-HP8200.jck.com>
To: John C Klensin <john-ietf@jck.com>
X-Mailer: Apple Mail (2.1499)
Cc: John Levine <johnl@taugh.com>, ietf@ietf.org, dean.willis@softarmor.com
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 24 Jan 2013 09:37:39 -0000

This is my last comment on the CRLF issue, which I just used as the
(for me) obvious example for what I was trying to say.

On Jan 24, 2013, at 02:20, John C Klensin <john-ietf@jck.com> wrote:

> Oh, my.  This is getting to be interesting.  I had no direct
> interaction with or insight into the ASA (later ANSI) committee
> that did ASCII=20

You are off by about six decades.

CR and LF were invented around 1901 by Donald Murray and became part
of "International Telegraph Alphabet No. 2" (ITA2, now CCITT S.1),
which was originally standardized in 1932.  (That is the 5-bit code
usually (incorrectly) called "Baudot code".)  This was, of course, the
state of the art from which the standardization of ASCII started six
decades later.

I think any further discussion of these details would be off-topic,
but it does amuse me that the vestigial we are talking about is about
111 years old.

Gr=FC=DFe, Carsten


From rjsparks@nostrum.com  Thu Jan 24 08:05:14 2013
Return-Path: <rjsparks@nostrum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0290121F8984; Thu, 24 Jan 2013 08:05:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.669
X-Spam-Level: 
X-Spam-Status: No, score=-101.669 tagged_above=-999 required=5 tests=[AWL=-0.931, BAYES_20=-0.74, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100]
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 i+gcOvrlx7o7; Thu, 24 Jan 2013 08:05:10 -0800 (PST)
Received: from shaman.nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id DB84221F8988; Thu, 24 Jan 2013 08:05:09 -0800 (PST)
Received: from unnumerable.local (pool-173-57-99-236.dllstx.fios.verizon.net [173.57.99.236]) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id r0OG59NA096817 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Thu, 24 Jan 2013 10:05:09 -0600 (CST) (envelope-from rjsparks@nostrum.com)
Message-ID: <51015BB3.7030406@nostrum.com>
Date: Thu, 24 Jan 2013 10:05:07 -0600
From: Robert Sparks <rjsparks@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130107 Thunderbird/17.0.2
MIME-Version: 1.0
To: ietf@ietf.org, draft-ietf-bmwg-sip-bench-term@tools.ietf.org, draft-ietf-bmwg-sip-bench-meth@tools.ietf.org, bmwg@ietf.org
Subject: Re: Last Call: <draft-ietf-bmwg-sip-bench-term-08.txt> (Terminology for Benchmarking Session Initiation Protocol (SIP) Networking Devices) to Informational RFC
References: <20130116214838.3092.88369.idtracker@ietfa.amsl.com>
In-Reply-To: <20130116214838.3092.88369.idtracker@ietfa.amsl.com>
Content-Type: multipart/alternative; boundary="------------060406070505080309030205"
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 24 Jan 2013 16:05:14 -0000

This is a multi-part message in MIME format.
--------------060406070505080309030205
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Reviews of draft-ietf-bmwg-sip-bench-term-08 and 
draft-ietf-bmwg-sip-bench-meth-08

Summary: These drafts are not ready for publication as RFCs.

First, some of the text in these documents shows signs of being old, and the
working group may have been staring at them so long that they've become 
hard to
see.  The terminology document says "The issue of overload in SIP 
networks is
currently a topic of discussion in the SIPPING WG." (SIPPING was closed in
2009). The methodology document suggests a "flooding" rate that is orders of
magnitude below what simple devices achieve at the moment. That these 
survived
working group last call indicates a different type of WG review may be 
needed
to groom other bugs out of the documents.

Who is asking for these benchmarks, and are they (still) participating 
in the
group?  The measurements defined here are very simplistic and will provide
limited insight into the relative performance of two elements in a real
deployment. The documents should be clear about their limitations, and 
it would
be good to know that the community asking for these benchmarks is 
getting tools
that will actually be useful to them. The crux of these two documents is 
in the
last paragraph of the introduction to the methodology doc: "Finally, the
overall value of these tests is to serve as a comparison function between
multiple SIP implementations".  The documents punt on providing any 
comparison
guidance, but even if we assume someone can figure that out, do these
benchmarks provide something actually useful for inputs?

It would be good to explain how these documents relate to RFC6076.

The terminology tries to refine the definition of session, but the 
definition
provided, "The combination of signaling and media messages and processes 
that
support a SIP-based service" doesn't answer what's in one session vs 
another.
Trying to generically define session has been hard and several working 
groups
have struggled with it (see INSIPID for a current version of that
conversation). This document doesn't _need_ a generic definition of 
session -
it only needs to define the set of messages that it is measuring. It 
would be
much clearer to say "for the purposes of this document, as session is 
the set
of SIP messages associated with an INVITE initiated dialog and any 
Associated
Media, or a series of related SIP MESSAGE requests". (And looking at the
benchmarks, you aren't leveraging related MESSAGE requests - they all 
appear to
be completely independent). Introducing the concepts of Invite-initiated
sessions and non-invite-initiated sessions doesn't actually help define the
metrics. When you get to the metrics, you can speak concretely in terms of a
series of INVITEs, REGISTERs, and MESSAGEs. Doing that, and providing a 
short
introduction pointing folks with PSTN backgrounds relating these to "Session
Attempts" will be clearer.

To be clear, I strongly suggest a fundamental restructuring of the 
document to
describe the benchmarks in terms of dialogs and transactions, and remove 
the IS
and NS concepts completely.

The INVITE related tests assume no provisional responses, leaving out the
effect on a device's memory when the state machines it is maintaining 
transition
to the proceeding state. Further, by not including provisionals, and 
building
the tests to search for Timer B firing, the tests insure there will be 
multiple
retransmissions of the INVITE (when using UDP) that the device being 
tested has
to handle. The traffic an element has to handle and likely the memory it 
will
consume will be very different with even a single 100 trying, which is 
the more
usual case in deployed networks. The document should be clear _why_ it chose
the test model it did and left out metrics that took having a provisional
response into account. Similarly, you are leaving out the delayed-offer 
INVITE
transactions used by 3pcc and it should be more obvious that you are 
doing so.

Likewise, the media oriented tests take a very basic approach to simulating
media. It should be explicitly stated that you are simulating the 
effects of a
codec like G.711 and that you are assuming an element would only be 
forwarding
packets and has to do no transcoding work. It's not clear from the documents
whether the EA is generating actual media or dummy packets. If it's actual
media, the test parameters that assume constant sized packets at a constant
rate will not work well for video (and I suspect endpoints, like B2BUAs, 
will
terminate your call early if you send them garbage).

The sections on a series of INVITEs is fairly clear that you mean each 
of them
to have different dialog identifiers.  I don't see any discussion of varying
the To: URI. If you don't, what's going to keep a gateway or B2BUA from
rejecting all but the first with something like Busy? Similarly, I'm not
finding where you talk about how many AoRs you are registering against 
in the
registration tests. I think, as written, someone could write this where 
all the
registers affected only one AoR.

The methodology document calls Stress Testing out of scope, but the very 
nature
of the Benchmarking algorithm is a stress test. You are iteratively 
pushing to
see at what point something fails, _exactly_ by finding the rate of 
attempted
sessions per second that the thing under test would consider too high.

Now to specific issues in document order, starting with the terminology
document (nits are separate and at the end):

* T (for Terminology document): The title and abstract are misleading - 
this is
not general benchmarking for SIP performance. You have a narrow set of
tests, gathering metrics on a small subset of the protocol machinery.
Please (as RFC 6076 did) look for a title that matches the scope of the
document. For instance, someone testing a SIP Events server would be 
ill-served
with the benchmarks defined here.

* T, section 1: RFC5393 should be a normative reference. You probably 
also need
to pull in RFCs 4320 and 6026 in general - they affect the state 
machines you
are measuring.

* T, 3.1.1: As noted above, this definition of session is not useful. It
doesn't provide any distinction between two different sessions. I strongly
disagree that SIP reserves "session" to describe services analogous to
telephone calls on a switched network - please provide a reference. SIP 
INVITE
transactions can pend forever - it is only the limited subset of the use of
the transactions (where you don't use a provisional response) that keeps 
this
communication "brief". In the normal case, an INVITE an its final 
response can
be separated by an arbitrary amount of time. Instead of trying to tweak this
text, I suggest replacing all of it with simpler, more direct 
descriptions of
the sequence of messages you are using for the benchmarks you are defining
here.

*T, 3.1.1: How is this vector notion (and graph) useful for this document? I
don't see that it's actually used anywhere in the documents. Similarly, the
arrays don't appear to be actually used (though you reference them from some
definitions) - What would be lost from the document if you simply 
removed all
this text?

*T, 3.1.5, Discussion, last sentence: Why is it important to say "For 
UA-type
of network devices such as gateways, it is expected that the UA will be 
driven
into overload based on the volume of media streams it is processing." 
It's not
clear that's true for all such devices. How is saying anything here useful?

*T, 3.1.6: This definition says an outstanding BYE or CANCEL is a Session
Attempt. Why not just say INVITE? You aren't actually measuring "session
attempts" for INVITEs or REGISTERs - you have separate benchmarks for them.

*T, 3.1.7: It needs to be explicit that these benchmarks are not accounting
for/allowing early dialogs.

*T, 3.1.8: The words "early media" appear here for the first time. Given the
way the benchmarks are defined, does it make sense to discuss early media in
these documents at all (beyond noting you do not account for it)? If so,
there needs to be much more clarity. (By the way, this Discussion will be
much easier to write in terms of dialogs).

*T, 3.1.9, Discussion point 2: What does "the media session is established"
mean? If you leave this written as a generic definition, then is this 
when an
MSRP connection has been made? If you simplify it to the simple media model
currently in the document, does it mean an RTP packet has been sent? Or 
does it
have to be received?. For the purposes of the benchmarks defined here, it
doesn't seem to matter, so why have this as part of the discussion anyway?

*T, 3.1.9, Definition: A series of CANCELs meets this definition.

*T, 3.1.10 Discussion: This doesn't talk about 3xx responses, and they 
aren't
covered elsewhere in the document.

*T, 3.1.11 Discussion: Isn't the MUST in this section methodology? Why 
is it in
this document and not -meth-?

*T, 3.1.11 Discussion, next to last sentence: "measured by the number of
distinct Call-IDs" means you are not supporting forking, or you would 
not count
answers from more than on leg of the fork as different sessions, like you
should. Or are you intending that there would never be an answer from 
more than
one leg of a fork? If so, the documents need to be clearer about the
methodology and what's actually being measured.

*T, 3.2.2 Definition: There's something wrong with this definition. For
example, proxies do not create sessions (or dialogs). Did you mean "forwards
messages between"?

*T, 3.2.2 Discussion: This is definition by enumeration since it uses a 
MUST,
and is exclusive of any future things that might sit in the middle. If 
that's
what you want, make this the definition. The MAY seems contradictory 
unless you
are saying a B2BUA or SBC is just a specialized User Agent Server. If so,
please say it that way.

*T, 3.2.3: This seems out of place or under-explored.  You don't appear to
actually _use_ this definition in the documents.You declare these things in
scope, but the only consequence is the line in this section about the not
lowering performance benchmarks when present. Consider making that part 
of the
methodology of a benchmark and removing this section. If you think it's
essential, please revisit the definition - you may want to generalize it 
into
_anything_ that sits on the path and may affect SIP processing times
(otherwise, what's special about this either being SIP Aware, or being a
Firewall)?

*T, 3.2.5 Definition: This definition just obfuscates things. Point to 
3261's
definition instead. How is TCP a measurement unit? Does the general 
terminology
template include "enumeration" as a type? Do you really want to limit this
enumeration to the set of currently defined transports? Will you never run
these benchmarks for SIP over websockets?

*T, 3.3.2 Discussion: Again, there needs to be clarity about what it 
means to
"create" a media session. This description differentiates attempt vs 
success,
so what is it exactly that makes a media session attempt successful? 
When you
say number of media sessions, do you mean number of M lines or total 
number of
INVITEs that have SDP with m lines?

*T, 3.3.3: This would much clearer written in terms of transactions and 
dialogs
(you are already diving into transaction state machine details). This is a
place where the document needs to point out that it is not providing 
benchmarks
relevant to environments where provisionals are allowed to happen and INVITE
transactions are allowed to pend.

*T, 3.3.4: How does this model (A single session duration separate from the
media session hold time) produce useful benchmarks? Are you using it to 
allow
media to go beyond the termination of a call? If not, then you have 
media only
for the first part of a call? What real world thing does this reflect?
Alternatively, what part of the device or system being benchmarked does this
provide insight to?

*T, 3.3.5: The document needs to be honest about the limits of this simple
model of media. It doesn't account for codecs that do not have constant 
packet
sizes. The benchmarks that use the model don't capture the differences 
based on
content of the media being sent - a B2BUA or gateway, may will behave
differently if it is transcoding or doing content processing (such as DTMF
detection) than it will if it is just shoveling packets without looking at
them.

*T, 3.3.6: Again, the model here is that any two media packets present 
the same
load to the thing under test. That's not true for transcoding, mixing, or
analysis (such as for dtmf detection). It's not clear that if you have two
streams, each stream has its own "constant rate". You call out having 
one audio
and one video stream - how do you configure different rates for them?

*T, 3.3.7: This document points to the methodology document for indicating
whether streams are bi-directional or uni-directional. I cant find where the
methodology document talks about this (the string 'direction' does not
occur in that document).

*T, 3.3.8: This text is old - it was probably written pre-RFC5056. If 
you fork,
loop detection is not optional. This, and the methodology document should be
updated to take that into account.

*T, 3.3.9: Clarify if more than one leg of a fork can be answered 
successfully
and update 3.1.11 accordingly. Talk about how this affects the success
benchmarks (how will the other legs getting failure responses affect the
scores?)

*T, 3.3.9, Measurement units: There is confusion here. The unit is probably
"endpoints". This section talks about two things, that, and type of forking.
How is "type of forking" a unit, and are these templates supposed to 
allow more
than one unit for a term?

*T, 3.4.2, Definition: It's not clear what "successfully completed" 
means. Did
you mean "successfully established"? This is a place where speaking in 
terms of
dialogs and transactions rather than sessions will be much clearer.

*T, 3.4.3, This benchmark metric is underdefined. I'll focus on that in the
context of the methodology document (where the docs come closer to 
defining it).
This definition includes a variable T but doesn't explain it - you have 
to read
the methodology to know what T is all about. You might just say "for the
duration of the test" or whatever is actually correct.

*T, 3.4.3, Discussion: "Media Session Hold Time MUST be set to 
infinity". Why?
The argument you give in the next sentence just says the media session hold
time has to be at least as long as the session duration. If they were equal,
and finite, the test result does not change. What's the utility of the 
infinity
concept here?

*T, 3.4.4: "until it stops responding". Any non-200 response is still a
response, and if something sends a 503 or 4xx with a retry-after (which is
likely when it's truly saturating) you've hit the condition you are 
trying to
find. The notion that the Overload Capacity is measurable by not getting any
responses at all is questionable.  This discussion has a lot of 
methodology in
it - why isn't that (only) in the methodology document?

*T, 3.4.5: A normal, fully correct system that challenged requests and
performed flawlessly would have a .5 Session Establishment Performance 
score.
Is that what you intended? The SHOULD in this section looks like 
methodology.
Why is this a SHOULD and not a MUST (the document should be clearer 
about why
sessions remaining established is important). Or wait - is this what 
Note 2 in
section 5.1 of the methodology document (which talks about reporting 
formats)
is supposed to change? If so, that needs to be moved to the actual 
methodology
and made _much_ clearer.

*T, 3.4.6: You talk of the first non-INVITE in an NS. How are you
distinguishing subsequent non-INVITES in this NS from requests in some other
NS? Are you using dialog identifiers or something else? Why do you 
expect that
to matter (why is the notion of a sequence of related non-INVITEs useful 
from a
benchmarking perspective - there isn't state kept in intermediaries 
because of
them - what will make this metric distinguishable from a metric that just
focuses on the transactions?)

*T, 3.4.7: What's special about MESSAGE? Why aren't you focusing on INFO or
some other end-to-end non-INVITE? I suspect it's because you are wanting to
focus on a simple non-INVITE transaction (which is why you are leaving out
SUBSCRIBE/NOTIFY). MESSAGE is good enough for that, but you should be clear
that's why you chose it. You should also talk about whether the payload 
of all
of the MESSAGE requests are the same size and whether that size is a 
parameter
to the benchmark. (You'll likely get very different behavior from a MESSAGE
that fragments.)

*T, 3.4.7: The definition says "messages completed" but the discussion talks
about "definition of success". Does success mean an IM transaction completed
successfully?  If so, the definition of success for a UAC has a problem. As
written, it describes a binary outcome for the whole test, not how to 
determine
the success of an individual transaction - how do you get from what it
describes to a rate?

*T, Appendix A: The document should better motivate why this is here.
Why does it mention SUBSCRIBE/NOTIFY when the rest of the document(s) are
silent on them.  The discussion says you are _selecting_ a Session Attempts
Arrival Rate distribution. It would be clearer to say you are selecting the
distribution of messages sent from the EA. It's not clear how this 
particular
metric will benefit from different sending distributions.

Now the Methodology document (comments prefixed with an M):

*M, Introduction: Can the document say why the subset of functionality
benchmarked here was chosen over other subsets? Why was Subscribe/Notify or
Info not included (or invites with MSRP or even simple early media, etc)?

*M, Introduction paragraph 4: This points to section 4 and section 2 of the
terminology document for configuration options. Section 4 is the iana
considerations section (which has no options). What did you mean to 
point to?

*M, Introduction paragraph 4, last sentence: This seems out of place - 
why is
it in the introduction and not in a section on that specific methodology.

*M, 4.1: It's not clear here, or in the methodology sections whether the 
tests
allow the transport to change as you go across an intermediary. Do you 
intend
to be able to benchmark a proxy that has TCP on one side and UDP on the 
other?

*M, 4.2: This is another spot where pointing to the Updates to 3261 that 
change
the transaction state machines is important.

*M, 4.4: Did you really mean RTSP? Maybe you meant MSRP or something 
else? RTSP
is not, itself, a media protocol.

*M, 4.9: There's something wrong with this sentence: "This test is run 
for an
extended period of time, which is referred to as infinity, and which is,
itself, a parameter of the test labeled T in the pseudo-code". What value is
there in giving some finite parameter T the name "infinity"?

*M, 4.9: Where did 100 (as an initial value for s) come from? Modern devices
process at many orders of magnitude higher rates than that. Do you want to
provide guidance instead of an absolute number here?

*M 4.9: In the pseudo-code, you often say "the largest value". It would 
help to
say the the largest value of _what_.

*M 4.9: What is the "steady_state" function called in the pseudo-code?

*M 6.3: Expected Results: The EA will have different performance
characteristics if you have them sending media or not. That could cause this
metric to be different from session establishment without media.

*M 6.5: This section should call out that loop detection is not optional 
when
forking. The Expected Results description is almost tautological - could it
instead say how having this measurement is _useful_ to those consuming this
benchmark?

*M 6.8, Procedure: Why is "May need to run for each transport of 
interest." in
a section titled "Session Establishement Rate with TLS Encrypted SIP"?

*M 6.10: This document doesn't define Flooding. What do you mean? How is 
this
different than "Stress test" as called out in section 4.8? Where does 
500 come
from?  (Again, I suspect that's a very old value - and you should be 
providing
guidance rather than an absolute number). But it's not clear how this isn't
just the session establishment rate test that just starts with a bigger 
number.
What is it actually trying to report on that's different from the session
establishment rate test, and how is the result useful?

*M 6.11: Is each registration going to a different AoR? (You must be, or the
re-registration test makes no sense.) You might talk about configuring the
registrar and the EA so they know what to use.

*M 6.12, Expected Results: Where do you get the idea that re-registration
should be faster than initial registration? How is knowing the 
difference (or
even that there is a difference) between this and the registration metric
likely to be useful to the consumer?

*M 6.14: Session Capacity, as defined in the terminology doc, is a count of
sessions, not a rate. This section treats it as a rate and says it can be
interpreted as "throughput". I'm struggling to see what it actually is
measuring. The way your algorithm is defined in section 4.9, I find s 
before I
use T. Lets say I've got a box where the value of s that's found is 
10000, and
I've got enough memory that I can deal with several large values of T. 
If I run
this test with T of 50000, my benchmark result is 500,000,000. If I run 
with a
T of 100000, my benchmark result is 1,000,000,000. How are those numbers
telling me _anything_ about session capacity. That the _real_ session 
capacity
is at least that much? Is there some part of this methodology that has 
me hunt
for a maximal value of T? Unless I've missed something, this metric 
needs more
clarification to not be completely misleading. Maybe instead of "Session
Capacity" you should simply be reporting "Simultaneous Sessions Measured"

*M 8: "and various other drafts" is not helpful - if you know of other
important documents to point to, point to them.

Nits:

T : The definition of Stateful Proxy and Stateless Proxy copied the words
"defined by this specification" from RFC3261. This literal copy introduces
confusion. Can you make it more visually obvious you are quoting? And 
even if
you do, could you replace "by this specification" with "by [RFC3261]"?

T, Introduction, 2nd paragraph, last sentence: This rules out stateless
proxies.

T, Section 3: In the places where this template is used, you are careful 
to say
None under Issues when there aren't any, but not so careful to say None 
under
See Also when there isn't anything. Leaving them blank makes some 
transitions
hard to read - they read like you are saying see also (whatever the next
section heading is).

T, 3.1.6, Discussion: s/tie interval/time interval/

M, Introduction, paragraph 2: You say "any [RFC3261] conforming device", but
you've ruled endpoint UAs out in other parts of the documents.

M 4.9: You have comments explaining send_traffic the _second_ time you 
use it.
They would be better positioned at the first use.

M 5.2: This is the first place the concept of re-Registration is 
mentioned. A
forward pointer to what you mean, or an introduction before you get to this
format would be clearer.


On 1/16/13 3:48 PM, The IESG wrote:
> The IESG has received a request from the Benchmarking Methodology WG
> (bmwg) to consider the following document:
> - 'Terminology for Benchmarking Session Initiation Protocol (SIP)
>     Networking Devices'
>    <draft-ietf-bmwg-sip-bench-term-08.txt> as Informational RFC
>
> The IESG plans to make a decision in the next few weeks, and solicits
> final comments on this action. Please send substantive comments to the
> ietf@ietf.org mailing lists by 2013-01-30. Exceptionally, comments may be
> sent to iesg@ietf.org instead. In either case, please retain the
> beginning of the Subject line to allow automated sorting.
>
> Abstract
>
>
>     This document provides a terminology for benchmarking the SIP
>     performance of networking devices.  The term performance in this
>     context means the capacity of the device- or system-under-test to
>     process SIP messages.  Terms are included for test components, test
>     setup parameters, and performance benchmark metrics for black-box
>     benchmarking of SIP networking devices.  The performance benchmark
>     metrics are obtained for the SIP signaling plane only.  The terms are
>     intended for use in a companion methodology document for
>     characterizing the performance of a SIP networking device under a
>     variety of conditions.  The intent of the two documents is to enable
>     a comparison of the capacity of SIP networking devices.  Test setup
>     parameters and a methodology document are necessary because SIP
>     allows a wide range of configuration and operational conditions that
>     can influence performance benchmark measurements.  A standard
>     terminology and methodology will ensure that benchmarks have
>     consistent definition and were obtained following the same
>     procedures.
>
>
>
>
> The file can be obtained via
> http://datatracker.ietf.org/doc/draft-ietf-bmwg-sip-bench-term/
>
> IESG discussion can be tracked via
> http://datatracker.ietf.org/doc/draft-ietf-bmwg-sip-bench-term/ballot/
>
>
> No IPR declarations have been submitted directly on this I-D.
>
>


--------------060406070505080309030205
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <div class="moz-cite-prefix">
      <meta http-equiv="content-type" content="text/html;
        charset=ISO-8859-1">
      Reviews of draft-ietf-bmwg-sip-bench-term-08 and
      draft-ietf-bmwg-sip-bench-meth-08<br>
      <br>
      Summary: These drafts are not ready for publication as RFCs.<br>
      <br>
      First, some of the text in these documents shows signs of being
      old, and the<br>
      working group may have been staring at them so long that they've
      become hard to<br>
      see.&nbsp; The terminology document says "The issue of overload in SIP
      networks is<br>
      currently a topic of discussion in the SIPPING WG." (SIPPING was
      closed in<br>
      2009). The methodology document suggests a "flooding" rate that is
      orders of<br>
      magnitude below what simple devices achieve at the moment. That
      these survived<br>
      working group last call indicates a different type of WG review
      may be needed<br>
      to groom other bugs out of the documents.<br>
      <br>
      Who is asking for these benchmarks, and are they (still)
      participating in the<br>
      group?&nbsp; The measurements defined here are very simplistic and will
      provide <br>
      limited insight into the relative performance of two elements in a
      real<br>
      deployment. The documents should be clear about their limitations,
      and it would<br>
      be good to know that the community asking for these benchmarks is
      getting tools<br>
      that will actually be useful to them. The crux of these two
      documents is in the<br>
      last paragraph of the introduction to the methodology doc:
      "Finally, the<br>
      overall value of these tests is to serve as a comparison function
      between<br>
      multiple SIP implementations".&nbsp; The documents punt on providing
      any comparison<br>
      guidance, but even if we assume someone can figure that out, do
      these<br>
      benchmarks provide something actually useful for inputs?<br>
      <br>
      It would be good to explain how these documents relate to RFC6076.<br>
      <br>
      The terminology tries to refine the definition of session, but the
      definition<br>
      provided, "The combination of signaling and media messages and
      processes that<br>
      support a SIP-based service" doesn't answer what's in one session
      vs another.<br>
      Trying to generically define session has been hard and several
      working groups<br>
      have struggled with it (see INSIPID for a current version of that<br>
      conversation). This document doesn't _need_ a generic definition
      of session -<br>
      it only needs to define the set of messages that it is measuring.
      It would be<br>
      much clearer to say "for the purposes of this document, as session
      is the set<br>
      of SIP messages associated with an INVITE initiated dialog and any
      Associated<br>
      Media, or a series of related SIP MESSAGE requests". (And looking
      at the<br>
      benchmarks, you aren't leveraging related MESSAGE requests - they
      all appear to<br>
      be completely independent). Introducing the concepts of
      Invite-initiated<br>
      sessions and non-invite-initiated sessions doesn't actually help
      define the<br>
      metrics. When you get to the metrics, you can speak concretely in
      terms of a<br>
      series of INVITEs, REGISTERs, and MESSAGEs. Doing that, and
      providing a short<br>
      introduction pointing folks with PSTN backgrounds relating these
      to "Session<br>
      Attempts" will be clearer. <br>
      <br>
      To be clear, I strongly suggest a fundamental restructuring of the
      document to<br>
      describe the benchmarks in terms of dialogs and transactions, and
      remove the IS<br>
      and NS concepts completely.<br>
      <br>
      The INVITE related tests assume no provisional responses, leaving
      out the<br>
      effect on a device's memory when the state machines it is
      maintaining transition<br>
      to the proceeding state. Further, by not including provisionals,
      and building<br>
      the tests to search for Timer B firing, the tests insure there
      will be multiple<br>
      retransmissions of the INVITE (when using UDP) that the device
      being tested has<br>
      to handle. The traffic an element has to handle and likely the
      memory it will<br>
      consume will be very different with even a single 100 trying,
      which is the more<br>
      usual case in deployed networks. The document should be clear
      _why_ it chose<br>
      the test model it did and left out metrics that took having a
      provisional<br>
      response into account. Similarly, you are leaving out the
      delayed-offer INVITE<br>
      transactions used by 3pcc and it should be more obvious that you
      are doing so.<br>
      <br>
      Likewise, the media oriented tests take a very basic approach to
      simulating<br>
      media. It should be explicitly stated that you are simulating the
      effects of a<br>
      codec like G.711 and that you are assuming an element would only
      be forwarding<br>
      packets and has to do no transcoding work. It's not clear from the
      documents<br>
      whether the EA is generating actual media or dummy packets. If
      it's actual<br>
      media, the test parameters that assume constant sized packets at a
      constant<br>
      rate will not work well for video (and I suspect endpoints, like
      B2BUAs, will<br>
      terminate your call early if you send them garbage).<br>
      <br>
      The sections on a series of INVITEs is fairly clear that you mean
      each of them<br>
      to have different dialog identifiers.&nbsp; I don't see any discussion
      of varying<br>
      the To: URI. If you don't, what's going to keep a gateway or B2BUA
      from<br>
      rejecting all but the first with something like Busy? Similarly,
      I'm not<br>
      finding where you talk about how many AoRs you are registering
      against in the<br>
      registration tests. I think, as written, someone could write this
      where all the<br>
      registers affected only one AoR.<br>
      <br>
      The methodology document calls Stress Testing out of scope, but
      the very nature<br>
      of the Benchmarking algorithm is a stress test. You are
      iteratively pushing to<br>
      see at what point something fails, _exactly_ by finding the rate
      of attempted<br>
      sessions per second that the thing under test would consider too
      high.<br>
      <br>
      Now to specific issues in document order, starting with the
      terminology<br>
      document (nits are separate and at the end):<br>
      <br>
      * T (for Terminology document): The title and abstract are
      misleading - this is<br>
      not general benchmarking for SIP performance. You have a narrow
      set of<br>
      tests, gathering metrics on a small subset of the protocol
      machinery.<br>
      Please (as RFC 6076 did) look for a title that matches the scope
      of the<br>
      document. For instance, someone testing a SIP Events server would
      be ill-served<br>
      with the benchmarks defined here.<br>
      <br>
      * T, section 1: RFC5393 should be a normative reference. You
      probably also need<br>
      to pull in RFCs 4320 and 6026 in general - they affect the state
      machines you<br>
      are measuring.<br>
      <br>
      * T, 3.1.1: As noted above, this definition of session is not
      useful. It<br>
      doesn't provide any distinction between two different sessions. I
      strongly<br>
      disagree that SIP reserves "session" to describe services
      analogous to<br>
      telephone calls on a switched network - please provide a
      reference. SIP INVITE<br>
      transactions can pend forever - it is only the limited subset of
      the use of<br>
      the transactions (where you don't use a provisional response) that
      keeps this<br>
      communication "brief". In the normal case, an INVITE an its final
      response can<br>
      be separated by an arbitrary amount of time. Instead of trying to
      tweak this<br>
      text, I suggest replacing all of it with simpler, more direct
      descriptions of<br>
      the sequence of messages you are using for the benchmarks you are
      defining<br>
      here.<br>
      <br>
      *T, 3.1.1: How is this vector notion (and graph) useful for this
      document? I<br>
      don't see that it's actually used anywhere in the documents.
      Similarly, the<br>
      arrays don't appear to be actually used (though you reference them
      from some<br>
      definitions) - What would be lost from the document if you simply
      removed all<br>
      this text?<br>
      <br>
      *T, 3.1.5, Discussion, last sentence: Why is it important to say
      "For UA-type<br>
      of network devices such as gateways, it is expected that the UA
      will be driven<br>
      into overload based on the volume of media streams it is
      processing." It's not<br>
      clear that's true for all such devices. How is saying anything
      here useful?<br>
      <br>
      *T, 3.1.6: This definition says an outstanding BYE or CANCEL is a
      Session<br>
      Attempt. Why not just say INVITE? You aren't actually measuring
      "session<br>
      attempts" for INVITEs or REGISTERs - you have separate benchmarks
      for them.<br>
      <br>
      *T, 3.1.7: It needs to be explicit that these benchmarks are not
      accounting<br>
      for/allowing early dialogs.<br>
      <br>
      *T, 3.1.8: The words "early media" appear here for the first time.
      Given the<br>
      way the benchmarks are defined, does it make sense to discuss
      early media in<br>
      these documents at all (beyond noting you do not account for it)?
      If so, <br>
      there needs to be much more clarity. (By the way, this Discussion
      will be <br>
      much easier to write in terms of dialogs).<br>
      <br>
      *T, 3.1.9, Discussion point 2: What does "the media session is
      established"<br>
      mean? If you leave this written as a generic definition, then is
      this when an<br>
      MSRP connection has been made? If you simplify it to the simple
      media model<br>
      currently in the document, does it mean an RTP packet has been
      sent? Or does it<br>
      have to be received?. For the purposes of the benchmarks defined
      here, it<br>
      doesn't seem to matter, so why have this as part of the discussion
      anyway?<br>
      <br>
      *T, 3.1.9, Definition: A series of CANCELs meets this definition.
      <br>
      <br>
      *T, 3.1.10 Discussion: This doesn't talk about 3xx responses, and
      they aren't<br>
      covered elsewhere in the document.<br>
      <br>
      *T, 3.1.11 Discussion: Isn't the MUST in this section methodology?
      Why is it in<br>
      this document and not -meth-?<br>
      <br>
      *T, 3.1.11 Discussion, next to last sentence: "measured by the
      number of<br>
      distinct Call-IDs" means you are not supporting forking, or you
      would not count<br>
      answers from more than on leg of the fork as different sessions,
      like you<br>
      should. Or are you intending that there would never be an answer
      from more than<br>
      one leg of a fork? If so, the documents need to be clearer about
      the<br>
      methodology and what's actually being measured. <br>
      <br>
      *T, 3.2.2 Definition: There's something wrong with this
      definition. For<br>
      example, proxies do not create sessions (or dialogs). Did you mean
      "forwards<br>
      messages between"?<br>
      <br>
      *T, 3.2.2 Discussion: This is definition by enumeration since it
      uses a MUST,<br>
      and is exclusive of any future things that might sit in the
      middle. If that's<br>
      what you want, make this the definition. The MAY seems
      contradictory unless you<br>
      are saying a B2BUA or SBC is just a specialized User Agent Server.
      If so,<br>
      please say it that way.<br>
      <br>
      *T, 3.2.3: This seems out of place or under-explored.&nbsp; You don't
      appear to<br>
      actually _use_ this definition in the documents.You declare these
      things in<br>
      scope, but the only consequence is the line in this section about
      the not<br>
      lowering performance benchmarks when present. Consider making that
      part of the<br>
      methodology of a benchmark and removing this section. If you think
      it's<br>
      essential, please revisit the definition - you may want to
      generalize it into<br>
      _anything_ that sits on the path and may affect SIP processing
      times<br>
      (otherwise, what's special about this either being SIP Aware, or
      being a<br>
      Firewall)?<br>
      <br>
      *T, 3.2.5 Definition: This definition just obfuscates things.
      Point to 3261's<br>
      definition instead. How is TCP a measurement unit? Does the
      general terminology<br>
      template include "enumeration" as a type? Do you really want to
      limit this<br>
      enumeration to the set of currently defined transports? Will you
      never run<br>
      these benchmarks for SIP over websockets?<br>
      <br>
      *T, 3.3.2 Discussion: Again, there needs to be clarity about what
      it means to<br>
      "create" a media session. This description differentiates attempt
      vs success,<br>
      so what is it exactly that makes a media session attempt
      successful? When you<br>
      say number of media sessions, do you mean number of M lines or
      total number of<br>
      INVITEs that have SDP with m lines?<br>
      <br>
      *T, 3.3.3: This would much clearer written in terms of
      transactions and dialogs<br>
      (you are already diving into transaction state machine details).
      This is a<br>
      place where the document needs to point out that it is not
      providing benchmarks<br>
      relevant to environments where provisionals are allowed to happen
      and INVITE<br>
      transactions are allowed to pend.<br>
      <br>
      *T, 3.3.4: How does this model (A single session duration separate
      from the<br>
      media session hold time) produce useful benchmarks? Are you using
      it to allow<br>
      media to go beyond the termination of a call? If not, then you
      have media only<br>
      for the first part of a call? What real world thing does this
      reflect?<br>
      Alternatively, what part of the device or system being benchmarked
      does this<br>
      provide insight to? <br>
      <br>
      *T, 3.3.5: The document needs to be honest about the limits of
      this simple<br>
      model of media. It doesn't account for codecs that do not have
      constant packet<br>
      sizes. The benchmarks that use the model don't capture the
      differences based on<br>
      content of the media being sent - a B2BUA or gateway, may will
      behave<br>
      differently if it is transcoding or doing content processing (such
      as DTMF<br>
      detection) than it will if it is just shoveling packets without
      looking at<br>
      them.<br>
      <br>
      *T, 3.3.6: Again, the model here is that any two media packets
      present the same<br>
      load to the thing under test. That's not true for transcoding,
      mixing, or<br>
      analysis (such as for dtmf detection). It's not clear that if you
      have two<br>
      streams, each stream has its own "constant rate". You call out
      having one audio<br>
      and one video stream - how do you configure different rates for
      them?<br>
      <br>
      *T, 3.3.7: This document points to the methodology document for
      indicating<br>
      whether streams are bi-directional or uni-directional. I cant find
      where the<br>
      methodology document talks about this (the string 'direction' does
      not<br>
      occur in that document).<br>
      <br>
      *T, 3.3.8: This text is old - it was probably written pre-RFC5056.
      If you fork,<br>
      loop detection is not optional. This, and the methodology document
      should be<br>
      updated to take that into account.<br>
      <br>
      *T, 3.3.9: Clarify if more than one leg of a fork can be answered
      successfully<br>
      and update 3.1.11 accordingly. Talk about how this affects the
      success<br>
      benchmarks (how will the other legs getting failure responses
      affect the<br>
      scores?)<br>
      <br>
      *T, 3.3.9, Measurement units: There is confusion here. The unit is
      probably<br>
      "endpoints". This section talks about two things, that, and type
      of forking.<br>
      How is "type of forking" a unit, and are these templates supposed
      to allow more<br>
      than one unit for a term?<br>
      <br>
      *T, 3.4.2, Definition: It's not clear what "successfully
      completed" means. Did<br>
      you mean "successfully established"? This is a place where
      speaking in terms of<br>
      dialogs and transactions rather than sessions will be much
      clearer.<br>
      <br>
      *T, 3.4.3, This benchmark metric is underdefined. I'll focus on
      that in the<br>
      context of the methodology document (where the docs come closer to
      defining it).<br>
      This definition includes a variable T but doesn't explain it - you
      have to read<br>
      the methodology to know what T is all about. You might just say
      "for the<br>
      duration of the test" or whatever is actually correct.<br>
      <br>
      *T, 3.4.3, Discussion: "Media Session Hold Time MUST be set to
      infinity". Why?<br>
      The argument you give in the next sentence just says the media
      session hold<br>
      time has to be at least as long as the session duration. If they
      were equal,<br>
      and finite, the test result does not change. What's the utility of
      the infinity<br>
      concept here?<br>
      <br>
      *T, 3.4.4: "until it stops responding". Any non-200 response is
      still a<br>
      response, and if something sends a 503 or 4xx with a retry-after
      (which is<br>
      likely when it's truly saturating) you've hit the condition you
      are trying to<br>
      find. The notion that the Overload Capacity is measurable by not
      getting any<br>
      responses at all is questionable.&nbsp; This discussion has a lot of
      methodology in<br>
      it - why isn't that (only) in the methodology document? <br>
      <br>
      *T, 3.4.5: A normal, fully correct system that challenged requests
      and<br>
      performed flawlessly would have a .5 Session Establishment
      Performance score.<br>
      Is that what you intended? The SHOULD in this section looks like
      methodology.<br>
      Why is this a SHOULD and not a MUST (the document should be
      clearer about why<br>
      sessions remaining established is important). Or wait - is this
      what Note 2 in<br>
      section 5.1 of the methodology document (which talks about
      reporting formats)<br>
      is supposed to change? If so, that needs to be moved to the actual
      methodology<br>
      and made _much_ clearer.<br>
      <br>
      *T, 3.4.6: You talk of the first non-INVITE in an NS. How are you<br>
      distinguishing subsequent non-INVITES in this NS from requests in
      some other<br>
      NS? Are you using dialog identifiers or something else? Why do you
      expect that<br>
      to matter (why is the notion of a sequence of related non-INVITEs
      useful from a<br>
      benchmarking perspective - there isn't state kept in
      intermediaries because of<br>
      them - what will make this metric distinguishable from a metric
      that just<br>
      focuses on the transactions?) <br>
      <br>
      *T, 3.4.7: What's special about MESSAGE? Why aren't you focusing
      on INFO or<br>
      some other end-to-end non-INVITE? I suspect it's because you are
      wanting to<br>
      focus on a simple non-INVITE transaction (which is why you are
      leaving out<br>
      SUBSCRIBE/NOTIFY). MESSAGE is good enough for that, but you should
      be clear<br>
      that's why you chose it. You should also talk about whether the
      payload of all<br>
      of the MESSAGE requests are the same size and whether that size is
      a parameter<br>
      to the benchmark. (You'll likely get very different behavior from
      a MESSAGE<br>
      that fragments.) <br>
      <br>
      *T, 3.4.7: The definition says "messages completed" but the
      discussion talks<br>
      about "definition of success". Does success mean an IM transaction
      completed<br>
      successfully?&nbsp; If so, the definition of success for a UAC has a
      problem. As<br>
      written, it describes a binary outcome for the whole test, not how
      to determine<br>
      the success of an individual transaction - how do you get from
      what it<br>
      describes to a rate?<br>
      <br>
      *T, Appendix A: The document should better motivate why this is
      here.<br>
      Why does it mention SUBSCRIBE/NOTIFY when the rest of the
      document(s) are<br>
      silent on them.&nbsp; The discussion says you are _selecting_ a Session
      Attempts<br>
      Arrival Rate distribution. It would be clearer to say you are
      selecting the<br>
      distribution of messages sent from the EA. It's not clear how this
      particular<br>
      metric will benefit from different sending distributions.<br>
      <br>
      Now the Methodology document (comments prefixed with an M):<br>
      <br>
      *M, Introduction: Can the document say why the subset of
      functionality<br>
      benchmarked here was chosen over other subsets? Why was
      Subscribe/Notify or<br>
      Info not included (or invites with MSRP or even simple early
      media, etc)?<br>
      <br>
      *M, Introduction paragraph 4: This points to section 4 and section
      2 of the<br>
      terminology document for configuration options. Section 4 is the
      iana<br>
      considerations section (which has no options). What did you mean
      to point to?<br>
      <br>
      *M, Introduction paragraph 4, last sentence: This seems out of
      place - why is<br>
      it in the introduction and not in a section on that specific
      methodology.<br>
      <br>
      *M, 4.1: It's not clear here, or in the methodology sections
      whether the tests<br>
      allow the transport to change as you go across an intermediary. Do
      you intend<br>
      to be able to benchmark a proxy that has TCP on one side and UDP
      on the other?<br>
      <br>
      *M, 4.2: This is another spot where pointing to the Updates to
      3261 that change<br>
      the transaction state machines is important.<br>
      <br>
      *M, 4.4: Did you really mean RTSP? Maybe you meant MSRP or
      something else? RTSP<br>
      is not, itself, a media protocol.<br>
      <br>
      *M, 4.9: There's something wrong with this sentence: "This test is
      run for an<br>
      extended period of time, which is referred to as infinity, and
      which is,<br>
      itself, a parameter of the test labeled T in the pseudo-code".
      What value is<br>
      there in giving some finite parameter T the name "infinity"?<br>
      <br>
      *M, 4.9: Where did 100 (as an initial value for s) come from?
      Modern devices<br>
      process at many orders of magnitude higher rates than that. Do you
      want to<br>
      provide guidance instead of an absolute number here?<br>
      <br>
      *M 4.9: In the pseudo-code, you often say "the largest value". It
      would help to<br>
      say the the largest value of _what_.<br>
      <br>
      *M 4.9: What is the "steady_state" function called in the
      pseudo-code?<br>
      <br>
      *M 6.3: Expected Results: The EA will have different performance<br>
      characteristics if you have them sending media or not. That could
      cause this<br>
      metric to be different from session establishment without media.<br>
      <br>
      *M 6.5: This section should call out that loop detection is not
      optional when<br>
      forking. The Expected Results description is almost tautological -
      could it<br>
      instead say how having this measurement is _useful_ to those
      consuming this<br>
      benchmark?<br>
      <br>
      *M 6.8, Procedure: Why is "May need to run for each transport of
      interest." in<br>
      a section titled "Session Establishement Rate with TLS Encrypted
      SIP"?<br>
      <br>
      *M 6.10: This document doesn't define Flooding. What do you mean?
      How is this<br>
      different than "Stress test" as called out in section 4.8? Where
      does 500 come<br>
      from?&nbsp; (Again, I suspect that's a very old value - and you should
      be providing<br>
      guidance rather than an absolute number). But it's not clear how
      this isn't<br>
      just the session establishment rate test that just starts with a
      bigger number.<br>
      What is it actually trying to report on that's different from the
      session<br>
      establishment rate test, and how is the result useful?<br>
      <br>
      *M 6.11: Is each registration going to a different AoR? (You must
      be, or the<br>
      re-registration test makes no sense.) You might talk about
      configuring the<br>
      registrar and the EA so they know what to use.<br>
      <br>
      *M 6.12, Expected Results: Where do you get the idea that
      re-registration<br>
      should be faster than initial registration? How is knowing the
      difference (or<br>
      even that there is a difference) between this and the registration
      metric<br>
      likely to be useful to the consumer? <br>
      <br>
      *M 6.14: Session Capacity, as defined in the terminology doc, is a
      count of<br>
      sessions, not a rate. This section treats it as a rate and says it
      can be<br>
      interpreted as "throughput". I'm struggling to see what it
      actually is<br>
      measuring. The way your algorithm is defined in section 4.9, I
      find s before I<br>
      use T. Lets say I've got a box where the value of s that's found
      is 10000, and<br>
      I've got enough memory that I can deal with several large values
      of T. If I run<br>
      this test with T of 50000, my benchmark result is 500,000,000. If
      I run with a<br>
      T of 100000, my benchmark result is 1,000,000,000. How are those
      numbers<br>
      telling me _anything_ about session capacity. That the _real_
      session capacity<br>
      is at least that much? Is there some part of this methodology that
      has me hunt<br>
      for a maximal value of T? Unless I've missed something, this
      metric needs more<br>
      clarification to not be completely misleading. Maybe instead of
      "Session<br>
      Capacity" you should simply be reporting "Simultaneous Sessions
      Measured"<br>
      <br>
      *M 8: "and various other drafts" is not helpful - if you know of
      other<br>
      important documents to point to, point to them. <br>
      <br>
      Nits:<br>
      <br>
      T : The definition of Stateful Proxy and Stateless Proxy copied
      the words<br>
      "defined by this specification" from RFC3261. This literal copy
      introduces<br>
      confusion. Can you make it more visually obvious you are quoting?
      And even if<br>
      you do, could you replace "by this specification" with "by
      [RFC3261]"? <br>
      <br>
      T, Introduction, 2nd paragraph, last sentence: This rules out
      stateless<br>
      proxies.<br>
      <br>
      T, Section 3: In the places where this template is used, you are
      careful to say<br>
      None under Issues when there aren't any, but not so careful to say
      None under<br>
      See Also when there isn't anything. Leaving them blank makes some
      transitions<br>
      hard to read - they read like you are saying see also (whatever
      the next<br>
      section heading is).<br>
      <br>
      T, 3.1.6, Discussion: s/tie interval/time interval/<br>
      <br>
      M, Introduction, paragraph 2: You say "any [RFC3261] conforming
      device", but<br>
      you've ruled endpoint UAs out in other parts of the documents.<br>
      <br>
      M 4.9: You have comments explaining send_traffic the _second_ time
      you use it.<br>
      They would be better positioned at the first use.<br>
      <br>
      M 5.2: This is the first place the concept of re-Registration is
      mentioned. A<br>
      forward pointer to what you mean, or an introduction before you
      get to this<br>
      format would be clearer.<br>
      <br>
      <br>
      On 1/16/13 3:48 PM, The IESG wrote:<br>
    </div>
    <blockquote
      cite="mid:20130116214838.3092.88369.idtracker@ietfa.amsl.com"
      type="cite">
      <pre wrap="">
The IESG has received a request from the Benchmarking Methodology WG
(bmwg) to consider the following document:
- 'Terminology for Benchmarking Session Initiation Protocol (SIP)
   Networking Devices'
  &lt;draft-ietf-bmwg-sip-bench-term-08.txt&gt; as Informational RFC

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action. Please send substantive comments to the
<a class="moz-txt-link-abbreviated" href="mailto:ietf@ietf.org">ietf@ietf.org</a> mailing lists by 2013-01-30. Exceptionally, comments may be
sent to <a class="moz-txt-link-abbreviated" href="mailto:iesg@ietf.org">iesg@ietf.org</a> instead. In either case, please retain the
beginning of the Subject line to allow automated sorting.

Abstract


   This document provides a terminology for benchmarking the SIP
   performance of networking devices.  The term performance in this
   context means the capacity of the device- or system-under-test to
   process SIP messages.  Terms are included for test components, test
   setup parameters, and performance benchmark metrics for black-box
   benchmarking of SIP networking devices.  The performance benchmark
   metrics are obtained for the SIP signaling plane only.  The terms are
   intended for use in a companion methodology document for
   characterizing the performance of a SIP networking device under a
   variety of conditions.  The intent of the two documents is to enable
   a comparison of the capacity of SIP networking devices.  Test setup
   parameters and a methodology document are necessary because SIP
   allows a wide range of configuration and operational conditions that
   can influence performance benchmark measurements.  A standard
   terminology and methodology will ensure that benchmarks have
   consistent definition and were obtained following the same
   procedures.




The file can be obtained via
<a class="moz-txt-link-freetext" href="http://datatracker.ietf.org/doc/draft-ietf-bmwg-sip-bench-term/">http://datatracker.ietf.org/doc/draft-ietf-bmwg-sip-bench-term/</a>

IESG discussion can be tracked via
<a class="moz-txt-link-freetext" href="http://datatracker.ietf.org/doc/draft-ietf-bmwg-sip-bench-term/ballot/">http://datatracker.ietf.org/doc/draft-ietf-bmwg-sip-bench-term/ballot/</a>


No IPR declarations have been submitted directly on this I-D.


</pre>
    </blockquote>
    <br>
  </body>
</html>

--------------060406070505080309030205--

From rjsparks@nostrum.com  Thu Jan 24 08:06:16 2013
Return-Path: <rjsparks@nostrum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E26B121F89EE for <ietf@ietfa.amsl.com>; Thu, 24 Jan 2013 08:06:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.367
X-Spam-Level: 
X-Spam-Status: No, score=-102.367 tagged_above=-999 required=5 tests=[AWL=0.232, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 xHC2GrWl0d1Z for <ietf@ietfa.amsl.com>; Thu, 24 Jan 2013 08:06:16 -0800 (PST)
Received: from shaman.nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id 4DE7E21F89C3 for <ietf@ietf.org>; Thu, 24 Jan 2013 08:06:16 -0800 (PST)
Received: from unnumerable.local (pool-173-57-99-236.dllstx.fios.verizon.net [173.57.99.236]) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id r0OG6Fsc096952 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Thu, 24 Jan 2013 10:06:15 -0600 (CST) (envelope-from rjsparks@nostrum.com)
Message-ID: <51015BF7.3020505@nostrum.com>
Date: Thu, 24 Jan 2013 10:06:15 -0600
From: Robert Sparks <rjsparks@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130107 Thunderbird/17.0.2
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Last Call: <draft-ietf-bmwg-sip-bench-meth-08.txt> (Methodology for Benchmarking SIP Networking Devices) to Informational RFC
References: <20130116214733.3096.50164.idtracker@ietfa.amsl.com>
In-Reply-To: <20130116214733.3096.50164.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 24 Jan 2013 16:06:17 -0000

Please see my response to the last call message for 
draft-ietf-bmwg-sip-bench-term. That review covered this document and 
that one at the same time.

RjS

On 1/16/13 3:47 PM, The IESG wrote:
> The IESG has received a request from the Benchmarking Methodology WG
> (bmwg) to consider the following document:
> - 'Methodology for Benchmarking SIP Networking Devices'
>    <draft-ietf-bmwg-sip-bench-meth-08.txt> as Informational RFC
>
> The IESG plans to make a decision in the next few weeks, and solicits
> final comments on this action. Please send substantive comments to the
> ietf@ietf.org mailing lists by 2013-01-30. Exceptionally, comments may be
> sent to iesg@ietf.org instead. In either case, please retain the
> beginning of the Subject line to allow automated sorting.
>
> Abstract
>
>
>     This document describes the methodology for benchmarking Session
>     Initiation Protocol (SIP) performance as described in SIP
>     benchmarking terminology document.  The methodology and terminology
>     are to be used for benchmarking signaling plane performance with
>     varying signaling and media load.  Both scale and establishment rate
>     are measured by signaling plane performance.  The SIP Devices to be
>     benchmarked may be a single device under test (DUT) or a system under
>     test (SUT).  Benchmarks can be obtained and compared for different
>     types of devices such as SIP Proxy Server, SBC, and server paired
>     with a media relay or Firewall/NAT device.
>
>
>
>
> The file can be obtained via
> http://datatracker.ietf.org/doc/draft-ietf-bmwg-sip-bench-meth/
>
> IESG discussion can be tracked via
> http://datatracker.ietf.org/doc/draft-ietf-bmwg-sip-bench-meth/ballot/
>
>
> No IPR declarations have been submitted directly on this I-D.
>
>


From dromasca@avaya.com  Thu Jan 24 08:22:55 2013
Return-Path: <dromasca@avaya.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 044D521F878F; Thu, 24 Jan 2013 08:22:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.932
X-Spam-Level: 
X-Spam-Status: No, score=-102.932 tagged_above=-999 required=5 tests=[AWL=-0.333, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 artzbMkHtFyN; Thu, 24 Jan 2013 08:22:54 -0800 (PST)
Received: from p-us1-iereast-outbound.us1.avaya.com (p-us1-iereast-outbound.us1.avaya.com [135.11.29.13]) by ietfa.amsl.com (Postfix) with ESMTP id 1578721F857D; Thu, 24 Jan 2013 08:22:53 -0800 (PST)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AjEKAAEvoFCHCzI1/2dsb2JhbABEgX9twGmBAQeCHgEBAQEDEig0CwwEAgEIDQQEAQELFAUEBzIUCQgCBA4FCBqHaAEKniacAZF+YQOXGIRxijaCb4IZ
X-IronPort-AV: E=Sophos;i="4.80,759,1344225600"; d="scan'208";a="45753280"
Received: from unknown (HELO p-us1-erheast.us1.avaya.com) ([135.11.50.53]) by p-us1-iereast-outbound.us1.avaya.com with ESMTP; 24 Jan 2013 11:10:50 -0500
Received: from unknown (HELO AZ-FFEXHC01.global.avaya.com) ([135.64.58.11]) by p-us1-erheast-out.us1.avaya.com with ESMTP; 24 Jan 2013 10:57:07 -0500
Received: from AZ-FFEXMB04.global.avaya.com ([fe80::6db7:b0af:8480:c126]) by AZ-FFEXHC01.global.avaya.com ([135.64.58.11]) with mapi id 14.02.0318.004; Thu, 24 Jan 2013 11:23:04 -0500
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: "ietf@ietf.org" <ietf@ietf.org>
Subject: RE: Last Call: <draft-ietf-opsawg-oam-overview-08.txt> (An Overview of	Operations, Administration,	and Maintenance (OAM) Mechanisms) to Informational RFC
Thread-Topic: Last Call: <draft-ietf-opsawg-oam-overview-08.txt> (An Overview of	Operations, Administration, and Maintenance (OAM) Mechanisms) to Informational RFC
Thread-Index: AQHN8DMMkdjU5d8tZk2bi1Jv4SI3NphYtB9w
Date: Thu, 24 Jan 2013 16:23:04 +0000
Message-ID: <9904FB1B0159DA42B0B887B7FA8119CA06A4B6@AZ-FFEXMB04.global.avaya.com>
References: <20130111193616.19158.16205.idtracker@ietfa.amsl.com>
In-Reply-To: <20130111193616.19158.16205.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [135.64.58.46]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "opsawg@ietf.org" <opsawg@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 24 Jan 2013 16:22:55 -0000

This is a useful and well-written document and I support its publication. I=
 have a few comments which I would be glad if they were addressed:=20

1. I believe that the document must include reference to TRILL OAM, referen=
cing draft-ietf-trill-oam-req-04 (which is close to approval) and including=
 a section on TRILL OAM in the table in 1.4.=20

2. The reference to Non-IETF documents in section 1.5 should mention the fa=
ct that non-IETF documents deal in many cases with OAM functions below the =
IP layer (layer 2, "2.5") and that operators use in some cases a multi-laye=
red OAM approach function of the way their networks are architectured.

3. Section 1.5 mentions [IEEE802.1ag] under 'OAM mechanisms for Ethernet ba=
sed networks'. In reality CFM as defined by IEEE 802.1ag is designed to app=
ly for all bridged networks in IEEE 802, whatever the media protocol is bei=
ng used.=20

4. Together with .1ag I would recommend to also include in the table and li=
st of references the CFM extensions defined in 802.1Qaw - Management of dat=
a-driven and data-dependent connectivity faults=20

5. I am a little concerned of this document defining - once more - in secti=
ons 3.4.3.8 and 3.4.3.9 metrics and speak about measurement methods for Pac=
ket Loss and Packet Delay. I would prefer to refer to IPPM RFCs for this pu=
rpose

6. Section 1.1 mentions delay variation when describing the Delay Measureme=
nt (DM) function, but section 3.4.3.9 'forgets' it. I believe that delay va=
riation is important and needs to be covered.=20

Regards,

Dan
=20


> -----Original Message-----
> From: ietf-announce-bounces@ietf.org [mailto:ietf-announce-
> bounces@ietf.org] On Behalf Of The IESG
> Sent: Friday, January 11, 2013 9:36 PM
> To: IETF-Announce
> Cc: opsawg@ietf.org
> Subject: Last Call: <draft-ietf-opsawg-oam-overview-08.txt> (An Overview
> of Operations, Administration, and Maintenance (OAM) Mechanisms) to
> Informational RFC
>=20
>=20
> The IESG has received a request from the Operations and Management Area
> Working Group WG (opsawg) to consider the following document:
> - 'An Overview of Operations, Administration, and Maintenance (OAM)
>    Mechanisms'
>   <draft-ietf-opsawg-oam-overview-08.txt> as Informational RFC
>=20
> The IESG plans to make a decision in the next few weeks, and solicits
> final comments on this action. Please send substantive comments to the
> ietf@ietf.org mailing lists by 2013-01-25. Exceptionally, comments may
> be sent to iesg@ietf.org instead. In either case, please retain the
> beginning of the Subject line to allow automated sorting.
>=20
> Abstract
>=20
>=20
>    Operations, Administration, and Maintenance (OAM) is a general term
>    that refers to a toolset that can be used for fault detection and
>    isolation, and for performance measurement. OAM mechanisms have been
>    defined for various layers in the protocol stack, and are used with a
>    variety of protocols.
>=20
>    This document presents an overview of the OAM mechanisms that have
>    been defined and are currently being defined by the IETF.
>=20
>=20
>=20
>=20
> The file can be obtained via
> http://datatracker.ietf.org/doc/draft-ietf-opsawg-oam-overview/
>=20
> IESG discussion can be tracked via
> http://datatracker.ietf.org/doc/draft-ietf-opsawg-oam-overview/ballot/
>=20
>=20
> No IPR declarations have been submitted directly on this I-D.
>=20


From john-ietf@jck.com  Thu Jan 24 10:34:37 2013
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5F12321F850C for <ietf@ietfa.amsl.com>; Thu, 24 Jan 2013 10:34:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.766
X-Spam-Level: 
X-Spam-Status: No, score=-102.766 tagged_above=-999 required=5 tests=[AWL=-0.167, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 ySQVlgghF-mW for <ietf@ietfa.amsl.com>; Thu, 24 Jan 2013 10:34:36 -0800 (PST)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id EB93621F84F3 for <ietf@ietf.org>; Thu, 24 Jan 2013 10:34:35 -0800 (PST)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1TyRd6-000Dey-SO; Thu, 24 Jan 2013 13:34:29 -0500
Date: Thu, 24 Jan 2013 13:34:20 -0500
From: John C Klensin <john-ietf@jck.com>
To: Thomas Narten <narten@us.ibm.com>, adrian@olddog.co.uk
Subject: Re: FW: Last Call: <draft-farrell-ft-03.txt> (A Fast-Track way to RFC	with Running Code) to Experimental RFC
Message-ID: <84D9F6D1AE454253626C8859@JcK-HP8200.jck.com>
In-Reply-To: <201301222131.r0MLVK8C015116@cichlid.raleigh.ibm.com>
References: <017001cdf017$c394df00$4abe9d00$@olddog.co.uk> <50FEC0B8.8060905@isi.edu> <201301222131.r0MLVK8C015116@cichlid.raleigh.ibm.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 24 Jan 2013 18:34:37 -0000

--On Tuesday, January 22, 2013 16:31 -0500 Thomas Narten
<narten@us.ibm.com> wrote:

> FWIW, I share Joe's concerns. And Stephen's responses don't
> really change my mind.
> 
> This document seems to have a bit of missing the forest for the
> trees. In the overall scheme of things, I don't believe the
> draft will materially help, and is at best a distraction from
> dealing with meaningful problems.
> 
> The crux of the issue is that any attempt at "fast tracking" is
> fundamentally about short-circuiting some aspect of our review
> processes. We should only do that very carefully. In almost
> all cases, individual judgement is needed as to when it is
> appropriate to do that. ADs/WG chairs already have some
> flexibility here. e.g., a WG can skip WG LC if they think its
>...

Hi.
First of all, I am completely in agreement with Thomas and his
analysis.  Anything  that can reasonably and appropriately be
done by this sort of effort can be done by discretion without
adoption of a formal procedure and adoption of a formal
procedure creates additional and unnecessary risks. 

As co-author of the process experiment model, I also object to
its use when it is not demonstrably necessary, for example to
give extra status and force IETF-wide use where the actions
suggested can be carried out as a matter of normal discretion
(see Section 5 of the document).  In this particular case, a
better experiment would be to use a process like this for some
otherwise-relevant drafts and in some areas only and compare the
results.  The "force IETF-wide use" part doesn't apply as long
as its invocation is a matter of WG Chair and AD discretion and
belief that the right conditions are met, so, other than
consuming a rather large amount of community time since it was
first proposed almost two months ago, I just don't see what it
accomplishes other than adding to the collection of process
documents and constraining the review process, including about
issues that running code doesn't help to inform.  The process
experiment mechanism is, IMO, an entirely inappropriate way to
simply make a statement that the IETF really, really, does
believe in running code and interoperability... especially since
one would hope that such a statement would not expire after a
year.

Another thing this draft accomplishes is to shift the
responsibility for determining whether a document is "good
enough" from an IESG interpretation of community consensus to
the decision of a single AD as to whether or not changes are
required (Section 3, item 5).  While it would probably improve
speed of processing, it is not, in general, a desirable change,
especially if one believes in the first part of the Clark quote.

It is probably just a nit in the grand scheme of things but, if
the responsible AD doesn't have time to do a sufficient review
to be confident in voting "yes" (Section 3, item 7) how can she
possibly sign off on the belief than no changes are required
(Section 3, item 5)?  It seems to me that situation creates a
situation in which an AD can initiate this process, take the
word of the WG that everything is in order, and then not only
avoid responsibility by abstaining but use the provisions of
Section 3 item 8 to let the document go through (as long as some
AD is willing to say "yes") without taking real responsibility.
Especially because we don't have firm rules against a WG Chair
and responsible AD coming from the same organization, I would
hope that those who are concerned about IETF CoI and antitrust
policies would take a careful look at that scenario because it
would seem to avoid many of the protections that are inherent in
wide community review and individual responsibility.  Other than
that, it is nothing more than a specific scenario consistent
with Thomas's concern that this procedure could be used to
short-circuit effective review.

I'm not going to quote extensively from Thomas's other arguments
or waste bits trying to summarize them, but let me add a few
observations to Thomas's about the document and how it is being
handled.

> If it is really urgent to get a document done, it is far
> better to take steps to make sure the editors are engaged and
> responsive. That is more likely the real issue!!!

And that no AD is going to screw around nit-picking or delaying
things in other ways.  Based on experience, I have absolutely no
confidence that a prohibition against anything that isn't
important (such as the one in this draft) will stop that
behavior if, e.g., someone thinks the document is
incomprehensible or ignores important issues.  (And, as Thomas
points out, it shouldn't).
 
> Running code is valuable. Always has been, always will be. But
> we need to resist the temptation of making "running code" more
> equal than other criteria or putting it on a pedestal as some
> sort of holy grail. Running code by itself is just a sound
> bite. The importance of running code is what it tells us about
> a protocol specification. Just the mere fact that there is
>...

Moreover, Dave Clark and sound bites notwithstanding,
interoperability is lots more important to us than running code,
partially because, while a lot of things might be learned by a
good-faith implementation of a specification by someone not
involved in its development, an implementation by an author or
other active participant in the development of a document may
actually tell us very little without third-party and
interoperability testing ... including not telling us whether it
is actually "running", much less conforming, code.  The latter
is a _huge_ can of worms if it is going to be a procedural
gating factor in the way the document proposes.

In that light, the document says "The spirit [...] is that early
implementations and ongoing development and testing throughout
the protocol work can significantly improve the quality of a
protocol and of its specification."  I agree with that and hope
everyone else does too.  But, other than general encouragement
and observations that such testing might be appropriate (e.g.,
in Section 4 item 13) this proposal makes no provision for
enabling or encouraging "ongoing development and testing
throughout the protocol work".  Instead, it concentrates only on
an assertion that an implementation exists, that it is
conformant enough to be informative, and that it "runs".  I
would have more sympathy with this proposal if its gating
condition was serious interoperability testing among independent
implementations, but that could still be done on a discretionary
basis (as 2026 points out in Section 4.1.1).



> But overall, I see this document at best as a no-op. However,
> I fear that it can be used to short-circuit our review
> processes in a way that doesn't help the IETF and that won't
> really speed things up enough to justify the downsides.

Yes.

In addition, this document moves a number of informal IESG
procedures -- including the DISCUSS criteria and even the
Shepherd report requirements (now Informational in RFC 4858 plus
a number of less formal "statements" and "templates" that have
sometimes changed rapidly) -- into the status of formal
procedural requirements despite the details of those procedures
never having gotten community consensus about those
specifications.  Under normal circumstances, the relationship
between this document and those specifications would require
additional actions to prevent this document from going into
permanent publication hold.   [DCRIT] is called out as a
normative reference without the discussion and alerts normally
required; the shepherding procedures and templates are not
called out at all.

I'm also feeling a need to say something that people seem to be
missing or avoiding.  In my experience in the IETF, we almost
never allow a individual submission document that is obviously
very controversial to turn into a extended debate on the IETF
list with the author trying to refute every comment.   Sooner or
later (usually sooner), the sponsoring AD says "hey, not ready
for the IETF List, much less Last Call" and pushes it off into
either a separate mailing list (to emerge only when there is
real consensus) or asks the author to take steps to propose and
organize a WG.

So, Adrian, noting the ratio between discussion of this draft on
the IETF list in the last few weeks and discussions of
everything else, how long does professional courtesy to another
IESG member (presumably in combination with your thinking this
is a good idea) encourage you to allow the unintentional DoS
attack on the IETF list to continue? 

regards,
   john


From touch@isi.edu  Thu Jan 24 11:35:36 2013
Return-Path: <touch@isi.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E2E1B11E80A5; Thu, 24 Jan 2013 11:35:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 xGf7BgYgBWV8; Thu, 24 Jan 2013 11:35:36 -0800 (PST)
Received: from vapor.isi.edu (vapor.isi.edu [128.9.64.64]) by ietfa.amsl.com (Postfix) with ESMTP id 2375811E80A3; Thu, 24 Jan 2013 11:35:36 -0800 (PST)
Received: from [128.9.160.166] (abc.isi.edu [128.9.160.166]) (authenticated bits=0) by vapor.isi.edu (8.13.8/8.13.8) with ESMTP id r0OJZ5Ni006195 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 24 Jan 2013 11:35:05 -0800 (PST)
Message-ID: <51018CE9.3030700@isi.edu>
Date: Thu, 24 Jan 2013 11:35:05 -0800
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130107 Thunderbird/17.0.2
MIME-Version: 1.0
To: Allison Mankin <allison.mankin@gmail.com>
Subject: Re: TSV-DIR review of draft-ietf-6man-ipv6-atomic-fragments-03
References: <CAP8yD=tF4_2RpNZNAHRR65HTZGwSPE+Pjx8-a8H_vQHNjqfEoA@mail.gmail.com>
In-Reply-To: <CAP8yD=tF4_2RpNZNAHRR65HTZGwSPE+Pjx8-a8H_vQHNjqfEoA@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: 6man@ietf.org, Transport Area <tsv-area@ietf.org>, IETF Discuss <ietf@ietf.org>, Transport Directorate <tsv-dir@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 24 Jan 2013 19:35:37 -0000

FWIW, this document includes text that somewhat defeats the previous 
recommendations of TCPM regarding RFC5927.

RFC5927 includes specific text indicating that the techniques described 
are being documented, but that the TCP standard was NOT being changed to 
include those ICMP validation checks.

This document states that:

       Many implementations fail to perform validation checks on the
       received ICMPv6 error messages, as recommended in Section 5.2 of
       [RFC4443] and [RFC5927].

I.e., the second RFC does NOT recommend changes; it documents them. This 
document should be VERY carefully reviewed to ensure that it does not 
undo the previous TCPM concerns about these techniques.

Joe

From ned+ietf@mauve.mrochek.com  Thu Jan 24 13:26:01 2013
Return-Path: <ned+ietf@mauve.mrochek.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5711B11E80A5 for <ietf@ietfa.amsl.com>; Thu, 24 Jan 2013 13:26:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 YlYWNmZFDiA0 for <ietf@ietfa.amsl.com>; Thu, 24 Jan 2013 13:26:00 -0800 (PST)
Received: from mauve.mrochek.com (mauve.mrochek.com [66.59.230.40]) by ietfa.amsl.com (Postfix) with ESMTP id 8C1BF11E8099 for <ietf@ietf.org>; Thu, 24 Jan 2013 13:26:00 -0800 (PST)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01OPDBI6HGWG0075N5@mauve.mrochek.com> for ietf@ietf.org; Thu, 24 Jan 2013 13:20:56 -0800 (PST)
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01OOJ8U2Q2U800008S@mauve.mrochek.com> (original mail from NED@mauve.mrochek.com) for ietf@ietf.org; Thu, 24 Jan 2013 13:20:51 -0800 (PST)
From: ned+ietf@mauve.mrochek.com
Message-id: <01OPDBI3MP4Q00008S@mauve.mrochek.com>
Date: Thu, 24 Jan 2013 13:12:16 -0800 (PST)
Subject: Re: Vestigial Features (was Re: CRLF (was: Re: A modest proposal))
In-reply-to: "Your message dated Thu, 24 Jan 2013 10:22:16 +0100" <6372D85B-041B-4FBF-B41E-7505C4B56E58@tzi.org>
MIME-version: 1.0
Content-type: TEXT/PLAIN; charset=iso-8859-1
References: <20130123061554.85592.qmail@joyce.lan> <C3CD7DDBD81323BD17837BCE@JcK-HP8200.jck.com> <8EFA8168-7F05-4010-975C-CE601361501C@tzi.org> <201301240341.r0O3fOui340901@shell01.TheWorld.com> <6372D85B-041B-4FBF-B41E-7505C4B56E58@tzi.org>
To: Carsten Bormann <cabo@tzi.org>
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 24 Jan 2013 21:26:01 -0000

> On Jan 24, 2013, at 04:41, worley@ariadne.com (Dale R. Worley) wrote:

> >> From: Carsten Bormann <cabo@tzi.org>
> >>
> >> I think in protocol evolution (as well as computer system evolution
> >> in general) we are missing triggers to get rid of vestigial
> >> features.
> >
> > That's quite true.  Let us start by rationalizing the spelling and
> > punctuation of written English (which is the coding system for *this
> > entire discussion*).  Once we've cleaned up that idiocy, we can start
> > in on SIP.

> I see I didn't make myself clear.
> I'm not suggesting we clean up vestigials in existing spec[ie]s, such as HTTP or SIP.
> (We might even do that, see HTTPbis, but only very carefully.)

> My point was about the case when we clone new stuff off existing protocols.
> (SIP was cloned off HTTP which was cloned off SMTP which was cloned off FTP
> which at least has had strong kinship with Telnet, hence all these use NVT.)

Actually, in regards to NVT, there's something of a break in HTTP: text
material is *not* required to use CRLF as a line terminator. Any of LF, CR, or 
CRLF is permissible.

I really don't want to get into the history of this choice or for that matter
the results it has produced. Suffice it to say it has had some advantages and
some disadvantages.

> Staying in your analogy: when you design a new language based on English, please do fix some of this stuff.
> (Maybe the analogy isn't that useful after all.)

> Actually, we haven't been that bad about this.

> E.g., we have been pretty good about getting rid of the madness of historic
> character coding by focusing on UTF-8 for new designs.

But a vital part of that choice is that it is backwards compatible with
US-ASCII.

> What I'm asking for: Apart from these big reformation projects, we also
> should occasionally fix little things.

Or not. How about instead of viewing these sorts past choices as things to be
fixed, we instead view them as what they were: Choices. And then decide, based
on the actual requirements of whatever we're doing, whether or not it makes
sense to make a change.

Sure, we can design some new format with LFs or CRs or maybe even line or page
separators as line breaks instead of CRLFs. And maybe that makes sense in some
cases. Or not: Such choices can have serious consequences if any degree of
backwards compatibility with exiting transfer services is desired. And constant
transcoding of stuff to make it work in various places is not necessarily a
winning approach.

> When "inventing" new stuff by drawing analogies off of old specs.

I really don't think unthinking copying from past specifications is the issue
here, your asssertions to the contrary notwithstanding.

				Ned

From mattmathis@google.com  Thu Jan 24 14:35:02 2013
Return-Path: <mattmathis@google.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9598A11E8099 for <ietf@ietfa.amsl.com>; Thu, 24 Jan 2013 14:35:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.727
X-Spam-Level: 
X-Spam-Status: No, score=-102.727 tagged_above=-999 required=5 tests=[AWL=0.250, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
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 P6Og7LIxs+wn for <ietf@ietfa.amsl.com>; Thu, 24 Jan 2013 14:35:01 -0800 (PST)
Received: from mail-oa0-f45.google.com (mail-oa0-f45.google.com [209.85.219.45]) by ietfa.amsl.com (Postfix) with ESMTP id EBBA311E80BF for <ietf@ietf.org>; Thu, 24 Jan 2013 14:35:00 -0800 (PST)
Received: by mail-oa0-f45.google.com with SMTP id m1so1117693oag.4 for <ietf@ietf.org>; Thu, 24 Jan 2013 14:35:00 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type:content-transfer-encoding; bh=53cZECbtpUio77i9WAnswJY9DEB9hTZ+4485c72unf0=; b=kTzC5NEOANOlPIHXILmSVy+aTpRNEUOJXwPz9MqwXBx+TRCDTMVsMvFyIKsWRyJrDU iAPD/EOdxdErCgksX4pd8EQ1R71LquAbUN+V799Yfeb8j0x5LmYjBikxr+z05wQGjQz9 3KNuwp+kbBX/xG605/BYY9NoQWbUaqDUuyGDIV8UuWy+IGG424fe8tHUcsgthtfy8wMu b0cB+yE3Yva8LBxo+Wk6C/Exk2c4xSXDf5ESU3n2isBDWCSpDLXfZCjeZj8kUcfNC46H kUrJTRST40LGkBabZxW9hnZySUcoOd3g5EnlsmOAVJH7NNH48AgZ0TE1Z9ADGW21m5nN gDsg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type:content-transfer-encoding :x-gm-message-state; bh=53cZECbtpUio77i9WAnswJY9DEB9hTZ+4485c72unf0=; b=C2GE5DmEgXxyp3j1j9I/7DH23TUAw3mL6yFQnDTXhiO1FOqvwJSkk03rvURwC96xGL K3dHO3QkDz6eoH59TPBizzDfpUC2JnAWx8asL5tSgjUQjE91Pa9ql6xQZiW+eaofnmtJ 6lOoCCy7yAI4WObLRps/beeJazl379d3STkmeBh2uGBVueHKj53y0CyTBYnXfPgtltMf 08a6Z8gCTd80OsbmmJd5lm82PZozFCl7R5DILABJ7i0ueexq7KOUrRCgMf0TX2rsIsUI /biRigsu6h2tQJOdyHl7W1wgwCARTudxeWywoQoNzte/8QBNn7EaOWttQjsfAb4VjUNX gVpw==
MIME-Version: 1.0
X-Received: by 10.50.237.103 with SMTP id vb7mr2640601igc.29.1359066900197; Thu, 24 Jan 2013 14:35:00 -0800 (PST)
Received: by 10.64.34.163 with HTTP; Thu, 24 Jan 2013 14:35:00 -0800 (PST)
In-Reply-To: <50C06CE6.40909@ericsson.com>
References: <20121126212940.20378.58186.idtracker@ietfa.amsl.com> <50C06CE6.40909@ericsson.com>
Date: Thu, 24 Jan 2013 14:35:00 -0800
Message-ID: <CAH56bmAC9tgC3JQV1mAAuDipDbTkY7wx08xvZ7g6wfgKQYE=kQ@mail.gmail.com>
Subject: Re: Last Call: <draft-ietf-tcpm-initcwnd-06.txt> (Increasing TCP's Initial Window) to Experimental RFC
From: Matt Mathis <mattmathis@google.com>
To: Magnus Westerlund <magnus.westerlund@ericsson.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
X-Gm-Message-State: ALoCoQnIeiI6rmR7iO5niMaYj77apwcw0SB4Ja7nCy4C0WDB3kGDGhNZ7mLKFt/U22LN3UXDtyT/GR/faJkPV9Pf6sRlkn+qeHmFuaSg/DzUnsH3WOK2kQL7/3Uj/0aLREXiCMHdUstbYSh3Q2xLKnfH4b52EdfZ9hWZeztsm5TBBEQsktX7CSO5qEMRWRBNxowLaHFFKyn5
Cc: tcpm@ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 24 Jan 2013 22:35:02 -0000

Magnus,

In behalf of the draft-ietf-tcpm-initcwnd authors I publicly address
the comments in your IETF LC  review of draft-ietf-tcpm-initcwnd-06.

In regards to interactions between IW and real time traffic (your
points 1&2 below and echoed in Robert Spark's DISCUSS):

By design TCP creates queues to measure the bottleneck bandwidth.
Reducing the jitter for real time traffic is not a goal for TCP.
Although there are a number of TCP centric approaches for reducing
jitter, including reducing queue space, deploying AQM and limiting IW,
none are general nor work in all situations.   Furthermore if you
construct a scenario where one of these approaches seems to help, a
slight variation on that scenario will fail.  In the case of IW,
larger transactions will produce equally large queue occupancy later
on during slowstart or during bulk transfers.

This observation is borne out by the work of Ilpo Jarvinen et al.  See
http://www.tschofenig.priv.at/cc-workshop/irtf_iab-ccirtcpaper9.pdf
and the tcpm slides from IETF 84
http://www.ietf.org/proceedings/84/slides/slides-84-tcpm-11.

We have not attempted to measure IW10 impact on real time traffic,
however we have investigated over one year of historical performance
data for our Hangout/Talk application where we track both the startup
delay of an audio/video call as well as a jitter metric. Our data
shows no degradation in either metric as IW10 is deployed at Google
and elsewhere.  In fact, we see a steady improvement in our metrics,
even for the tail end of the users, which we attribute to generally
better connectivity.

As you noted, the only real solution to controlling jitter is to put
real time and throughput maximizing traffic into separate queues.
All other solutions have the property that they force implementers to
make tradeoffs between peak queuing delay and link utilization, and as
such are just workarounds that don't actually solve the root problem.
The real time community has finally come to understand this reality,
as reflected in the RMCAT charter.

These workarounds can be characterized as protecting RT traffic by
deliberately making TCP less aggressive than desired to quickly fill
the network.   Continuing to use these workarounds widens the gap
between actual application performance and raw network capacity.  This
fact is not lost on application developers and users who often observe
only slight application performance improvements after deploying
expensive faster networks, unless they take things under their own
control by opening multiple connections.  As we all know, this
approach undermines TCP's ability to control congestion.

Trying to make TCP compensate for the lack of segregated queueing (a
network problem) prevents correct solutions to problems caused by TCP
itself, namely it being too timid for most of todays networks.   Given
the wide discussion of bufferbloat and the need for traffic
segregation to support important RT applications, it is fairly likely
that the network problems will come to be solved and the solutions
widely deployed in the next few years.  A side benefit of these
changes to better support RT will be to further limit any possible
impact of IW10 on other Internet traffic.

In regards to your point 3, about client domains that experience
persistent problems with IW10.   We propose to add a sentence at the
end of section 12 (Usage and Deployment Recommendation): "Resolution
of these experiments and tighter specifications of the suggestions
here might be grounds for a future standards track document on the
same topic."

In regards to your point 4, clarify incentives in section 3 by
replacing end of the 2nd paragraph: "A larger initial window will
incentivize applications to use fewer concurrent TCP connections."
With: "If a larger initial window causes harm to any other flows then
local application tuning will reveal that fewer concurrent connections
yields better performance for some users.   Any content provider
deploying IW10 in conjunction with content distributed across multiple
domains is explicitly encouraged to perform measurement experiments to
detect such problems, and to consider reducing the number of
concurrent connections used to retrieve their content."

Other planned change to the draft as requested by IESG feedback:

Drop "Updates RFC 3390 and 5681" from the metadata.

This change answers the DISCUSSes posted by Brian Haberman and Ralph Droms.

I believe that together these chanes should address all of the IESG
DISCUSS items.

Thanks,
--MM--
The best way to predict the future is to create it.  - Alan Kay

Privacy matters!  We know from recent events that people are using our
services to speak in defiance of unjust governments.   We treat
privacy and security as matters of life and death, because for some
users, they are.


On Thu, Dec 6, 2012 at 2:01 AM, Magnus Westerlund
<magnus.westerlund@ericsson.com> wrote:
> Hi,
>
> I have reviewed draft-ietf-tcpm-initcwnd-06 and have some questions and
> comments.
>
> 1) First of all the experiments done appear to cover the impact on other
> applications, like measuring the RTT variations when using IW10 compared
> to IW3. If one is interested in the impact this proposal have on
> real-time traffic flows over a shared bottle-neck the variations in
> queue time at the bottleneck combined with that flows seen loss rates
> are the most important factors. As a sudden delay spike of sufficient
> magnitude will most likely result in a real-time media packet being
> late, i.e. late loss rather than being lost in the network there might
> be significant impact on such traffic from these IW10 packet bursts.
> Have I missed any material discussing this aspect?
>
> All the latency figures in the parts I was looking at was discussing
> cases when the object transfer takes longer time. But it appear obvious
> that even with a 100 ms increased one-way transfer time for a packet is
> the end of the initial window the total transfer goes faster compared to
> the delay caused by growing the window.
>
> 2) If I assume that most users are behind buffer-bloated links the
> introduction of IW10 on wide scale will additionally disrupt interactive
> applications and cause increased delay and possible late loss depending
> on application. Especially in combination with domain sharding. For
> example a Swedish newspaper's website front page results in that more
> than 40 TCP connections are opened in a current browser. If these all
> was using IW10, the amount of packets being sent initially will grow
> roughly from 40*3 =3D 120 to 40*10 =3D 400. There are some distribution o=
ver
> time but still this likely results in a larger delay spike.
>
> I don't quite know how I should consider this case. One stand point is
> that the interactive application is anyway buggered and IW10 effects are
> not making it significantly worse. The only remedy is queue separation
> so that what ever happens with the web-downloads doesn't affect the
> interactive traffic. Another is that it will make the existing situation
> worse and we should try to avoid making it worse.
>
> I think I am more in the first camp, but still the second one is
> worrying to me. But I dare to guess that the performance gains might be
> worth the issues, but without real progress on mitigation of the buffer
> bloat issues for interactive real-time traffic this will add
> significantly to the issues real-time has to face.
>
>
> 3) The documents talks in quite loose terms about what can be done to
> avoid to continue cause issues for destinations which has issues with
> IW10. However I think it is a bit unspecific here. I can see that a
> content deliverer can have lists for destination address blocks that
> they see issues with which configures the sending server side with a
> lower IW value. It also talks about the clients can configure to keep
> the window low initially to prevent an IW10 sender to clobber ones link
> if that is known. My question here is if the recommendation for auto
> detection and configuration can be made more explicit. Fortunately the
> issues with misconfiguration in this cases is not that serious. But
> otherwise there is commonly need to be quite careful with such auto
> configs that affects the behavior.
>
> 4) I am also worried that the document is a bit to positive in regards
> to that IW10 will reduce the domain sharding practice. I think the only
> thing that can do is likely a new HTTP transport strata that shows that
> significantly improved performance for multiple objects from the same
> domain over fewer transport flows. Maybe SPDY + IW10 can provide such
> incentive, but I don't think IW10 alone will do much.
>
> Cheers
>
> Magnus
>
> On 2012-11-26 22:29, The IESG wrote:
>>
>> The IESG has received a request from the TCP Maintenance and Minor
>> Extensions WG (tcpm) to consider the following document:
>> - 'Increasing TCP's Initial Window'
>>   <draft-ietf-tcpm-initcwnd-06.txt> as Experimental RFC
>>
>> The IESG plans to make a decision in the next few weeks, and solicits
>> final comments on this action. Please send substantive comments to the
>> ietf@ietf.org mailing lists by 2012-12-10. Exceptionally, comments may b=
e
>> sent to iesg@ietf.org instead. In either case, please retain the
>> beginning of the Subject line to allow automated sorting.
>>
>> Abstract
>>
>>
>>    This document proposes an experiment to increase the permitted TCP
>>    initial window (IW) from between 2 and 4 segments, as specified in
>>    RFC 3390, to 10 segments, with a fallback to the existing
>>    recommendation when performance issues are detected. It discusses the
>>    motivation behind the increase, the advantages and disadvantages of
>>    the higher initial window, and presents results from several large
>>    scale experiments showing that the higher initial window improves the
>>    overall performance of many web services without resulting in a
>>    congestion collapse. The document closes with a discussion of usage
>>    and deployment for further experimental purpose recommended by the
>>    IETF TCP Maintenance and Minor Extensions (TCPM) working group.
>>
>>
>>
>>
>> The file can be obtained via
>> http://datatracker.ietf.org/doc/draft-ietf-tcpm-initcwnd/
>>
>> IESG discussion can be tracked via
>> http://datatracker.ietf.org/doc/draft-ietf-tcpm-initcwnd/ballot/
>>
>>
>> No IPR declarations have been submitted directly on this I-D.
>>
>>
>>
>>
>
>
> --
>
> Magnus Westerlund
>
> ----------------------------------------------------------------------
> Multimedia Technologies, Ericsson Research EAB/TVM
> ----------------------------------------------------------------------
> Ericsson AB                | Phone  +46 10 7148287
> F=E4r=F6gatan 6                | Mobile +46 73 0949079
> SE-164 80 Stockholm, Sweden| mailto: magnus.westerlund@ericsson.com
> ----------------------------------------------------------------------
>

From mrex@sap.com  Thu Jan 24 15:05:50 2013
Return-Path: <mrex@sap.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7303C11E809A for <ietf@ietfa.amsl.com>; Thu, 24 Jan 2013 15:05:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.249
X-Spam-Level: 
X-Spam-Status: No, score=-10.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_HI=-8]
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 gQKY5HjlXKr4 for <ietf@ietfa.amsl.com>; Thu, 24 Jan 2013 15:05:49 -0800 (PST)
Received: from smtpde02.sap-ag.de (smtpde02.sap-ag.de [155.56.68.140]) by ietfa.amsl.com (Postfix) with ESMTP id 77C9411E8099 for <ietf@ietf.org>; Thu, 24 Jan 2013 15:05:49 -0800 (PST)
Received: from mail05.wdf.sap.corp by smtpde02.sap-ag.de (26) with ESMTP id r0ON5c8U001518 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 25 Jan 2013 00:05:38 +0100 (MET)
Subject: Re: Vestigial Features (was Re: CRLF (was: Re: A modest proposal))
In-Reply-To: <201301240341.r0O3fOui340901@shell01.TheWorld.com>
To: "Dale R. Worley" <worley@ariadne.com>
Date: Fri, 25 Jan 2013 00:05:36 +0100 (CET)
X-Mailer: ELM [version 2.4ME+ PL125 (25)]
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="US-ASCII"
Message-Id: <20130124230536.5D5C51A487@ld9781.wdf.sap.corp>
From: mrex@sap.com (Martin Rex)
X-SAP: out
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: mrex@sap.com
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 24 Jan 2013 23:05:50 -0000

Dale R. Worley wrote:
> > From: Carsten Bormann <cabo@tzi.org>
> > 
> > I think in protocol evolution (as well as computer system evolution
> > in general) we are missing triggers to get rid of vestigial
> > features.
> 
> That's quite true.  Let us start by rationalizing the spelling and
> punctuation of written English (which is the coding system for *this
> entire discussion*).  Once we've cleaned up that idiocy, we can start
> in on SIP.

You mean some along the line of:

  http://everything2.com/user/m_turner/writeups/A+Plan+for+the+Improvement+of+English+Spelling

I don't think the IETF is the right forum for such a project,
and my personal feeling is that it is infeasible anyway.


While it would have probably much easier to teach everyone english
(and use ASCII), the opposite approach was taken and every piece
of technology was spoiled with I18N, L10N and Unicode, reinforcing
the communication barriers that exist throughout this world,
among machines/devices and among human beings.


-Martin

From fgont@si6networks.com  Thu Jan 24 16:13:17 2013
Return-Path: <fgont@si6networks.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 470A621F850C; Thu, 24 Jan 2013 16:13:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 MumQoqbCd5nj; Thu, 24 Jan 2013 16:13:16 -0800 (PST)
Received: from web01.jbserver.net (web01.jbserver.net [93.186.182.34]) by ietfa.amsl.com (Postfix) with ESMTP id 84A2C21F84F6; Thu, 24 Jan 2013 16:13:04 -0800 (PST)
Received: from [190.174.155.31] (helo=[192.168.1.43]) by web01.jbserver.net with esmtpsa (TLSv1:DHE-RSA-CAMELLIA256-SHA:256) (Exim 4.80.1) (envelope-from <fgont@si6networks.com>) id 1TyWuD-0004gT-NB; Fri, 25 Jan 2013 01:12:30 +0100
Message-ID: <5101A671.4090906@si6networks.com>
Date: Thu, 24 Jan 2013 18:24:01 -0300
From: Fernando Gont <fgont@si6networks.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130106 Thunderbird/17.0.2
MIME-Version: 1.0
To: Joe Touch <touch@isi.edu>
Subject: Re: TSV-DIR review of draft-ietf-6man-ipv6-atomic-fragments-03
References: <CAP8yD=tF4_2RpNZNAHRR65HTZGwSPE+Pjx8-a8H_vQHNjqfEoA@mail.gmail.com> <51018CE9.3030700@isi.edu>
In-Reply-To: <51018CE9.3030700@isi.edu>
X-Enigmail-Version: 1.4.6
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: Transport Directorate <tsv-dir@ietf.org>, 6man@ietf.org, Transport Area <tsv-area@ietf.org>, IETF Discuss <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 25 Jan 2013 00:13:17 -0000

Joe,

On 01/24/2013 04:35 PM, Joe Touch wrote:
> FWIW, this document includes text that somewhat defeats the previous
> recommendations of TCPM regarding RFC5927.
> 
> RFC5927 includes specific text indicating that the techniques described
> are being documented, but that the TCP standard was NOT being changed to
> include those ICMP validation checks.
> 
> This document states that:
> 
>       Many implementations fail to perform validation checks on the
>       received ICMPv6 error messages, as recommended in Section 5.2 of
>       [RFC4443] and [RFC5927].

Are we fine if I remove "and [RFC5927]"? -- Because RFC4443 does
recommend that ICMPv6 messages be validated.


> I.e., the second RFC does NOT recommend changes; it documents them. This
> document should be VERY carefully reviewed to ensure that it does not
> undo the previous TCPM concerns about these techniques.

We can remove "and [RFC5927]" or change it to "...Section 5.2 of
[RFC4443] and documented in [RFC5927]"

Thoughts?

Thanks,
-- 
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492





From touch@isi.edu  Thu Jan 24 16:19:59 2013
Return-Path: <touch@isi.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 223CE11E809B; Thu, 24 Jan 2013 16:19:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 LRlgpr+bZha3; Thu, 24 Jan 2013 16:19:58 -0800 (PST)
Received: from vapor.isi.edu (vapor.isi.edu [128.9.64.64]) by ietfa.amsl.com (Postfix) with ESMTP id 3659C11E8099; Thu, 24 Jan 2013 16:19:58 -0800 (PST)
Received: from [128.9.160.166] (abc.isi.edu [128.9.160.166]) (authenticated bits=0) by vapor.isi.edu (8.13.8/8.13.8) with ESMTP id r0P0JW5Q001300 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 24 Jan 2013 16:19:32 -0800 (PST)
Message-ID: <5101CF94.4070208@isi.edu>
Date: Thu, 24 Jan 2013 16:19:32 -0800
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130107 Thunderbird/17.0.2
MIME-Version: 1.0
To: Fernando Gont <fgont@si6networks.com>
Subject: Re: TSV-DIR review of draft-ietf-6man-ipv6-atomic-fragments-03
References: <CAP8yD=tF4_2RpNZNAHRR65HTZGwSPE+Pjx8-a8H_vQHNjqfEoA@mail.gmail.com> <51018CE9.3030700@isi.edu> <5101A671.4090906@si6networks.com>
In-Reply-To: <5101A671.4090906@si6networks.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: Transport Directorate <tsv-dir@ietf.org>, 6man@ietf.org, Transport Area <tsv-area@ietf.org>, IETF Discuss <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 25 Jan 2013 00:19:59 -0000

On 1/24/2013 1:24 PM, Fernando Gont wrote:
> Joe,
>
> On 01/24/2013 04:35 PM, Joe Touch wrote:
>> FWIW, this document includes text that somewhat defeats the previous
>> recommendations of TCPM regarding RFC5927.
>>
>> RFC5927 includes specific text indicating that the techniques described
>> are being documented, but that the TCP standard was NOT being changed to
>> include those ICMP validation checks.
>>
>> This document states that:
>>
>>        Many implementations fail to perform validation checks on the
>>        received ICMPv6 error messages, as recommended in Section 5.2 of
>>        [RFC4443] and [RFC5927].
>
> Are we fine if I remove "and [RFC5927]"? -- Because RFC4443 does
> recommend that ICMPv6 messages be validated.

Sure.

>> I.e., the second RFC does NOT recommend changes; it documents them. This
>> document should be VERY carefully reviewed to ensure that it does not
>> undo the previous TCPM concerns about these techniques.
>
> We can remove "and [RFC5927]" or change it to "...Section 5.2 of
> [RFC4443] and documented in [RFC5927]"

That might do it, but it would be useful if another pair of eyes would 
check.

Joe

>
> Thoughts?
>
> Thanks,
>

From allison.mankin@gmail.com  Thu Jan 24 17:57:12 2013
Return-Path: <allison.mankin@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 07B3721F841E; Thu, 24 Jan 2013 17:57:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.299
X-Spam-Level: 
X-Spam-Status: No, score=-2.299 tagged_above=-999 required=5 tests=[AWL=0.300,  BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
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 IBFDYnzhLFxn; Thu, 24 Jan 2013 17:57:11 -0800 (PST)
Received: from mail-we0-x22f.google.com (mail-we0-x22f.google.com [IPv6:2a00:1450:400c:c03::22f]) by ietfa.amsl.com (Postfix) with ESMTP id 8CDCE21F841C; Thu, 24 Jan 2013 17:57:10 -0800 (PST)
Received: by mail-we0-f175.google.com with SMTP id x8so280795wey.20 for <multiple recipients>; Thu, 24 Jan 2013 17:57:09 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=nlQ4Qmr1wu1D9OA0xAn+Q6qhD2azDPtzYf5DoGo40KU=; b=YhKuEwnpWBWEMZjfp1RuacYlM4hA2rjMO8rJGc4UfK61UKtUehV8pBpnXb+LSWeP7a XK31/hLrakftde7TGSYEEXm2WQD0QPi13DaBlOaEEYvI46Funj69JZA2cpRj54LcMXEl IR+HAF/JBnPZQtKHhHqi+lEwhE0IL8bhoZLKUl+BU8T+Vl1ziXxQjFIgwF2cSS3jzVP4 LUlQ7b9xG30ageKdjPSrHVy3tSmPofCM3E3iRSyj8Fl7LABzJ4WjDaIXn3DOL64ji9pD al13sRQmTLCXnSXQfnPPw5u8CymCD74eLPBU6n0QaWm3jSyD7Ecqp7FIZzsSr1cs9ioK 56Xg==
MIME-Version: 1.0
X-Received: by 10.180.85.226 with SMTP id k2mr6022072wiz.34.1359079029735; Thu, 24 Jan 2013 17:57:09 -0800 (PST)
Received: by 10.217.80.2 with HTTP; Thu, 24 Jan 2013 17:57:09 -0800 (PST)
Received: by 10.217.80.2 with HTTP; Thu, 24 Jan 2013 17:57:09 -0800 (PST)
In-Reply-To: <5101CF94.4070208@isi.edu>
References: <CAP8yD=tF4_2RpNZNAHRR65HTZGwSPE+Pjx8-a8H_vQHNjqfEoA@mail.gmail.com> <51018CE9.3030700@isi.edu> <5101A671.4090906@si6networks.com> <5101CF94.4070208@isi.edu>
Date: Thu, 24 Jan 2013 20:57:09 -0500
Message-ID: <CAP8yD=vOrtS6EeFyFn8iJ2jiBVTTtBB4O=8vjSNxcUOaAEhScQ@mail.gmail.com>
Subject: Re: TSV-DIR review of draft-ietf-6man-ipv6-atomic-fragments-03
From: Allison Mankin <allison.mankin@gmail.com>
To: Joe Touch <touch@isi.edu>
Content-Type: multipart/alternative; boundary=f46d04428230ca001204d4133e83
Cc: 6man@ietf.org, Transport Area <tsv-area@ietf.org>, IETF Discuss <ietf@ietf.org>, Transport Directorate <tsv-dir@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 25 Jan 2013 01:57:12 -0000

--f46d04428230ca001204d4133e83
Content-Type: text/plain; charset=ISO-8859-1

Joe and Fernando,

I just looked at how RFC 5297 is handled in the draft, to be that other
pair of eyes.

The first fix is right, to remove reference to RFC 5297 from that sentence
entirely.

Allison

On Jan 24, 2013 7:19 PM, "Joe Touch" <touch@isi.edu> wrote:
>
>
>
> On 1/24/2013 1:24 PM, Fernando Gont wrote:
>>
>> Joe,
>>
>> On 01/24/2013 04:35 PM, Joe Touch wrote:
>>>
>>> FWIW, this document includes text that somewhat defeats the previous
>>> recommendations of TCPM regarding RFC5927.
>>>
>>> RFC5927 includes specific text indicating that the techniques described
>>> are being documented, but that the TCP standard was NOT being changed to
>>> include those ICMP validation checks.
>>>
>>> This document states that:
>>>
>>>        Many implementations fail to perform validation checks on the
>>>        received ICMPv6 error messages, as recommended in Section 5.2 of
>>>        [RFC4443] and [RFC5927].
>>
>>
>> Are we fine if I remove "and [RFC5927]"? -- Because RFC4443 does
>> recommend that ICMPv6 messages be validated.
>
>
> Sure.
>
>
>>> I.e., the second RFC does NOT recommend changes; it documents them. This
>>> document should be VERY carefully reviewed to ensure that it does not
>>> undo the previous TCPM concerns about these techniques.
>>
>>
>> We can remove "and [RFC5927]" or change it to "...Section 5.2 of
>> [RFC4443] and documented in [RFC5927]"
>
>
> That might do it, but it would be useful if another pair of eyes would
check.
>
> Joe
>
>>
>> Thoughts?
>>
>> Thanks,
>>

--f46d04428230ca001204d4133e83
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<p>Joe and Fernando,</p>
<p>I just looked at how RFC 5297 is handled in the draft, to be that other =
pair of eyes.=A0=A0 </p>
<p>The first fix is right, to remove reference to RFC 5297 from that senten=
ce entirely. </p>
<p>Allison</p>
<p>On Jan 24, 2013 7:19 PM, &quot;Joe Touch&quot; &lt;<a href=3D"mailto:tou=
ch@isi.edu">touch@isi.edu</a>&gt; wrote:<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; On 1/24/2013 1:24 PM, Fernando Gont wrote:<br>
&gt;&gt;<br>
&gt;&gt; Joe,<br>
&gt;&gt;<br>
&gt;&gt; On 01/24/2013 04:35 PM, Joe Touch wrote:<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; FWIW, this document includes text that somewhat defeats the pr=
evious<br>
&gt;&gt;&gt; recommendations of TCPM regarding RFC5927.<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; RFC5927 includes specific text indicating that the techniques =
described<br>
&gt;&gt;&gt; are being documented, but that the TCP standard was NOT being =
changed to<br>
&gt;&gt;&gt; include those ICMP validation checks.<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; This document states that:<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; =A0 =A0 =A0 =A0Many implementations fail to perform validation=
 checks on the<br>
&gt;&gt;&gt; =A0 =A0 =A0 =A0received ICMPv6 error messages, as recommended =
in Section 5.2 of<br>
&gt;&gt;&gt; =A0 =A0 =A0 =A0[RFC4443] and [RFC5927].<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt; Are we fine if I remove &quot;and [RFC5927]&quot;? -- Because RFC4=
443 does<br>
&gt;&gt; recommend that ICMPv6 messages be validated.<br>
&gt;<br>
&gt;<br>
&gt; Sure.<br>
&gt;<br>
&gt;<br>
&gt;&gt;&gt; I.e., the second RFC does NOT recommend changes; it documents =
them. This<br>
&gt;&gt;&gt; document should be VERY carefully reviewed to ensure that it d=
oes not<br>
&gt;&gt;&gt; undo the previous TCPM concerns about these techniques.<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt; We can remove &quot;and [RFC5927]&quot; or change it to &quot;...S=
ection 5.2 of<br>
&gt;&gt; [RFC4443] and documented in [RFC5927]&quot;<br>
&gt;<br>
&gt;<br>
&gt; That might do it, but it would be useful if another pair of eyes would=
 check.<br>
&gt;<br>
&gt; Joe<br>
&gt;<br>
&gt;&gt;<br>
&gt;&gt; Thoughts?<br>
&gt;&gt;<br>
&gt;&gt; Thanks,<br>
&gt;&gt;<br>
</p>

--f46d04428230ca001204d4133e83--

From touch@isi.edu  Thu Jan 24 17:59:39 2013
Return-Path: <touch@isi.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 29FCC11E80DC; Thu, 24 Jan 2013 17:59:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.599
X-Spam-Level: 
X-Spam-Status: No, score=-104.599 tagged_above=-999 required=5 tests=[AWL=2.000, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 0lGKiHHsV0Hu; Thu, 24 Jan 2013 17:59:38 -0800 (PST)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by ietfa.amsl.com (Postfix) with ESMTP id 9B64611E80D9; Thu, 24 Jan 2013 17:59:38 -0800 (PST)
Received: from [128.9.184.216] ([128.9.184.216]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id r0P1x0pu026227 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 24 Jan 2013 17:59:02 -0800 (PST)
Message-ID: <5101E6E4.8080407@isi.edu>
Date: Thu, 24 Jan 2013 17:59:00 -0800
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:17.0) Gecko/20130107 Thunderbird/17.0.2
MIME-Version: 1.0
To: Allison Mankin <allison.mankin@gmail.com>
Subject: Re: TSV-DIR review of draft-ietf-6man-ipv6-atomic-fragments-03
References: <CAP8yD=tF4_2RpNZNAHRR65HTZGwSPE+Pjx8-a8H_vQHNjqfEoA@mail.gmail.com> <51018CE9.3030700@isi.edu> <5101A671.4090906@si6networks.com> <5101CF94.4070208@isi.edu> <CAP8yD=vOrtS6EeFyFn8iJ2jiBVTTtBB4O=8vjSNxcUOaAEhScQ@mail.gmail.com>
In-Reply-To: <CAP8yD=vOrtS6EeFyFn8iJ2jiBVTTtBB4O=8vjSNxcUOaAEhScQ@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: 6man@ietf.org, Transport Area <tsv-area@ietf.org>, IETF Discuss <ietf@ietf.org>, Transport Directorate <tsv-dir@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 25 Jan 2013 01:59:39 -0000

Thanks - I wasn't positive about the second one. Glad to have it 
resolved quickly.

Joe

On 1/24/2013 5:57 PM, Allison Mankin wrote:
> Joe and Fernando,
>
> I just looked at how RFC 5297 is handled in the draft, to be that other
> pair of eyes.
>
> The first fix is right, to remove reference to RFC 5297 from that
> sentence entirely.
>
> Allison
>
> On Jan 24, 2013 7:19 PM, "Joe Touch" <touch@isi.edu
> <mailto:touch@isi.edu>> wrote:
>  >
>  >
>  >
>  > On 1/24/2013 1:24 PM, Fernando Gont wrote:
>  >>
>  >> Joe,
>  >>
>  >> On 01/24/2013 04:35 PM, Joe Touch wrote:
>  >>>
>  >>> FWIW, this document includes text that somewhat defeats the previous
>  >>> recommendations of TCPM regarding RFC5927.
>  >>>
>  >>> RFC5927 includes specific text indicating that the techniques described
>  >>> are being documented, but that the TCP standard was NOT being
> changed to
>  >>> include those ICMP validation checks.
>  >>>
>  >>> This document states that:
>  >>>
>  >>>        Many implementations fail to perform validation checks on the
>  >>>        received ICMPv6 error messages, as recommended in Section 5.2 of
>  >>>        [RFC4443] and [RFC5927].
>  >>
>  >>
>  >> Are we fine if I remove "and [RFC5927]"? -- Because RFC4443 does
>  >> recommend that ICMPv6 messages be validated.
>  >
>  >
>  > Sure.
>  >
>  >
>  >>> I.e., the second RFC does NOT recommend changes; it documents them.
> This
>  >>> document should be VERY carefully reviewed to ensure that it does not
>  >>> undo the previous TCPM concerns about these techniques.
>  >>
>  >>
>  >> We can remove "and [RFC5927]" or change it to "...Section 5.2 of
>  >> [RFC4443] and documented in [RFC5927]"
>  >
>  >
>  > That might do it, but it would be useful if another pair of eyes
> would check.
>  >
>  > Joe
>  >
>  >>
>  >> Thoughts?
>  >>
>  >> Thanks,
>  >>
>

From narten@us.ibm.com  Thu Jan 24 21:53:11 2013
Return-Path: <narten@us.ibm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C93C621F8570 for <ietf@ietfa.amsl.com>; Thu, 24 Jan 2013 21:53:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.599
X-Spam-Level: 
X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
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 kfpAluOT97Vf for <ietf@ietfa.amsl.com>; Thu, 24 Jan 2013 21:53:10 -0800 (PST)
Received: from e9.ny.us.ibm.com (e9.ny.us.ibm.com [32.97.182.139]) by ietfa.amsl.com (Postfix) with ESMTP id 35E2721F848B for <ietf@ietf.org>; Thu, 24 Jan 2013 21:53:09 -0800 (PST)
Received: from /spool/local by e9.ny.us.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for <ietf@ietf.org> from <narten@us.ibm.com>; Fri, 25 Jan 2013 00:53:08 -0500
Received: from d01dlp02.pok.ibm.com (9.56.250.167) by e9.ny.us.ibm.com (192.168.1.109) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted;  Fri, 25 Jan 2013 00:53:06 -0500
Received: from d01relay02.pok.ibm.com (d01relay02.pok.ibm.com [9.56.227.234]) by d01dlp02.pok.ibm.com (Postfix) with ESMTP id 425906E803A for <ietf@ietf.org>; Fri, 25 Jan 2013 00:53:04 -0500 (EST)
Received: from d01av01.pok.ibm.com (d01av01.pok.ibm.com [9.56.224.215]) by d01relay02.pok.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id r0P5r5dx314038 for <ietf@ietf.org>; Fri, 25 Jan 2013 00:53:05 -0500
Received: from d01av01.pok.ibm.com (loopback [127.0.0.1]) by d01av01.pok.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP id r0P5r5Lu008317 for <ietf@ietf.org>; Fri, 25 Jan 2013 00:53:05 -0500
Received: from rotala.raleigh.ibm.com (rotala.raleigh.ibm.com [9.44.115.148]) by d01av01.pok.ibm.com (8.14.4/8.13.1/NCO v10.0 AVin) with ESMTP id r0P5r4GT008302 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Fri, 25 Jan 2013 00:53:04 -0500
Received: from rotala.raleigh.ibm.com (localhost.localdomain [127.0.0.1]) by rotala.raleigh.ibm.com (8.14.5/8.12.5) with ESMTP id r0P5r3Jw013516 for <ietf@ietf.org>; Fri, 25 Jan 2013 00:53:04 -0500
Received: (from narten@localhost) by rotala.raleigh.ibm.com (8.14.5/8.14.5/Submit) id r0P5r32g013473 for ietf@ietf.org; Fri, 25 Jan 2013 00:53:03 -0500
From: Thomas Narten <narten@us.ibm.com>
Message-Id: <201301250553.r0P5r32g013473@rotala.raleigh.ibm.com>
Date: Fri, 25 Jan 2013 00:53:03 -0500
To: ietf@ietf.org
Subject: Weekly posting summary for ietf@ietf.org
User-Agent: Heirloom mailx 12.5 7/5/10
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Content-Scanned: Fidelis XPS MAILER
x-cbid: 13012505-7182-0000-0000-000004B29E18
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 25 Jan 2013 05:53:11 -0000

Total of 97 messages in the last 7 days.
 
script run at: Fri Jan 25 00:53:03 EST 2013
 
    Messages   |      Bytes        | Who
--------+------+--------+----------+------------------------
  1.03% |    1 | 25.97% |   295206 | bclaise@cisco.com
  5.15% |    5 |  4.19% |    47613 | stephen.farrell@cs.tcd.ie
  2.06% |    2 |  6.06% |    68919 | rjsparks@nostrum.com
  5.15% |    5 |  2.77% |    31495 | touch@isi.edu
  4.12% |    4 |  3.39% |    38512 | john-ietf@jck.com
  4.12% |    4 |  2.34% |    26567 | abdussalambaryun@gmail.com
  4.12% |    4 |  2.31% |    26302 | wjordan129@gmail.com
  4.12% |    4 |  2.22% |    25235 | cabo@tzi.org
  4.12% |    4 |  2.14% |    24365 | melinda.shore@gmail.com
  2.06% |    2 |  4.15% |    47135 | jeff.hodges@kingsmountain.com
  3.09% |    3 |  2.57% |    29240 | narten@us.ibm.com
  3.09% |    3 |  1.93% |    21972 | jeanjour@comcast.net
  3.09% |    3 |  1.70% |    19320 | joelja@bogus.com
  2.06% |    2 |  2.68% |    30464 | allison.mankin@gmail.com
  3.09% |    3 |  1.46% |    16546 | worley@ariadne.com
  1.03% |    1 |  2.75% |    31261 | adrian@olddog.co.uk
  2.06% |    2 |  1.66% |    18818 | peter@akayla.com
  2.06% |    2 |  1.47% |    16758 | ietf@shaftek.org
  2.06% |    2 |  1.41% |    16079 | daedulus@btconnect.com
  2.06% |    2 |  1.32% |    15055 | fgont@si6networks.com
  2.06% |    2 |  1.28% |    14544 | dean.willis@softarmor.com
  2.06% |    2 |  1.12% |    12674 | dwm@xpasc.com
  2.06% |    2 |  1.11% |    12614 | hannes.tschofenig@gmx.net
  2.06% |    2 |  1.02% |    11578 | johnl@taugh.com
  2.06% |    2 |  0.96% |    10862 | dot@dotat.at
  1.03% |    1 |  1.51% |    17218 | mattmathis@google.com
  1.03% |    1 |  0.96% |    10952 | elwynd@dial.pipex.com
  1.03% |    1 |  0.95% |    10828 | ron.even.tlv@gmail.com
  1.03% |    1 |  0.92% |    10419 | john@jlc.net
  1.03% |    1 |  0.88% |    10016 | akatlas@gmail.com
  1.03% |    1 |  0.87% |     9939 | hsantos@isdg.net
  1.03% |    1 |  0.82% |     9346 | jgunn6@csc.com
  1.03% |    1 |  0.81% |     9210 | agmalis@gmail.com
  1.03% |    1 |  0.78% |     8849 | dromasca@avaya.com
  1.03% |    1 |  0.78% |     8814 | cpignata@cisco.com
  1.03% |    1 |  0.69% |     7891 | lars@netapp.com
  1.03% |    1 |  0.69% |     7799 | randy_presuhn@mindspring.com
  1.03% |    1 |  0.67% |     7621 | dave@cridland.net
  1.03% |    1 |  0.66% |     7494 | chair@ietf.org
  1.03% |    1 |  0.66% |     7468 | ned+ietf@mauve.mrochek.com
  1.03% |    1 |  0.65% |     7440 | petithug@acm.org
  1.03% |    1 |  0.58% |     6638 | presnick@qti.qualcomm.com
  1.03% |    1 |  0.57% |     6424 | smb@cs.columbia.edu
  1.03% |    1 |  0.56% |     6352 | fernando@gont.com.ar
  1.03% |    1 |  0.56% |     6330 | huubatwork@gmail.com
  1.03% |    1 |  0.55% |     6270 | derhoermi@gmx.net
  1.03% |    1 |  0.54% |     6122 | cntreras@gmail.com
  1.03% |    1 |  0.53% |     5993 | brian.e.carpenter@gmail.com
  1.03% |    1 |  0.50% |     5641 | warren@kumari.net
  1.03% |    1 |  0.49% |     5612 | john@jck.com
  1.03% |    1 |  0.48% |     5505 | mrex@sap.com
  1.03% |    1 |  0.47% |     5304 | mcr@sandelman.ca
  1.03% |    1 |  0.46% |     5220 | iad@ietf.org
  1.03% |    1 |  0.41% |     4702 | bygg@cafax.se
--------+------+--------+----------+------------------------
100.00% |   97 |100.00% |  1136551 | Total


From daedulus@btconnect.com  Fri Jan 25 02:05:31 2013
Return-Path: <daedulus@btconnect.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B9EB321F8795 for <ietf@ietfa.amsl.com>; Fri, 25 Jan 2013 02:05:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.349
X-Spam-Level: 
X-Spam-Status: No, score=-4.349 tagged_above=-999 required=5 tests=[AWL=-0.750, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 07OT2jc8U38b for <ietf@ietfa.amsl.com>; Fri, 25 Jan 2013 02:05:30 -0800 (PST)
Received: from va3outboundpool.messaging.microsoft.com (va3ehsobe005.messaging.microsoft.com [216.32.180.31]) by ietfa.amsl.com (Postfix) with ESMTP id A1C1021F8782 for <ietf@ietf.org>; Fri, 25 Jan 2013 02:05:30 -0800 (PST)
Received: from mail257-va3-R.bigfish.com (10.7.14.249) by VA3EHSOBE011.bigfish.com (10.7.40.61) with Microsoft SMTP Server id 14.1.225.23; Fri, 25 Jan 2013 10:05:29 +0000
Received: from mail257-va3 (localhost [127.0.0.1])	by mail257-va3-R.bigfish.com (Postfix) with ESMTP id 985751A00202; Fri, 25 Jan 2013 10:05:29 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.249.85; KIP:(null); UIP:(null); IPV:NLI; H:AMSPRD0710HT002.eurprd07.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: -20
X-BigFish: PS-20(z10d0kz9371Ie6eL542I1432Izz1ee6h1de0h1202h1e76h1d1ah1d2ahzz1033IL8275bh8275dhz2dh2a8h5a9h668h839h947hd24hf0ah1177h1179h1288h12a5h12a9h12bdh137ah139eh13b6h1441h1504h1537h162dh1631h1758h17f1h184fh1898h18e1h304l1155h)
Received: from mail257-va3 (localhost.localdomain [127.0.0.1]) by mail257-va3 (MessageSwitch) id 1359108327278312_24170; Fri, 25 Jan 2013 10:05:27 +0000 (UTC)
Received: from VA3EHSMHS026.bigfish.com (unknown [10.7.14.236])	by mail257-va3.bigfish.com (Postfix) with ESMTP id 3DA9D13C0055; Fri, 25 Jan 2013 10:05:27 +0000 (UTC)
Received: from AMSPRD0710HT002.eurprd07.prod.outlook.com (157.56.249.85) by VA3EHSMHS026.bigfish.com (10.7.99.36) with Microsoft SMTP Server (TLS) id 14.1.225.23; Fri, 25 Jan 2013 10:05:25 +0000
Received: from AMXPRD0111HT002.eurprd01.prod.exchangelabs.com (157.56.250.117) by pod51017.outlook.com (10.255.160.165) with Microsoft SMTP Server (TLS) id 14.16.257.4; Fri, 25 Jan 2013 10:05:16 +0000
Message-ID: <00b801cdfae3$1918fa80$4001a8c0@gateway.2wire.net>
From: t.p. <daedulus@btconnect.com>
To: Joe Touch <touch@isi.edu>, Thomas Narten <narten@us.ibm.com>
References: <017001cdf017$c394df00$4abe9d00$@olddog.co.uk><50FEC0B8.8060905@isi.edu> <201301222131.r0MLVK8C015116@cichlid.raleigh.ibm.com>
Subject: Re: FW: Last Call: <draft-farrell-ft-03.txt> (A Fast-Track way to RFCwith Running Code) to Experimental RFC
Date: Fri, 25 Jan 2013 10:02:27 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Originating-IP: [157.56.250.117]
X-OriginatorOrg: btconnect.com
Cc: adrian@olddog.co.uk, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 25 Jan 2013 10:05:31 -0000

----- Original Message -----
From: "Thomas Narten" <narten@us.ibm.com>
To: "Joe Touch" <touch@isi.edu>
Cc: <adrian@olddog.co.uk>; <ietf@ietf.org>
Sent: Tuesday, January 22, 2013 9:31 PM
> FWIW, I share Joe's concerns. And Stephen's responses don't really
> change my mind.
>
> This document seems to have a bit of missing the forest for the
> trees. In the overall scheme of things, I don't believe the draft will
> materially help, and is at best a distraction from dealing with
> meaningful problems.

I agree.  This proposal asks the ADs and WG Chairs to do more work and I
perceive lack of resouces in that area to be the single biggest reason
for I-Ds to fail to progress as fast as they might.  Putting more load
on the critical path can only make things worse, for the work as a
whole.  Some favoured I-Ds will progress faster but overall, RFCs will
take longer to appear.

In this vein, I have commented before how progress in the IETF tends to
take place in three bursts, in the course of each year, and that if only
we had a way of bringing the three pauses to life, then progress would
be much improved.  Quality would almost certainly also improve, since
data would not get lost or forgotten in the pauses.  This month, most WG
mailing lists seem to be in a mega-pause (I keep checking the archives
to see if I have been accidentally unsubscribed!): that is the real
problem.

Tom Petch

> The crux of the issue is that any attempt at "fast tracking" is
> fundamentally about short-circuiting some aspect of our review
> processes. We should only do that very carefully. In almost all cases,
> individual judgement is needed as to when it is appropriate to do
> that. ADs/WG chairs already have some flexibility here. e.g., a WG can
> skip WG LC if they think its not needed.  And nothing stops an AD from
> going to WGLC before doing a careful review. But I'd rather that be
> done because the case at hand justifies such an optimization, not
> because there is some "running code" checkmark that allows a special
> case to be fast tracked..
>
> This document risks substituting process for judgement. I'd rather see
> more of the latter and less of the former.
>
> Some specifics from the doc:
>
> >    In summary this experiment collapses three stages of the
publication
> >    process to run concurrently: working group last call, AD review,
and
> >    IETF last call.  Additionally, the experiment will only require
>
> IMO, it is almost never appropriate to collapse WG LC and IETF LC. In
> cases where it is appropriate to do so, there presumably isn't a need
> for a WG LC to start with.  And an AD has always been able to start an
> IETF LC without doing a detailed review. The point, is judgement is
> needed, and all such cases are best handled on a case-by-case
> basis.
>
> Surely, we don't need a document to justify doing this in those cases
> where it makes sense...
>
> >    IETF last call.  Additionally, the experiment will only require
> >    issues raised during these three stages to be addressed if they
meet
> >    the IESG's Discuss criteria.  The former is not formally a
> >    process
>
> and later:
>
> >    4.  Only comments that would be "DISCUSS-worthy" according to the
> >        IESG Discuss Criteria [DCRIT] need be handled during last
call.
> >        Other comments can be handled or not, at the authors/editors
> >        discretion.
>
> The above can easily become a way to dismiss legitimate review
> comments. No doubt, when a AD or reviewer suggests "this needs
> fixing", the proponents will hold up this document and say "you
> shouldn't do this, per the RFC -- you're violating the spirit of this
> document, only really really critical stuff needs to get addressed..."
> No thanks. That is not what the IETF is about.
>
> If it is really urgent to get a document done, it is far better to
> take steps to make sure the editors are engaged and responsive. That
> is more likely the real issue!!!
>
> >    It is understood that the savings in time for the end-to-end
delivery
> >    of a proposed standard or experimental RFC may be modest,
however,
> >    the modifications to normal IETF process will also serve as an
> >    indication of the importance that the IETF places in running
code.
>
> Running code is valuable. Always has been, always will be. But we need
> to resist the temptation of making "running code" more equal than
> other criteria or putting it on a pedestal as some sort of holy
> grail. Running code by itself is just a sound bite. The importance of
> running code is what it tells us about a protocol specification. Just
> the mere fact that there is running code doesn't mean there is
> anything particularly enlightening to learn from an
> implementation. For example, "running code" of a router function in
> software doesn't necessarily say anything as to whether the code can
> be implemented efficiently using ASICs, which may be the real
> requirement.
>
> >
> >    5.  The responsible AD for the WG concerned makes the decision as
to
> >        whether changes are required as a result of review comments,
and
> >        determines whether or not those have been completed.  If
> >        significant change or extended discussion is required, or if
> >        changes are not complete within two weeks after the end of
fast-
> >        track last call, then the draft is returned to the WG by the
> >        responsible AD and the document is withdrawn from the
experiment.
>
> The two week figure is too stringent. The above is too prescriptive to
> be practical. For starters, how will the IESG telechat align with the
> ending of LC? Or what if an IESG member issues a defer (or will those
> be disallowed?).
>
> Section 4 has a bit too much detail and process in it. I'm sure it has
> both too much and too little actually. I.e., it probably misses some
> corner cases, and then what do you do given how prescriptive the rest
> of the section is?
>
> But overall, I see this document at best as a no-op. However, I fear
> that it can be used to short-circuit our review processes in a way
> that doesn't help the IETF and that won't really speed things up
> enough to justify the downsides.
>
> Thomas
>
>



From adrian@olddog.co.uk  Fri Jan 25 02:25:09 2013
Return-Path: <adrian@olddog.co.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F209221F8830 for <ietf@ietfa.amsl.com>; Fri, 25 Jan 2013 02:25:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.627
X-Spam-Level: 
X-Spam-Status: No, score=-2.627 tagged_above=-999 required=5 tests=[AWL=-0.028, BAYES_00=-2.599]
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 kWh17JNyfJAM for <ietf@ietfa.amsl.com>; Fri, 25 Jan 2013 02:25:08 -0800 (PST)
Received: from asmtp1.iomartmail.com (asmtp1.iomartmail.com [62.128.201.248]) by ietfa.amsl.com (Postfix) with ESMTP id EFE9721F87FB for <ietf@ietf.org>; Fri, 25 Jan 2013 02:25:07 -0800 (PST)
Received: from asmtp1.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp1.iomartmail.com (8.13.8/8.13.8) with ESMTP id r0PAP6Ia001987;  Fri, 25 Jan 2013 10:25:06 GMT
Received: from 950129200 (089144192091.atnat0001.highway.a1.net [89.144.192.91]) (authenticated bits=0) by asmtp1.iomartmail.com (8.13.8/8.13.8) with ESMTP id r0PAP3Bw001952 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 25 Jan 2013 10:25:05 GMT
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "'John C Klensin'" <john-ietf@jck.com>
Subject: RE: FW: Last Call: <draft-farrell-ft-03.txt> (A Fast-Track way to RFC with Running Code) to Experimental RFC
Date: Fri, 25 Jan 2013 10:25:04 -0000
Message-ID: <00c301cdfae6$3edd8760$bc989620$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: Ac365jVmCE5PgWUcRnW+EAuOVjoXgA==
Content-Language: en-gb
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: adrian@olddog.co.uk
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 25 Jan 2013 10:25:09 -0000

Hello,

Sorry I missed your last paragraph in the snow storm.

> So, Adrian, noting the ratio between discussion of this draft on
> the IETF list in the last few weeks and discussions of
> everything else, how long does professional courtesy to another
> IESG member (presumably in combination with your thinking this
> is a good idea) encourage you to allow the unintentional DoS
> attack on the IETF list to continue?

No-one is obliged to continue discussions beyond expressing their irreconcilable
discontent with the document.

The document progressed this far not out of professional courtesy to another
IESG member, but according to the rules of RFC3933. Page 3 bullet 1 had
completed, and the conditional part of bullet 2 was completed, so the next step
was IETF last call.

The IETF last call is four weeks (according to RFC3933). It ends on 2/8/13. I am
unaccustomed to calling consensus before the end of a last call.

My personal view, in sponsoring this document, is that the community needs the
opportunity to test whether there is support for running an experiment. I also
have a view that experimentation can be made safe and non-damaging to the rest
of the IETF. In that way we can often be surprised that something we thought
would never work, or was pointless, or potentially harmful, turns out to be
harmless/OK/beneficial.

Nevertheless, whatever my views on this experiment, or on experimentation in
general, when the last call completes I will summarise the last call comments to
the IESG so that they can act on bullet 3 (i.e. decide whether the proposed
experiment is plausible and appropriate.

Thanks,
Adrian


From brian.e.carpenter@gmail.com  Fri Jan 25 02:30:26 2013
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A95DF21F86DA for <ietf@ietfa.amsl.com>; Fri, 25 Jan 2013 02:30:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.598
X-Spam-Level: 
X-Spam-Status: No, score=-101.598 tagged_above=-999 required=5 tests=[AWL=0.093, BAYES_00=-2.599, RCVD_ILLEGAL_IP=1.908, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
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 ma3oL4h1C9EV for <ietf@ietfa.amsl.com>; Fri, 25 Jan 2013 02:30:26 -0800 (PST)
Received: from mail-ee0-f45.google.com (mail-ee0-f45.google.com [74.125.83.45]) by ietfa.amsl.com (Postfix) with ESMTP id D398421F86D9 for <ietf@ietf.org>; Fri, 25 Jan 2013 02:30:25 -0800 (PST)
Received: by mail-ee0-f45.google.com with SMTP id b57so112366eek.32 for <ietf@ietf.org>; Fri, 25 Jan 2013 02:30:25 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:organization:user-agent :mime-version:to:cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=5PxReZjDpbH3fb9wtZD28hQ4aN91P5h/1MHq35Sg9ws=; b=S6SpZ5akvJptp9SWLL0s/m0H5PpRMI/OItBoGrncLN1reRGD99J1k6Xf607kvI38ab 32mKkA9Ra141l7+n5m/c6i6y9eMtgitM8EjrN0xYJ7gAzFMVira3l48PiAKkx8BUEUJo W+qWp3Jsk+ai+xgHi/PmBHfaaF26d/oKNUybyhj102ba4IQ+T4PySnCH8aDlbk3622sI vcf2qfqWjxTmHY9kWYcFeOy8JwHYa28zcJKyc3iBszl/FDnuLStdZW4rTdlg0jmeLOsq 083sWIot4GUA6H9sdFQznxp3VUNmWWxHfXz15IIJx+vSJGAlTYqbEb/FOglWgmdmEtMt Cg3w==
X-Received: by 10.14.225.72 with SMTP id y48mr16526717eep.46.1359109824983; Fri, 25 Jan 2013 02:30:24 -0800 (PST)
Received: from [192.168.1.65] (host-2-102-216-213.as13285.net. [2.102.216.213]) by mx.google.com with ESMTPS id k4sm948669eep.15.2013.01.25.02.30.22 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 25 Jan 2013 02:30:24 -0800 (PST)
Message-ID: <51025ECD.3010806@gmail.com>
Date: Fri, 25 Jan 2013 10:30:37 +0000
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: "t.p." <daedulus@btconnect.com>
Subject: Re: FW: Last Call: <draft-farrell-ft-03.txt> (A Fast-Track way to RFC with Running Code) to Experimental RFC
References: <017001cdf017$c394df00$4abe9d00$@olddog.co.uk><50FEC0B8.8060905@isi.edu>	<201301222131.r0MLVK8C015116@cichlid.raleigh.ibm.com> <00b801cdfae3$1918fa80$4001a8c0@gateway.2wire.net>
In-Reply-To: <00b801cdfae3$1918fa80$4001a8c0@gateway.2wire.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: Thomas Narten <narten@us.ibm.com>, adrian@olddog.co.uk, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 25 Jan 2013 10:30:26 -0000

Thomas said:

> The crux of the issue is that any attempt at "fast tracking" is
> fundamentally about short-circuiting some aspect of our review
> processes.

Speaking as a Gen-ART reviewer, I am indeed worried by this aspect.
I feel I would have to spend much longer reviewing a draft if I
knew it had not been through WGLC. The fact that a spec is
implementable does not mean it is correct, which is exactly why
we want review by subject matter experts.

I would expect other late reviewers, including ADs, to react the
same way.

I welcome anything that encourages early implementations;
interop challenges are a good way to do that. But in the end,
is the IETF process the right vehicle for this?

Can we start a new tradition of interop challenges?

    Brian


From loa@pi.nu  Fri Jan 25 02:54:17 2013
Return-Path: <loa@pi.nu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 61DDC21F8795 for <ietf@ietfa.amsl.com>; Fri, 25 Jan 2013 02:54:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.048
X-Spam-Level: 
X-Spam-Status: No, score=-101.048 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_RELAY_NODNS=1.451, RDNS_NONE=0.1, USER_IN_WHITELIST=-100]
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 vBigS6WUcxXY for <ietf@ietfa.amsl.com>; Fri, 25 Jan 2013 02:54:16 -0800 (PST)
Received: from mail.pi.nu (unknown [195.206.248.139]) by ietfa.amsl.com (Postfix) with ESMTP id ABB5721F8759 for <ietf@ietf.org>; Fri, 25 Jan 2013 02:54:12 -0800 (PST)
Received: from [192.168.1.104] (81-236-221-144-no93.tbcn.telia.com [81.236.221.144]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.pi.nu (Postfix) with ESMTPSA id 5A80F823B5 for <ietf@ietf.org>; Fri, 25 Jan 2013 11:54:09 +0100 (CET)
Message-ID: <51026457.9000108@pi.nu>
Date: Fri, 25 Jan 2013 11:54:15 +0100
From: Loa Andersson <loa@pi.nu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:17.0) Gecko/20130107 Thunderbird/17.0.2
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: FW: Last Call: <draft-farrell-ft-03.txt> (A Fast-Track way to RFCwith Running Code) to Experimental RFC
References: <017001cdf017$c394df00$4abe9d00$@olddog.co.uk><50FEC0B8.8060905@isi.edu> <201301222131.r0MLVK8C015116@cichlid.raleigh.ibm.com> <00b801cdfae3$1918fa80$4001a8c0@gateway.2wire.net>
In-Reply-To: <00b801cdfae3$1918fa80$4001a8c0@gateway.2wire.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 25 Jan 2013 10:54:17 -0000

Folks,

I'm very much on the same page as Tom, the normal problem we have
is not too much review, it is that we don't have enough.

Running code is valuable, but does not normally replace review.

/Loa

On 2013-01-25 11:02, t.p. wrote:
> ----- Original Message -----
> From: "Thomas Narten" <narten@us.ibm.com>
> To: "Joe Touch" <touch@isi.edu>
> Cc: <adrian@olddog.co.uk>; <ietf@ietf.org>
> Sent: Tuesday, January 22, 2013 9:31 PM
>> FWIW, I share Joe's concerns. And Stephen's responses don't really
>> change my mind.
>>
>> This document seems to have a bit of missing the forest for the
>> trees. In the overall scheme of things, I don't believe the draft will
>> materially help, and is at best a distraction from dealing with
>> meaningful problems.
>
> I agree.  This proposal asks the ADs and WG Chairs to do more work and I
> perceive lack of resouces in that area to be the single biggest reason
> for I-Ds to fail to progress as fast as they might.  Putting more load
> on the critical path can only make things worse, for the work as a
> whole.  Some favoured I-Ds will progress faster but overall, RFCs will
> take longer to appear.
>
> In this vein, I have commented before how progress in the IETF tends to
> take place in three bursts, in the course of each year, and that if only
> we had a way of bringing the three pauses to life, then progress would
> be much improved.  Quality would almost certainly also improve, since
> data would not get lost or forgotten in the pauses.  This month, most WG
> mailing lists seem to be in a mega-pause (I keep checking the archives
> to see if I have been accidentally unsubscribed!): that is the real
> problem.
>
> Tom Petch
>
>> The crux of the issue is that any attempt at "fast tracking" is
>> fundamentally about short-circuiting some aspect of our review
>> processes. We should only do that very carefully. In almost all cases,
>> individual judgement is needed as to when it is appropriate to do
>> that. ADs/WG chairs already have some flexibility here. e.g., a WG can
>> skip WG LC if they think its not needed.  And nothing stops an AD from
>> going to WGLC before doing a careful review. But I'd rather that be
>> done because the case at hand justifies such an optimization, not
>> because there is some "running code" checkmark that allows a special
>> case to be fast tracked..
>>
>> This document risks substituting process for judgement. I'd rather see
>> more of the latter and less of the former.
>>
>> Some specifics from the doc:
>>
>>>     In summary this experiment collapses three stages of the
> publication
>>>     process to run concurrently: working group last call, AD review,
> and
>>>     IETF last call.  Additionally, the experiment will only require
>>
>> IMO, it is almost never appropriate to collapse WG LC and IETF LC. In
>> cases where it is appropriate to do so, there presumably isn't a need
>> for a WG LC to start with.  And an AD has always been able to start an
>> IETF LC without doing a detailed review. The point, is judgement is
>> needed, and all such cases are best handled on a case-by-case
>> basis.
>>
>> Surely, we don't need a document to justify doing this in those cases
>> where it makes sense...
>>
>>>     IETF last call.  Additionally, the experiment will only require
>>>     issues raised during these three stages to be addressed if they
> meet
>>>     the IESG's Discuss criteria.  The former is not formally a
>>>     process
>>
>> and later:
>>
>>>     4.  Only comments that would be "DISCUSS-worthy" according to the
>>>         IESG Discuss Criteria [DCRIT] need be handled during last
> call.
>>>         Other comments can be handled or not, at the authors/editors
>>>         discretion.
>>
>> The above can easily become a way to dismiss legitimate review
>> comments. No doubt, when a AD or reviewer suggests "this needs
>> fixing", the proponents will hold up this document and say "you
>> shouldn't do this, per the RFC -- you're violating the spirit of this
>> document, only really really critical stuff needs to get addressed..."
>> No thanks. That is not what the IETF is about.
>>
>> If it is really urgent to get a document done, it is far better to
>> take steps to make sure the editors are engaged and responsive. That
>> is more likely the real issue!!!
>>
>>>     It is understood that the savings in time for the end-to-end
> delivery
>>>     of a proposed standard or experimental RFC may be modest,
> however,
>>>     the modifications to normal IETF process will also serve as an
>>>     indication of the importance that the IETF places in running
> code.
>>
>> Running code is valuable. Always has been, always will be. But we need
>> to resist the temptation of making "running code" more equal than
>> other criteria or putting it on a pedestal as some sort of holy
>> grail. Running code by itself is just a sound bite. The importance of
>> running code is what it tells us about a protocol specification. Just
>> the mere fact that there is running code doesn't mean there is
>> anything particularly enlightening to learn from an
>> implementation. For example, "running code" of a router function in
>> software doesn't necessarily say anything as to whether the code can
>> be implemented efficiently using ASICs, which may be the real
>> requirement.
>>
>>>
>>>     5.  The responsible AD for the WG concerned makes the decision as
> to
>>>         whether changes are required as a result of review comments,
> and
>>>         determines whether or not those have been completed.  If
>>>         significant change or extended discussion is required, or if
>>>         changes are not complete within two weeks after the end of
> fast-
>>>         track last call, then the draft is returned to the WG by the
>>>         responsible AD and the document is withdrawn from the
> experiment.
>>
>> The two week figure is too stringent. The above is too prescriptive to
>> be practical. For starters, how will the IESG telechat align with the
>> ending of LC? Or what if an IESG member issues a defer (or will those
>> be disallowed?).
>>
>> Section 4 has a bit too much detail and process in it. I'm sure it has
>> both too much and too little actually. I.e., it probably misses some
>> corner cases, and then what do you do given how prescriptive the rest
>> of the section is?
>>
>> But overall, I see this document at best as a no-op. However, I fear
>> that it can be used to short-circuit our review processes in a way
>> that doesn't help the IETF and that won't really speed things up
>> enough to justify the downsides.
>>
>> Thomas
>>
>>
>
>

-- 


Loa Andersson                        email: loa@mail01.huawei.com
MPLS Expert                                 loa@pi.nu
Huawei Technologies (consult)        phone: +46 739 81 21 64

From benl@google.com  Fri Jan 25 03:16:22 2013
Return-Path: <benl@google.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2BA1021F886C for <ietf@ietfa.amsl.com>; Fri, 25 Jan 2013 03:16:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.439
X-Spam-Level: 
X-Spam-Status: No, score=-102.439 tagged_above=-999 required=5 tests=[AWL=-0.062, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, J_CHICKENPOX_22=0.6, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
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 puNuqfeWqxWl for <ietf@ietfa.amsl.com>; Fri, 25 Jan 2013 03:16:20 -0800 (PST)
Received: from mail-bk0-f42.google.com (mail-bk0-f42.google.com [209.85.214.42]) by ietfa.amsl.com (Postfix) with ESMTP id 9E1EB21F886A for <ietf@ietf.org>; Fri, 25 Jan 2013 03:16:19 -0800 (PST)
Received: by mail-bk0-f42.google.com with SMTP id ji2so157047bkc.29 for <ietf@ietf.org>; Fri, 25 Jan 2013 03:16:18 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to:cc :content-type; bh=edE3TD/MdoX82Lxo2iSlEi38ZQHJETgOfhu6MXeHQwE=; b=g3DCoBN1LO3Wjn+E9GbHLFJkWG98v1MjHHMSmLfxMle+wXbMiZpeoSzCR8W7nub3Ku iMf3UAa2mdP4f6Dj8X+aDUt7eFNLk9JHN97NJWLu96nE/D1HiSBWy3LeezMMIVFl3q/4 3b/3vOQSNgG+1xfLx8cSpbugjNohb/79OA8wNgsnqnPQcSeZXys4O4z8YuAh+j8FLfq4 A4WzndNZDCoKwnsEAOStG4I5JN6Bc+1H0A/97oWrzY0SJSVKeuV1TMBQgglFWQQZyRnB BMl4VtTUdD0sqYTYwaDmroWBd84UBwNOP2ytB34MSMP7cCOxFBqrdvTkC3bkSQnVw4Cf W4rg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to:cc :content-type:x-gm-message-state; bh=edE3TD/MdoX82Lxo2iSlEi38ZQHJETgOfhu6MXeHQwE=; b=c2yhkehrfoLp1kOgWyOffPC9zjlBs/zQK/PagA/Dg5YA8R3nsv5qORuVS3z/T311Zl j8lFGHoBxw3HhKeLwrCvecMK4wpEK56o3QcCJmZjosORwulscMZNagL7SsKQqUjzQVwo ptHHfxDrCW58Sf+/iT80Ce0AR/0pwzUALJAa8DdZt/1afyydvM+HTocp1xdCuw9u6Epc ObHjvK2yD3NQAvKwQQxw6qJ0fluawnRWaxn7uU6Y4GbFA196Txjmn5THiSqnmzhnhaet vDkVvZjioAbnNQY7zom9hto/gIzLq9NnBuDyUK4ACKKRIfaXABDz2ydW2UHExlqL+O3o fc3w==
MIME-Version: 1.0
X-Received: by 10.204.141.4 with SMTP id k4mr1735727bku.60.1359112578417; Fri, 25 Jan 2013 03:16:18 -0800 (PST)
Received: by 10.204.38.198 with HTTP; Fri, 25 Jan 2013 03:16:18 -0800 (PST)
Date: Fri, 25 Jan 2013 11:16:18 +0000
Message-ID: <CABrd9SQMAGtOTcWVaUfxRE9SZS2dZVhUa3WbJVk8or_LxH6i1w@mail.gmail.com>
Subject: Re: LC comments on draft-laurie-pki-sunlight-05
From: Ben Laurie <benl@google.com>
To: "=JeffH" <Jeff.Hodges@kingsmountain.com>
Content-Type: text/plain; charset=ISO-8859-1
X-Gm-Message-State: ALoCoQlQt+3AK8W8cgv8kmM/S6srC7QHLm1sXBYpyE8GwZrZdAdwcB2f9HvbjMoeYyA7n2e4vhXOWPJAdTBTrMGuriNLYY3yGNqYkyfP0K6qxxK+v1PgOiJ5N8TfwJ8mW4YLAIOQ71npqnv92VnBrnfuwwYviNabhKFKsn8zlsXVFG2f3T4uQrrUsHn7us6oJJyl2q0LMnos
Cc: Emilia Kasper <ekasper@google.com>, "therightkey@ietf.org" <therightkey@ietf.org>, IETF Discussion List <ietf@ietf.org>, Adam Langley <agl@google.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 25 Jan 2013 11:16:22 -0000

Apologies for responding to recent comments in random order: I'm
travelling and have accumulated something of a backlog.

On 22 January 2013 03:11, =JeffH <Jeff.Hodges@kingsmountain.com> wrote:
> apologies for latency, many meetings and a conference in the last couple of
> weeks.
>
> BenL replied:
>> On 1 January 2013 21:50, =JeffH <Jeff.Hodges@kingsmountain.com> wrote:
>
> [ in the below discussion:
>
>  "the spec", "this spec" refers to draft-laurie-pki-sunlight-05.
>
> "TLS-CT client"  refers to a TLS client capable of processing CT information
> that is included in the TLS handshake in any of the specified manners.
>
> "ok" means in general: "ok, will check this in next rev of the spec..".
>
> ]
>
> <snip>
>>>
>>> comments on draft-laurie-pki-sunlight-05
>>>
>>> substantive comments (in somewhat arbitrary order)
>>> --------------------------------------------------
>>>
>
> [ I demoted the comments wrt "JSON object" terminology and put them down at
> the end of this msg ]
>
>
>>> Also, the syntax for GETS isn't fully specified. Are the URL parameters
>>> to
>>> be encoded as (order independent) key-value pairs, or just as
>>> order-dependent values?  Which separator character is to be used between
>>> parameters? RFC3986 should be cited.
>>
>> RFC 3986 says nothing about parameter format, though
>
> correct, it doesn't, and I wasn't trying to imply that it did, sorry.  I was
> just trying to say that RFC3986 should be cited in this spec because this
> spec normatively employs URLs, but perhaps referencing RFC2616 HTTP is
> better because it defines "http_URL".

ok.

>>  - is there a
>> standard reference for that? I've refereced HTML 4.01, but perhaps
>> there's a better one?
>
> hm, AFAICT, there is not a standard for URI query component formating and
> thus parameter encoding, so this spec will have to explicitly specify
> something. Section 3.4 of RFC3986 gives allowed chars for the query
> component, but that's about it.
>
> Have you mocked up code that parses the log client messages? If so, what
> query component syntax does it handle?

I have specified the "standard" format via HTML 4.01.

>>> 3. There appear to be three defined methods for TLS servers to provide
>>> TLS
>>> clients with CT data, in S3.2.  For this experiment, which approach is
>>> mandatory to implement for servers and clients?  Or, is it the case that
>>> participating TLS clients (ie web browsers etc) implement all three
>>> methods,
>>> and TLS servers can choose any of them?
>>
>> The latter.
>
> That should be made very clear. Is the reason for doing so to obtain
> operational experience wrt the three defined methods such that they perhaps
> can be narrowed down in the future, or is the expectation that TLS-CT
> clients will need to support all three methods in perpetuity?

I think I made that clear.

The reason three methods exist are as follows (I don't intend to get
into this in the RFC, but for your edification):

1. TLS extension is the right way to do it, but requires a server s/w
change - this adds many years to full deployment.

2. So, alternatives must be provided. One is to put the stuff in the
certificate, but...

3. ... some CAs have said they'd rather not gate issuance on the log,
so alternatively, wedge the stuff in an OCSP response (which must be
stapled - servers exist that support this option already).

>>> 5. The recursive equations in S2.1 describe how to calculate a Merkle
>>> Tree
>>> Hash (MTH) (aka "root hash"), and thus as a side effect generate a Merkle
>>> Tree, for a given set of input data. However, there doesn't seem to be a
>>> defined algorithm (or even hints, really) for adding further inputs to an
>>> existing tree. Even though this may be reasonably left as an exercise for
>>> implementers, it should probably be discussed to some degree in the spec.
>>> E.g., note that leaf hashes are "frozen" and various interior tree node
>>> hashes become "frozen" as the tree grows. Is it not sub-optimal to employ
>>> the obvious default brute-force mechanism of rebuilding a tree entirely
>>> from
>>> scratch when new inputs are available?  Would not a recursive algorithm
>>> for
>>> adding new inputs to an existing tree be straightforward to provide?
>>
>> I dunno about straightforward.
>
> yeah, agreed.
>
>
>> I'll think about it.
>
> ok. At least providing some hints would be useful it seems.

We do provide working code :-)

>>> 6. Signed tree heads (STHs) are denoted in terms of "tree size" (number
>>> of
>>> entries), but SCTs are denoted in terms of a timestamp.  Should there be
>>> a
>>> log client message supporting the return of the nearest STH (and thus
>>> tree
>>> size) to a given timestamp?
>>
>> I'm not sure why? Any STH (that includes that SCT) will do.
>
> Hm, it was sort of a gut feel that it might be useful, but perhaps not.
>
> S5.2. Auditor says..
>
>    A certificate accompanied by an SCT can be verified against any STH
>    dated after the SCT timestamp + the Maximum Merge Delay by requesting
>    a Merkle Audit Proof using Section 4.5.
>
> S4.5 get-proof-by-hash stipulates tree_size as an input,  but
> if a log auditor doesn't already have tree_size, then I suppose it first
> calls S4.3 get-sth, which will return a timestamp and a tree_size, which if
> generated max merge delay (MMD) after the SCT was gen'd, ought to be
> sufficient, yes?

Yes.

> I don't see in the spec where/how MMD is published.  Does MMD vary per log
> service?  The latter isn't stipulated in the spec it seems AFAICT ?

We have not really figured out how MMD is specified. I suspect it is
something that will be agreed between browser vendors and logs.

>>> 7. S3 paragraph 2 states that "TLS clients MUST reject certificates that
>>> do
>>> not have a valid SCT for the end-entity certificate" (i.e., hard-fail).
>>> Presummably this requirement is only for TLS clients participating in the
>>> CT
>>> experiment and that understand this protocol.
>>
>> Of course - what other way could it be? In other words, all RFCs can
>> only say what implementations that conform with them do.
>>
>>> This, or whatever the
>>> requirement actually is, should be further explained.
>
> I guess what I was getting at is that CT-conformant TLS clients should be
> differentiated from non-CT-conformant ones. Stipulating a name for
> CT-conformant TLS clients would clarify this (seems to me), e.g. "TLS-CT
> client" or something similar.

I understand what you're getting at, but not why. CT conformant TLS
clients obey all the MUSTs and non-conformant ones do not. That is
what MUST means.

>>> 8. The spec implies, but doesn't clearly describe, especially in S3.1,
>>> that
>>> the hashes are "labels" for tree entries, and that given a leaf hash, the
>>> log implementation should be able to look up and present the LogEntry
>>> data
>>> defined in that section.
>>
>> We actually only require an entry to be retrievable by hash (in
>> effect) for the message in 4.7, which we (at least currently) label as
>> a debugging message - so I am not sure that logs really are required
>> to be able to do that - certainly the system would work fine if they
>> couldn't, I believe (other than being unable to provide the debugging
>> data).
>
> I think what I was getting at was that this is stated at the end of S3.2..
>
>    The leaves of the Merkle Tree are the hashes of the corresponding
>    "MerkleTreeLeaf" structures.
>
> ..but it is somewhat confusing because (abstractly) each leaf also contains
> (or has a reference to) the LogEntry data (that's defined back in S3.1)
> ...if I understand this correctly.


I suppose this reflects our own confusion :-)

A LogEntry shows that someone we know can be blamed for the creation
of the certificate - perhaps indirectly. This is desirable because:

a) We want to limit spam, and

b) If someone starts misissuing, we probably want to know who that is...

However, this information is not need to _fix_ the misissuance, it
turns out. It also is not necessarily the information TLS clients may
see (because of cross-signing). So, I think we;re a bit ambivalent
about the precise role of this information.

>>> While in CT, if the input set is an odd number of entries, then the hash
>>> of
>>> the final single leaf is at layer 1, and is calculated as a leaf hash
>>> using
>>> 0x00. Thus CT "interior nodes" always have two children, but if the tree
>>> has
>>> an odd number of entries, the rightmost hash at layer 1 ("j" in the
>>> "binary
>>> Merkle tree with 7 leaves" figure) is a leaf node hash rather than an
>>> interior node hash.
>>>
>>>
>>> O-8. [CrosbyWallach] discusses auditing and gossiping and could be cited
>>> as
>>> a source for further discussion on those topics.
>>>
>>>
>>> O-9. The notion of "commitments" isn't well defined, and where "add a
>>> commitment to D[k:n]"  couldn't  "add an interior/intermediate node to
>>> D[k:n}"  be used?
>>>
>>> Is not the term "commitment" used in [CrosbyWallach] equivalent to the
>>> sha256_root_hash (an STH component) in the spec?
>>>
>>> [CrosbyWallach] uses the term "interior node(s)" while the spec uses
>>> "intermediate nodes" (in one place).
>>
>> CT is not actually derived from [CrosbyWallach], we just mention it as
>> a useful reference.
>
> yeah, it is useful, it would've been much harder to figure out the spec
> without it. Is there an existing paper that the spec is based more closely
> on?

No, we started afresh :-)

> The differences between the spec and [CrosbyWallach] doesn't seem to be that
> large, and so if there aren't more closely matching paper(s) to cite (?), it
> may be worth summarizing the differences between the spec and
> [CrosbyWallach] e.g. in an appendix.
>
>
>> "commitment" is a term of cryptographic art.
>
> so it is, but its definitions in the literature seem to vary somewhat
> depending on context.  IIUC, the spec uses "commitment" to refer to the hash
> labels of intermediate nodes ('interior nodes' in [CrosbyWallach]) as well
> as the root hash, yes?
>
> In S2.1.1, where it says..
>
>          We prove that the left subtree entries D[0:k] are consistent
>    and add a commitment to D[k:n]:
>
> ..it's not clear just what "add a commitment" means. add it (an
> intermediate-node hash?) to the list of hashes that the recursive algorthm
> is constructing?
>
> Overall, I'm finding S2.1.1 pretty difficult to parse and sort out.
>
> E.g., it isn't clear to me how/why/when the apparently boolean 3d parameter
> of SUBPROOF is either true or false, and whether there's an implied "if b
> then ... else ..."  in there somewhere.

Its reasonably hard to define this thing rigorously, and so I'm not
surprised you find it hard to follow - but as I think I've said
before, we did try various different phrasings and did not find an
easier one. Suggestions welcome.

>>> O-10. The recursive algorithms in S2 are dense and take effort to work
>>> through, perhaps adding simplistic example code (in an appendix) which
>>> implements, and/or actually working through the algorithms to arrive at
>>> some
>>> of the audit paths and consistency proofs in S2.1.3, would be helpful.
>>
>> We have actual working code - would a reference to that be better?
>
> I don't know if it would be better (I've compiled it and am poking through
> the code). I sorta think pseudo code in an appendix that would generate the
> trees in S2.1.3. would be helpful.

I suspect this is more relevant to a non experimental RFC - right now
I have no evidence that anyone is planning to actually write code
other than us - AFAIK, so far everyone who has played with it has used
our code.

>>> O-14. Detailed comments on S2...
>>> ------------------------------
>>>
>>>> 2. Cryptographic components
>>>>
>>>>
>>>> 2.1. Merkle Hash Trees
>>>>
>>>>
>>>>    Logs use a binary Merkle hash tree for efficient auditing.  The
>>>>    hashing algorithm is SHA-256 (note that this is fixed for this
>>>>    experiment but it is anticipated that each log would be able to
>>>>    specify a hash algorithm).  The input to the Merkle tree hash is a
>>>>    list of data entries; these entries will be hashed to form the leaves
>>>>    of the Merkle hash tree.  The output is a single 32-byte root hash.
>>>>    Given an ordered list of n inputs, D[n] = {d(0), d(1), ..., d(n-1)},
>>>>    the Merkle Tree Hash (MTH) is thus defined as follows:
>>>>
>>>>    The hash of an empty list is the hash of an empty string:
>>>>
>>>>    MTH({}) = SHA-256().
>>>
>>>
>>> This MTH({}) construct doesn't appear to be used anywhere else in the
>>> spec
>>> (yes?), and so does it really need mentioning?
>>
>> If it is not defined, then we cannot represent an empty tree.
>
> yeah, I agree from a mathematical completeness perspective.  but I still
> found it sort of distracting in that I don't know that it's actually germane
> from an implementor's perspective. maybe it is because
>
>
>>>>    The hash of a list with one entry is:
>>>>
>>>>    MTH({d(0)}) = SHA-256(0x00 || d(0)).
>>>
>>>
>>> The immediately above equation is for leaf entries (yes?),
>>
>> Yes.
>>
>>> where in this
>>> notation n = 1, perhaps it should be stated explicitly:
>>>
>>>     When n = 1, a leaf entry is denoted, and D[1] = {d(0)}. The leaf hash
>>>     (LH) for a leaf entry is calculated as:
>>>
>>>     MTH(D[1]) = LH(D[1]) = SHA-256( 0x00 || d(0) )
>>
>> Ugh. LH(D[1]) seems meaningless to me. A leaf hash is always of a "1
>> entry tree".
>
> yeah, for those who have grokked this stuff. for others it isn't immediately
> obvious. also,  the above comment was motivated in part due to the missing
> formal definition for "Leaf Hash" noted in item (4) above. even if the
> LH(D[1]) notation isn't used, some additional prose along the lines
> suggested above would be helpful to less initiated readers imv.
>
>
>
>>>>    For n > 1, let k be the largest power of two smaller than n.
>>>
>>>
>>> The unqualified "power of two" phrase is arguably ambiguous.
>>
>> It is?
>
> uh, yeah.
>
> but "let k be a number which is the largest power of two such that..."
> isn't.
>
>
>>> Suggested rephrase for this where it occurs throughout section 2..
>>>
>>>     For n > 1, let k be a number which is the largest power of two
>>>     such that k = 2^i, 0 <= i < n, and k < n.
>>
>> If we're going to go down that path, then it should say:
>>
>> For n > 1, let k be the largest number such that k = 2^i and k < n.
>>
>> or
>>
>> For n > 1, let k = 2^i s.t. k < n and 2k >= n.
>>
>> surely?
>
> well, yes (i prefer the former), but i think it's also important to
> explicitly state 0 <= i < n

Why? Its weird! its also not generally true - e.g. n=2 and i=1.

>>>>    The Merkle Tree Hash of an n-element list D[n] is then defined
>>>>    recursively as
>>>
>>>
>>> The above statement applies to the combination of the n = 1 equation
>>> above
>>> and the equation below, and so should perhaps be moved up above the n = 1
>>> equation.
>>
>> ? It says n > 1, so doesn't apply to n = 1?
>
> oh yeah huh.
>
> in any case, I found the prose separation of the "list with one entry" and
> the "n > 1" case to be confusing because the former is part of the recursive
> definition of MTH(), yes?

OK, so D[0] = {} and D[1] = {d[0]} and we should make that more
explicit as you say which I expect will make this a lot clearer.

>
>
>>>>    MTH(D[n]) = SHA-256(0x01 || MTH(D[0:k]) || MTH(D[k:n])),
>>>>
>>>>    where || is concatenation and D[k1:k2] denotes the length (k2 - k1)
>>>>    list {d(k1), d(k1+1),..., d(k2-1)}.
>>>
>>>
>>> The above phrase doesn't parse well and is somewhat ambiguous, here it is
>>> extracted for clarity:
>>>
>>>  "D[k1:k2] denotes the length (k2 - k1) list {d(k1), d(k1+1),...,
>>> d(k2-1)}"
>>>
>>>
>>> How about rephrasing it along the lines of this:
>>>
>>>     D[k1:k2] denotes a sublist {d(k1), d(k1+1),..., d(k2-1)}, having
>>>     (k2 - k1) elements, of the original input list D[n]. When (k2 - k1)
>>>     is 1, a leaf hash is calculated.
>>
>> We tried lots of different ways of saying this and they were all a
>> little messy. Yours mixes concerns and is rather verbose, so not
>> convinced it is actually an improvement.
>
> well, the way it's presently said in the spec is (to me) pretty darn hard to
> understand.
>
> which concerns are missed in the suggested reformulation?

I said "mixes" :-)

That is, it mixes the hashing up with the definition of the list.
Other than that, I'm OK with the rephrasing.


>>>>    Anyone can submit certificates to certificate logs for public
>>>>    auditing, however, since certificates will not be accepted by clients
>>>>    unless logged, it is expected that certificate owners or their CAs
>>>>    will usually submit them.  A log is a single, ever-growing, append-
>>>>    only Merkle Tree of such certificates.
>>>>
>>>>    When a valid certificate is submitted to a log, the log MUST
>>>>    immediately return a Signed Certificate Timestamp (SCT).  The SCT is
>>>>    the log's promise to incorporate the certificate in the Merkle Tree
>>>>    within a fixed amount of time known as the Maximum Merge Delay (MMD).
>>>>    If the log has previously seen the certificate, it MAY return the
>>>>    same SCT as it returned before.
>>>
>>>
>>> What if the submitted end entity cert is the same, but the certificate
>>> chain
>>> is different (yet valid)?
>>
>> The purpose of the chain is to:
>>
>> a) Prevent spam, and
>>
>> b) Identify who to blame in the event of a misissue.
>>
>> Alternate chains presumably don't actually change the direct blame,
>> and so I see no reason to do other than what the I-D says - i.e.
>> return the same SCT as before.
>
> ok. tho i wonder if there's any value in caching the alternate chain or the
> new portions thereof.

Logs are free to keep additional information, of course :-)

We probably will.

Its not clear that its particularly useful.

>>>>                                     TLS servers MUST present an SCT from
>>>>    one or more logs to the client together with the certificate.  TLS
>>>>    clients MUST reject certificates that do not have a valid SCT for the
>>>>    end-entity certificate.
>>>
>>>
>>> [ see comment (7) above ]
>>>
>>>
>>>>    Periodically, each log appends all its new entries to the Merkle
>>>>    Tree, and signs the root of the tree.  Clients and auditors can thus
>>>
>>>
>>> Should "Clients and auditors" actually be "TLS Clients, log monitors, and
>>> log auditors" ?
>>
>> Bearing in mind that these are actually roles rather than distinct
>> entities, it should probably just say "auditors".
>
> I dunno, that may loose some readers.  in any case, the distinction between
> roles and distinct entities should probably be mentioned/discussed e.g. in
> the Introduction or thereabouts.

Yeah.

>
>
> <snip>
>
>>>> 3.1. Log Entries
>>>>
>>>>
>>>>    Anyone can submit a certificate to any log.  In order to enable
>>>>    attribution of each logged certificate to its issuer, the log SHALL
>>>>    publish a list of acceptable root certificates (this list might
>>>>    usefully be the union of root certificates trusted by major browser
>>>>    vendors).  Each submitted certificate MUST be accompanied by all
>>>>    additional certificates required to verify the certificate chain up
>>>>    to an accepted root certificate.  The root certificate itself MAY be
>>>>    omitted from this list.
>>>>
>>>>    Alternatively, (root as well as intermediate) Certificate Authorities
>>>
>>>
>>> Additionally?  which manner is the experiment going to operate, or is it
>>> TBD
>>> ?
>>
>> Not sure what you mean? The log will accept either type of submission.
>
> oh, sorry, I meant s/Alternatively/Additionally/

Probably the other way round? In any case, as I said, the log will
accept either type - some CAs seem to prefer one, some the other.

>>>>    Structure of the Signed Certificate Timestamp:
>>>
>>>
>>> The SCT discussion here should probably be its own subsection.
>>
>> OK.
>>
>>>
>>>
>>>>
>>>>        enum { certificate_timestamp(0), tree_hash(1), 255 }
>>>>          SignatureType;
>>>>
>>>>        enum { v1(0), 255 }
>>>>          Version;
>>>
>>>>
>>>>
>>>>          struct {
>>>>              opaque key_id[32];
>>>>          } LogID;
>>>>
>>>>          opaque CtExtensions<0..2^16-1>;
>>>>
>>>>    "key_id" is the SHA-256 hash of the log's public key, calculated over
>>>>    the DER encoding of the key represented as SubjectPublicKeyInfo.
>>>
>>>
>>> I'd place the above paragraph regarding "key_id" down below the
>>> SignedCertificateTimestamp definition.
>>>
>>>
>>>>        struct {
>>>>            Version sct_version;
>>>>            LogID id;
>>>>            uint64 timestamp;
>>>>            CtExtensions extensions;
>>>>            digitally-signed struct {
>>>>                Version sct_version;
>>>>                SignatureType signature_type = certificate_timestamp;
>>>>                uint64 timestamp;
>>>>                LogEntryType entry_type;
>>>>                select(entry_type) {
>>>>                    case x509_entry: ASN.1Cert;
>>>>                    case precert_entry: ASN.1Cert;
>>>>                } signed_entry;
>>>>               CtExtensions extensions;
>>>>            };
>>>>        } SignedCertificateTimestamp;
>>>>
>>>>    The encoding of the digitally-signed element is defined in [RFC5246].
>>>
>>>
>>> I would add a few words here summarizing that what happens here is that
>>> the
>>> digitally-signed struct here is replaced in the actual serialized binary
>>> structure by a struct DigitallySigned and cross-ref to S4.7 of RFC5246.
>>
>> Except it isn't :-)
>
> ok, then I don't understand what's going on here.  RFC5246 S4.7 sez...
>
>    A digitally-signed element is encoded as a struct DigitallySigned:
>
>       struct {
>          SignatureAndHashAlgorithm algorithm;
>          opaque signature<0..2^16-1>;
>       } DigitallySigned;
>
>
> ..and I take the "digitally-signed struct" within SignedCertificateTimestamp
> to be a "digitally-signed element".  Please help me understand what am I
> missing?

We've actually significantly revamped this whole thing, so hopefully
you'll find it clearer in the next version.


>>>> 5.1. Monitor
>>>>
>>>>
>>>>    Monitors watch logs and check that they behave correctly.  They also
>>>>    watch for certificates of interest.
>>>
>>>
>>> "Monitor" should be "Log Monitor" ?
>>
>> There's no other kind of monitor :-)
>
> in the explicit context of this spec, agreed.  but in general I
> favor/advocate creation and use of more fully descriptive words/phrases so
> at least one is more likely to find them with a search when you're wondering
> what sort of "monitor" someone down the road is yammering on about.
>
> [ I would add a terminology section to the spec ]
>
>>>> 5.2. Auditor
>>>>
>>>>
>>>>    Auditors take partial information about a log as input and verify
>>>>    that this information is consistent with other partial information
>>>>    they have.  An auditor might be an integral component of a TLS
>>>>    client, it might be a standalone service or it might be a secondary
>>>>    function of a monitor.
>>>
>>>
>>> "Auditor" should be "Log Auditor" ?
>>
>> And there's no other kind of auditor.
>
> see above :)
>
> e.g. in the overall webpki world, there /are/ other forms of auditors (e.g.
> the ones noted here <http://wiki.cacert.org/Audit/CriteriaAlphabetSoup>) and
> so it's worth using a more descriptive term, imv.
>
>
>>>> 8. Efficiency Considerations
>>>>
>>>>
>>>>    The Merkle tree design serves the purpose of keeping communication
>>>>    overhead low.
>>>>
>>>>    Auditing logs for integrity does not require third parties to
>>>>    maintain a copy of each entire log.  The Signed Tree Heads can be
>>>>    updated as new entries become available, without recomputing entire
>>>>    trees.  Third party auditors need only fetch the Merkle consistency
>>>>    proofs against a log's existing STH to efficiently verify the append-
>>>>    only property of updates to their Merkle Trees, without auditing the
>>>>    entire tree.
>>>
>>>
>>> The above could be explained in more detail, and S5.1 should be
>>> cross-referenced. Is the last sentence above essentially a summary of
>>> step
>>> #8 in S5.1? Or are there differences?
>>
>> It is a summary of 5.1
>
> ok, but it'd be helpful to state that and crossref S5.1.

Actually, its the auditor not the monitor, but I have referenced it now.

> wrt he JSON stuff...
>
>>> 1. The client messages S4 don't explicitly lay out the syntax for request
>>> messages or responses. E.g., for S4.1 "Add Chain to Log", is the input a
>>> stand-alone JSON text array, or a JSON text object containing a JSON text
>>> array?
>>>
>>> The term "JSON object" as used in the first paragraph is ambiguous and
>>> perhaps what is mean is simply "JSON texts" or "JSON text objects or JSON
>>> text arrays". RFC4627 clearly defines "JSON text", and should be cited.
>>> But
>>> RFC4627 is a little ambiguous itself regarding "JSON object" and so I
>>> suggest these definitions:
>>>
>>>     JSON text object:   A JSON text matching the "object" ABNF production
>>>        in Section 2.2 of [RFC4627].
>>>
>>>     JSON text array:   A JSON text matching the "array" ABNF production
>>>        in Section 2.3 of [RFC4627].
>>
>> I agree that RFC 4627 should be cited and I will correct that.
>
> ok.
>
>> The
>> rest of this confuses me: JSON is a textual representation of
>> structured data, as it states in the RFC. It defines an object quite
>> clearly
>>
>> " An object is an unordered collection of zero or more name/value
>>    pairs, where a name is a string and a value is a string, number,
>>    boolean, null, object, or array."
>
> well, yes, but that's in just the introduction of RFC 4627.
>
>> Defining a "JSON text object" seems pointless to me - clearly a JSON
>> object is an object as defined by JSON, surely? Introducing another
>> term seems like to add confusion rather than remove it.
>
> note that "JSON text" is very explicitly defined in RFC4627 at the beginning
> of S2 as..
>
>    A JSON text is a sequence of tokens.  The set of tokens includes six
>    structural characters, strings, numbers, and three literal names.
>
>    A JSON text is a serialized object or array.
>
>       JSON-text = object / array
>
> the reason I flagged this issue is that I just recently reviewed a different
> internet-draft where they'd confused a JSON object -- in the sense of a JSON
> text matching the object production of S2.2 RFC4627 -- and a "JSON object"
> in the sense of an abstract programming construct, and they didn't
> understand that in the protocol on-the-wire world a JSON object /is a
> string/  (i.e. it is string-serialized according to the grammar of RFC4627).
>
> It seems the term "JSON object" is ambiguous depending on whether you're
> looking at it from a programming perspective or an on-the-wire protocol
> perspective (eg see <http://www.json.org/javadoc/org/json/JSONObject.html>
> which talks about "internal form" and "external form" (ugh)), hence my
> (perhaps feeble) attempt to invent a more explicit term for the on-the-wire
> protocol form.
>
> So maybe a more palatable definition would be..
>
>   JSON object: A JSON text matching the "object" ABNF production
>                in Section 2.2 of [RFC4627].

ok

>
> ?
>
>
> ---
> end
>
>
>
>
>
>
>
>

From stephen.farrell@cs.tcd.ie  Fri Jan 25 05:07:37 2013
Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6B57021F854F for <ietf@ietfa.amsl.com>; Fri, 25 Jan 2013 05:07:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.953
X-Spam-Level: 
X-Spam-Status: No, score=-101.953 tagged_above=-999 required=5 tests=[AWL=-0.646, BAYES_00=-2.599, MISSING_HEADERS=1.292, USER_IN_WHITELIST=-100]
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 wl+38ql+cyt2 for <ietf@ietfa.amsl.com>; Fri, 25 Jan 2013 05:07:36 -0800 (PST)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) by ietfa.amsl.com (Postfix) with ESMTP id 9294021F853E for <ietf@ietf.org>; Fri, 25 Jan 2013 05:07:33 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id C2F95BE62 for <ietf@ietf.org>; Fri, 25 Jan 2013 13:07:10 +0000 (GMT)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id y20c23at8QQV for <ietf@ietf.org>; Fri, 25 Jan 2013 13:07:09 +0000 (GMT)
Received: from [IPv6:2001:770:10:203:810d:eba8:c654:6e65] (unknown [IPv6:2001:770:10:203:810d:eba8:c654:6e65]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 5377FBE65 for <ietf@ietf.org>; Fri, 25 Jan 2013 13:07:00 +0000 (GMT)
Message-ID: <51028374.9070702@cs.tcd.ie>
Date: Fri, 25 Jan 2013 13:07:00 +0000
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130106 Thunderbird/17.0.2
MIME-Version: 1.0
CC: ietf@ietf.org
Subject: Re: FW: Last Call: <draft-farrell-ft-03.txt> (A Fast-Track way to RFCwith Running Code) to Experimental RFC
References: <017001cdf017$c394df00$4abe9d00$@olddog.co.uk><50FEC0B8.8060905@isi.edu> <201301222131.r0MLVK8C015116@cichlid.raleigh.ibm.com> <00b801cdfae3$1918fa80$4001a8c0@gateway.2wire.net> <51026457.9000108@pi.nu>
In-Reply-To: <51026457.9000108@pi.nu>
X-Enigmail-Version: 1.5
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 25 Jan 2013 13:07:37 -0000

Responses to some points below but I'd really like to ask
people to consider a few things here:

- what's proposed is an experiment, it'd likely get tried out
  a few times and won't consume any huge resource anywhere
- its optional, WG chairs that want to try it could, those
  that don't can just ignore the whole thing
- argument that there are other or better process issues to
  address is misdirected
- on a meta-level, if every process proposal, even small
  experiments like this, generates huge concerns then we're
  not in a good place and it seems to me that we are in that
  bad place (that's not an argument to do this experiment,
  but just an observation)

On 01/25/2013 10:54 AM, Loa Andersson wrote:
> Running code is valuable, but does not normally replace review.

This proposal doesn't "replace review." Its an optional way
to get some of that done in parallel with a few other rule
tweaks.

On 01/25/2013 10:30 AM, Brian E Carpenter wrote:
> Speaking as a Gen-ART reviewer, I am indeed worried by this aspect.
> I feel I would have to spend much longer reviewing a draft if I
> knew it had not been through WGLC.

Its an experiment that would be used for a few drafts, your
concern might be justified if this were proposed as a
permanent change (it's not) that applied to many drafts (it
won't ever IMO, but certainly not during the experiment).

On 01/25/2013 10:02 AM, t.p. wrote:
> This proposal asks the ADs and WG Chairs to do more work

It does not. WG chairs *choose* to take this route if they
want to. The timers and checking the implementation could
increase the workload for the responsible AD at a time not of
her choosing and its the timing that's more pertinent but not
so bad since ADs are already clearly gullible enough when
it comes to additional workload:-)

On 01/24/2013 06:34 PM, John C Klensin wrote:
> As co-author of the process experiment model, I also object to
> its use when it is not demonstrably necessary,

That's a really weird objection. I just re-read 3933 and it
says nothing whatsoever like that, in fact it says 'This
specification permits and encourages the IESG to adopt and
institute "process experiments"...' and the whole tenor of
the RFC is that stuff ought be tried out.

John also said:

> this document moves a number of informal IESG
> procedures -- including the DISCUSS criteria and even the
> Shepherd report requirements (now Informational in RFC 4858 plus
> a number of less formal "statements" and "templates" that have
> sometimes changed rapidly) -- into the status of formal
> procedural requirements

That's just wrong. It includes those as part of an experiment
that is optional to use which I don't think qualifies as
"formal process requirements" in any useful sense.

And lastly...

> In my experience in the IETF, we almost
> never allow a individual submission document that is obviously
> very controversial to turn into a extended debate on the IETF
> list with the author trying to refute every comment.

"Trying to refute every comment" is (IMO wildly) inaccurate.
This was proposed a couple of months ago. Some people liked
the idea of trying it out, others didn't. I'm following up
on that as described in 3933. Every proposal to do with
process seems this controversial unfortunately, even teeny
little ones like this. I'd love if it were otherwise.

And if Adrian or the IESG decide we should not go ahead and
try this particular experiment, that's just fine and the
world will not end. (And nor will it end if this experiment
is run.)

What's less fine, but I suspect is also the case, is that
any proposal for process change would get the same kinds
of negative reception from a similarly sized set of folks
and with similarly good, bad and irrelevant arguments
against whatever change or experiment is proposed.

Regards,
S.






From lear@cisco.com  Fri Jan 25 05:36:58 2013
Return-Path: <lear@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4233D21F85AB for <ietf@ietfa.amsl.com>; Fri, 25 Jan 2013 05:36:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.549
X-Spam-Level: 
X-Spam-Status: No, score=-110.549 tagged_above=-999 required=5 tests=[AWL=0.050, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
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 laz6a9xHpC5c for <ietf@ietfa.amsl.com>; Fri, 25 Jan 2013 05:36:57 -0800 (PST)
Received: from ams-iport-4.cisco.com (ams-iport-4.cisco.com [144.254.224.147]) by ietfa.amsl.com (Postfix) with ESMTP id 73C2921F85C0 for <ietf@ietf.org>; Fri, 25 Jan 2013 05:36:57 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=206; q=dns/txt; s=iport; t=1359121017; x=1360330617; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=G0i14RK3PvQcJbEk4fmhqvc7omKCWjOTWb1WlhkIhpQ=; b=I2l0oaohzPo1XVPWWELeoCOScsbQyjb1wB11ZKjyfYW3NXnnzmMJnfre NKEyNzE1LlQr/QnCcMTJ8DjtJyLXiUFKn2rtrTDLrWaxO+g8+KW6sNIr/ ypjzt/5QyVYTM7iMF+iQyBlP56jb4f/9T9Pp7YFPFEdnqjIemrdRuFIAo 0=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgEFAGWJAlGQ/khN/2dsb2JhbABEhka4CxZzgh4BAQEEI1UBEAsYAgIFFgQHAgIJAwIBAgE8CQYNAQcBAYgWq2OSU4EjjwiBEwOWDJBIgnk
X-IronPort-AV: E=Sophos;i="4.84,538,1355097600"; d="scan'208";a="11346875"
Received: from ams-core-4.cisco.com ([144.254.72.77]) by ams-iport-4.cisco.com with ESMTP; 25 Jan 2013 13:36:56 +0000
Received: from ams3-vpn-dhcp6975.cisco.com (ams3-vpn-dhcp6975.cisco.com [10.61.91.62]) by ams-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id r0PDatHS004723 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 25 Jan 2013 13:36:56 GMT
Message-ID: <51028A77.2060808@cisco.com>
Date: Fri, 25 Jan 2013 14:36:55 +0100
From: Eliot Lear <lear@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130107 Thunderbird/17.0.2
MIME-Version: 1.0
To: Thomas Narten <narten@us.ibm.com>
Subject: Re: FW: Last Call: <draft-farrell-ft-03.txt> (A Fast-Track way to RFC with Running Code) to Experimental RFC
References: <017001cdf017$c394df00$4abe9d00$@olddog.co.uk> <50FEC0B8.8060905@isi.edu> <201301222131.r0MLVK8C015116@cichlid.raleigh.ibm.com>
In-Reply-To: <201301222131.r0MLVK8C015116@cichlid.raleigh.ibm.com>
X-Enigmail-Version: 1.5
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: adrian@olddog.co.uk, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 25 Jan 2013 13:36:58 -0000

On 1/22/13 10:31 PM, Thomas Narten wrote:
> a WG can
> skip WG LC if they think its not needed.

???

When was the last time that happened?  Did it require a consensus call
to determine?

Eliot

From john-ietf@jck.com  Fri Jan 25 07:27:22 2013
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5C5C921F8782 for <ietf@ietfa.amsl.com>; Fri, 25 Jan 2013 07:27:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.742
X-Spam-Level: 
X-Spam-Status: No, score=-102.742 tagged_above=-999 required=5 tests=[AWL=-0.143, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 2MTXG7dBjh6Y for <ietf@ietfa.amsl.com>; Fri, 25 Jan 2013 07:27:21 -0800 (PST)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id BDFCA21F8439 for <ietf@ietf.org>; Fri, 25 Jan 2013 07:27:21 -0800 (PST)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1TylBT-000FPS-Pk; Fri, 25 Jan 2013 10:27:15 -0500
Date: Fri, 25 Jan 2013 10:27:10 -0500
From: John C Klensin <john-ietf@jck.com>
To: Eliot Lear <lear@cisco.com>, Thomas Narten <narten@us.ibm.com>
Subject: Re: FW: Last Call: <draft-farrell-ft-03.txt> (A Fast-Track way to	RFC with Running Code) to Experimental RFC
Message-ID: <E2AC36AC55ED79756BE8929E@JcK-HP8200.jck.com>
In-Reply-To: <51028A77.2060808@cisco.com>
References: <017001cdf017$c394df00$4abe9d00$@olddog.co.uk> <50FEC0B8.8060905@isi.edu> <201301222131.r0MLVK8C015116@cichlid.raleigh.ibm.com> <51028A77.2060808@cisco.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Cc: adrian@olddog.co.uk, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 25 Jan 2013 15:27:22 -0000

--On Friday, January 25, 2013 14:36 +0100 Eliot Lear
<lear@cisco.com> wrote:

> 
> On 1/22/13 10:31 PM, Thomas Narten wrote:
>> a WG can
>> skip WG LC if they think its not needed.
> 
> ???
> 
> When was the last time that happened?  Did it require a
> consensus call to determine?

Chair discretion.  It is seems clear that the WG is in agreement
on all relevant issues and has adequately reviewed the document,
a WG LC is just another way to waste time.  Keep in mind that,
whether there is a WG LC or not, WG members are permitted to
comment in IETF LC.  Although it may be bad taste for a WG
member to disagree during IETF LC about issues already settled,
we don't forbid that and, because of a lot of edge cases and the
vague possibility of abuse, it would be a terrible idea to
forbid it.

Other than added bureaucracy, a WG LC serves only the following
purposes:

	* If the WG participants haven't adequately reviewed the
	document(s), a WG LC can provide a deadline and forcing
	function for more reviews.
	
	* Surprises during IETF LC and long debates on the IETF
	list waste the community's time and distract from other
	discussions.  If a WG LC might contribute to identifying
	and understanding the issues before the document reaches
	IETF LC and possibly even resolving them in the WG, that
	is almost certainly A Good Thing.   A WG Chair who can't
	make an guess about whether such issues are likely to
	arise (or issues that were thought settled really were
	not) probably needs to retire (and should certainly err 
   in the direction of doing a WG LC).

In the context of draft-farrell-ft, the above makes the idea of
WG LC in parallel with IETF LC either irrelevant or bad news.
If the WG Chair (or AD) concludes that a WG LC is needed, then
the procedure should not be invoked.  If a WG LC is not needed,
then organizing things so that one is conducted in parallel with
the IETF LC risks having two discussions going on in parallel
with comments made to the WG list not being exposed to the
community (remember the days when IETF LC comments were
routinely sent to the IESG and not to the IETF list?).   And, if
the WG does conduct a WG LC, the document can be read as
forbidding use of the FT procedure to condense and set timelines
on the rest of the process (something I'd suggest fixing if we
are going to go ahead with this).

All of this points out one of my main concerns.  Almost as a
side-effect, the proposal formalizes a number of informal
procedures and mechanisms work pretty well most of the time but,
because they are informal, can be used flexibly without a big
fuss.  If we are going to formalize them, we really should be
asking questions about consensus, exception cases, and so on...
and risk another several steps in the direction of trying to
substitute procedures for judgment, responsibility, and
accountability.

    john




From lear@cisco.com  Fri Jan 25 07:31:09 2013
Return-Path: <lear@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ACDCF21F8896 for <ietf@ietfa.amsl.com>; Fri, 25 Jan 2013 07:31:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.556
X-Spam-Level: 
X-Spam-Status: No, score=-110.556 tagged_above=-999 required=5 tests=[AWL=0.043, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
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 Zk+2Hgw9uH5x for <ietf@ietfa.amsl.com>; Fri, 25 Jan 2013 07:31:09 -0800 (PST)
Received: from ams-iport-4.cisco.com (ams-iport-4.cisco.com [144.254.224.147]) by ietfa.amsl.com (Postfix) with ESMTP id E0FDE21F8682 for <ietf@ietf.org>; Fri, 25 Jan 2013 07:31:08 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=384; q=dns/txt; s=iport; t=1359127869; x=1360337469; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=n6yRBwnD8GNUtcuFuWs38rC4qkhOqtWDmws8jknTQ9o=; b=f06UUfNk3lnw14NtWN1cuVAd1gsj2Ig4AjgeeLH6r15ejUAk9y36iz9H yBWuzpj6ozB+K7ZJoxBetCpAdX6IDVGMDTmxw09VerJRa4g7iRmbQ0bhe SMEhHIM4qyxp0yZnFOLhB2BqRds8tLealldq0sBgeVa9lC1vv7KCj/Rcj Q=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgEFAKKjAlGQ/khR/2dsb2JhbABEhka4DRZzgh4BAQEEI1UBEAsYAgIFFgQHAgIJAwIBAgE8CQYNAQcBAYgLrACSVoEjjwmBEwOWDZBIgng
X-IronPort-AV: E=Sophos;i="4.84,538,1355097600"; d="scan'208";a="11350216"
Received: from ams-core-1.cisco.com ([144.254.72.81]) by ams-iport-4.cisco.com with ESMTP; 25 Jan 2013 15:31:07 +0000
Received: from ams3-vpn-dhcp6975.cisco.com (ams3-vpn-dhcp6975.cisco.com [10.61.91.62]) by ams-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id r0PFV6FM017718 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 25 Jan 2013 15:31:07 GMT
Message-ID: <5102A53A.8070206@cisco.com>
Date: Fri, 25 Jan 2013 16:31:06 +0100
From: Eliot Lear <lear@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130107 Thunderbird/17.0.2
MIME-Version: 1.0
To: John C Klensin <john-ietf@jck.com>
Subject: Re: FW: Last Call: <draft-farrell-ft-03.txt> (A Fast-Track way to RFC with Running Code) to Experimental RFC
References: <017001cdf017$c394df00$4abe9d00$@olddog.co.uk> <50FEC0B8.8060905@isi.edu> <201301222131.r0MLVK8C015116@cichlid.raleigh.ibm.com> <51028A77.2060808@cisco.com> <E2AC36AC55ED79756BE8929E@JcK-HP8200.jck.com>
In-Reply-To: <E2AC36AC55ED79756BE8929E@JcK-HP8200.jck.com>
X-Enigmail-Version: 1.5
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: Thomas Narten <narten@us.ibm.com>, adrian@olddog.co.uk, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 25 Jan 2013 15:31:09 -0000

John,

On 1/25/13 4:27 PM, John C Klensin wrote:
>>> a WG can
>>> skip WG LC if they think its not needed.
>> ???
>>
>> When was the last time that happened?  Did it require a
>> consensus call to determine?
> Chair discretion [... and five of paragraphs of text]

None of which answered my above questions.  When was the last time
chairs USED that discretion?!

Eliot


From stephen.farrell@cs.tcd.ie  Fri Jan 25 07:34:34 2013
Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CC8EC21F8945 for <ietf@ietfa.amsl.com>; Fri, 25 Jan 2013 07:34:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.491
X-Spam-Level: 
X-Spam-Status: No, score=-102.491 tagged_above=-999 required=5 tests=[AWL=0.108, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 wK0L6Xnzbl68 for <ietf@ietfa.amsl.com>; Fri, 25 Jan 2013 07:34:34 -0800 (PST)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) by ietfa.amsl.com (Postfix) with ESMTP id EC7B121F886F for <ietf@ietf.org>; Fri, 25 Jan 2013 07:34:33 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id E73C2BE5A; Fri, 25 Jan 2013 15:34:11 +0000 (GMT)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qP8h9WZAsuMU; Fri, 25 Jan 2013 15:34:06 +0000 (GMT)
Received: from [IPv6:2001:770:10:203:810d:eba8:c654:6e65] (unknown [IPv6:2001:770:10:203:810d:eba8:c654:6e65]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 37B5DBE58; Fri, 25 Jan 2013 15:34:06 +0000 (GMT)
Message-ID: <5102A5ED.6050902@cs.tcd.ie>
Date: Fri, 25 Jan 2013 15:34:05 +0000
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130106 Thunderbird/17.0.2
MIME-Version: 1.0
To: John C Klensin <john-ietf@jck.com>
Subject: Re: FW: Last Call: <draft-farrell-ft-03.txt> (A Fast-Track way to RFC with Running Code) to Experimental RFC
References: <017001cdf017$c394df00$4abe9d00$@olddog.co.uk> <50FEC0B8.8060905@isi.edu> <201301222131.r0MLVK8C015116@cichlid.raleigh.ibm.com> <51028A77.2060808@cisco.com> <E2AC36AC55ED79756BE8929E@JcK-HP8200.jck.com>
In-Reply-To: <E2AC36AC55ED79756BE8929E@JcK-HP8200.jck.com>
X-Enigmail-Version: 1.5
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: Thomas Narten <narten@us.ibm.com>, adrian@olddog.co.uk, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 25 Jan 2013 15:34:34 -0000

On 01/25/2013 03:27 PM, John C Klensin wrote:
> In the context of draft-farrell-ft, the above makes the idea of
> WG LC in parallel with IETF LC either irrelevant or bad news.
> If the WG Chair (or AD) concludes that a WG LC is needed, then
> the procedure should not be invoked.  If a WG LC is not needed,
> then organizing things so that one is conducted in parallel with
> the IETF LC risks having two discussions going on in parallel
> with comments made to the WG list not being exposed to the
> community (remember the days when IETF LC comments were
> routinely sent to the IESG and not to the IETF list?).   And, if
> the WG does conduct a WG LC, the document can be read as
> forbidding use of the FT procedure to condense and set timelines
> on the rest of the process (something I'd suggest fixing if we
> are going to go ahead with this).

That's a fair point and I'd be open to incorporating
a change to make that better if we are going ahead
with the experiment. I'll add a pointer to this mail
to the working copy [1] in a bit.

> 
> All of this points out one of my main concerns.  Almost as a
> side-effect, the proposal formalizes a number of informal
> procedures and mechanisms work pretty well most of the time but,
> because they are informal, can be used flexibly without a big
> fuss.  If we are going to formalize them, we really should be
> asking questions about consensus, exception cases, and so on...
> and risk another several steps in the direction of trying to
> substitute procedures for judgment, responsibility, and
> accountability.

I disagree that doing an experiment formalises these things.
I do agree that more thought would be needed if the
experiment turned up something that we did want to make
permanent.

S.

[1] http://down.dsg.cs.tcd.ie/misc/draft-farrell-ft-04.txt



From john-ietf@jck.com  Fri Jan 25 07:45:55 2013
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ACC2021F8860 for <ietf@ietfa.amsl.com>; Fri, 25 Jan 2013 07:45:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.724
X-Spam-Level: 
X-Spam-Status: No, score=-102.724 tagged_above=-999 required=5 tests=[AWL=-0.125, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 n3ZsP5EIjFOt for <ietf@ietfa.amsl.com>; Fri, 25 Jan 2013 07:45:55 -0800 (PST)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 3628421F8884 for <ietf@ietf.org>; Fri, 25 Jan 2013 07:45:55 -0800 (PST)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1TylTU-000FR8-S9; Fri, 25 Jan 2013 10:45:52 -0500
Date: Fri, 25 Jan 2013 10:45:47 -0500
From: John C Klensin <john-ietf@jck.com>
To: Eliot Lear <lear@cisco.com>
Subject: Re: FW: Last Call: <draft-farrell-ft-03.txt> (A Fast-Track way to RFC with Running Code) to Experimental RFC
Message-ID: <CEC955279696EBA7E7C3AD96@JcK-HP8200.jck.com>
In-Reply-To: <5102A53A.8070206@cisco.com>
References: <017001cdf017$c394df00$4abe9d00$@olddog.co.uk> <50FEC0B8.8060905@isi.edu> <201301222131.r0MLVK8C015116@cichlid.raleigh.ibm.com> <51028A77.2060808@cisco.com> <E2AC36AC55ED79756BE8929E@JcK-HP8200.jck.com> <5102A53A.8070206@cisco.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Cc: Thomas Narten <narten@us.ibm.com>, adrian@olddog.co.uk, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 25 Jan 2013 15:45:55 -0000

--On Friday, January 25, 2013 16:31 +0100 Eliot Lear
<lear@cisco.com> wrote:

> John,
> 
> On 1/25/13 4:27 PM, John C Klensin wrote:
>>>> a WG can
>>>> skip WG LC if they think its not needed.
>>> ???
>>> 
>>> When was the last time that happened?  Did it require a
>>> consensus call to determine?
>> Chair discretion [... and five of paragraphs of text]
> 
> None of which answered my above questions.  When was the last
> time chairs USED that discretion?!

I didn't answer because I don't know.  It isn't something I've
tried to track and my first-hand experience is limited because
I've tried to avoid WG Chair roles in favor of advising for the
last decade or so.   The times when I didn't do a WG LC are both
long ago and probably before much of the community assumed they
were required.  We did short ones in EAI, not because they were
required but because we were trying to encourage additional
internal reviews and to verify that any issues that were missed
were identified.  But that WG was quite difficult in terms of
getting explicit reviews and discussion so WG LC was used as a
tool to address known problems.

   john




From john-ietf@jck.com  Fri Jan 25 08:37:37 2013
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 61B1C21F88E2 for <ietf@ietfa.amsl.com>; Fri, 25 Jan 2013 08:37:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.71
X-Spam-Level: 
X-Spam-Status: No, score=-102.71 tagged_above=-999 required=5 tests=[AWL=-0.111, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 d+zbOYUUwnu2 for <ietf@ietfa.amsl.com>; Fri, 25 Jan 2013 08:37:36 -0800 (PST)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 9B3B021F88D6 for <ietf@ietf.org>; Fri, 25 Jan 2013 08:37:36 -0800 (PST)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1TymHP-000FTh-An; Fri, 25 Jan 2013 11:37:27 -0500
Date: Fri, 25 Jan 2013 11:37:22 -0500
From: John C Klensin <john-ietf@jck.com>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Subject: Re: FW: Last Call: <draft-farrell-ft-03.txt> (A Fast-Track way to RFC with Running Code) to Experimental RFC
Message-ID: <80C0B979748114A8E9308A63@JcK-HP8200.jck.com>
In-Reply-To: <5102A5ED.6050902@cs.tcd.ie>
References: <017001cdf017$c394df00$4abe9d00$@olddog.co.uk> <50FEC0B8.8060905@isi.edu> <201301222131.r0MLVK8C015116@cichlid.raleigh.ibm.com> <51028A77.2060808@cisco.com> <E2AC36AC55ED79756BE8929E@JcK-HP8200.jck.com> <5102A5ED.6050902@cs.tcd.ie>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Cc: adrian@olddog.co.uk, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 25 Jan 2013 16:37:37 -0000

--On Friday, January 25, 2013 15:34 +0000 Stephen Farrell
<stephen.farrell@cs.tcd.ie> wrote:

>...
>> All of this points out one of my main concerns.  Almost as a
>> side-effect, the proposal formalizes a number of informal
>> procedures and mechanisms work pretty well most of the time
>> but, because they are informal, can be used flexibly without
>> a big fuss.  If we are going to formalize them, we really
>> should be asking questions about consensus, exception cases,
>> and so on... and risk another several steps in the direction
>> of trying to substitute procedures for judgment,
>> responsibility, and accountability.
> 
> I disagree that doing an experiment formalises these things.
> I do agree that more thought would be needed if the
> experiment turned up something that we did want to make
> permanent.

If I correctly understand the above, it lies at the root of the
problem I was trying to describe.  This is really an experiment
if the effect of deciding we didn't want to make it permanent
was that we were at status quo ante, i.e., as if the experiment
had never been initiated.  If the experimental procedure doesn't
turn out to be useful but we then need to rethink things that
have changed, then we are in rather different territory.   In
other language, if the worst possible consequence of this
proposed experiment would be a harmless waste of time, then a
number of us who are now expressing reservations or opposition
would be saying "ok, try it and let us know how it works out".

To the degree to which you can modify the document to be clear
than the experiment has no permanent procedural side-effects
whether it is judged to be a success or not, the specification
becomes more attractive.

As an example, Barry has initiated an experiment in a different
shepherd write-up regime that moves away from the "yes, I
checked this and yes, I checked that too" format and toward
narrative about notable points.   Because the shepherd write-up
format and requirements have never been part of a formal
procedure, that particular experiment could be initiated without
a big fuss (and, in particular, without a 3933 procedure). I
don't know if the requirements on shepherd write-ups in item 11
of Section 4 is compatible with Barry's template, would require
modifications to it, or would require use of some other template
if one intended to use the Fast Track procedure.  Nor do I know
whether having this provision would frustrate other experiments
with shepherd templates during the course of the experiment.

Similarly, this experiment is heavily dependent on retention of
the IESG's current voting categories and DISCUSS criteria.  Does
it prevent changing those categories and criteria during the
course of the experiment?  Does it give them a status they don't
now have (I think it does, YMMD) and, if it does so, does their
status revert at the end of the experiment?

I think you could add language to the document that would
clarify these things and either eliminate those concerns or
bring them more clearly into focus.

All of that said, I'm about to go back to lurking but want to
make a prediction about a likely outcome of this experiment
(assuming it is approved) that the document doesn't mention.  A
document is moved into this procedure and fast-tracked.  Someone
concludes, as Thomas, Brian, and others have suggested, that
some aspect of the procedure has frustrated adequate review and
that there are bad associated consequences.  They appeal on the
grounds that the things that this procedure shortcuts are
insufficient to ensure fairness given the things that the claim
that there is a running implementation doesn't demonstrate
(e.g., as others have suggested, while "cannot be implemented"
would certainly indicate there is something wrong with a spec,
"can be implemented" doesn't show that the spec is correct or
does what is wanted).   The moment that appeal is filed, the
document in question moves from "fast track" to the slowest
track of all.

    john






From davids@iit.edu  Thu Jan 24 20:56:22 2013
Return-Path: <davids@iit.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 06F0A21F8782 for <ietf@ietfa.amsl.com>; Thu, 24 Jan 2013 20:56:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.779
X-Spam-Level: *
X-Spam-Status: No, score=1.779 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_HOST_EQ_D_D_D_D=0.765, HTML_MESSAGE=0.001, IP_NOT_FRIENDLY=0.334, MIME_QP_LONG_LINE=1.396, RCVD_IN_PBL=0.905, RCVD_IN_SORBS_DUL=0.877, RDNS_DYNAMIC=0.1]
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 22tNskFKrhoQ for <ietf@ietfa.amsl.com>; Thu, 24 Jan 2013 20:56:18 -0800 (PST)
Received: from mail-ia0-x233.google.com (ia-in-x0233.1e100.net [IPv6:2607:f8b0:4001:c02::233]) by ietfa.amsl.com (Postfix) with ESMTP id 7096D21F8778 for <ietf@ietf.org>; Thu, 24 Jan 2013 20:56:17 -0800 (PST)
Received: by mail-ia0-f179.google.com with SMTP id x24so6036211iak.24 for <ietf@ietf.org>; Thu, 24 Jan 2013 20:56:17 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:user-agent:date:subject:from:to:message-id:thread-topic :in-reply-to:mime-version:content-type:x-gm-message-state; bh=TZHq01OEwBgyUCi8Pjmjb2rrnVqcG/vy/uEAn4nZN5U=; b=g31QE1iuinitwY0EoB6MKi0q29118964uP5FvlZBx2IJGefsXg2nAkyXovXMW9DbmR ZTgq7+AyLZENTM9m3k3yIOnBRvGH8nWO+nDGtM7h8UCltVqelUjJkuZzKa49uzpN4Bji 7BQWvsahl6E/Qp4nXJv8dyZcg3xc+u99Q02X2qTejzI5EbSIUuBndVeif+K5S+/LREe5 vIf5aee6ch2El2myTRvg92k/ESa2CeOU7Fdp1AEnZfkylHmAjfKxmXF1X8NB8TFv1I/h OU5GoUAP2mGo9JqH4x/u99o/A7zxx2K5ZQMkvLIwLUnOX4VoN+EWORgD549A7SlmX9jg rR1g==
X-Received: by 10.50.5.177 with SMTP id t17mr3160825igt.48.1359089776944; Thu, 24 Jan 2013 20:56:16 -0800 (PST)
Received: from [192.168.0.197] (c-67-184-3-189.hsd1.il.comcast.net. [67.184.3.189]) by mx.google.com with ESMTPS id l6sm3281091igw.10.2013.01.24.20.56.10 (version=TLSv1 cipher=RC4-SHA bits=128/128); Thu, 24 Jan 2013 20:56:15 -0800 (PST)
User-Agent: Microsoft-MacOutlook/14.2.5.121010
Date: Thu, 24 Jan 2013 22:56:07 -0600
Subject: Re: Last Call: <draft-ietf-bmwg-sip-bench-term-08.txt> (Terminology for Benchmarking Session Initiation Protocol (SIP) Networking Devices) to Informational RFC
From: Carol Davids <davids@iit.edu>
To: Robert Sparks <rjsparks@nostrum.com>, <ietf@ietf.org>, <draft-ietf-bmwg-sip-bench-term@tools.ietf.org>, <draft-ietf-bmwg-sip-bench-meth@tools.ietf.org>, <bmwg@ietf.org>
Message-ID: <CD2769FF.31306%davids@iit.edu>
Thread-Topic: Last Call: <draft-ietf-bmwg-sip-bench-term-08.txt> (Terminology for Benchmarking Session Initiation Protocol (SIP) Networking Devices) to Informational RFC
In-Reply-To: <51015BB3.7030406@nostrum.com>
Mime-version: 1.0
Content-type: multipart/alternative; boundary="B_3441912973_13556270"
X-Gm-Message-State: ALoCoQkTW96OWp0vfwaMfWHJCVBhdFSDwNjtLWyq24ErLlFRiR20RKeo1OErCk6Is3CTkEgKkTig
X-Mailman-Approved-At: Fri, 25 Jan 2013 08:47:52 -0800
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 25 Jan 2013 04:56:22 -0000

> This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

--B_3441912973_13556270
Content-type: text/plain;
	charset="US-ASCII"
Content-transfer-encoding: 7bit

Robert,

Thank you for your careful review and your detailed questions and comments.
We appreciate the time and effort.

Yours,

Carol

Carol Davids
Professor &  Director RTC Lab
Illinois Institute of Technology
Office: 630-682-6024
Mobile: 630-292-9417
Email: davids@iit.edu
Skype: caroldavids1
Web: rtc-lab.itm.iit.edu





From:  Robert Sparks <rjsparks@nostrum.com>
Date:  Thursday, January 24, 2013 10:05 AM
To:  <ietf@ietf.org>, <draft-ietf-bmwg-sip-bench-term@tools.ietf.org>,
<draft-ietf-bmwg-sip-bench-meth@tools.ietf.org>, "bmwg.ietf.org"
<bmwg@ietf.org>
Subject:  Re: Last Call: <draft-ietf-bmwg-sip-bench-term-08.txt>
(Terminology for Benchmarking Session Initiation Protocol (SIP) Networking
Devices) to Informational RFC
Resent-From:  <draft-alias-bounces@tools.ietf.org>
Resent-To:  Carol Davids <davids@iit.edu>, Scott Poretsky
<sporetsky@allot.com>, <vkg@bell-labs.com>
Resent-Date:  Thu, 24 Jan 2013 10:05:36 -0600 (CST)

    
 
  Reviews of draft-ietf-bmwg-sip-bench-term-08 and
draft-ietf-bmwg-sip-bench-meth-08
 
 Summary: These drafts are not ready for publication as RFCs.
 
 First, some of the text in these documents shows signs of being old, and
the
 working group may have been staring at them so long that they've become
hard to
 see.  The terminology document says "The issue of overload in SIP networks
is
 currently a topic of discussion in the SIPPING WG." (SIPPING was closed in
 2009). The methodology document suggests a "flooding" rate that is orders
of
 magnitude below what simple devices achieve at the moment. That these
survived
 working group last call indicates a different type of WG review may be
needed
 to groom other bugs out of the documents.
 
 Who is asking for these benchmarks, and are they (still) participating in
the
 group?  The measurements defined here are very simplistic and will provide
 limited insight into the relative performance of two elements in a real
 deployment. The documents should be clear about their limitations, and it
would
 be good to know that the community asking for these benchmarks is getting
tools
 that will actually be useful to them. The crux of these two documents is in
the
 last paragraph of the introduction to the methodology doc: "Finally, the
 overall value of these tests is to serve as a comparison function between
 multiple SIP implementations".  The documents punt on providing any
comparison
 guidance, but even if we assume someone can figure that out, do these
 benchmarks provide something actually useful for inputs?
 
 It would be good to explain how these documents relate to RFC6076.
 
 The terminology tries to refine the definition of session, but the
definition
 provided, "The combination of signaling and media messages and processes
that
 support a SIP-based service" doesn't answer what's in one session vs
another.
 Trying to generically define session has been hard and several working
groups
 have struggled with it (see INSIPID for a current version of that
 conversation). This document doesn't _need_ a generic definition of session
-
 it only needs to define the set of messages that it is measuring. It would
be
 much clearer to say "for the purposes of this document, as session is the
set
 of SIP messages associated with an INVITE initiated dialog and any
Associated
 Media, or a series of related SIP MESSAGE requests". (And looking at the
 benchmarks, you aren't leveraging related MESSAGE requests - they all
appear to
 be completely independent). Introducing the concepts of Invite-initiated
 sessions and non-invite-initiated sessions doesn't actually help define the
 metrics. When you get to the metrics, you can speak concretely in terms of
a
 series of INVITEs, REGISTERs, and MESSAGEs. Doing that, and providing a
short
 introduction pointing folks with PSTN backgrounds relating these to
"Session
 Attempts" will be clearer.
 
 To be clear, I strongly suggest a fundamental restructuring of the document
to
 describe the benchmarks in terms of dialogs and transactions, and remove
the IS
 and NS concepts completely.
 
 The INVITE related tests assume no provisional responses, leaving out the
 effect on a device's memory when the state machines it is maintaining
transition
 to the proceeding state. Further, by not including provisionals, and
building
 the tests to search for Timer B firing, the tests insure there will be
multiple
 retransmissions of the INVITE (when using UDP) that the device being tested
has
 to handle. The traffic an element has to handle and likely the memory it
will
 consume will be very different with even a single 100 trying, which is the
more
 usual case in deployed networks. The document should be clear _why_ it
chose
 the test model it did and left out metrics that took having a provisional
 response into account. Similarly, you are leaving out the delayed-offer
INVITE
 transactions used by 3pcc and it should be more obvious that you are doing
so.
 
 Likewise, the media oriented tests take a very basic approach to simulating
 media. It should be explicitly stated that you are simulating the effects
of a
 codec like G.711 and that you are assuming an element would only be
forwarding
 packets and has to do no transcoding work. It's not clear from the
documents
 whether the EA is generating actual media or dummy packets. If it's actual
 media, the test parameters that assume constant sized packets at a constant
 rate will not work well for video (and I suspect endpoints, like B2BUAs,
will
 terminate your call early if you send them garbage).
 
 The sections on a series of INVITEs is fairly clear that you mean each of
them
 to have different dialog identifiers.  I don't see any discussion of
varying
 the To: URI. If you don't, what's going to keep a gateway or B2BUA from
 rejecting all but the first with something like Busy? Similarly, I'm not
 finding where you talk about how many AoRs you are registering against in
the
 registration tests. I think, as written, someone could write this where all
the
 registers affected only one AoR.
 
 The methodology document calls Stress Testing out of scope, but the very
nature
 of the Benchmarking algorithm is a stress test. You are iteratively pushing
to
 see at what point something fails, _exactly_ by finding the rate of
attempted
 sessions per second that the thing under test would consider too high.
 
 Now to specific issues in document order, starting with the terminology
 document (nits are separate and at the end):
 
 * T (for Terminology document): The title and abstract are misleading -
this is
 not general benchmarking for SIP performance. You have a narrow set of
 tests, gathering metrics on a small subset of the protocol machinery.
 Please (as RFC 6076 did) look for a title that matches the scope of the
 document. For instance, someone testing a SIP Events server would be
ill-served
 with the benchmarks defined here.
 
 * T, section 1: RFC5393 should be a normative reference. You probably also
need
 to pull in RFCs 4320 and 6026 in general - they affect the state machines
you
 are measuring.
 
 * T, 3.1.1: As noted above, this definition of session is not useful. It
 doesn't provide any distinction between two different sessions. I strongly
 disagree that SIP reserves "session" to describe services analogous to
 telephone calls on a switched network - please provide a reference. SIP
INVITE
 transactions can pend forever - it is only the limited subset of the use of
 the transactions (where you don't use a provisional response) that keeps
this
 communication "brief". In the normal case, an INVITE an its final response
can
 be separated by an arbitrary amount of time. Instead of trying to tweak
this
 text, I suggest replacing all of it with simpler, more direct descriptions
of
 the sequence of messages you are using for the benchmarks you are defining
 here.
 
 *T, 3.1.1: How is this vector notion (and graph) useful for this document?
I
 don't see that it's actually used anywhere in the documents. Similarly, the
 arrays don't appear to be actually used (though you reference them from
some
 definitions) - What would be lost from the document if you simply removed
all
 this text?
 
 *T, 3.1.5, Discussion, last sentence: Why is it important to say "For
UA-type
 of network devices such as gateways, it is expected that the UA will be
driven
 into overload based on the volume of media streams it is processing." It's
not
 clear that's true for all such devices. How is saying anything here useful?
 
 *T, 3.1.6: This definition says an outstanding BYE or CANCEL is a Session
 Attempt. Why not just say INVITE? You aren't actually measuring "session
 attempts" for INVITEs or REGISTERs - you have separate benchmarks for them.
 
 *T, 3.1.7: It needs to be explicit that these benchmarks are not accounting
 for/allowing early dialogs.
 
 *T, 3.1.8: The words "early media" appear here for the first time. Given
the
 way the benchmarks are defined, does it make sense to discuss early media
in
 these documents at all (beyond noting you do not account for it)? If so,
 there needs to be much more clarity. (By the way, this Discussion will be
 much easier to write in terms of dialogs).
 
 *T, 3.1.9, Discussion point 2: What does "the media session is established"
 mean? If you leave this written as a generic definition, then is this when
an
 MSRP connection has been made? If you simplify it to the simple media model
 currently in the document, does it mean an RTP packet has been sent? Or
does it
 have to be received?. For the purposes of the benchmarks defined here, it
 doesn't seem to matter, so why have this as part of the discussion anyway?
 
 *T, 3.1.9, Definition: A series of CANCELs meets this definition.
 
 *T, 3.1.10 Discussion: This doesn't talk about 3xx responses, and they
aren't
 covered elsewhere in the document.
 
 *T, 3.1.11 Discussion: Isn't the MUST in this section methodology? Why is
it in
 this document and not -meth-?
 
 *T, 3.1.11 Discussion, next to last sentence: "measured by the number of
 distinct Call-IDs" means you are not supporting forking, or you would not
count
 answers from more than on leg of the fork as different sessions, like you
 should. Or are you intending that there would never be an answer from more
than
 one leg of a fork? If so, the documents need to be clearer about the
 methodology and what's actually being measured.
 
 *T, 3.2.2 Definition: There's something wrong with this definition. For
 example, proxies do not create sessions (or dialogs). Did you mean
"forwards
 messages between"?
 
 *T, 3.2.2 Discussion: This is definition by enumeration since it uses a
MUST,
 and is exclusive of any future things that might sit in the middle. If
that's
 what you want, make this the definition. The MAY seems contradictory unless
you
 are saying a B2BUA or SBC is just a specialized User Agent Server. If so,
 please say it that way.
 
 *T, 3.2.3: This seems out of place or under-explored.  You don't appear to
 actually _use_ this definition in the documents.You declare these things in
 scope, but the only consequence is the line in this section about the not
 lowering performance benchmarks when present. Consider making that part of
the
 methodology of a benchmark and removing this section. If you think it's
 essential, please revisit the definition - you may want to generalize it
into
 _anything_ that sits on the path and may affect SIP processing times
 (otherwise, what's special about this either being SIP Aware, or being a
 Firewall)?
 
 *T, 3.2.5 Definition: This definition just obfuscates things. Point to
3261's
 definition instead. How is TCP a measurement unit? Does the general
terminology
 template include "enumeration" as a type? Do you really want to limit this
 enumeration to the set of currently defined transports? Will you never run
 these benchmarks for SIP over websockets?
 
 *T, 3.3.2 Discussion: Again, there needs to be clarity about what it means
to
 "create" a media session. This description differentiates attempt vs
success,
 so what is it exactly that makes a media session attempt successful? When
you
 say number of media sessions, do you mean number of M lines or total number
of
 INVITEs that have SDP with m lines?
 
 *T, 3.3.3: This would much clearer written in terms of transactions and
dialogs
 (you are already diving into transaction state machine details). This is a
 place where the document needs to point out that it is not providing
benchmarks
 relevant to environments where provisionals are allowed to happen and
INVITE
 transactions are allowed to pend.
 
 *T, 3.3.4: How does this model (A single session duration separate from the
 media session hold time) produce useful benchmarks? Are you using it to
allow
 media to go beyond the termination of a call? If not, then you have media
only
 for the first part of a call? What real world thing does this reflect?
 Alternatively, what part of the device or system being benchmarked does
this
 provide insight to?
 
 *T, 3.3.5: The document needs to be honest about the limits of this simple
 model of media. It doesn't account for codecs that do not have constant
packet
 sizes. The benchmarks that use the model don't capture the differences
based on
 content of the media being sent - a B2BUA or gateway, may will behave
 differently if it is transcoding or doing content processing (such as DTMF
 detection) than it will if it is just shoveling packets without looking at
 them.
 
 *T, 3.3.6: Again, the model here is that any two media packets present the
same
 load to the thing under test. That's not true for transcoding, mixing, or
 analysis (such as for dtmf detection). It's not clear that if you have two
 streams, each stream has its own "constant rate". You call out having one
audio
 and one video stream - how do you configure different rates for them?
 
 *T, 3.3.7: This document points to the methodology document for indicating
 whether streams are bi-directional or uni-directional. I cant find where
the
 methodology document talks about this (the string 'direction' does not
 occur in that document).
 
 *T, 3.3.8: This text is old - it was probably written pre-RFC5056. If you
fork,
 loop detection is not optional. This, and the methodology document should
be
 updated to take that into account.
 
 *T, 3.3.9: Clarify if more than one leg of a fork can be answered
successfully
 and update 3.1.11 accordingly. Talk about how this affects the success
 benchmarks (how will the other legs getting failure responses affect the
 scores?)
 
 *T, 3.3.9, Measurement units: There is confusion here. The unit is probably
 "endpoints". This section talks about two things, that, and type of
forking.
 How is "type of forking" a unit, and are these templates supposed to allow
more
 than one unit for a term?
 
 *T, 3.4.2, Definition: It's not clear what "successfully completed" means.
Did
 you mean "successfully established"? This is a place where speaking in
terms of
 dialogs and transactions rather than sessions will be much clearer.
 
 *T, 3.4.3, This benchmark metric is underdefined. I'll focus on that in the
 context of the methodology document (where the docs come closer to defining
it).
 This definition includes a variable T but doesn't explain it - you have to
read
 the methodology to know what T is all about. You might just say "for the
 duration of the test" or whatever is actually correct.
 
 *T, 3.4.3, Discussion: "Media Session Hold Time MUST be set to infinity".
Why?
 The argument you give in the next sentence just says the media session hold
 time has to be at least as long as the session duration. If they were
equal,
 and finite, the test result does not change. What's the utility of the
infinity
 concept here?
 
 *T, 3.4.4: "until it stops responding". Any non-200 response is still a
 response, and if something sends a 503 or 4xx with a retry-after (which is
 likely when it's truly saturating) you've hit the condition you are trying
to
 find. The notion that the Overload Capacity is measurable by not getting
any
 responses at all is questionable.  This discussion has a lot of methodology
in
 it - why isn't that (only) in the methodology document?
 
 *T, 3.4.5: A normal, fully correct system that challenged requests and
 performed flawlessly would have a .5 Session Establishment Performance
score.
 Is that what you intended? The SHOULD in this section looks like
methodology.
 Why is this a SHOULD and not a MUST (the document should be clearer about
why
 sessions remaining established is important). Or wait - is this what Note 2
in
 section 5.1 of the methodology document (which talks about reporting
formats)
 is supposed to change? If so, that needs to be moved to the actual
methodology
 and made _much_ clearer.
 
 *T, 3.4.6: You talk of the first non-INVITE in an NS. How are you
 distinguishing subsequent non-INVITES in this NS from requests in some
other
 NS? Are you using dialog identifiers or something else? Why do you expect
that
 to matter (why is the notion of a sequence of related non-INVITEs useful
from a
 benchmarking perspective - there isn't state kept in intermediaries because
of
 them - what will make this metric distinguishable from a metric that just
 focuses on the transactions?)
 
 *T, 3.4.7: What's special about MESSAGE? Why aren't you focusing on INFO or
 some other end-to-end non-INVITE? I suspect it's because you are wanting to
 focus on a simple non-INVITE transaction (which is why you are leaving out
 SUBSCRIBE/NOTIFY). MESSAGE is good enough for that, but you should be clear
 that's why you chose it. You should also talk about whether the payload of
all
 of the MESSAGE requests are the same size and whether that size is a
parameter
 to the benchmark. (You'll likely get very different behavior from a MESSAGE
 that fragments.) 
 
 *T, 3.4.7: The definition says "messages completed" but the discussion
talks
 about "definition of success". Does success mean an IM transaction
completed
 successfully?  If so, the definition of success for a UAC has a problem. As
 written, it describes a binary outcome for the whole test, not how to
determine
 the success of an individual transaction - how do you get from what it
 describes to a rate?
 
 *T, Appendix A: The document should better motivate why this is here.
 Why does it mention SUBSCRIBE/NOTIFY when the rest of the document(s) are
 silent on them.  The discussion says you are _selecting_ a Session Attempts
 Arrival Rate distribution. It would be clearer to say you are selecting the
 distribution of messages sent from the EA. It's not clear how this
particular
 metric will benefit from different sending distributions.
 
 Now the Methodology document (comments prefixed with an M):
 
 *M, Introduction: Can the document say why the subset of functionality
 benchmarked here was chosen over other subsets? Why was Subscribe/Notify or
 Info not included (or invites with MSRP or even simple early media, etc)?
 
 *M, Introduction paragraph 4: This points to section 4 and section 2 of the
 terminology document for configuration options. Section 4 is the iana
 considerations section (which has no options). What did you mean to point
to?
 
 *M, Introduction paragraph 4, last sentence: This seems out of place - why
is
 it in the introduction and not in a section on that specific methodology.
 
 *M, 4.1: It's not clear here, or in the methodology sections whether the
tests
 allow the transport to change as you go across an intermediary. Do you
intend
 to be able to benchmark a proxy that has TCP on one side and UDP on the
other?
 
 *M, 4.2: This is another spot where pointing to the Updates to 3261 that
change
 the transaction state machines is important.
 
 *M, 4.4: Did you really mean RTSP? Maybe you meant MSRP or something else?
RTSP
 is not, itself, a media protocol.
 
 *M, 4.9: There's something wrong with this sentence: "This test is run for
an
 extended period of time, which is referred to as infinity, and which is,
 itself, a parameter of the test labeled T in the pseudo-code". What value
is
 there in giving some finite parameter T the name "infinity"?
 
 *M, 4.9: Where did 100 (as an initial value for s) come from? Modern
devices
 process at many orders of magnitude higher rates than that. Do you want to
 provide guidance instead of an absolute number here?
 
 *M 4.9: In the pseudo-code, you often say "the largest value". It would
help to
 say the the largest value of _what_.
 
 *M 4.9: What is the "steady_state" function called in the pseudo-code?
 
 *M 6.3: Expected Results: The EA will have different performance
 characteristics if you have them sending media or not. That could cause
this
 metric to be different from session establishment without media.
 
 *M 6.5: This section should call out that loop detection is not optional
when
 forking. The Expected Results description is almost tautological - could it
 instead say how having this measurement is _useful_ to those consuming this
 benchmark?
 
 *M 6.8, Procedure: Why is "May need to run for each transport of interest."
in
 a section titled "Session Establishement Rate with TLS Encrypted SIP"?
 
 *M 6.10: This document doesn't define Flooding. What do you mean? How is
this
 different than "Stress test" as called out in section 4.8? Where does 500
come
 from?  (Again, I suspect that's a very old value - and you should be
providing
 guidance rather than an absolute number). But it's not clear how this isn't
 just the session establishment rate test that just starts with a bigger
number.
 What is it actually trying to report on that's different from the session
 establishment rate test, and how is the result useful?
 
 *M 6.11: Is each registration going to a different AoR? (You must be, or
the
 re-registration test makes no sense.) You might talk about configuring the
 registrar and the EA so they know what to use.
 
 *M 6.12, Expected Results: Where do you get the idea that re-registration
 should be faster than initial registration? How is knowing the difference
(or
 even that there is a difference) between this and the registration metric
 likely to be useful to the consumer?
 
 *M 6.14: Session Capacity, as defined in the terminology doc, is a count of
 sessions, not a rate. This section treats it as a rate and says it can be
 interpreted as "throughput". I'm struggling to see what it actually is
 measuring. The way your algorithm is defined in section 4.9, I find s
before I
 use T. Lets say I've got a box where the value of s that's found is 10000,
and
 I've got enough memory that I can deal with several large values of T. If I
run
 this test with T of 50000, my benchmark result is 500,000,000. If I run
with a
 T of 100000, my benchmark result is 1,000,000,000. How are those numbers
 telling me _anything_ about session capacity. That the _real_ session
capacity
 is at least that much? Is there some part of this methodology that has me
hunt
 for a maximal value of T? Unless I've missed something, this metric needs
more
 clarification to not be completely misleading. Maybe instead of "Session
 Capacity" you should simply be reporting "Simultaneous Sessions Measured"
 
 *M 8: "and various other drafts" is not helpful - if you know of other
 important documents to point to, point to them.
 
 Nits:
 
 T : The definition of Stateful Proxy and Stateless Proxy copied the words
 "defined by this specification" from RFC3261. This literal copy introduces
 confusion. Can you make it more visually obvious you are quoting? And even
if
 you do, could you replace "by this specification" with "by [RFC3261]"?
 
 T, Introduction, 2nd paragraph, last sentence: This rules out stateless
 proxies.
 
 T, Section 3: In the places where this template is used, you are careful to
say
 None under Issues when there aren't any, but not so careful to say None
under
 See Also when there isn't anything. Leaving them blank makes some
transitions
 hard to read - they read like you are saying see also (whatever the next
 section heading is).
 
 T, 3.1.6, Discussion: s/tie interval/time interval/
 
 M, Introduction, paragraph 2: You say "any [RFC3261] conforming device",
but
 you've ruled endpoint UAs out in other parts of the documents.
 
 M 4.9: You have comments explaining send_traffic the _second_ time you use
it.
 They would be better positioned at the first use.
 
 M 5.2: This is the first place the concept of re-Registration is mentioned.
A
 forward pointer to what you mean, or an introduction before you get to this
 format would be clearer.
 
 
 On 1/16/13 3:48 PM, The IESG wrote:
 
 
>  
> The IESG has received a request from the Benchmarking Methodology WG
> (bmwg) to consider the following document:
> - 'Terminology for Benchmarking Session Initiation Protocol (SIP)
>    Networking Devices'
>   <draft-ietf-bmwg-sip-bench-term-08.txt> as Informational RFC
> 
> The IESG plans to make a decision in the next few weeks, and solicits
> final comments on this action. Please send substantive comments to the
> ietf@ietf.org mailing lists by 2013-01-30. Exceptionally, comments may be
> sent to iesg@ietf.org instead. In either case, please retain the
> beginning of the Subject line to allow automated sorting.
> 
> Abstract
> 
> 
>    This document provides a terminology for benchmarking the SIP
>    performance of networking devices.  The term performance in this
>    context means the capacity of the device- or system-under-test to
>    process SIP messages.  Terms are included for test components, test
>    setup parameters, and performance benchmark metrics for black-box
>    benchmarking of SIP networking devices.  The performance benchmark
>    metrics are obtained for the SIP signaling plane only.  The terms are
>    intended for use in a companion methodology document for
>    characterizing the performance of a SIP networking device under a
>    variety of conditions.  The intent of the two documents is to enable
>    a comparison of the capacity of SIP networking devices.  Test setup
>    parameters and a methodology document are necessary because SIP
>    allows a wide range of configuration and operational conditions that
>    can influence performance benchmark measurements.  A standard
>    terminology and methodology will ensure that benchmarks have
>    consistent definition and were obtained following the same
>    procedures.
> 
> 
> 
> 
> The file can be obtained via
> http://datatracker.ietf.org/doc/draft-ietf-bmwg-sip-bench-term/
> 
> IESG discussion can be tracked via
> http://datatracker.ietf.org/doc/draft-ietf-bmwg-sip-bench-term/ballot/
> 
> 
> No IPR declarations have been submitted directly on this I-D.
> 
> 
>  
 
 



--B_3441912973_13556270
Content-type: text/html;
	charset="US-ASCII"
Content-transfer-encoding: quoted-printable

<html><head></head><body style=3D"word-wrap: break-word; -webkit-nbsp-mode: s=
pace; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size:=
 16px; font-family: Calibri, sans-serif; "><div><div><div>Robert,</div><div>=
<br></div><div>Thank you for your careful review and your detailed questions=
 and comments. We appreciate the time and effort. &nbsp;</div><div><br></div=
><div>Yours,</div><div><br></div><div>Carol</div><div><br></div><div><div st=
yle=3D"font-family: Calibri, sans-serif; "><font class=3D"Apple-style-span" colo=
r=3D"rgb(0, 0, 0)"><font class=3D"Apple-style-span" face=3D"Calibri"><span class=3D"=
Apple-style-span" style=3D"font-size: 14px; ">Carol Davids</span></font></font=
></div><div style=3D"font-family: Calibri, sans-serif; "><font class=3D"Apple-st=
yle-span" color=3D"rgb(0, 0, 0)"><font class=3D"Apple-style-span" face=3D"Calibri"=
><span class=3D"Apple-style-span" style=3D"font-size: 14px;">Professor &amp; &nb=
sp;</span></font></font><span class=3D"Apple-style-span" style=3D"font-family: C=
alibri; ">Director RTC Lab</span></div><div style=3D"font-family: Calibri, san=
s-serif; "><span class=3D"Apple-style-span" style=3D"font-family: Calibri; ">Ill=
inois Institute of Technology</span></div><div style=3D"font-family: Calibri, =
sans-serif; "><span class=3D"Apple-style-span" style=3D"font-family: Calibri; ">=
Office: 630-682-6024</span></div><div style=3D"font-family: Calibri, sans-seri=
f; "><span class=3D"Apple-style-span" style=3D"font-family: Calibri; ">Mobile: 6=
30-292-9417</span></div><div style=3D"font-family: Calibri, sans-serif; "><spa=
n class=3D"Apple-style-span" style=3D"font-family: Calibri; ">Email: davids@iit.=
edu</span></div><div style=3D"font-family: Calibri, sans-serif; "><span class=3D=
"Apple-style-span" style=3D"font-family: Calibri; ">Skype: caroldavids1</span>=
</div><div style=3D"font-family: Calibri, sans-serif; "><span class=3D"Apple-sty=
le-span" style=3D"font-family: Calibri; ">Web: rtc-lab</span><span class=3D"Appl=
e-style-span" style=3D"font-family: Calibri; ">.itm.iit.edu</span></div><div s=
tyle=3D"font-family: Calibri, sans-serif; "><br></div><div style=3D"font-family:=
 Calibri, sans-serif; "><br></div><div style=3D"font-family: Calibri, sans-ser=
if; "><span class=3D"Apple-style-span" style=3D"font-family: Calibri; "><br></sp=
an></div><div style=3D"font-family: Calibri, sans-serif; "><font class=3D"Apple-=
style-span" color=3D"rgb(0, 0, 0)"><font class=3D"Apple-style-span" face=3D"Calibr=
i"><span class=3D"Apple-style-span" style=3D"font-size: 14px;"><br></span></font=
></font></div></div></div></div><div><br></div><span id=3D"OLK_SRC_BODY_SECTIO=
N"><div style=3D"font-family:Calibri; font-size:11pt; text-align:left; color:b=
lack; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: =
0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; B=
ORDER-RIGHT: medium none; PADDING-TOP: 3pt"><span style=3D"font-weight:bold">F=
rom: </span> Robert Sparks &lt;<a href=3D"mailto:rjsparks@nostrum.com">rjspark=
s@nostrum.com</a>&gt;<br><span style=3D"font-weight:bold">Date: </span> Thursd=
ay, January 24, 2013 10:05 AM<br><span style=3D"font-weight:bold">To: </span> =
&lt;<a href=3D"mailto:ietf@ietf.org">ietf@ietf.org</a>&gt;, &lt;<a href=3D"mailt=
o:draft-ietf-bmwg-sip-bench-term@tools.ietf.org">draft-ietf-bmwg-sip-bench-t=
erm@tools.ietf.org</a>&gt;, &lt;<a href=3D"mailto:draft-ietf-bmwg-sip-bench-me=
th@tools.ietf.org">draft-ietf-bmwg-sip-bench-meth@tools.ietf.org</a>&gt;, "b=
mwg.ietf.org" &lt;<a href=3D"mailto:bmwg@ietf.org">bmwg@ietf.org</a>&gt;<br><s=
pan style=3D"font-weight:bold">Subject: </span> Re: Last Call: &lt;draft-ietf-=
bmwg-sip-bench-term-08.txt&gt; (Terminology for Benchmarking Session Initiat=
ion Protocol (SIP) Networking Devices) to Informational RFC<br><span style=3D"=
font-weight:bold">Resent-From: </span> &lt;<a href=3D"mailto:draft-alias-bounc=
es@tools.ietf.org">draft-alias-bounces@tools.ietf.org</a>&gt;<br><span style=
=3D"font-weight:bold">Resent-To: </span> Carol Davids &lt;<a href=3D"mailto:davi=
ds@iit.edu">davids@iit.edu</a>&gt;, Scott Poretsky &lt;<a href=3D"mailto:spore=
tsky@allot.com">sporetsky@allot.com</a>&gt;, &lt;<a href=3D"mailto:vkg@bell-la=
bs.com">vkg@bell-labs.com</a>&gt;<br><span style=3D"font-weight:bold">Resent-D=
ate: </span> Thu, 24 Jan 2013 10:05:36 -0600 (CST)<br></div><div><br></div><=
div>
  
    <meta content=3D"text/html; charset=3DISO-8859-1" http-equiv=3D"Content-Type"=
>
  
  <div bgcolor=3D"#FFFFFF" text=3D"#000000">
    <div class=3D"moz-cite-prefix">
      <meta http-equiv=3D"content-type" content=3D"text/html;
        charset=3DISO-8859-1">
      Reviews of draft-ietf-bmwg-sip-bench-term-08 and
      draft-ietf-bmwg-sip-bench-meth-08<br>
      <br>
      Summary: These drafts are not ready for publication as RFCs.<br>
      <br>
      First, some of the text in these documents shows signs of being
      old, and the<br>
      working group may have been staring at them so long that they've
      become hard to<br>
      see.&nbsp; The terminology document says "The issue of overload in SI=
P
      networks is<br>
      currently a topic of discussion in the SIPPING WG." (SIPPING was
      closed in<br>
      2009). The methodology document suggests a "flooding" rate that is
      orders of<br>
      magnitude below what simple devices achieve at the moment. That
      these survived<br>
      working group last call indicates a different type of WG review
      may be needed<br>
      to groom other bugs out of the documents.<br>
      <br>
      Who is asking for these benchmarks, and are they (still)
      participating in the<br>
      group?&nbsp; The measurements defined here are very simplistic and wi=
ll
      provide <br>
      limited insight into the relative performance of two elements in a
      real<br>
      deployment. The documents should be clear about their limitations,
      and it would<br>
      be good to know that the community asking for these benchmarks is
      getting tools<br>
      that will actually be useful to them. The crux of these two
      documents is in the<br>
      last paragraph of the introduction to the methodology doc:
      "Finally, the<br>
      overall value of these tests is to serve as a comparison function
      between<br>
      multiple SIP implementations".&nbsp; The documents punt on providing
      any comparison<br>
      guidance, but even if we assume someone can figure that out, do
      these<br>
      benchmarks provide something actually useful for inputs?<br>
      <br>
      It would be good to explain how these documents relate to RFC6076.<br=
>
      <br>
      The terminology tries to refine the definition of session, but the
      definition<br>
      provided, "The combination of signaling and media messages and
      processes that<br>
      support a SIP-based service" doesn't answer what's in one session
      vs another.<br>
      Trying to generically define session has been hard and several
      working groups<br>
      have struggled with it (see INSIPID for a current version of that<br>=

      conversation). This document doesn't _need_ a generic definition
      of session -<br>
      it only needs to define the set of messages that it is measuring.
      It would be<br>
      much clearer to say "for the purposes of this document, as session
      is the set<br>
      of SIP messages associated with an INVITE initiated dialog and any
      Associated<br>
      Media, or a series of related SIP MESSAGE requests". (And looking
      at the<br>
      benchmarks, you aren't leveraging related MESSAGE requests - they
      all appear to<br>
      be completely independent). Introducing the concepts of
      Invite-initiated<br>
      sessions and non-invite-initiated sessions doesn't actually help
      define the<br>
      metrics. When you get to the metrics, you can speak concretely in
      terms of a<br>
      series of INVITEs, REGISTERs, and MESSAGEs. Doing that, and
      providing a short<br>
      introduction pointing folks with PSTN backgrounds relating these
      to "Session<br>
      Attempts" will be clearer. <br>
      <br>
      To be clear, I strongly suggest a fundamental restructuring of the
      document to<br>
      describe the benchmarks in terms of dialogs and transactions, and
      remove the IS<br>
      and NS concepts completely.<br>
      <br>
      The INVITE related tests assume no provisional responses, leaving
      out the<br>
      effect on a device's memory when the state machines it is
      maintaining transition<br>
      to the proceeding state. Further, by not including provisionals,
      and building<br>
      the tests to search for Timer B firing, the tests insure there
      will be multiple<br>
      retransmissions of the INVITE (when using UDP) that the device
      being tested has<br>
      to handle. The traffic an element has to handle and likely the
      memory it will<br>
      consume will be very different with even a single 100 trying,
      which is the more<br>
      usual case in deployed networks. The document should be clear
      _why_ it chose<br>
      the test model it did and left out metrics that took having a
      provisional<br>
      response into account. Similarly, you are leaving out the
      delayed-offer INVITE<br>
      transactions used by 3pcc and it should be more obvious that you
      are doing so.<br>
      <br>
      Likewise, the media oriented tests take a very basic approach to
      simulating<br>
      media. It should be explicitly stated that you are simulating the
      effects of a<br>
      codec like G.711 and that you are assuming an element would only
      be forwarding<br>
      packets and has to do no transcoding work. It's not clear from the
      documents<br>
      whether the EA is generating actual media or dummy packets. If
      it's actual<br>
      media, the test parameters that assume constant sized packets at a
      constant<br>
      rate will not work well for video (and I suspect endpoints, like
      B2BUAs, will<br>
      terminate your call early if you send them garbage).<br>
      <br>
      The sections on a series of INVITEs is fairly clear that you mean
      each of them<br>
      to have different dialog identifiers.&nbsp; I don't see any discussio=
n
      of varying<br>
      the To: URI. If you don't, what's going to keep a gateway or B2BUA
      from<br>
      rejecting all but the first with something like Busy? Similarly,
      I'm not<br>
      finding where you talk about how many AoRs you are registering
      against in the<br>
      registration tests. I think, as written, someone could write this
      where all the<br>
      registers affected only one AoR.<br>
      <br>
      The methodology document calls Stress Testing out of scope, but
      the very nature<br>
      of the Benchmarking algorithm is a stress test. You are
      iteratively pushing to<br>
      see at what point something fails, _exactly_ by finding the rate
      of attempted<br>
      sessions per second that the thing under test would consider too
      high.<br>
      <br>
      Now to specific issues in document order, starting with the
      terminology<br>
      document (nits are separate and at the end):<br>
      <br>
      * T (for Terminology document): The title and abstract are
      misleading - this is<br>
      not general benchmarking for SIP performance. You have a narrow
      set of<br>
      tests, gathering metrics on a small subset of the protocol
      machinery.<br>
      Please (as RFC 6076 did) look for a title that matches the scope
      of the<br>
      document. For instance, someone testing a SIP Events server would
      be ill-served<br>
      with the benchmarks defined here.<br>
      <br>
      * T, section 1: RFC5393 should be a normative reference. You
      probably also need<br>
      to pull in RFCs 4320 and 6026 in general - they affect the state
      machines you<br>
      are measuring.<br>
      <br>
      * T, 3.1.1: As noted above, this definition of session is not
      useful. It<br>
      doesn't provide any distinction between two different sessions. I
      strongly<br>
      disagree that SIP reserves "session" to describe services
      analogous to<br>
      telephone calls on a switched network - please provide a
      reference. SIP INVITE<br>
      transactions can pend forever - it is only the limited subset of
      the use of<br>
      the transactions (where you don't use a provisional response) that
      keeps this<br>
      communication "brief". In the normal case, an INVITE an its final
      response can<br>
      be separated by an arbitrary amount of time. Instead of trying to
      tweak this<br>
      text, I suggest replacing all of it with simpler, more direct
      descriptions of<br>
      the sequence of messages you are using for the benchmarks you are
      defining<br>
      here.<br>
      <br>
      *T, 3.1.1: How is this vector notion (and graph) useful for this
      document? I<br>
      don't see that it's actually used anywhere in the documents.
      Similarly, the<br>
      arrays don't appear to be actually used (though you reference them
      from some<br>
      definitions) - What would be lost from the document if you simply
      removed all<br>
      this text?<br>
      <br>
      *T, 3.1.5, Discussion, last sentence: Why is it important to say
      "For UA-type<br>
      of network devices such as gateways, it is expected that the UA
      will be driven<br>
      into overload based on the volume of media streams it is
      processing." It's not<br>
      clear that's true for all such devices. How is saying anything
      here useful?<br>
      <br>
      *T, 3.1.6: This definition says an outstanding BYE or CANCEL is a
      Session<br>
      Attempt. Why not just say INVITE? You aren't actually measuring
      "session<br>
      attempts" for INVITEs or REGISTERs - you have separate benchmarks
      for them.<br>
      <br>
      *T, 3.1.7: It needs to be explicit that these benchmarks are not
      accounting<br>
      for/allowing early dialogs.<br>
      <br>
      *T, 3.1.8: The words "early media" appear here for the first time.
      Given the<br>
      way the benchmarks are defined, does it make sense to discuss
      early media in<br>
      these documents at all (beyond noting you do not account for it)?
      If so, <br>
      there needs to be much more clarity. (By the way, this Discussion
      will be <br>
      much easier to write in terms of dialogs).<br>
      <br>
      *T, 3.1.9, Discussion point 2: What does "the media session is
      established"<br>
      mean? If you leave this written as a generic definition, then is
      this when an<br>
      MSRP connection has been made? If you simplify it to the simple
      media model<br>
      currently in the document, does it mean an RTP packet has been
      sent? Or does it<br>
      have to be received?. For the purposes of the benchmarks defined
      here, it<br>
      doesn't seem to matter, so why have this as part of the discussion
      anyway?<br>
      <br>
      *T, 3.1.9, Definition: A series of CANCELs meets this definition.
      <br>
      <br>
      *T, 3.1.10 Discussion: This doesn't talk about 3xx responses, and
      they aren't<br>
      covered elsewhere in the document.<br>
      <br>
      *T, 3.1.11 Discussion: Isn't the MUST in this section methodology?
      Why is it in<br>
      this document and not -meth-?<br>
      <br>
      *T, 3.1.11 Discussion, next to last sentence: "measured by the
      number of<br>
      distinct Call-IDs" means you are not supporting forking, or you
      would not count<br>
      answers from more than on leg of the fork as different sessions,
      like you<br>
      should. Or are you intending that there would never be an answer
      from more than<br>
      one leg of a fork? If so, the documents need to be clearer about
      the<br>
      methodology and what's actually being measured. <br>
      <br>
      *T, 3.2.2 Definition: There's something wrong with this
      definition. For<br>
      example, proxies do not create sessions (or dialogs). Did you mean
      "forwards<br>
      messages between"?<br>
      <br>
      *T, 3.2.2 Discussion: This is definition by enumeration since it
      uses a MUST,<br>
      and is exclusive of any future things that might sit in the
      middle. If that's<br>
      what you want, make this the definition. The MAY seems
      contradictory unless you<br>
      are saying a B2BUA or SBC is just a specialized User Agent Server.
      If so,<br>
      please say it that way.<br>
      <br>
      *T, 3.2.3: This seems out of place or under-explored.&nbsp; You don't=

      appear to<br>
      actually _use_ this definition in the documents.You declare these
      things in<br>
      scope, but the only consequence is the line in this section about
      the not<br>
      lowering performance benchmarks when present. Consider making that
      part of the<br>
      methodology of a benchmark and removing this section. If you think
      it's<br>
      essential, please revisit the definition - you may want to
      generalize it into<br>
      _anything_ that sits on the path and may affect SIP processing
      times<br>
      (otherwise, what's special about this either being SIP Aware, or
      being a<br>
      Firewall)?<br>
      <br>
      *T, 3.2.5 Definition: This definition just obfuscates things.
      Point to 3261's<br>
      definition instead. How is TCP a measurement unit? Does the
      general terminology<br>
      template include "enumeration" as a type? Do you really want to
      limit this<br>
      enumeration to the set of currently defined transports? Will you
      never run<br>
      these benchmarks for SIP over websockets?<br>
      <br>
      *T, 3.3.2 Discussion: Again, there needs to be clarity about what
      it means to<br>
      "create" a media session. This description differentiates attempt
      vs success,<br>
      so what is it exactly that makes a media session attempt
      successful? When you<br>
      say number of media sessions, do you mean number of M lines or
      total number of<br>
      INVITEs that have SDP with m lines?<br>
      <br>
      *T, 3.3.3: This would much clearer written in terms of
      transactions and dialogs<br>
      (you are already diving into transaction state machine details).
      This is a<br>
      place where the document needs to point out that it is not
      providing benchmarks<br>
      relevant to environments where provisionals are allowed to happen
      and INVITE<br>
      transactions are allowed to pend.<br>
      <br>
      *T, 3.3.4: How does this model (A single session duration separate
      from the<br>
      media session hold time) produce useful benchmarks? Are you using
      it to allow<br>
      media to go beyond the termination of a call? If not, then you
      have media only<br>
      for the first part of a call? What real world thing does this
      reflect?<br>
      Alternatively, what part of the device or system being benchmarked
      does this<br>
      provide insight to? <br>
      <br>
      *T, 3.3.5: The document needs to be honest about the limits of
      this simple<br>
      model of media. It doesn't account for codecs that do not have
      constant packet<br>
      sizes. The benchmarks that use the model don't capture the
      differences based on<br>
      content of the media being sent - a B2BUA or gateway, may will
      behave<br>
      differently if it is transcoding or doing content processing (such
      as DTMF<br>
      detection) than it will if it is just shoveling packets without
      looking at<br>
      them.<br>
      <br>
      *T, 3.3.6: Again, the model here is that any two media packets
      present the same<br>
      load to the thing under test. That's not true for transcoding,
      mixing, or<br>
      analysis (such as for dtmf detection). It's not clear that if you
      have two<br>
      streams, each stream has its own "constant rate". You call out
      having one audio<br>
      and one video stream - how do you configure different rates for
      them?<br>
      <br>
      *T, 3.3.7: This document points to the methodology document for
      indicating<br>
      whether streams are bi-directional or uni-directional. I cant find
      where the<br>
      methodology document talks about this (the string 'direction' does
      not<br>
      occur in that document).<br>
      <br>
      *T, 3.3.8: This text is old - it was probably written pre-RFC5056.
      If you fork,<br>
      loop detection is not optional. This, and the methodology document
      should be<br>
      updated to take that into account.<br>
      <br>
      *T, 3.3.9: Clarify if more than one leg of a fork can be answered
      successfully<br>
      and update 3.1.11 accordingly. Talk about how this affects the
      success<br>
      benchmarks (how will the other legs getting failure responses
      affect the<br>
      scores?)<br>
      <br>
      *T, 3.3.9, Measurement units: There is confusion here. The unit is
      probably<br>
      "endpoints". This section talks about two things, that, and type
      of forking.<br>
      How is "type of forking" a unit, and are these templates supposed
      to allow more<br>
      than one unit for a term?<br>
      <br>
      *T, 3.4.2, Definition: It's not clear what "successfully
      completed" means. Did<br>
      you mean "successfully established"? This is a place where
      speaking in terms of<br>
      dialogs and transactions rather than sessions will be much
      clearer.<br>
      <br>
      *T, 3.4.3, This benchmark metric is underdefined. I'll focus on
      that in the<br>
      context of the methodology document (where the docs come closer to
      defining it).<br>
      This definition includes a variable T but doesn't explain it - you
      have to read<br>
      the methodology to know what T is all about. You might just say
      "for the<br>
      duration of the test" or whatever is actually correct.<br>
      <br>
      *T, 3.4.3, Discussion: "Media Session Hold Time MUST be set to
      infinity". Why?<br>
      The argument you give in the next sentence just says the media
      session hold<br>
      time has to be at least as long as the session duration. If they
      were equal,<br>
      and finite, the test result does not change. What's the utility of
      the infinity<br>
      concept here?<br>
      <br>
      *T, 3.4.4: "until it stops responding". Any non-200 response is
      still a<br>
      response, and if something sends a 503 or 4xx with a retry-after
      (which is<br>
      likely when it's truly saturating) you've hit the condition you
      are trying to<br>
      find. The notion that the Overload Capacity is measurable by not
      getting any<br>
      responses at all is questionable.&nbsp; This discussion has a lot of
      methodology in<br>
      it - why isn't that (only) in the methodology document? <br>
      <br>
      *T, 3.4.5: A normal, fully correct system that challenged requests
      and<br>
      performed flawlessly would have a .5 Session Establishment
      Performance score.<br>
      Is that what you intended? The SHOULD in this section looks like
      methodology.<br>
      Why is this a SHOULD and not a MUST (the document should be
      clearer about why<br>
      sessions remaining established is important). Or wait - is this
      what Note 2 in<br>
      section 5.1 of the methodology document (which talks about
      reporting formats)<br>
      is supposed to change? If so, that needs to be moved to the actual
      methodology<br>
      and made _much_ clearer.<br>
      <br>
      *T, 3.4.6: You talk of the first non-INVITE in an NS. How are you<br>=

      distinguishing subsequent non-INVITES in this NS from requests in
      some other<br>
      NS? Are you using dialog identifiers or something else? Why do you
      expect that<br>
      to matter (why is the notion of a sequence of related non-INVITEs
      useful from a<br>
      benchmarking perspective - there isn't state kept in
      intermediaries because of<br>
      them - what will make this metric distinguishable from a metric
      that just<br>
      focuses on the transactions?) <br>
      <br>
      *T, 3.4.7: What's special about MESSAGE? Why aren't you focusing
      on INFO or<br>
      some other end-to-end non-INVITE? I suspect it's because you are
      wanting to<br>
      focus on a simple non-INVITE transaction (which is why you are
      leaving out<br>
      SUBSCRIBE/NOTIFY). MESSAGE is good enough for that, but you should
      be clear<br>
      that's why you chose it. You should also talk about whether the
      payload of all<br>
      of the MESSAGE requests are the same size and whether that size is
      a parameter<br>
      to the benchmark. (You'll likely get very different behavior from
      a MESSAGE<br>
      that fragments.) <br>
      <br>
      *T, 3.4.7: The definition says "messages completed" but the
      discussion talks<br>
      about "definition of success". Does success mean an IM transaction
      completed<br>
      successfully?&nbsp; If so, the definition of success for a UAC has a
      problem. As<br>
      written, it describes a binary outcome for the whole test, not how
      to determine<br>
      the success of an individual transaction - how do you get from
      what it<br>
      describes to a rate?<br>
      <br>
      *T, Appendix A: The document should better motivate why this is
      here.<br>
      Why does it mention SUBSCRIBE/NOTIFY when the rest of the
      document(s) are<br>
      silent on them.&nbsp; The discussion says you are _selecting_ a Sessi=
on
      Attempts<br>
      Arrival Rate distribution. It would be clearer to say you are
      selecting the<br>
      distribution of messages sent from the EA. It's not clear how this
      particular<br>
      metric will benefit from different sending distributions.<br>
      <br>
      Now the Methodology document (comments prefixed with an M):<br>
      <br>
      *M, Introduction: Can the document say why the subset of
      functionality<br>
      benchmarked here was chosen over other subsets? Why was
      Subscribe/Notify or<br>
      Info not included (or invites with MSRP or even simple early
      media, etc)?<br>
      <br>
      *M, Introduction paragraph 4: This points to section 4 and section
      2 of the<br>
      terminology document for configuration options. Section 4 is the
      iana<br>
      considerations section (which has no options). What did you mean
      to point to?<br>
      <br>
      *M, Introduction paragraph 4, last sentence: This seems out of
      place - why is<br>
      it in the introduction and not in a section on that specific
      methodology.<br>
      <br>
      *M, 4.1: It's not clear here, or in the methodology sections
      whether the tests<br>
      allow the transport to change as you go across an intermediary. Do
      you intend<br>
      to be able to benchmark a proxy that has TCP on one side and UDP
      on the other?<br>
      <br>
      *M, 4.2: This is another spot where pointing to the Updates to
      3261 that change<br>
      the transaction state machines is important.<br>
      <br>
      *M, 4.4: Did you really mean RTSP? Maybe you meant MSRP or
      something else? RTSP<br>
      is not, itself, a media protocol.<br>
      <br>
      *M, 4.9: There's something wrong with this sentence: "This test is
      run for an<br>
      extended period of time, which is referred to as infinity, and
      which is,<br>
      itself, a parameter of the test labeled T in the pseudo-code".
      What value is<br>
      there in giving some finite parameter T the name "infinity"?<br>
      <br>
      *M, 4.9: Where did 100 (as an initial value for s) come from?
      Modern devices<br>
      process at many orders of magnitude higher rates than that. Do you
      want to<br>
      provide guidance instead of an absolute number here?<br>
      <br>
      *M 4.9: In the pseudo-code, you often say "the largest value". It
      would help to<br>
      say the the largest value of _what_.<br>
      <br>
      *M 4.9: What is the "steady_state" function called in the
      pseudo-code?<br>
      <br>
      *M 6.3: Expected Results: The EA will have different performance<br>
      characteristics if you have them sending media or not. That could
      cause this<br>
      metric to be different from session establishment without media.<br>
      <br>
      *M 6.5: This section should call out that loop detection is not
      optional when<br>
      forking. The Expected Results description is almost tautological -
      could it<br>
      instead say how having this measurement is _useful_ to those
      consuming this<br>
      benchmark?<br>
      <br>
      *M 6.8, Procedure: Why is "May need to run for each transport of
      interest." in<br>
      a section titled "Session Establishement Rate with TLS Encrypted
      SIP"?<br>
      <br>
      *M 6.10: This document doesn't define Flooding. What do you mean?
      How is this<br>
      different than "Stress test" as called out in section 4.8? Where
      does 500 come<br>
      from?&nbsp; (Again, I suspect that's a very old value - and you shoul=
d
      be providing<br>
      guidance rather than an absolute number). But it's not clear how
      this isn't<br>
      just the session establishment rate test that just starts with a
      bigger number.<br>
      What is it actually trying to report on that's different from the
      session<br>
      establishment rate test, and how is the result useful?<br>
      <br>
      *M 6.11: Is each registration going to a different AoR? (You must
      be, or the<br>
      re-registration test makes no sense.) You might talk about
      configuring the<br>
      registrar and the EA so they know what to use.<br>
      <br>
      *M 6.12, Expected Results: Where do you get the idea that
      re-registration<br>
      should be faster than initial registration? How is knowing the
      difference (or<br>
      even that there is a difference) between this and the registration
      metric<br>
      likely to be useful to the consumer? <br>
      <br>
      *M 6.14: Session Capacity, as defined in the terminology doc, is a
      count of<br>
      sessions, not a rate. This section treats it as a rate and says it
      can be<br>
      interpreted as "throughput". I'm struggling to see what it
      actually is<br>
      measuring. The way your algorithm is defined in section 4.9, I
      find s before I<br>
      use T. Lets say I've got a box where the value of s that's found
      is 10000, and<br>
      I've got enough memory that I can deal with several large values
      of T. If I run<br>
      this test with T of 50000, my benchmark result is 500,000,000. If
      I run with a<br>
      T of 100000, my benchmark result is 1,000,000,000. How are those
      numbers<br>
      telling me _anything_ about session capacity. That the _real_
      session capacity<br>
      is at least that much? Is there some part of this methodology that
      has me hunt<br>
      for a maximal value of T? Unless I've missed something, this
      metric needs more<br>
      clarification to not be completely misleading. Maybe instead of
      "Session<br>
      Capacity" you should simply be reporting "Simultaneous Sessions
      Measured"<br>
      <br>
      *M 8: "and various other drafts" is not helpful - if you know of
      other<br>
      important documents to point to, point to them. <br>
      <br>
      Nits:<br>
      <br>
      T : The definition of Stateful Proxy and Stateless Proxy copied
      the words<br>
      "defined by this specification" from RFC3261. This literal copy
      introduces<br>
      confusion. Can you make it more visually obvious you are quoting?
      And even if<br>
      you do, could you replace "by this specification" with "by
      [RFC3261]"? <br>
      <br>
      T, Introduction, 2nd paragraph, last sentence: This rules out
      stateless<br>
      proxies.<br>
      <br>
      T, Section 3: In the places where this template is used, you are
      careful to say<br>
      None under Issues when there aren't any, but not so careful to say
      None under<br>
      See Also when there isn't anything. Leaving them blank makes some
      transitions<br>
      hard to read - they read like you are saying see also (whatever
      the next<br>
      section heading is).<br>
      <br>
      T, 3.1.6, Discussion: s/tie interval/time interval/<br>
      <br>
      M, Introduction, paragraph 2: You say "any [RFC3261] conforming
      device", but<br>
      you've ruled endpoint UAs out in other parts of the documents.<br>
      <br>
      M 4.9: You have comments explaining send_traffic the _second_ time
      you use it.<br>
      They would be better positioned at the first use.<br>
      <br>
      M 5.2: This is the first place the concept of re-Registration is
      mentioned. A<br>
      forward pointer to what you mean, or an introduction before you
      get to this<br>
      format would be clearer.<br>
      <br>
      <br>
      On 1/16/13 3:48 PM, The IESG wrote:<br>
    </div>
    <blockquote cite=3D"mid:20130116214838.3092.88369.idtracker@ietfa.amsl.co=
m" type=3D"cite">
      <pre wrap=3D"">The IESG has received a request from the Benchmarking Me=
thodology WG
(bmwg) to consider the following document:
- 'Terminology for Benchmarking Session Initiation Protocol (SIP)
   Networking Devices'
  &lt;draft-ietf-bmwg-sip-bench-term-08.txt&gt; as Informational RFC

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action. Please send substantive comments to the
<a class=3D"moz-txt-link-abbreviated" href=3D"mailto:ietf@ietf.org">ietf@ietf.o=
rg</a> mailing lists by 2013-01-30. Exceptionally, comments may be
sent to <a class=3D"moz-txt-link-abbreviated" href=3D"mailto:iesg@ietf.org">ies=
g@ietf.org</a> instead. In either case, please retain the
beginning of the Subject line to allow automated sorting.

Abstract


   This document provides a terminology for benchmarking the SIP
   performance of networking devices.  The term performance in this
   context means the capacity of the device- or system-under-test to
   process SIP messages.  Terms are included for test components, test
   setup parameters, and performance benchmark metrics for black-box
   benchmarking of SIP networking devices.  The performance benchmark
   metrics are obtained for the SIP signaling plane only.  The terms are
   intended for use in a companion methodology document for
   characterizing the performance of a SIP networking device under a
   variety of conditions.  The intent of the two documents is to enable
   a comparison of the capacity of SIP networking devices.  Test setup
   parameters and a methodology document are necessary because SIP
   allows a wide range of configuration and operational conditions that
   can influence performance benchmark measurements.  A standard
   terminology and methodology will ensure that benchmarks have
   consistent definition and were obtained following the same
   procedures.




The file can be obtained via
<a class=3D"moz-txt-link-freetext" href=3D"http://datatracker.ietf.org/doc/draf=
t-ietf-bmwg-sip-bench-term/">http://datatracker.ietf.org/doc/draft-ietf-bmwg=
-sip-bench-term/</a>

IESG discussion can be tracked via
<a class=3D"moz-txt-link-freetext" href=3D"http://datatracker.ietf.org/doc/draf=
t-ietf-bmwg-sip-bench-term/ballot/">http://datatracker.ietf.org/doc/draft-ie=
tf-bmwg-sip-bench-term/ballot/</a>


No IPR declarations have been submitted directly on this I-D.


</pre>
    </blockquote>
    <br>
  </div></div></span></body></html>

--B_3441912973_13556270--



From stephen.farrell@cs.tcd.ie  Fri Jan 25 09:26:17 2013
Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A3F9421F8896 for <ietf@ietfa.amsl.com>; Fri, 25 Jan 2013 09:26:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.518
X-Spam-Level: 
X-Spam-Status: No, score=-102.518 tagged_above=-999 required=5 tests=[AWL=0.081, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 5t9O6JstuZgp for <ietf@ietfa.amsl.com>; Fri, 25 Jan 2013 09:26:17 -0800 (PST)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) by ietfa.amsl.com (Postfix) with ESMTP id E44C621F87FA for <ietf@ietf.org>; Fri, 25 Jan 2013 09:26:16 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id 49361BE2F; Fri, 25 Jan 2013 17:25:55 +0000 (GMT)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id S-peN7TDCGeq; Fri, 25 Jan 2013 17:25:53 +0000 (GMT)
Received: from [IPv6:2001:770:10:203:810d:eba8:c654:6e65] (unknown [IPv6:2001:770:10:203:810d:eba8:c654:6e65]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 98756BE5C; Fri, 25 Jan 2013 17:25:53 +0000 (GMT)
Message-ID: <5102C021.1010805@cs.tcd.ie>
Date: Fri, 25 Jan 2013 17:25:53 +0000
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130106 Thunderbird/17.0.2
MIME-Version: 1.0
To: John C Klensin <john-ietf@jck.com>
Subject: Re: FW: Last Call: <draft-farrell-ft-03.txt> (A Fast-Track way to RFC with Running Code) to Experimental RFC
References: <017001cdf017$c394df00$4abe9d00$@olddog.co.uk> <50FEC0B8.8060905@isi.edu> <201301222131.r0MLVK8C015116@cichlid.raleigh.ibm.com> <51028A77.2060808@cisco.com> <E2AC36AC55ED79756BE8929E@JcK-HP8200.jck.com> <5102A5ED.6050902@cs.tcd.ie> <80C0B979748114A8E9308A63@JcK-HP8200.jck.com>
In-Reply-To: <80C0B979748114A8E9308A63@JcK-HP8200.jck.com>
X-Enigmail-Version: 1.5
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: adrian@olddog.co.uk, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 25 Jan 2013 17:26:17 -0000

Hiya,

On 01/25/2013 04:37 PM, John C Klensin wrote:
> If I correctly understand the above, it lies at the root of the
> problem I was trying to describe.  This is really an experiment
> if the effect of deciding we didn't want to make it permanent
> was that we were at status quo ante, i.e., as if the experiment
> had never been initiated.  

That is definitely my intention. I'm happy to make it
clear in the draft, though I guess I'd assumed it was
inherent in the use of 3933. Anyway, yes, I'll add text
saying that explicitly. For now, I've put in a note
in the working copy. [1]

> ... The moment that appeal is filed, the
> document in question moves from "fast track" to the slowest
> track of all.

I think I recall someone sometime hoping there'd be more
appeals:-)

Yes, if this generated more appeals then that'd be a bad
outcome. Would it be more likely? I don't know to be honest
but I'd hope not, though perhaps you're right that it sort
of paints a target on a draft. I think this is similar to
points made about picking suitable drafts/implementations
and would be a good thing to say in a wiki rather than
put into the draft. I've added a reminder note to do that
also in [1].

Thanks,
S.

[1] http://down.dsg.cs.tcd.ie/misc/draft-farrell-ft-04.txt

From daedulus@btconnect.com  Fri Jan 25 10:06:33 2013
Return-Path: <daedulus@btconnect.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AE91C21F889C for <ietf@ietfa.amsl.com>; Fri, 25 Jan 2013 10:06:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.599
X-Spam-Level: 
X-Spam-Status: No, score=-5.599 tagged_above=-999 required=5 tests=[AWL=1.000,  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 MdoQL9y2eJEe for <ietf@ietfa.amsl.com>; Fri, 25 Jan 2013 10:06:33 -0800 (PST)
Received: from co9outboundpool.messaging.microsoft.com (co9ehsobe003.messaging.microsoft.com [207.46.163.26]) by ietfa.amsl.com (Postfix) with ESMTP id 3728321F8795 for <ietf@ietf.org>; Fri, 25 Jan 2013 10:06:33 -0800 (PST)
Received: from mail88-co9-R.bigfish.com (10.236.132.245) by CO9EHSOBE025.bigfish.com (10.236.130.88) with Microsoft SMTP Server id 14.1.225.23; Fri, 25 Jan 2013 18:06:32 +0000
Received: from mail88-co9 (localhost [127.0.0.1])	by mail88-co9-R.bigfish.com (Postfix) with ESMTP id 8E43F2A02F9; Fri, 25 Jan 2013 18:06:32 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.253.85; KIP:(null); UIP:(null); IPV:NLI; H:DB3PRD0710HT002.eurprd07.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: -21
X-BigFish: PS-21(zzbb2dI98dI9371I542I1432Izz1ee6h1de0h1202h1e76h1d1ah1d2ahzz1033IL8275bh8275dhz2dh2a8h5a9h668h839h93fhd24hf0ah1177h1179h1288h12a5h12a9h12bdh137ah139eh13b6h1441h1504h1537h162dh1631h1758h17f1h184fh1898h18e1h304l1155h)
Received: from mail88-co9 (localhost.localdomain [127.0.0.1]) by mail88-co9 (MessageSwitch) id 1359137190463597_13345; Fri, 25 Jan 2013 18:06:30 +0000 (UTC)
Received: from CO9EHSMHS032.bigfish.com (unknown [10.236.132.234])	by mail88-co9.bigfish.com (Postfix) with ESMTP id 6B5033C00A0; Fri, 25 Jan 2013 18:06:30 +0000 (UTC)
Received: from DB3PRD0710HT002.eurprd07.prod.outlook.com (157.56.253.85) by CO9EHSMHS032.bigfish.com (10.236.130.42) with Microsoft SMTP Server (TLS) id 14.1.225.23; Fri, 25 Jan 2013 18:06:29 +0000
Received: from DB3PRD0210HT005.eurprd02.prod.outlook.com (157.56.253.69) by pod51017.outlook.com (10.255.75.37) with Microsoft SMTP Server (TLS) id 14.16.257.4; Fri, 25 Jan 2013 18:06:27 +0000
Message-ID: <00e001cdfb26$50e31200$4001a8c0@gateway.2wire.net>
From: t.p. <daedulus@btconnect.com>
To: Eliot Lear <lear@cisco.com>, John C Klensin <john-ietf@jck.com>
References: <017001cdf017$c394df00$4abe9d00$@olddog.co.uk><50FEC0B8.8060905@isi.edu><201301222131.r0MLVK8C015116@cichlid.raleigh.ibm.com><51028A77.2060808@cisco.com><E2AC36AC55ED79756BE8929E@JcK-HP8200.jck.com> <5102A53A.8070206@cisco.com>
Subject: Re: FW: Last Call: <draft-farrell-ft-03.txt> (A Fast-Track way toRFC with Running Code) to Experimental RFC
Date: Fri, 25 Jan 2013 17:59:16 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Originating-IP: [157.56.253.69]
X-OriginatorOrg: btconnect.com
Cc: Thomas Narten <narten@us.ibm.com>, adrian@olddog.co.uk, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 25 Jan 2013 18:06:33 -0000

----- Original Message -----
From: "Eliot Lear" <lear@cisco.com>
To: "John C Klensin" <john-ietf@jck.com>
Cc: "Thomas Narten" <narten@us.ibm.com>; <adrian@olddog.co.uk>;
<ietf@ietf.org>
Sent: Friday, January 25, 2013 3:31 PM
> John,
>
> On 1/25/13 4:27 PM, John C Klensin wrote:
> >>> a WG can
> >>> skip WG LC if they think its not needed.
> >> ???
> >>
> >> When was the last time that happened?  Did it require a
> >> consensus call to determine?
> > Chair discretion [... and five of paragraphs of text]
>
> None of which answered my above questions.  When was the last time
> chairs USED that discretion?!

I believe that it was used for
draft-ietf-tls-renegotiation
in December 2009.

Tom Petch


>
> Eliot
>
>



From mrex@sap.com  Fri Jan 25 13:36:35 2013
Return-Path: <mrex@sap.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 815F321F885E for <ietf@ietfa.amsl.com>; Fri, 25 Jan 2013 13:36:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.249
X-Spam-Level: 
X-Spam-Status: No, score=-10.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_HI=-8]
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 hqXAkLMDUreH for <ietf@ietfa.amsl.com>; Fri, 25 Jan 2013 13:36:34 -0800 (PST)
Received: from smtpde01.sap-ag.de (smtpde01.sap-ag.de [155.56.68.170]) by ietfa.amsl.com (Postfix) with ESMTP id AC9B321F8734 for <ietf@ietf.org>; Fri, 25 Jan 2013 13:36:29 -0800 (PST)
Received: from mail05.wdf.sap.corp by smtpde01.sap-ag.de (26) with ESMTP id r0PLaP8R014358 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 25 Jan 2013 22:36:25 +0100 (MET)
Subject: Re: FW: Last Call: <draft-farrell-ft-03.txt> (A Fast-Track way to RFC with Running Code) to Experimental RFC
In-Reply-To: <5102A53A.8070206@cisco.com>
To: Eliot Lear <lear@cisco.com>
Date: Fri, 25 Jan 2013 22:36:24 +0100 (CET)
X-Mailer: ELM [version 2.4ME+ PL125 (25)]
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="US-ASCII"
Message-Id: <20130125213624.E984F1A495@ld9781.wdf.sap.corp>
From: mrex@sap.com (Martin Rex)
X-SAP: out
Cc: John C Klensin <john-ietf@jck.com>, Thomas Narten <narten@us.ibm.com>, ietf@ietf.org, adrian@olddog.co.uk
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: mrex@sap.com
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 25 Jan 2013 21:36:35 -0000

Eliot Lear wrote:
> 
> On 1/25/13 4:27 PM, John C Klensin wrote:
> >>> a WG can skip WG LC if they think its not needed.
> >>
> >> When was the last time that happened?
> >> Did it require a consensus call to determine?
>
> > Chair discretion [... and five of paragraphs of text]
> 
> None of which answered my above questions.  When was the last time
> chairs USED that discretion?!

I don't know about the last time it happened, but I know about
one time in Nov-2009 in the TLS WG (now rfc5746).

The WG chair *did* a WG consensus call before AD & WG chair short-cutted
to IETF LC.  IMHO, at the very minimum, a WG consensus call with a specific
question or choice is necessary to gauge consensus in a WG.

WG Consensus call (20-Nov-2009):
  http://www.ietf.org/mail-archive/web/tls/current/msg04571.html

AD taking over (27-Nov-2009):
  http://www.ietf.org/mail-archive/web/tls/current/msg04928.html

IETF LC (30-Nov-2009):
  http://www.ietf.org/mail-archive/web/tls/current/msg04962.html


While I was OK with skipping the WGLC, I really didn't like some
of the AD's shortcut, in particular with respect to standardizing
two methods for signaling, and his refusal to perform a consensus
call for mandating the simpler version of the signaling, which
would have significantly facilitated the creation of fixes for
the installed base.

  http://www.ietf.org/mail-archive/web/tls/current/msg05287.html


There is a REAL issue with rushing a document pointing to implementations,
when it turns out pretty quickly that what has been implemented is really
just half of a solution.  I'm actually afraid that rushing things on
the process side is going to worsen problems.

What I was slighly missing in that process was (a) leadership, in
recognizing that mandating one signaling scheme will simplify the
spec, implementations and interop effort and (b) true consensus calls
on issues that are obviously contentious.  Even running a
consensus call during / in parallel to an IETF LC is better than
blaming time-constraints and the AD infering his "desired" outcome
from prior discussions of *MUCH* broader topics. 

Process-wise, we need to be extra careful about collision of interest,
each time when short-cutting processes.

-Martin

From stephen.farrell@cs.tcd.ie  Fri Jan 25 14:47:45 2013
Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EE3E321F855A for <ietf@ietfa.amsl.com>; Fri, 25 Jan 2013 14:47:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.499
X-Spam-Level: 
X-Spam-Status: No, score=-102.499 tagged_above=-999 required=5 tests=[AWL=0.100, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 RAxIz3p0erNe for <ietf@ietfa.amsl.com>; Fri, 25 Jan 2013 14:47:45 -0800 (PST)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) by ietfa.amsl.com (Postfix) with ESMTP id 6056C21F842A for <ietf@ietf.org>; Fri, 25 Jan 2013 14:47:43 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id E5B48BE5F; Fri, 25 Jan 2013 22:47:19 +0000 (GMT)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9CrouYVRx8g8; Fri, 25 Jan 2013 22:47:19 +0000 (GMT)
Received: from [10.87.48.12] (unknown [86.46.24.28]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id E58E5BE2F; Fri, 25 Jan 2013 22:47:18 +0000 (GMT)
Message-ID: <51030B76.2070401@cs.tcd.ie>
Date: Fri, 25 Jan 2013 22:47:18 +0000
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130106 Thunderbird/17.0.2
MIME-Version: 1.0
To: mrex@sap.com
Subject: Re: FW: Last Call: <draft-farrell-ft-03.txt> (A Fast-Track way to RFC with Running Code) to Experimental RFC
References: <20130125213624.E984F1A495@ld9781.wdf.sap.corp>
In-Reply-To: <20130125213624.E984F1A495@ld9781.wdf.sap.corp>
X-Enigmail-Version: 1.5
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: John C Klensin <john-ietf@jck.com>, Thomas Narten <narten@us.ibm.com>, ietf@ietf.org, adrian@olddog.co.uk
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 25 Jan 2013 22:47:46 -0000

Hi Martin,

On 01/25/2013 09:36 PM, Martin Rex wrote:
> I don't know about the last time it happened, but I know about
> one time in Nov-2009 in the TLS WG (now rfc5746).

I recall that and agree with the sequence of events you
describe, but I'm not sure that that situation is
relevant when considering this draft, for two reasons:

- First, that was the IETF in security-incident-handling
mode, and that's just different from normal process for
us, whether fast-tracked or not. Its in the nature of things
that the vast majority of security incidents don't
directly affect IETF protocols so as to require a
backwards incompatible change. So I think that was a
highly unusual case. (And let's hope things stay that
way.)

- Second, there was significant controversy within the
WG before the last calls, (with many hundreds of mails;-)
so a set of WG chairs that chose to try a fast-track
experiment in such circumstances would be crazy basically.
(Remember, we're only talking about an experiment here.)

As for Eliot's question, I don't recall any case when
a WG skipped WGLC. Even if its not part of 2026, right
now it's a de-facto but mandatory part of the process
as far as I can see. I'd be interested if there are cases
where WGLC was skipped, esp. if its been regularly done.

S.


From mrex@sap.com  Fri Jan 25 18:20:38 2013
Return-Path: <mrex@sap.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4D9DD21F845F for <ietf@ietfa.amsl.com>; Fri, 25 Jan 2013 18:20:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.249
X-Spam-Level: 
X-Spam-Status: No, score=-10.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_HI=-8]
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 O7UrGSCeYY4z for <ietf@ietfa.amsl.com>; Fri, 25 Jan 2013 18:20:37 -0800 (PST)
Received: from smtpde02.sap-ag.de (smtpde02.sap-ag.de [155.56.68.140]) by ietfa.amsl.com (Postfix) with ESMTP id 4EB8521F843B for <ietf@ietf.org>; Fri, 25 Jan 2013 18:20:36 -0800 (PST)
Received: from mail05.wdf.sap.corp by smtpde02.sap-ag.de (26) with ESMTP id r0Q2KWgu017621 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Sat, 26 Jan 2013 03:20:32 +0100 (MET)
Subject: Re: FW: Last Call: <draft-farrell-ft-03.txt> (A Fast-Track way to RFC with Running Code) to Experimental RFC
In-Reply-To: <51030B76.2070401@cs.tcd.ie>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Date: Sat, 26 Jan 2013 03:20:32 +0100 (CET)
X-Mailer: ELM [version 2.4ME+ PL125 (25)]
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="US-ASCII"
Message-Id: <20130126022032.33A4B1A496@ld9781.wdf.sap.corp>
From: mrex@sap.com (Martin Rex)
X-SAP: out
Cc: Thomas Narten <narten@us.ibm.com>, ietf@ietf.org, John C Klensin <john-ietf@jck.com>, adrian@olddog.co.uk
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: mrex@sap.com
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 26 Jan 2013 02:20:38 -0000

Stephen Farrell wrote:
> 
> On 01/25/2013 09:36 PM, Martin Rex wrote:
> >
> > I don't know about the last time it happened, but I know about
> > one time in Nov-2009 in the TLS WG (now rfc5746).
> 
> I recall that and agree with the sequence of events you
> describe, but I'm not sure that that situation is
> relevant when considering this draft, for two reasons:

Uh-oh!


> 
> - First, that was the IETF in security-incident-handling
> mode, and that's just different from normal process for
> us, whether fast-tracked or not.

If I hadn't stumbled upon the TLS renegotiation issue while
discussing the proposal for TLS channel bindings, then
the "solution" would have been developed and shipped
under NDA and entirely with involvement of the IETF TLS WG
(just some selected TLS WG members), and likely there would
have been a request for rubber stamping the (half-baked) solution
*AFTER* deploymend of the fixes by major vendors.

  http://www.ietf.org/mail-archive/web/tls/current/msg03928.html
  http://www.ietf.org/mail-archive/web/tls/current/msg03942.html


Myself, I'm worried by the idea of shortcutting review and marginalization
of comments that do not meet the discuss criteria.


> 
> - Second, there was significant controversy within the
> WG before the last calls, (with many hundreds of mails;-)
> so a set of WG chairs that chose to try a fast-track
> experiment in such circumstances would be crazy basically.
> (Remember, we're only talking about an experiment here.)


Admittedly, I deserve part of the blame for the heated discussion.

But if occasional heated discussions turn out to be a serious problem
for creating or improving technical solutions, then we may need more
procedural safeguards (such as independent leadership), not less.

The true essence of most of the 2009 TLS WG discussion was actually
fairly small and simple:

  http://www.ietf.org/mail-archive/web/tls/current/msg05365.html


-Martin

From abdussalambaryun@gmail.com  Sat Jan 26 08:16:17 2013
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5036C21F86D2 for <ietf@ietfa.amsl.com>; Sat, 26 Jan 2013 08:16:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.587
X-Spam-Level: 
X-Spam-Status: No, score=-3.587 tagged_above=-999 required=5 tests=[AWL=0.012,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 H+sJkQrb062x for <ietf@ietfa.amsl.com>; Sat, 26 Jan 2013 08:16:16 -0800 (PST)
Received: from mail-pa0-f52.google.com (mail-pa0-f52.google.com [209.85.220.52]) by ietfa.amsl.com (Postfix) with ESMTP id BC5A821F8432 for <ietf@ietf.org>; Sat, 26 Jan 2013 08:16:16 -0800 (PST)
Received: by mail-pa0-f52.google.com with SMTP id fb1so784272pad.39 for <ietf@ietf.org>; Sat, 26 Jan 2013 08:16:16 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to:cc :content-type; bh=xsQnOXa30WEdzRBXgDHUi1xdVIqP2rI3NDEroJtS4Fo=; b=jmcYxwADfZhvd+PQEvcpa/iZVAybSD9rkI17E/kZ52wzXEbpNtTwtq+N0JHRU6hFCu irUOVJ4i5Wsrrn/AsYUduHg5Fy8DMTCvM9re2Qb3O0fLZy3zAKd8hvfPCOe61U5lA27Z BmHVb32fptSsKYKmxU0ZbXV0pjDtfldbvdotTjyallIHfgOvcfdU/0mqyCazTgItd6Zr /N8BGIKf2sio7i7toMw0bbKSLPJQk5wc5PS3v6vlZi4Xonegu2cLunK53C9JZT7WTHGH Fuh1an3DoDU6hJU373cRjyHZk0801Uffu3S+hEKcYICx+AqNF2MI2IL9E5BoFCOq9Zlg XD7Q==
MIME-Version: 1.0
X-Received: by 10.68.227.33 with SMTP id rx1mr23890225pbc.67.1359216976459; Sat, 26 Jan 2013 08:16:16 -0800 (PST)
Received: by 10.68.218.134 with HTTP; Sat, 26 Jan 2013 08:16:16 -0800 (PST)
Date: Sat, 26 Jan 2013 17:16:16 +0100
Message-ID: <CADnDZ8_yMkg6WKqmOUpfGjO168N+4MjbV_m6ngOMHc96wFJySQ@mail.gmail.com>
Subject: Re: FW: Last Call: <draft-farrell-ft-03.txt> (A Fast-Track way to RFC with Running Code) to Experimental RFC
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: mrex@sap.com
Content-Type: text/plain; charset=ISO-8859-1
Cc: ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 26 Jan 2013 16:16:17 -0000

I agree with your concerns and may suggest that the tests' results of
the running code SHOULD be reported inside a mandatory section of the
Fast-Tracked I-D to RFC.

AB

On 01/26/2013 Martin Rex wrote:
>Stephen Farrell wrote:
>
>> On 01/25/2013 09:36 PM, Martin Rex wrote:
> >
> > I don't know about the last time it happened, but I know about
> > one time in Nov-2009 in the TLS WG (now rfc5746).
>
> I recall that and agree with the sequence of events you
> describe, but I'm not sure that that situation is
> relevant when considering this draft, for two reasons:

Uh-oh!


>
> - First, that was the IETF in security-incident-handling
> mode, and that's just different from normal process for
> us, whether fast-tracked or not.

If I hadn't stumbled upon the TLS renegotiation issue while
discussing the proposal for TLS channel bindings, then
the "solution" would have been developed and shipped
under NDA and entirely with involvement of the IETF TLS WG
(just some selected TLS WG members), and likely there would
have been a request for rubber stamping the (half-baked) solution
*AFTER* deploymend of the fixes by major vendors.

  http://www.ietf.org/mail-archive/web/tls/current/msg03928.html
  http://www.ietf.org/mail-archive/web/tls/current/msg03942.html


Myself, I'm worried by the idea of shortcutting review and marginalization
of comments that do not meet the discuss criteria.


>
> - Second, there was significant controversy within the
> WG before the last calls, (with many hundreds of mails;-)
> so a set of WG chairs that chose to try a fast-track
> experiment in such circumstances would be crazy basically.
> (Remember, we're only talking about an experiment here.)


Admittedly, I deserve part of the blame for the heated discussion.

But if occasional heated discussions turn out to be a serious problem
for creating or improving technical solutions, then we may need more
procedural safeguards (such as independent leadership), not less.

The true essence of most of the 2009 TLS WG discussion was actually
fairly small and simple:

  http://www.ietf.org/mail-archive/web/tls/current/msg05365.html


-Martin

From daedulus@btconnect.com  Sun Jan 27 03:22:26 2013
Return-Path: <daedulus@btconnect.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 10B0F21F84C5 for <ietf@ietfa.amsl.com>; Sun, 27 Jan 2013 03:22:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[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 6SlPJ+Yrf1ei for <ietf@ietfa.amsl.com>; Sun, 27 Jan 2013 03:22:23 -0800 (PST)
Received: from tx2outboundpool.messaging.microsoft.com (tx2ehsobe001.messaging.microsoft.com [65.55.88.11]) by ietfa.amsl.com (Postfix) with ESMTP id 5F18921F84C2 for <ietf@ietf.org>; Sun, 27 Jan 2013 03:22:22 -0800 (PST)
Received: from mail146-tx2-R.bigfish.com (10.9.14.239) by TX2EHSOBE010.bigfish.com (10.9.40.30) with Microsoft SMTP Server id 14.1.225.23; Sun, 27 Jan 2013 11:22:22 +0000
Received: from mail146-tx2 (localhost [127.0.0.1])	by mail146-tx2-R.bigfish.com (Postfix) with ESMTP id 553F92013A; Sun, 27 Jan 2013 11:22:22 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.250.181; KIP:(null); UIP:(null); IPV:NLI; H:AMSPRD0711HT002.eurprd07.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: -22
X-BigFish: PS-22(zzbb2dI98dI9371I542I1432I1418Izz1ee6h1de0h1202h1e76h1d1ah1d2ahzz1033IL8275dh8275bhz2dh2a8h5a9h668h839h947hd24hf0ah1177h1179h1288h12a5h12a9h12bdh137ah139eh13b6h1441h1504h1537h162dh1631h1758h17f1h184fh1898h18e1h304l1155h)
Received: from mail146-tx2 (localhost.localdomain [127.0.0.1]) by mail146-tx2 (MessageSwitch) id 135928574013619_23200; Sun, 27 Jan 2013 11:22:20 +0000 (UTC)
Received: from TX2EHSMHS043.bigfish.com (unknown [10.9.14.243])	by mail146-tx2.bigfish.com (Postfix) with ESMTP id E9A444C004B; Sun, 27 Jan 2013 11:22:19 +0000 (UTC)
Received: from AMSPRD0711HT002.eurprd07.prod.outlook.com (157.56.250.181) by TX2EHSMHS043.bigfish.com (10.9.99.143) with Microsoft SMTP Server (TLS) id 14.1.225.23; Sun, 27 Jan 2013 11:22:15 +0000
Received: from pc6 (86.168.111.137) by pod51017.outlook.com (10.242.14.163) with Microsoft SMTP Server (TLS) id 14.16.263.1; Sun, 27 Jan 2013 11:22:13 +0000
Message-ID: <00c401cdfc80$2bcbc380$4001a8c0@gateway.2wire.net>
From: t.p. <daedulus@btconnect.com>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
References: <20130125213624.E984F1A495@ld9781.wdf.sap.corp> <51030B76.2070401@cs.tcd.ie>
Subject: Re: FW: Last Call: <draft-farrell-ft-03.txt> (A Fast-Track way toRFC with Running Code) to Experimental RFC
Date: Sun, 27 Jan 2013 11:19:23 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Originating-IP: [86.168.111.137]
X-OriginatorOrg: btconnect.com
Cc: John C Klensin <john-ietf@jck.com>, Thomas Narten <narten@us.ibm.com>, ietf@ietf.org, adrian@olddog.co.uk
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 27 Jan 2013 11:22:26 -0000

----- Original Message -----
From: "Stephen Farrell" <stephen.farrell@cs.tcd.ie>
To: <mrex@sap.com>
Cc: "John C Klensin" <john-ietf@jck.com>; "Thomas Narten"
<narten@us.ibm.com>; <ietf@ietf.org>; <adrian@olddog.co.uk>
Sent: Friday, January 25, 2013 10:47 PM
>
> Hi Martin,
>
> On 01/25/2013 09:36 PM, Martin Rex wrote:
> > I don't know about the last time it happened, but I know about
> > one time in Nov-2009 in the TLS WG (now rfc5746).
>
> I recall that and agree with the sequence of events you
> describe, but I'm not sure that that situation is
> relevant when considering this draft, for two reasons:

Sounds a bit like 'don't confuse me with the facts, my mind is made
up:-)'

The point that Thomas made and John endorsed is that when we want to
speed things up, our current procedures allow us to do just that.  We do
not need a formal process (more complications, more work).  And as John
pointed out, having two independent Last Call discussions, on two
different lists, on communities that may have little overlap, is not the
way, IMO, to establish a clear consensus.

Tom Petch


> - First, that was the IETF in security-incident-handling
> mode, and that's just different from normal process for
> us, whether fast-tracked or not. Its in the nature of things
> that the vast majority of security incidents don't
> directly affect IETF protocols so as to require a
> backwards incompatible change. So I think that was a
> highly unusual case. (And let's hope things stay that
> way.)
>
> - Second, there was significant controversy within the
> WG before the last calls, (with many hundreds of mails;-)
> so a set of WG chairs that chose to try a fast-track
> experiment in such circumstances would be crazy basically.
> (Remember, we're only talking about an experiment here.)
>
> As for Eliot's question, I don't recall any case when
> a WG skipped WGLC. Even if its not part of 2026, right
> now it's a de-facto but mandatory part of the process
> as far as I can see. I'd be interested if there are cases
> where WGLC was skipped, esp. if its been regularly done.
>
> S.
>
>



From stephen.farrell@cs.tcd.ie  Sun Jan 27 03:51:22 2013
Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BA00C21F85FE for <ietf@ietfa.amsl.com>; Sun, 27 Jan 2013 03:51:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.25
X-Spam-Level: 
X-Spam-Status: No, score=-102.25 tagged_above=-999 required=5 tests=[AWL=0.349, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 LOWARC5jn6Ql for <ietf@ietfa.amsl.com>; Sun, 27 Jan 2013 03:51:21 -0800 (PST)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) by ietfa.amsl.com (Postfix) with ESMTP id 074CB21F85EE for <ietf@ietf.org>; Sun, 27 Jan 2013 03:51:19 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id 60B5DBE2F; Sun, 27 Jan 2013 11:50:57 +0000 (GMT)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dmyLFlYzeZ+C; Sun, 27 Jan 2013 11:50:54 +0000 (GMT)
Received: from [10.87.48.12] (unknown [86.45.57.26]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 6FCA7BDDC; Sun, 27 Jan 2013 11:50:54 +0000 (GMT)
Message-ID: <5105149E.70909@cs.tcd.ie>
Date: Sun, 27 Jan 2013 11:50:54 +0000
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130106 Thunderbird/17.0.2
MIME-Version: 1.0
To: "t.p." <daedulus@btconnect.com>
Subject: Re: FW: Last Call: <draft-farrell-ft-03.txt> (A Fast-Track way toRFC with Running Code) to Experimental RFC
References: <20130125213624.E984F1A495@ld9781.wdf.sap.corp> <51030B76.2070401@cs.tcd.ie> <00c401cdfc80$2bcbc380$4001a8c0@gateway.2wire.net>
In-Reply-To: <00c401cdfc80$2bcbc380$4001a8c0@gateway.2wire.net>
X-Enigmail-Version: 1.5
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: John C Klensin <john-ietf@jck.com>, Thomas Narten <narten@us.ibm.com>, ietf@ietf.org, adrian@olddog.co.uk
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 27 Jan 2013 11:51:22 -0000

On 01/27/2013 11:19 AM, t.p. wrote:
> ----- Original Message -----
> From: "Stephen Farrell" <stephen.farrell@cs.tcd.ie>
> To: <mrex@sap.com>
> Cc: "John C Klensin" <john-ietf@jck.com>; "Thomas Narten"
> <narten@us.ibm.com>; <ietf@ietf.org>; <adrian@olddog.co.uk>
> Sent: Friday, January 25, 2013 10:47 PM
>>
>> Hi Martin,
>>
>> On 01/25/2013 09:36 PM, Martin Rex wrote:
>>> I don't know about the last time it happened, but I know about
>>> one time in Nov-2009 in the TLS WG (now rfc5746).
>>
>> I recall that and agree with the sequence of events you
>> describe, but I'm not sure that that situation is
>> relevant when considering this draft, for two reasons:
> 
> Sounds a bit like 'don't confuse me with the facts, my mind is made
> up:-)'

Absolutely not. Handling the TLS renegotiation bug was just
not the kind of thing that's relevant for this experiment.
It'd have been entirely dumb, stupid and crazy to try use any
kind of process experiment to handle that situation.

*After* this experiment is run, and if it turns up something
that we might want to make part of the normal formal process
then perhaps we might want to think about whether security
incident handling could be done that way or not. (I'd think
maybe not.) That'd happen in a year or so at the end of the
experiment if the experiment seems to have gone well. But,
that's not relevant now.

This IETF LC is about whether or not to run a process experiment
for a limited time that's optional to use at the discretion
of WG chairs.

This IETF LC is not about whether this or any proposal ought
be part of our formal, long-term process.

> The point that Thomas made and John endorsed is that when we want to
> speed things up, our current procedures allow us to do just that.  We do
> not need a formal process (more complications, more work).  And as John
> pointed out, having two independent Last Call discussions, on two
> different lists, on communities that may have little overlap, is not the
> way, IMO, to establish a clear consensus.

John's point about the two discussions in parallel was well
made and already acknowledged as such.

S.

> 
> Tom Petch
> 
> 
>> - First, that was the IETF in security-incident-handling
>> mode, and that's just different from normal process for
>> us, whether fast-tracked or not. Its in the nature of things
>> that the vast majority of security incidents don't
>> directly affect IETF protocols so as to require a
>> backwards incompatible change. So I think that was a
>> highly unusual case. (And let's hope things stay that
>> way.)
>>
>> - Second, there was significant controversy within the
>> WG before the last calls, (with many hundreds of mails;-)
>> so a set of WG chairs that chose to try a fast-track
>> experiment in such circumstances would be crazy basically.
>> (Remember, we're only talking about an experiment here.)
>>
>> As for Eliot's question, I don't recall any case when
>> a WG skipped WGLC. Even if its not part of 2026, right
>> now it's a de-facto but mandatory part of the process
>> as far as I can see. I'd be interested if there are cases
>> where WGLC was skipped, esp. if its been regularly done.
>>
>> S.
>>
>>
> 
> 
> 
> 

From tglassey@earthlink.net  Sun Jan 27 07:07:23 2013
Return-Path: <tglassey@earthlink.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AC8EB21F854A for <ietf@ietfa.amsl.com>; Sun, 27 Jan 2013 07:07:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.849
X-Spam-Level: 
X-Spam-Status: No, score=-2.849 tagged_above=-999 required=5 tests=[AWL=-0.250, BAYES_00=-2.599]
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 MK2vAlYZ3u0N for <ietf@ietfa.amsl.com>; Sun, 27 Jan 2013 07:07:23 -0800 (PST)
Received: from elasmtp-spurfowl.atl.sa.earthlink.net (elasmtp-spurfowl.atl.sa.earthlink.net [209.86.89.66]) by ietfa.amsl.com (Postfix) with ESMTP id E49D321F853A for <ietf@ietf.org>; Sun, 27 Jan 2013 07:07:22 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net; b=AoeRPcUFOUsD+IFrw8LJyl9KjKTc/8whiq9ICrpVi2/kZuo0/UBrwwzKGoRhCDPT; h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:Subject:Content-Type:Content-Transfer-Encoding:X-ELNK-Trace:X-Originating-IP;
Received: from [67.180.133.21] (helo=[192.168.15.2]) by elasmtp-spurfowl.atl.sa.earthlink.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.67) (envelope-from <tglassey@earthlink.net>) id 1TzTpB-000215-H4 for ietf@ietf.org; Sun, 27 Jan 2013 10:07:13 -0500
Message-ID: <5105429C.5000900@earthlink.net>
Date: Sun, 27 Jan 2013 07:07:08 -0800
From: tglassey <tglassey@earthlink.net>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:13.0) Gecko/20120614 Thunderbird/13.0.1
MIME-Version: 1.0
To: ietf <ietf@ietf.org>
Subject: IPv6 update for BCP5?
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ELNK-Trace: 01b7a7e171bdf5911aa676d7e74259b7b3291a7d08dfec79d0d23626bf98c46495f5a34e40ee8755350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 67.180.133.21
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 27 Jan 2013 15:07:23 -0000

So... we probably need a IPv6 update for BCP5 (RFC1918), doesnt that 
make sense?

Todd

-- 
Regards TSG
"Ex-Cruce-Leo"

//Confidential Mailing - Please destroy this if you are not the intended recipient.


From brian@innovationslab.net  Sun Jan 27 07:28:35 2013
Return-Path: <brian@innovationslab.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9124E21F868B for <ietf@ietfa.amsl.com>; Sun, 27 Jan 2013 07:28:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.577
X-Spam-Level: 
X-Spam-Status: No, score=-102.577 tagged_above=-999 required=5 tests=[AWL=0.022, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 hRYYf2EAwDci for <ietf@ietfa.amsl.com>; Sun, 27 Jan 2013 07:28:35 -0800 (PST)
Received: from uillean.fuaim.com (uillean.fuaim.com [206.197.161.140]) by ietfa.amsl.com (Postfix) with ESMTP id 05CDB21F8689 for <ietf@ietf.org>; Sun, 27 Jan 2013 07:28:34 -0800 (PST)
Received: from clairseach.fuaim.com (clairseach-high.fuaim.com [206.197.161.158]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by uillean.fuaim.com (Postfix) with ESMTP id 9C1D98817F for <ietf@ietf.org>; Sun, 27 Jan 2013 07:28:32 -0800 (PST)
Received: from clemson.local (c-69-140-213-249.hsd1.md.comcast.net [69.140.213.249]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by clairseach.fuaim.com (Postfix) with ESMTP id 5C1E0140039 for <ietf@ietf.org>; Sun, 27 Jan 2013 07:28:32 -0800 (PST)
Message-ID: <510547A0.60100@innovationslab.net>
Date: Sun, 27 Jan 2013 10:28:32 -0500
From: Brian Haberman <brian@innovationslab.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130107 Thunderbird/17.0.2
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: IPv6 update for BCP5?
References: <5105429C.5000900@earthlink.net>
In-Reply-To: <5105429C.5000900@earthlink.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 27 Jan 2013 15:28:35 -0000

On 1/27/13 10:07 AM, tglassey wrote:
> So... we probably need a IPv6 update for BCP5 (RFC1918), doesnt that
> make sense?

My understanding is people have been using ULAs (RFC 4193) for this type 
of functionality.

>
> Todd
>


From lear@cisco.com  Sun Jan 27 11:18:24 2013
Return-Path: <lear@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CB16921F8653 for <ietf@ietfa.amsl.com>; Sun, 27 Jan 2013 11:18:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.566
X-Spam-Level: 
X-Spam-Status: No, score=-110.566 tagged_above=-999 required=5 tests=[AWL=0.033, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
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 iqs3BLl+HCqe for <ietf@ietfa.amsl.com>; Sun, 27 Jan 2013 11:18:24 -0800 (PST)
Received: from ams-iport-2.cisco.com (ams-iport-2.cisco.com [144.254.224.141]) by ietfa.amsl.com (Postfix) with ESMTP id D9C2A21F8534 for <ietf@ietf.org>; Sun, 27 Jan 2013 11:18:23 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1001; q=dns/txt; s=iport; t=1359314304; x=1360523904; h=message-id:date:from:mime-version:to:subject:references: in-reply-to:content-transfer-encoding; bh=PWm3//aRa0N2CE25ECQsUAWVf/3qmDed8QZfjNDxqY4=; b=AR4st+uvy0HuCTC/CqtrCiTl36N4bcgrR/bzWiidGy70jbH5VhgwClq9 xXW8YHs7FFYALdEbv+QPd4XgC5JlgRsed+5ONDAZKAJUSh2HeM3kAfx9n a+o75PdzZdCIH/edJ85DtUEmZXttvNpAyH0Xb/b1qcELdftHDqrD0eFAa U=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgEFANh8BVGQ/khM/2dsb2JhbABFhka4GhZzgh4BAQEEI1URCxgCAgUWBAcCAgkDAgECATwJBgEMCAEBGId1rH2RWIEjjmqBEwOWDZBIgng
X-IronPort-AV: E=Sophos;i="4.84,547,1355097600"; d="scan'208";a="80037743"
Received: from ams-core-3.cisco.com ([144.254.72.76]) by ams-iport-2.cisco.com with ESMTP; 27 Jan 2013 19:18:22 +0000
Received: from ams3-vpn-dhcp7002.cisco.com (ams3-vpn-dhcp7002.cisco.com [10.61.91.89]) by ams-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id r0RJILpM016941 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 27 Jan 2013 19:18:22 GMT
Message-ID: <51057D7D.3090104@cisco.com>
Date: Sun, 27 Jan 2013 20:18:21 +0100
From: Eliot Lear <lear@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130107 Thunderbird/17.0.2
MIME-Version: 1.0
To: "t.p." <daedulus@btconnect.com>, IETF Discussion <ietf@ietf.org>
Subject: Re: FW: Last Call: <draft-farrell-ft-03.txt> (A Fast-Track way toRFC with Running Code) to Experimental RFC
References: <20130125213624.E984F1A495@ld9781.wdf.sap.corp> <51030B76.2070401@cs.tcd.ie> <00c401cdfc80$2bcbc380$4001a8c0@gateway.2wire.net>
In-Reply-To: <00c401cdfc80$2bcbc380$4001a8c0@gateway.2wire.net>
X-Enigmail-Version: 1.5
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 27 Jan 2013 19:18:24 -0000

On 1/27/13 12:19 PM, t.p. wrote:
> The point that Thomas made and John endorsed is that when we want to
> speed things up, our current procedures allow us to do just that. We
> do not need a formal process (more complications, more work). And as
> John pointed out, having two independent Last Call discussions, on two
> different lists, on communities that may have little overlap, is not
> the way, IMO, to establish a clear consensus.

If we don't need a formal process, then I'd like it clarified in WG
training that this procedure already exists.  Furthermore, I don't buy
the notion about confusion.  In the cases where this is likely to be
done, either an emergency exists (which was the case with TLS, IMHO), or
the draft is likely not to elicit much in the way of objection.  This
DOES happen.  But that having been said, if both a WG chair and an AD
make a bad call, there are numerous opportunities to correct it in this
process, the NOMCOM process, appeal, etc.

Eliot

From johnl@iecc.com  Sun Jan 27 12:22:41 2013
Return-Path: <johnl@iecc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6281921F8522 for <ietf@ietfa.amsl.com>; Sun, 27 Jan 2013 12:22:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.797
X-Spam-Level: 
X-Spam-Status: No, score=-110.797 tagged_above=-999 required=5 tests=[AWL=0.402, BAYES_00=-2.599, HABEAS_ACCREDITED_SOI=-4.3, RCVD_IN_BSP_TRUSTED=-4.3, USER_IN_WHITELIST=-100]
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 lz-p-z2BdwWT for <ietf@ietfa.amsl.com>; Sun, 27 Jan 2013 12:22:40 -0800 (PST)
Received: from leila.iecc.com (leila6.iecc.com [IPv6:2001:470:1f07:1126:0:4c:6569:6c61]) by ietfa.amsl.com (Postfix) with ESMTP id 8A10F21F843D for <ietf@ietf.org>; Sun, 27 Jan 2013 12:22:40 -0800 (PST)
Received: (qmail 3199 invoked from network); 27 Jan 2013 20:22:39 -0000
Received: from leila.iecc.com (64.57.183.34) by mail1.iecc.com with QMQP; 27 Jan 2013 20:22:39 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:vbr-info; s=51058c8e.xn--30v786c.k1301; i=johnl@user.iecc.com; bh=5+Mpes1xbrNk6HNHL0TVHFrWiJ+fvfY9BqD7oDgrguU=; b=EewE/UpSIwSz4S8KXctE44oXX8LBKpVIwdiZYaHwHVgk+ts7/6m9vcS+gm9JwEYXRohlU8YM7HLSJLBDB2hCWt735kNpAlEMmKbeltkRtG7FtaAvDfj0uOVp/fW1gRSwfMboq1OvLgxbPNXkkP/uqSfDVSm7Otjb4Qrgp2SLjNo=
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:vbr-info; s=51058c8e.xn--30v786c.k1301; olt=johnl@user.iecc.com; bh=5+Mpes1xbrNk6HNHL0TVHFrWiJ+fvfY9BqD7oDgrguU=; b=U/KRlPJDh835nQv7xgWDVXE2maAJSrgVKQdNt/bHYq8mBdLf11VDjOG77ya/0m9NVrTBh2S88CRDe4jMMY3cvjLWnDxRHMqCG9k0wy2BU7UpxvV/dL7sX7A0dDaG+hJe4ElmJ8CaZhz1ixRhvEKL6JtB6BVW2+jLifY7MXOvzXQ=
VBR-Info: md=iecc.com; mc=all; mv=dwl.spamhaus.org
Date: 27 Jan 2013 20:22:16 -0000
Message-ID: <20130127202216.73256.qmail@joyce.lan>
From: "John Levine" <johnl@taugh.com>
To: ietf@ietf.org
Subject: Re: IPv6 update for BCP5?
In-Reply-To: <510547A0.60100@innovationslab.net>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 27 Jan 2013 20:22:41 -0000

>On 1/27/13 10:07 AM, tglassey wrote:
>> So... we probably need a IPv6 update for BCP5 (RFC1918), doesnt that
>> make sense?
>
>My understanding is people have been using ULAs (RFC 4193) for this type 
>of functionality.

That's certainly one option.

The other is just to apply for some IPv6 address space from your local
RIR.  There's plenty of it, they don't care if you don't plan to make
it routable outside your own network.

It is definitely NOT a goal of IPv6 to create hacks to permit two
different interfaces to have the same IP address, anywhere.



From touch@isi.edu  Sun Jan 27 20:27:52 2013
Return-Path: <touch@isi.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B1A5721F884B for <ietf@ietfa.amsl.com>; Sun, 27 Jan 2013 20:27:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.599
X-Spam-Level: 
X-Spam-Status: No, score=-104.599 tagged_above=-999 required=5 tests=[AWL=2.000, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 7u04kgO90u6Y for <ietf@ietfa.amsl.com>; Sun, 27 Jan 2013 20:27:52 -0800 (PST)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by ietfa.amsl.com (Postfix) with ESMTP id 38C4521F87BA for <ietf@ietf.org>; Sun, 27 Jan 2013 20:27:52 -0800 (PST)
Received: from [192.168.1.81] (pool-71-105-87-221.lsanca.dsl-w.verizon.net [71.105.87.221]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id r0S4RFYj008298 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Sun, 27 Jan 2013 20:27:25 -0800 (PST)
Message-ID: <5105FE25.6010409@isi.edu>
Date: Sun, 27 Jan 2013 20:27:17 -0800
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:17.0) Gecko/20130107 Thunderbird/17.0.2
MIME-Version: 1.0
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Subject: Re: FW: Last Call: <draft-farrell-ft-03.txt> (A Fast-Track way to RFCwith Running Code) to Experimental RFC
References: <017001cdf017$c394df00$4abe9d00$@olddog.co.uk><50FEC0B8.8060905@isi.edu> <201301222131.r0MLVK8C015116@cichlid.raleigh.ibm.com> <00b801cdfae3$1918fa80$4001a8c0@gateway.2wire.net> <51026457.9000108@pi.nu> <51028374.9070702@cs.tcd.ie>
In-Reply-To: <51028374.9070702@cs.tcd.ie>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 28 Jan 2013 04:27:52 -0000

About the idea of an "experiment":

On 1/25/2013 5:07 AM, Stephen Farrell wrote:
>
> Responses to some points below but I'd really like to ask
> people to consider a few things here:
>
> - what's proposed is an experiment, it'd likely get tried out
>    a few times and won't consume any huge resource anywhere

If this is an experiment, then you presumably answers to the following 
questions:

	1- what is your an hypothesis?
	2- what you intend to measure?
	3- what is your 'control' against which to compare the results?
	4- what is your objective metric for success/failure?

I've heard only one hypothesis - that this reduces time to publication. 
I disagree that this is a useful hypothesis to test for the following 
reasons:

	- time to publication isn't a goal of the IETF
		IMO, any doc that isn't useful in 5 years ought
		to not be published here; we don't need to
		document every sneeze

	- thorough review ought to be a requirement
		and this 'experiment' potentially compromises that
		by reducing the overall time of review

	- community resources ought to be considered
		and this 'experiment' burns group resources
		due to having a broad group concurrently review
		a doc that could have been reviewed by smaller
		groups first

Given the limited cycles this community has to review docs, I cannot see 
a benefit to this experiment that is worth the cost.

Having this entire community burn cycles on this document speaks for 
itself. It should have been vetted in a smaller, more invested community 
first.

Calling something an 'experiment' doesn't make it worthwhile to test.

Joe



From abdussalambaryun@gmail.com  Mon Jan 28 02:55:18 2013
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8578321F8D71 for <ietf@ietfa.amsl.com>; Mon, 28 Jan 2013 02:55:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.588
X-Spam-Level: 
X-Spam-Status: No, score=-3.588 tagged_above=-999 required=5 tests=[AWL=0.011,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 WJD-tLHyljWB for <ietf@ietfa.amsl.com>; Mon, 28 Jan 2013 02:55:18 -0800 (PST)
Received: from mail-pb0-f46.google.com (mail-pb0-f46.google.com [209.85.160.46]) by ietfa.amsl.com (Postfix) with ESMTP id C246321F8CEF for <ietf@ietf.org>; Mon, 28 Jan 2013 02:55:17 -0800 (PST)
Received: by mail-pb0-f46.google.com with SMTP id mc17so754245pbc.19 for <ietf@ietf.org>; Mon, 28 Jan 2013 02:55:17 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=9WHvgvAlTBUyQP+/3OD2UZDkHQbs10F6dMiEJo+MOLM=; b=UeBAvAP+cV7Trfiz7d2vYxSNRundB709SDsJFSwLbGTyEAsqUyDzS72p7zEehwpsVW IkGsP/HKZxsUvyQgUrA+pmYDwiSsG1Z9Dn6PXPTtjJ/OAm+jAsKLT1i1Z33WgUcM58bT mC7ngwTadTlkuBHZHQhZdeAcBlSGe6WYkhuwakS0Rafg2s2I5jd3+v/9QwSg5MPMDKlZ nbkDFq9MyhS6CJhm6eznn2xskIMc6f71hLfRCx5qCb9OITG39FzoyteVcHMSrUYWqbsR cLKA1x/gNLum+Ph7pZSiNNxa3tPmhIracRQYXDwx+bHTa1302CiJ2HXhGELbKVh9OtBL g9Xw==
MIME-Version: 1.0
X-Received: by 10.68.227.33 with SMTP id rx1mr36991818pbc.67.1359370517424; Mon, 28 Jan 2013 02:55:17 -0800 (PST)
Received: by 10.68.218.134 with HTTP; Mon, 28 Jan 2013 02:55:17 -0800 (PST)
In-Reply-To: <CADnDZ8_yMkg6WKqmOUpfGjO168N+4MjbV_m6ngOMHc96wFJySQ@mail.gmail.com>
References: <CADnDZ8_yMkg6WKqmOUpfGjO168N+4MjbV_m6ngOMHc96wFJySQ@mail.gmail.com>
Date: Mon, 28 Jan 2013 11:55:17 +0100
Message-ID: <CADnDZ8_BEGALi+MZzNgc4yXDMbJ9GZ6aUXRwyDHZh1NoVrF+uQ@mail.gmail.com>
Subject: Re: FW: Last Call: <draft-farrell-ft-03.txt> (A Fast-Track way to RFC with Running Code) to Experimental RFC
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: touch@isi.edu
Content-Type: text/plain; charset=ISO-8859-1
Cc: ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 28 Jan 2013 10:55:18 -0000

I agree with your approach. However, if it should be tested by
community and reported successful then why we need to go through 5
years, just publish fast ways,

AB

++++++++++++
Sun, 27 Jan 2013 20:27:17 -0800
If this is an experiment, then you presumably answers to the following
questions:
	1- what is your an hypothesis?
	2- what you intend to measure?
	3- what is your 'control' against which to compare the results?
	4- what is your objective metric for success/failure?


I've heard only one hypothesis - that this reduces time to
publication. I disagree that this is a useful hypothesis to test for
the following reasons:
	- time to publication isn't a goal of the IETF
		IMO, any doc that isn't useful in 5 years ought
		to not be published here; we don't need to
		document every sneeze

	- thorough review ought to be a requirement
		and this 'experiment' potentially compromises that
		by reducing the overall time of review

	- community resources ought to be considered
		and this 'experiment' burns group resources
		due to having a broad group concurrently review
		a doc that could have been reviewed by smaller
		groups first


Given the limited cycles this community has to review docs, I cannot
see a benefit to this experiment that is worth the cost.

Having this entire community burn cycles on this document speaks for
itself. It should have been vetted in a smaller, more invested
community first.
Calling something an 'experiment' doesn't make it worthwhile to test.

Joe

From stephen.farrell@cs.tcd.ie  Mon Jan 28 03:12:59 2013
Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DC5E621F843B for <ietf@ietfa.amsl.com>; Mon, 28 Jan 2013 03:12:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 Ieryzlht4Hjg for <ietf@ietfa.amsl.com>; Mon, 28 Jan 2013 03:12:59 -0800 (PST)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) by ietfa.amsl.com (Postfix) with ESMTP id A381521F8BC4 for <ietf@ietf.org>; Mon, 28 Jan 2013 03:12:58 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id E2212BE5B; Mon, 28 Jan 2013 11:12:35 +0000 (GMT)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id E8wW3AE5uyYY; Mon, 28 Jan 2013 11:12:34 +0000 (GMT)
Received: from [IPv6:2001:770:10:203:d03a:b6e9:52e7:3e1e] (unknown [IPv6:2001:770:10:203:d03a:b6e9:52e7:3e1e]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id A6AF1BE58; Mon, 28 Jan 2013 11:12:34 +0000 (GMT)
Message-ID: <51065D23.5020509@cs.tcd.ie>
Date: Mon, 28 Jan 2013 11:12:35 +0000
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130106 Thunderbird/17.0.2
MIME-Version: 1.0
To: Joe Touch <touch@isi.edu>
Subject: Re: FW: Last Call: <draft-farrell-ft-03.txt> (A Fast-Track way to RFCwith Running Code) to Experimental RFC
References: <017001cdf017$c394df00$4abe9d00$@olddog.co.uk><50FEC0B8.8060905@isi.edu> <201301222131.r0MLVK8C015116@cichlid.raleigh.ibm.com> <00b801cdfae3$1918fa80$4001a8c0@gateway.2wire.net> <51026457.9000108@pi.nu> <51028374.9070702@cs.tcd.ie> <5105FE25.6010409@isi.edu>
In-Reply-To: <5105FE25.6010409@isi.edu>
X-Enigmail-Version: 1.5
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 28 Jan 2013 11:13:00 -0000

On 01/28/2013 04:27 AM, Joe Touch wrote:
> About the idea of an "experiment":

Right. The context being its an RFC 3933 IETF process
experiment.

> 
> On 1/25/2013 5:07 AM, Stephen Farrell wrote:
>>
>> Responses to some points below but I'd really like to ask
>> people to consider a few things here:
>>
>> - what's proposed is an experiment, it'd likely get tried out
>>    a few times and won't consume any huge resource anywhere
> 
> If this is an experiment, then you presumably answers to the following
> questions:
> 
>     1- what is your an hypothesis?
>     2- what you intend to measure?
>     3- what is your 'control' against which to compare the results?
>     4- what is your objective metric for success/failure?

Well, its not a scientific experiment, and nor does it need to
be. Quoting 3933:

-   " A statement of the problem expected to be resolved is
      desirable but not required (the intent is to keep the firm
      requirements for such an experiment as lightweight as possible).
      Similarly, specific experimental or evaluative criteria, although
      highly desirable, are not required -- for some of the process
      changes we anticipate, having the IESG reach a conclusion at the
      end of the sunset period that the community generally believes
      things to be better (or worse) will be both adequate and
      sufficient. "

My take is that even though 3933 says "desirable" a couple of
times there, it's probably best to not go there, at least in this
case, but for now probably more generally. The reason I think
that is that I reckon the IETF has got itself into a log-jam
that almost prevents us from modifying our processes in any way
and every additional word provides additional barriers to doing
anything, since there'll always be someone for whom those added
words raise what seems to them to be a red flag.

I do agree that's far from ideal, but so is our current
process-change log-jam. (BTW, I already said this a few months
ago in response to a similar comment on I think -00 or -01.)

Separately, I don't believe this proposed experiment does have
any objective criteria on which we could get consensus and that
would be practical to measure - I think the outcome is more
likely to be subjective, (e.g. "seemed to help because of X")
and that the follow-up, if any, would require further
consideration - my guess is that if the experiment were some
form of success then we'd need to start over on documenting
the thing(s) that might be worth including in an update to
BCP9, but then that'd be based on some experience with
running the experiment rather than on your or my speculation
as to what might or might not work well or badly.

> 
> I've heard only one hypothesis - that this reduces time to publication.
> I disagree that this is a useful hypothesis to test for the following
> reasons:
> 
>     - time to publication isn't a goal of the IETF
>         IMO, any doc that isn't useful in 5 years ought
>         to not be published here; we don't need to
>         document every sneeze

IMO reduced time to publication is definitely *a* goal.
I've heard lots of IETF participants complain about how
long things take, lots of times. Perhaps you're in the
rough on that. (I also note that this experiment doesn't
actually aim for any major reduction in time to publication
as it says in the draft.)

The draft itself also discusses reasons why running code
might also lead to better quality specifications.

>     - thorough review ought to be a requirement
>         and this 'experiment' potentially compromises that
>         by reducing the overall time of review

I think the liklihood of that doing damage during the
experiment is very small. In addition, I might be wrong,
but the thoroughness of review doesn't correlate that
well with the duration of review would be my guess. While
secdir reviews are pretty variable, they are almost all
done in a tight timeframe and a good number of them are
very good. Same for gen-art and apps-dir reviews. So
we do have evidence that good review can be done in a
short timeframe. Equally, I've seen quite a few drafts
that have reached the IESG after years that still
have quite a lot that needs to be fixed and that a
thorough review ought have caught.

>     - community resources ought to be considered
>         and this 'experiment' burns group resources
>         due to having a broad group concurrently review
>         a doc that could have been reviewed by smaller
>         groups first

Yes, this experiment should bring a few drafts to IETF
review earlier. The WG chairs are still supposed to
only send a publication request when they're satisfied
the draft represents the rough consensus of the WG.
However, I'm looking at changing some of the wording
on this in response to John's point about having two
parallel discussions. I'll post to the list when I've
had a chance to write that up in the working version.

> 
> Given the limited cycles this community has to review docs, I cannot see
> a benefit to this experiment that is worth the cost.

Fair enough. We disagree.

> Having this entire community burn cycles on this document speaks for
> itself. It should have been vetted in a smaller, more invested community
> first.

I'm following the 3933 process.

I don't know of any smaller but open venue for discussing rfc
3933 experiments. Perhaps there ought be such, but given how
rarely 3933 experiments are proposed, that'd be a very quiet
list.

In any case I would confidently predict that any process change
or experiment will generate this much traffic during IETF
last call so I'm not sure there's a saving;-) If someone manages
to get any kind of process change approved without a major flare
up on this list then I'll happily buy them a beer to celebrate.

If you'd rather we make 3933 historic or replace it with
something else, that's a different topic.

> Calling something an 'experiment' doesn't make it worthwhile to test.

I believe this draft does meet all the requirements of
3933 and is an experiment in that sense. I agree that not all
such things would be worthwhile to test, but a number of
people have agreed that this was worthwhile to test. Whether
or not that means we ought go forward with this is a call
for Adrian and the IESG at the end of IETF LC.

S.

> 
> Joe
> 
> 
> 
> 

From touch@isi.edu  Mon Jan 28 07:23:41 2013
Return-Path: <touch@isi.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AB85821F8717 for <ietf@ietfa.amsl.com>; Mon, 28 Jan 2013 07:23:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.932
X-Spam-Level: 
X-Spam-Status: No, score=-102.932 tagged_above=-999 required=5 tests=[AWL=-0.333, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 e+qF2zw2LwEk for <ietf@ietfa.amsl.com>; Mon, 28 Jan 2013 07:23:39 -0800 (PST)
Received: from darkstar.isi.edu (darkstar.isi.edu [128.9.128.127]) by ietfa.amsl.com (Postfix) with ESMTP id 1A03D21F870E for <ietf@ietf.org>; Mon, 28 Jan 2013 07:23:39 -0800 (PST)
Received: from [192.168.1.81] (pool-71-105-87-221.lsanca.dsl-w.verizon.net [71.105.87.221]) (authenticated bits=0) by darkstar.isi.edu (8.13.8/8.13.8) with ESMTP id r0SFNGOq001283 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 28 Jan 2013 07:23:20 -0800 (PST)
Message-ID: <510697E6.6070602@isi.edu>
Date: Mon, 28 Jan 2013 07:23:18 -0800
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:17.0) Gecko/20130107 Thunderbird/17.0.2
MIME-Version: 1.0
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Subject: Re: FW: Last Call: <draft-farrell-ft-03.txt> (A Fast-Track way to RFCwith Running Code) to Experimental RFC
References: <017001cdf017$c394df00$4abe9d00$@olddog.co.uk><50FEC0B8.8060905@isi.edu> <201301222131.r0MLVK8C015116@cichlid.raleigh.ibm.com> <00b801cdfae3$1918fa80$4001a8c0@gateway.2wire.net> <51026457.9000108@pi.nu> <51028374.9070702@cs.tcd.ie> <5105FE25.6010409@isi.edu> <51065D23.5020509@cs.tcd.ie>
In-Reply-To: <51065D23.5020509@cs.tcd.ie>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 28 Jan 2013 15:23:41 -0000

On 1/28/2013 3:12 AM, Stephen Farrell wrote:
>
> On 01/28/2013 04:27 AM, Joe Touch wrote:
>
...
>> If this is an experiment, then you presumably answers to the following
>> questions:
>>
>>      1- what is your an hypothesis?
>>      2- what you intend to measure?
>>      3- what is your 'control' against which to compare the results?
>>      4- what is your objective metric for success/failure?
>
> Well, its not a scientific experiment, and nor does it need to
> be. Quoting 3933:
>
> -   " A statement of the problem expected to be resolved is
>        desirable but not required (the intent is to keep the firm
>        requirements for such an experiment as lightweight as possible).
>        Similarly, specific experimental or evaluative criteria, although
>        highly desirable, are not required -- for some of the process
>        changes we anticipate, having the IESG reach a conclusion at the
>        end of the sunset period that the community generally believes
>        things to be better (or worse) will be both adequate and
>        sufficient. "
>
> My take is that even though 3933 says "desirable" a couple of
> times there, it's probably best to not go there, at least in this
> case, but for now probably more generally. The reason I think
> that is that I reckon the IETF has got itself into a log-jam
> that almost prevents us from modifying our processes in any way
> and every additional word provides additional barriers to doing
> anything, since there'll always be someone for whom those added
> words raise what seems to them to be a red flag.

Lightweight != vacuous.

Perhaps the lack of the discussion of these issues is part of the reason 
so many previous proposals have not been tried.

That isn't a reason to ignore those issues here. But a bigger concern is 
your reasoning as presented in this response:

>> I've heard only one hypothesis - that this reduces time to publication.
>> I disagree that this is a useful hypothesis to test for the following
>> reasons:
>>
>>      - time to publication isn't a goal of the IETF
>>          IMO, any doc that isn't useful in 5 years ought
>>          to not be published here; we don't need to
>>          document every sneeze
>
> IMO reduced time to publication is definitely *a* goal.
> I've heard lots of IETF participants complain about how
> long things take, lots of times. Perhaps you're in the
> rough on that. (I also note that this experiment doesn't
> actually aim for any major reduction in time to publication
> as it says in the draft.)

There are plenty of places where existing process is in a logjam. My 
experience over the past 15 years is most of the delay happens during 
the following:

	- changes in the IETF process where ideas like this throw
	a wrench into the process, and create confusion

		I had a few informational docs wait over a year
		in the queue because a process change was put
		into effect before the necessary boilerplate
		was resolved.

	--> this has a *simple* solution. Grandfather everything that
	has been submitted to a given queue to changes in that queue's
	process.

	- IESG review, during which issues are often raised that
	were addressed during WG review that are then re-hashed,
	even though they are not relevant to the area of their
	appointment

Overlapping community review has no impact on either of these.

> The draft itself also discusses reasons why running code
> might also lead to better quality specifications.

No disagreement there, but "better quality" doesn't mean the doc 
wouldn't still need - and substantively benefit from - serial review in 
increasingly larger communities.

>>      - thorough review ought to be a requirement
>>          and this 'experiment' potentially compromises that
>>          by reducing the overall time of review
>
> I think the likelihood of that doing damage during the
> experiment is very small.

Damage =
	- publishing ideas not sufficiently vetted
	that later need to be updated/errata'd

	- wasting the community's time by having a
	large group review an issue that could have been
	addressed and corrected within a smaller community

Do you seriously think these concerns should outweigh a few weeks of 
reduced time to publication?

> In addition, I might be wrong,
> but the thoroughness of review doesn't correlate that
> well with the duration of review would be my guess.

I've heard many on this list - including myself - point out specific 
reasons why this should not be believed.

If still believe every process can be accelerated, I encourage you to 
review Brooks "the Mythical Man Month".

>> Having this entire community burn cycles on this document speaks for
>> itself. It should have been vetted in a smaller, more invested community
>> first.
>
> I'm following the 3933 process.
 >
> I don't know of any smaller but open venue for discussing rfc
> 3933 experiments. Perhaps there ought be such, but given how
> rarely 3933 experiments are proposed, that'd be a very quiet
> list.

This is a perfect issue for a bar BOF, FWIW.

Joe

From Jeff.Hodges@KingsMountain.com  Mon Jan 28 14:41:59 2013
Return-Path: <Jeff.Hodges@KingsMountain.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 03A4921E8030 for <ietf@ietfa.amsl.com>; Mon, 28 Jan 2013 14:41:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.599
X-Spam-Level: 
X-Spam-Status: No, score=-103.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
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 O2eemsPxe89j for <ietf@ietfa.amsl.com>; Mon, 28 Jan 2013 14:41:57 -0800 (PST)
Received: from oproxy12-pub.bluehost.com (oproxy12-pub.bluehost.com [50.87.16.10]) by ietfa.amsl.com (Postfix) with SMTP id 9780921F874B for <ietf@ietf.org>; Mon, 28 Jan 2013 14:41:57 -0800 (PST)
Received: (qmail 15020 invoked by uid 0); 28 Jan 2013 22:41:33 -0000
Received: from unknown (HELO box514.bluehost.com) (74.220.219.114) by oproxy12.bluehost.com with SMTP; 28 Jan 2013 22:41:33 -0000
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=kingsmountain.com; s=default;  h=Content-Transfer-Encoding:Content-Type:Subject:CC:To:MIME-Version:From:Date:Message-ID; bh=qihiElDa5DlHSFzyHAIanPS/t/9q8RVs+EvRYPh0P38=;  b=sa9Zi75h1T7Sb4RDON5kQlvM1xm4oamsYHUcx4/9mFCIKnkOaCix3sFtvw2yeizwhVqlBGrdHwp9tYYblAaWA1AIsDe00X3G/uNzMPyP/qDnKhpGZuTH9fmKfMJHCPxY;
Received: from [70.199.81.220] (port=63698 helo=[10.0.0.1]) by box514.bluehost.com with esmtpsa (TLSv1:CAMELLIA256-SHA:256) (Exim 4.80) (envelope-from <Jeff.Hodges@KingsMountain.com>) id 1TzxON-0005Ps-Cx; Mon, 28 Jan 2013 15:41:32 -0700
Message-ID: <5106FE98.2020904@KingsMountain.com>
Date: Mon, 28 Jan 2013 14:41:28 -0800
From: =JeffH <Jeff.Hodges@KingsMountain.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130106 Thunderbird/17.0.2
MIME-Version: 1.0
To: Ben Laurie <benl@google.com>
Subject: Re: LC comments on draft-laurie-pki-sunlight-05 - "acceptable root certificates" ?
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Identified-User: {11025:box514.bluehost.com:kingsmou:kingsmountain.com} {sentby:smtp auth 70.199.81.220 authed with jeff.hodges+kingsmountain.com}
Cc: Emilia Kasper <ekasper@google.com>, "therightkey@ietf.org" <therightkey@ietf.org>, IETF Discussion List <ietf@ietf.org>, Adam Langley <agl@google.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 28 Jan 2013 22:41:59 -0000

 > Apologies for responding to recent comments in random order: I'm
 > travelling and have accumulated something of a backlog.

no worries :)

thx again for your thoughts.


BenL replied:
 > On 22 January 2013 03:11, =JeffH <Jeff.Hodges@kingsmountain.com> wrote:

<snip>
 >>>  - is there a
 >>> standard reference for that? I've refereced HTML 4.01, but perhaps
 >>> there's a better one?
 >>
 >> hm, AFAICT, there is not a standard for URI query component formating and
 >> thus parameter encoding, so this spec will have to explicitly specify
 >> something. Section 3.4 of RFC3986 gives allowed chars for the query
 >> component, but that's about it.
 >>
 >> Have you mocked up code that parses the log client messages? If so, what
 >> query component syntax does it handle?
 >
 > I have specified the "standard" format via HTML 4.01.

ok, i assume you're referring to section 17.13 "form submission" of HTML 4.01, 
and using the  application/x-www-form-urlencoded  content type, with the 
parameters appended to the url encoded according to S17.13.4 ?



 >
 >>>> 3. There appear to be three defined methods for TLS servers to provide
 >>>> TLS
 >>>> clients with CT data, in S3.2.  For this experiment, which approach is
 >>>> mandatory to implement for servers and clients?  Or, is it the case that
 >>>> participating TLS clients (ie web browsers etc) implement all three
 >>>> methods,
 >>>> and TLS servers can choose any of them?
 >>>
 >>> The latter.
 >>
 >> That should be made very clear. Is the reason for doing so to obtain
 >> operational experience wrt the three defined methods such that they perhaps
 >> can be narrowed down in the future, or is the expectation that TLS-CT
 >> clients will need to support all three methods in perpetuity?
 >
 > I think I made that clear.
 >
 > The reason three methods exist are as follows (I don't intend to get
 > into this in the RFC, but for your edification):
 >
 > 1. TLS extension is the right way to do it, but requires a server s/w
 > change - this adds many years to full deployment.
 >
 > 2. So, alternatives must be provided. One is to put the stuff in the
 > certificate, but...
 >
 > 3. ... some CAs have said they'd rather not gate issuance on the log,
 > so alternatively, wedge the stuff in an OCSP response (which must be
 > stapled - servers exist that support this option already).

ok, thx for elucidation.


<snip>
 >>>> 6. Signed tree heads (STHs) are denoted in terms of "tree size" (number
 >>>> of
 >>>> entries), but SCTs are denoted in terms of a timestamp.  Should there be
 >>>> a
 >>>> log client message supporting the return of the nearest STH (and thus
 >>>> tree
 >>>> size) to a given timestamp?
 >>>
 >>> I'm not sure why? Any STH (that includes that SCT) will do.
 >>
 >> Hm, it was sort of a gut feel that it might be useful, but perhaps not.
 >>
 >> S5.2. Auditor says..
 >>
 >>    A certificate accompanied by an SCT can be verified against any STH
 >>    dated after the SCT timestamp + the Maximum Merge Delay by requesting
 >>    a Merkle Audit Proof using Section 4.5.
 >>
 >> S4.5 get-proof-by-hash stipulates tree_size as an input,  but
 >> if a log auditor doesn't already have tree_size, then I suppose it first
 >> calls S4.3 get-sth, which will return a timestamp and a tree_size, which if
 >> generated max merge delay (MMD) after the SCT was gen'd, ought to be
 >> sufficient, yes?
 >
 > Yes.
 >
 >> I don't see in the spec where/how MMD is published.  Does MMD vary per log
 >> service?  The latter isn't stipulated in the spec it seems AFAICT ?
 >
 > We have not really figured out how MMD is specified. I suspect it is
 > something that will be agreed between browser vendors and logs.

ok, tho specified in terms of an operational value agreed between browser 
vendors and logs is different than whatever mechanism a log service uses to 
"publish" its chosen MMD value, and log monitors/auditors will want to get the 
MMD value(s), yes?


 >>>> 7. S3 paragraph 2 states that "TLS clients MUST reject certificates that
 >>>> do
 >>>> not have a valid SCT for the end-entity certificate" (i.e., hard-fail).
 >>>> Presummably this requirement is only for TLS clients participating in the
 >>>> CT
 >>>> experiment and that understand this protocol.
 >>>
 >>> Of course - what other way could it be? In other words, all RFCs can
 >>> only say what implementations that conform with them do.
 >>>
 >>>> This, or whatever the
 >>>> requirement actually is, should be further explained.
 >>
 >> I guess what I was getting at is that CT-conformant TLS clients should be
 >> differentiated from non-CT-conformant ones. Stipulating a name for
 >> CT-conformant TLS clients would clarify this (seems to me), e.g. "TLS-CT
 >> client" or something similar.
 >
 > I understand what you're getting at, but not why.

well, its a minor item, but the "why" is that when folks come across this spec 
(eg in searching for TLS specs), and in discussions in various fora, that 
there's a name for ct-capable TLS clients, since not all tls clients will be so 
capable.



<snip>
 >> The differences between the spec and [CrosbyWallach] doesn't seem to be that
 >> large, and so if there aren't more closely matching paper(s) to cite (?), it
 >> may be worth summarizing the differences between the spec and
 >> [CrosbyWallach] e.g. in an appendix.
 >>
 >>
 >>> "commitment" is a term of cryptographic art.
 >>
 >> so it is, but its definitions in the literature seem to vary somewhat
 >> depending on context.  IIUC, the spec uses "commitment" to refer to the hash
 >> labels of intermediate nodes ('interior nodes' in [CrosbyWallach]) as well
 >> as the root hash, yes?
 >>
 >> In S2.1.1, where it says..
 >>
 >>          We prove that the left subtree entries D[0:k] are consistent
 >>    and add a commitment to D[k:n]:
 >>
 >> ..it's not clear just what "add a commitment" means. add it (an
 >> intermediate-node hash?) to the list of hashes that the recursive algorthm
 >> is constructing?
 >>
 >> Overall, I'm finding S2.1.1 pretty difficult to parse and sort out.
 >>
 >> E.g., it isn't clear to me how/why/when the apparently boolean 3d parameter
 >> of SUBPROOF is either true or false, and whether there's an implied "if b
 >> then ... else ..."  in there somewhere.
 >
 > Its reasonably hard to define this thing rigorously, and so I'm not
 > surprised you find it hard to follow - but as I think I've said
 > before, we did try various different phrasings and did not find an
 > easier one. Suggestions welcome.

ok. I suppose clarifying the use of the boolean 3d parameter of SUBPROOF is a 
place to start, tho I'm not sure of its use at this time, so don't feel able to 
suggest text :(      (i haven't grokked the code on this point either..)



 >> I don't know if it would be better (I've compiled it and am poking through
 >> the code). I sorta think pseudo code in an appendix that would generate the
 >> trees in S2.1.3. would be helpful.
 >
 > I suspect this is more relevant to a non experimental RFC -

I spose.

 >  right now
 > I have no evidence that anyone is planning to actually write code
 > other than us - AFAIK, so far everyone who has played with it has used
 > our code.

ok.


<snip>
 >>>> Suggested rephrase for this where it occurs throughout section 2..
 >>>>
 >>>>     For n > 1, let k be a number which is the largest power of two
 >>>>     such that k = 2^i, 0 <= i < n, and k < n.
 >>>
 >>> If we're going to go down that path, then it should say:
 >>>
 >>> For n > 1, let k be the largest number such that k = 2^i and k < n.
 >>>
 >>> or
 >>>
 >>> For n > 1, let k = 2^i s.t. k < n and 2k >= n.
 >>>
 >>> surely?
 >>
 >> well, yes (i prefer the former), but i think it's also important to
 >> explicitly state 0 <= i < n
 >
 > Why? Its weird! its also not generally true - e.g. n=2 and i=1.

ok, what i was getting at is that in the latter statement..

   For n > 1, let k = 2^i s.t. k < n and 2k >= n

..shouldn't the range of "i" also be specified? especially that it's lower bound 
is 0 <= i ?   (i haven't stared at math texts for a while and don't recall 
whether they'd leave "i" only tacitly specified..)

For n=2, k=1, i=0   yes?


<snip>
 >>>>>    MTH(D[n]) = SHA-256(0x01 || MTH(D[0:k]) || MTH(D[k:n])),
 >>>>>
 >>>>>    where || is concatenation and D[k1:k2] denotes the length (k2 - k1)
 >>>>>    list {d(k1), d(k1+1),..., d(k2-1)}.
 >>>>
 >>>>
 >>>> The above phrase doesn't parse well and is somewhat ambiguous, here it is
 >>>> extracted for clarity:
 >>>>
 >>>>  "D[k1:k2] denotes the length (k2 - k1) list {d(k1), d(k1+1),...,
 >>>> d(k2-1)}"
 >>>>
 >>>>
 >>>> How about rephrasing it along the lines of this:
 >>>>
 >>>>     D[k1:k2] denotes a sublist {d(k1), d(k1+1),..., d(k2-1)}, having
 >>>>     (k2 - k1) elements, of the original input list D[n]. When (k2 - k1)
 >>>>     is 1, a leaf hash is calculated.
 >>>
 >>> We tried lots of different ways of saying this and they were all a
 >>> little messy. Yours mixes concerns and is rather verbose, so not
 >>> convinced it is actually an improvement.
 >>
 >> well, the way it's presently said in the spec is (to me) pretty darn hard to
 >> understand.
 >>
 >> which concerns are missed in the suggested reformulation?
 >
 > I said "mixes" :-)

doh :)

 > That is, it mixes the hashing up with the definition of the list.
 > Other than that, I'm OK with the rephrasing.

oh, well, perhaps just saying..

      D[k1:k2] denotes a sublist {d(k1), d(k1+1),..., d(k2-1)}, having
      (k2 - k1) elements, of the original input list D[n].

..to supplant..

  "D[k1:k2] denotes the length (k2 - k1) list {d(k1), d(k1+1),..., d(k2-1)}"

?

and placing "When (k2 - k1) is 1, a leaf hash is calculated." (or something 
akin) elsewhere appropriate?  (sounds like from your various msgs you might have 
already done the equivalent)


HTH,

=JeffH



From fluffy@cisco.com  Mon Jan 28 21:06:32 2013
Return-Path: <fluffy@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 010BE1F0D06 for <ietf@ietfa.amsl.com>; Mon, 28 Jan 2013 21:06:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.599
X-Spam-Level: 
X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
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 YZnWrohHw2eW for <ietf@ietfa.amsl.com>; Mon, 28 Jan 2013 21:06:31 -0800 (PST)
Received: from rcdn-iport-4.cisco.com (rcdn-iport-4.cisco.com [173.37.86.75]) by ietfa.amsl.com (Postfix) with ESMTP id 010E81F0D05 for <ietf@ietf.org>; Mon, 28 Jan 2013 21:06:30 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3940; q=dns/txt; s=iport; t=1359435991; x=1360645591; h=from:to:subject:date:message-id:references:in-reply-to: content-id:content-transfer-encoding:mime-version; bh=EyWsNCpF41pTsDuR/gVQTC2GDfAbkUCwJjSAlHR4IFs=; b=ep6LCYWznn99o0O3Mg00cr9yTkPL3MazMnCQps+ZWMYu4ELmfG+GkZbx U9ixTDmqKuHna013+kzXASO3XSWpZuDRv3iWl3pDBX1mKoH7Kw11vqQHq x0NMCpsBY/ug2giuOjmFrCaKNpFiGG/xrww3yl+BJccVZIc4cTWRYCNPq 0=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av8EAHZXB1GtJV2d/2dsb2JhbABEvloWc4IeAQEBAwE6LQcGFQIBCCIUBQsyFBECBBMIiAMGDLAokBaNCoMaYQOXKY8sgneBbzU
X-IronPort-AV: E=Sophos;i="4.84,556,1355097600"; d="scan'208";a="169644881"
Received: from rcdn-core-6.cisco.com ([173.37.93.157]) by rcdn-iport-4.cisco.com with ESMTP; 29 Jan 2013 05:06:30 +0000
Received: from xhc-aln-x09.cisco.com (xhc-aln-x09.cisco.com [173.36.12.83]) by rcdn-core-6.cisco.com (8.14.5/8.14.5) with ESMTP id r0T56UWR028254 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <ietf@ietf.org>; Tue, 29 Jan 2013 05:06:30 GMT
Received: from xmb-aln-x02.cisco.com ([169.254.5.197]) by xhc-aln-x09.cisco.com ([173.36.12.83]) with mapi id 14.02.0318.004; Mon, 28 Jan 2013 23:06:29 -0600
From: "Cullen Jennings (fluffy)" <fluffy@cisco.com>
To: "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: Last Call: <draft-farrell-ft-03.txt> (A Fast-Track way to RFC with Running Code) to Experimental RFC
Thread-Topic: Last Call: <draft-farrell-ft-03.txt> (A Fast-Track way to RFC with Running Code) to Experimental RFC
Thread-Index: AQHN/d5ljmwMCvb81E+mN8nEnmYlBA==
Date: Tue, 29 Jan 2013 05:06:12 +0000
Message-ID: <C5E08FE080ACFD4DAE31E4BDBF944EB1133A0FB4@xmb-aln-x02.cisco.com>
References: <20130111151453.22161.50884.idtracker@ietfa.amsl.com>
In-Reply-To: <20130111151453.22161.50884.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.20.249.164]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <FB02959576C59B4A8DFFF1350FB6B6F6@cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 29 Jan 2013 05:06:32 -0000

My read of this draft is that it eliminates the need for rough consensus at=
 both the WG and IETF level. Basically the WG chair can just decide and eve=
n if the WG disagrees with the chair. If the WG does not have consensus in =
WGLC that they they do want to publish the draft, it still gets published. =
I realize from the email list discussions this may not be what the author o=
f the draft intended but it is how I read this draft. =20

Because of this, I am against approving this and also believe it would need=
 to be BCP not experimental as it changes the fundamental process to approv=
e PS drafts.=20

The rest of this draft, the part about overlapping, is already allowed by t=
he process today as the draft points out. The WGLC is not required at all, =
the AD processing and  IETF LC can overlap. However, I think that the AD sh=
ould do their processing before they LC the draft because that means they c=
heck it is ready before wasting the IESG and everyone else's time revving a=
 document. AD processing can often be done in a few hours or less if the dr=
aft is ready. Generally, WGLC avoids late surprises which take more time in=
 the long run but all of this is a general guideline and there are cases wh=
ere it make sense to overlap all this and put it through. Thus I think it i=
s good that the current process allows this to all be overlapped at the cha=
ir and AD discretion.=20

I encourage the AD & Chairs to overlap where they think it will 1) is appro=
priate 2) will speed things up and 3) the speed up actually helps the inter=
net or some groups of users in a meaningful way. I'm certainly not against =
some chairs, ADs, etc trying to put a draft throughout quickly that they th=
ink is ready (running code or not) but I don't see the need for this change=
 to the process.=20

I also have a question for the each IESG member that I think is very releva=
nt - Do all of you agree to only put discussed that meet the "Discuss Crite=
ria" this draft refers too? I really hope you do. If you don't that raises =
even more issues for how this draft changes the process.=20

Cullen




On Jan 11, 2013, at 8:14 AM, The IESG <iesg-secretary@ietf.org> wrote:

>=20
> The IESG has received a request from an individual submitter to consider
> the following document:
> - 'A Fast-Track way to RFC with Running Code'
>  <draft-farrell-ft-03.txt> as Experimental RFC
>=20
> The IESG plans to make a decision in the next few weeks, and solicits
> final comments on this action. Please send substantive comments to the
> ietf@ietf.org mailing lists by 2013-02-08. Exceptionally, comments may be
> sent to iesg@ietf.org instead. In either case, please retain the
> beginning of the Subject line to allow automated sorting.
>=20
> Abstract
>=20
>   This memo describes an optional, fast-track way to progress a working
>   group document to IESG review.  It is provided as a process
>   experiment as defined in RFC 3933 for use when working group chairs
>   believe that there is running code that implements a working group
>   Internet-Draft.  The motivation is to have the IETF process
>   explicitly consider running code, consistent with the IETF's overall
>   philosophy of running code and rough consensus.
>=20
>   In this process all of working group last call, IETF last call, and
>   Area Director review are carried out in the same two week period.
>   Only comments that meet IESG Discuss criteria need to be addressed
>   during this stage, and authors are required to make any changes
>   within two weeks.
>=20
>   This experiment will run for one year.
>=20
>=20
> The file can be obtained via
> http://datatracker.ietf.org/doc/draft-farrell-ft/
>=20
> IESG discussion can be tracked via
> http://datatracker.ietf.org/doc/draft-farrell-ft/ballot/
>=20
> No IPR declarations have been submitted directly on this I-D.


From stephen.farrell@cs.tcd.ie  Tue Jan 29 02:00:10 2013
Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1DBE121F85EA for <ietf@ietfa.amsl.com>; Tue, 29 Jan 2013 02:00:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.524
X-Spam-Level: 
X-Spam-Status: No, score=-102.524 tagged_above=-999 required=5 tests=[AWL=0.075, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 ui41+-62W0Ab for <ietf@ietfa.amsl.com>; Tue, 29 Jan 2013 02:00:09 -0800 (PST)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) by ietfa.amsl.com (Postfix) with ESMTP id F2B6221F85AD for <ietf@ietf.org>; Tue, 29 Jan 2013 02:00:08 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id 08FC3BE51; Tue, 29 Jan 2013 09:59:46 +0000 (GMT)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id b3-H8F+a6Mu7; Tue, 29 Jan 2013 09:59:44 +0000 (GMT)
Received: from [IPv6:2001:770:10:203:75b2:48e:2a5f:bc82] (unknown [IPv6:2001:770:10:203:75b2:48e:2a5f:bc82]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 876A8BE1E; Tue, 29 Jan 2013 09:59:44 +0000 (GMT)
Message-ID: <51079D91.3070308@cs.tcd.ie>
Date: Tue, 29 Jan 2013 09:59:45 +0000
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130106 Thunderbird/17.0.2
MIME-Version: 1.0
To: "Cullen Jennings (fluffy)" <fluffy@cisco.com>
Subject: Re: Last Call: <draft-farrell-ft-03.txt> (A Fast-Track way to RFC with Running Code) to Experimental RFC
References: <20130111151453.22161.50884.idtracker@ietfa.amsl.com> <C5E08FE080ACFD4DAE31E4BDBF944EB1133A0FB4@xmb-aln-x02.cisco.com>
In-Reply-To: <C5E08FE080ACFD4DAE31E4BDBF944EB1133A0FB4@xmb-aln-x02.cisco.com>
X-Enigmail-Version: 1.5
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 29 Jan 2013 10:00:10 -0000

Responses to Cullen below, but this is getting to the point
where unless someone else who likes the idea wants to join
the discussion, I'm going to conclude that we're collectively
either unwilling or unable to consider 3933 experiments and
regard this one as dead, which maybe means 3933 is dead-ish
too, I dunno. (And before someone asks: no, I don't conclude
that its just a problem with this particular experiment, and
yes, I might be wrong there:-)

On 01/29/2013 05:06 AM, Cullen Jennings (fluffy) wrote:
> 
> My read of this draft is that it eliminates the need for rough consensus at both the WG and IETF level. Basically the WG chair can just decide and even if the WG disagrees with the chair. If the WG does not have consensus in WGLC that they they do want to publish the draft, it still gets published. I realize from the email list discussions this may not be what the author of the draft intended but it is how I read this draft.  

Right, that is not the intent. I also don't think this
experiment would have that effect, but neither of us
can prove either thing. I'll note yet again that this
experiment would only affect a few drafts where WG chairs
have chosen to try it out, and only for a year, so I
fully disagree that this "eliminates the need for rough
consensus" at all and consider that as a fairly whopping
overstatement that assumes that all drafts must follow
this fast-track process and assumes that the worst thing
happens as a result.

> Because of this, I am against approving this and also believe it would need to be BCP not experimental as it changes the fundamental process to approve PS drafts. 

If you've read 3933 then I don't get how you can say
that - 3933 calls for this draft to be last called for
experimental.


> The rest of this draft, the part about overlapping, is already allowed by the process today as the draft points out. The WGLC is not required at all, the AD processing and  IETF LC can overlap. However, I think that the AD should do their processing before they LC the draft because that means they check it is ready before wasting the IESG and everyone else's time revving a document. AD processing can often be done in a few hours or less if the draft is ready. Generally, WGLC avoids late surprises which take more time in the long run but all of this is a general guideline and there are cases where it make sense to overlap all this and put it through. Thus I think it is good that the current process allows this to all be overlapped at the chair and AD discretion. 

That seems to contradict your first paragraph where you
seem to say that we do need a WGLC so I'm not getting
how those can go together.

> I encourage the AD & Chairs to overlap where they think it will 1) is appropriate 2) will speed things up and 3) the speed up actually helps the internet or some groups of users in a meaningful way. I'm certainly not against some chairs, ADs, etc trying to put a draft throughout quickly that they think is ready (running code or not) but I don't see the need for this change to the process. 

Again, its not a process change. Its meant as a process
experiment. That means that after a year, things go back
to where they were, and we evaluate whether or not there's
anything that ought become a process change.

> I also have a question for the each IESG member that I think is very relevant - Do all of you agree to only put discussed that meet the "Discuss Criteria" this draft refers too? I really hope you do. If you don't that raises even more issues for how this draft changes the process. 

There's an IESG statement [1] that says that and that
does get brought up when one AD thinks another's
DISCUSS doesn't meet the criteria. That doesn't
happen on every call, but maybe every month or two,
and the DISCUSSing ADs do afaics take that seriously.
Authors and chairs ought to feel free to say if
they think the DISCUSS doesn't fit [1] IMO, (not
many do, mostly former ADs funnily enough;-) so
I don't think other IESG members need to directly
respond here.

Cheers,
S.

[1] https://www.ietf.org/iesg/statement/discuss-criteria.html


> Cullen
> 
> 
> 
> 
> On Jan 11, 2013, at 8:14 AM, The IESG <iesg-secretary@ietf.org> wrote:
> 
>>
>> The IESG has received a request from an individual submitter to consider
>> the following document:
>> - 'A Fast-Track way to RFC with Running Code'
>>  <draft-farrell-ft-03.txt> as Experimental RFC
>>
>> The IESG plans to make a decision in the next few weeks, and solicits
>> final comments on this action. Please send substantive comments to the
>> ietf@ietf.org mailing lists by 2013-02-08. Exceptionally, comments may be
>> sent to iesg@ietf.org instead. In either case, please retain the
>> beginning of the Subject line to allow automated sorting.
>>
>> Abstract
>>
>>   This memo describes an optional, fast-track way to progress a working
>>   group document to IESG review.  It is provided as a process
>>   experiment as defined in RFC 3933 for use when working group chairs
>>   believe that there is running code that implements a working group
>>   Internet-Draft.  The motivation is to have the IETF process
>>   explicitly consider running code, consistent with the IETF's overall
>>   philosophy of running code and rough consensus.
>>
>>   In this process all of working group last call, IETF last call, and
>>   Area Director review are carried out in the same two week period.
>>   Only comments that meet IESG Discuss criteria need to be addressed
>>   during this stage, and authors are required to make any changes
>>   within two weeks.
>>
>>   This experiment will run for one year.
>>
>>
>> The file can be obtained via
>> http://datatracker.ietf.org/doc/draft-farrell-ft/
>>
>> IESG discussion can be tracked via
>> http://datatracker.ietf.org/doc/draft-farrell-ft/ballot/
>>
>> No IPR declarations have been submitted directly on this I-D.
> 

From benl@google.com  Tue Jan 29 02:52:56 2013
Return-Path: <benl@google.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3BF6621F8884 for <ietf@ietfa.amsl.com>; Tue, 29 Jan 2013 02:52:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.876
X-Spam-Level: 
X-Spam-Status: No, score=-102.876 tagged_above=-999 required=5 tests=[AWL=0.101, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
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 y8aILhXIBsZm for <ietf@ietfa.amsl.com>; Tue, 29 Jan 2013 02:52:55 -0800 (PST)
Received: from mail-bk0-f48.google.com (mail-bk0-f48.google.com [209.85.214.48]) by ietfa.amsl.com (Postfix) with ESMTP id 6674921F86FA for <ietf@ietf.org>; Tue, 29 Jan 2013 02:52:55 -0800 (PST)
Received: by mail-bk0-f48.google.com with SMTP id jf20so165068bkc.35 for <ietf@ietf.org>; Tue, 29 Jan 2013 02:52:54 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=PCRjv7osl+AhzB7sMf3M8nJnsnWQZK5obs57EZA4t2o=; b=JnS4cK5iT/2tJMIsY/gYQFmEpy6WEizaEo2r+XFJPV0F/8k2hkaKaBHAIOOPqdnZre y79Keuhjdf9PdXFGNbKDe9z2+JthXda+pPZqiObwFFjj+UuuVd3LoqNo+9jyOJznenCK nZwcLXDZghEfP4L5zuWKsCgINRyxtQ7G5QiSmHRJUzCvvCbXxdWwTaQY8QSIZtAQJ1jM 5vSzBuVwsGhb8+OylVA0UPCH2hYesQP1rKIPPhFXNipIVM2vNh00sV2fr8pih5noBD8P V1u8A01DkajPZE9+1mpzWB4eSQlVf0bnMdG2Acy5Wko0oGlzbMeixBazp+bn3Ix7O9KV M88Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type:x-gm-message-state; bh=PCRjv7osl+AhzB7sMf3M8nJnsnWQZK5obs57EZA4t2o=; b=WFtbDdED8yWiq49HUfndfrEfTi09UyUScFpGy8RBde8MJk97mAtaAWWNFEla05j08z 7VXpRABjrpV3sOiiUAtEQyg5Z9uy0vJAFbB6Nn+eDgO4eJ6RSrZZ4Tp+e4xeDrNgItsb Ti03ncdA6kqeoBqMmMrYEij+c1SKtB91eSgMjai5qHoD8eVPqfsk0IY2Im4PL+8twWwd hfvKw1uJ+ekJK+cwlSckYyPREOUFctKK570AYWykF41ThwEas7/fdcg6X/YNm/RXXfum HQTKagBAx8L5uuw2MwkCiAtLAs/QIxlVQAYjpZrJOu2SpH3HJgYD6OyWOX5NZPs78zQv Mn1w==
MIME-Version: 1.0
X-Received: by 10.204.150.205 with SMTP id z13mr211930bkv.16.1359456774147; Tue, 29 Jan 2013 02:52:54 -0800 (PST)
Received: by 10.204.38.198 with HTTP; Tue, 29 Jan 2013 02:52:54 -0800 (PST)
In-Reply-To: <50FF084B.5040508@KingsMountain.com>
References: <50FF084B.5040508@KingsMountain.com>
Date: Tue, 29 Jan 2013 10:52:54 +0000
Message-ID: <CABrd9SRztyz60nA+CNc4po0obnfJFo=uqnFdhadoNAQJJuin1Q@mail.gmail.com>
Subject: Re: LC comments on draft-laurie-pki-sunlight-05 - "acceptable root certificates" ?
From: Ben Laurie <benl@google.com>
To: "=JeffH" <Jeff.Hodges@kingsmountain.com>
Content-Type: text/plain; charset=ISO-8859-1
X-Gm-Message-State: ALoCoQmui9MC0QlAqKhGGW1bZHinhZgx2koHqyonGMwmuDV5BeXFr1KeB29tWqr+TrIHT5+kkm8uz8ZBdRazFT9UMctgpC+3rQgEJy/6rDwMbr2DcOxMNgGRrR2ZIXQMo5mxaCMoblBha/pyFSL8fmgr8nO3vASBT+uK1/8/+RXy8hUmYxjmtv2d+DVQMGr0LiFna39NQI4g
Cc: Emilia Kasper <ekasper@google.com>, "therightkey@ietf.org" <therightkey@ietf.org>, IETF Discussion List <ietf@ietf.org>, Adam Langley <agl@google.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 29 Jan 2013 10:52:57 -0000

On 22 January 2013 21:44, =JeffH <Jeff.Hodges@kingsmountain.com> wrote:
> <snip>
>
>>>> 3.1. Log Entries
>>>>
>>>>    Anyone can submit a certificate to any log.  In order to enable
>>>>    attribution of each logged certificate to its issuer, the log SHALL
>>>>    publish a list of acceptable root certificates (this list might
>>>>    usefully be the union of root certificates trusted by major browser
>>>>    vendors).  Each submitted certificate MUST be accompanied by all
>>>>    additional certificates required to verify the certificate chain up
>>>>    to an accepted root certificate.  The root certificate itself MAY be
>>>>    omitted from this list.
>
> a question I neglected to add here is: how do log services publish their
> lists of "acceptable root certificates" ?

In the next version there's a URL for it.

From benl@google.com  Tue Jan 29 03:16:28 2013
Return-Path: <benl@google.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2F59621F8833 for <ietf@ietfa.amsl.com>; Tue, 29 Jan 2013 03:16:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.899
X-Spam-Level: 
X-Spam-Status: No, score=-102.899 tagged_above=-999 required=5 tests=[AWL=0.078, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
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 BmG0lulolhHH for <ietf@ietfa.amsl.com>; Tue, 29 Jan 2013 03:16:27 -0800 (PST)
Received: from mail-bk0-f41.google.com (mail-bk0-f41.google.com [209.85.214.41]) by ietfa.amsl.com (Postfix) with ESMTP id C848421F8821 for <ietf@ietf.org>; Tue, 29 Jan 2013 03:16:26 -0800 (PST)
Received: by mail-bk0-f41.google.com with SMTP id q16so177069bkw.14 for <ietf@ietf.org>; Tue, 29 Jan 2013 03:16:26 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=FBMmMuT5YoPz3Y4FucHTJDW3G61Zf2ktoEOUGKBg1Uo=; b=FzOiwhF2nuFly2QEcutbisSRhgqwhqN0ym1lisXrti7dRIAexOoggsKFmwgXMeSBf5 lR7vTu0/adg8ZJSJQcxBNGAZBe4a1iUBAWKIVbPjU9h6GscmOcH5OtlTtoD59iuAFaFr 5iM10eOBMWHdJnnQbk9TiwctkUvmlcsZf+QwkD85ITwxxOIM+oLMoZEojsL5cafbulBN KfnHw7gPfl1aNqSLbhi43EWZvbMLE2UE96ZTWbVEBUfcOxzUeT9sRy3PY1LfRkufjRn8 /BYpG0cagvaNzhq5QALYCh3MMyUPByKsO+Iy6tgJn+NqrlUL94gOsJxj1CGlkS27ZmYa nTzA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type:x-gm-message-state; bh=FBMmMuT5YoPz3Y4FucHTJDW3G61Zf2ktoEOUGKBg1Uo=; b=XaFNB+W/tFiyyih/j7m2FrHu4qbw6o4bFL+qXh/B45uJwmuOi/UDFSD/gpuFqmhnI1 XAWOqiPEQez7RCo25OOGFnVDFUHigccI9gV15PeAIcKLEMBXOH9c04AmbzNWs56w5TKK rruGOBoaSOZ2ZXbHvgPFLpXx3UKNoF8njYRzetvWnVLUriDr8aPK6xxvwzV4kAfQt+i8 T1CYM05+8UCjuOCdYZKVTkpOaMFycmKf87dh+LqLM25vQ1ux2J4nShZ7AqakdycD2BVN cDZ4Z/njgyh2ny60Q2X9toizZun4uIph/FdIBDRUI1gYOY5j/EqqJBhOT07tpi9tLnUN AkcA==
MIME-Version: 1.0
X-Received: by 10.204.149.149 with SMTP id t21mr216632bkv.85.1359458185771; Tue, 29 Jan 2013 03:16:25 -0800 (PST)
Received: by 10.204.38.198 with HTTP; Tue, 29 Jan 2013 03:16:25 -0800 (PST)
In-Reply-To: <5106FE98.2020904@KingsMountain.com>
References: <5106FE98.2020904@KingsMountain.com>
Date: Tue, 29 Jan 2013 11:16:25 +0000
Message-ID: <CABrd9ST3-wF+9oJ3-YSvK6=jdr5W2W3H0Y-CPBpsDsHaB-Umqw@mail.gmail.com>
Subject: Re: LC comments on draft-laurie-pki-sunlight-05 - "acceptable root certificates" ?
From: Ben Laurie <benl@google.com>
To: "=JeffH" <Jeff.Hodges@kingsmountain.com>
Content-Type: text/plain; charset=ISO-8859-1
X-Gm-Message-State: ALoCoQnFpHg5yd6ngC9cL/OlzDluuRaBA5K1EfkcRhACETUL1GnueYcWmUtaIOFlsNdbpHME7ZpJQWNg5R7189ZfiwU+1WEkPuo2VTCgVT755QEx+BeIEfsvAnYm4s2q2mY4/1wVOeTwEE1G1kg8dd6ihZ8j53moGfwz2bGYiyV1752FGVWeRtq1f16IIDh1XrFhM6CKQ4Aa
Cc: Emilia Kasper <ekasper@google.com>, "therightkey@ietf.org" <therightkey@ietf.org>, IETF Discussion List <ietf@ietf.org>, Adam Langley <agl@google.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 29 Jan 2013 11:16:28 -0000

On 28 January 2013 22:41, =JeffH <Jeff.Hodges@kingsmountain.com> wrote:
>> Apologies for responding to recent comments in random order: I'm
>> travelling and have accumulated something of a backlog.
>
> no worries :)
>
> thx again for your thoughts.
>
>
> BenL replied:
>> On 22 January 2013 03:11, =JeffH <Jeff.Hodges@kingsmountain.com> wrote:
>
> <snip>
>>>>  - is there a
>>>> standard reference for that? I've refereced HTML 4.01, but perhaps
>>>> there's a better one?
>>>
>>> hm, AFAICT, there is not a standard for URI query component formating and
>>> thus parameter encoding, so this spec will have to explicitly specify
>>> something. Section 3.4 of RFC3986 gives allowed chars for the query
>>> component, but that's about it.
>>>
>>> Have you mocked up code that parses the log client messages? If so, what
>>> query component syntax does it handle?
>>
>> I have specified the "standard" format via HTML 4.01.
>
> ok, i assume you're referring to section 17.13 "form submission" of HTML
> 4.01, and using the  application/x-www-form-urlencoded  content type, with
> the parameters appended to the url encoded according to S17.13.4 ?

Yes.

>>>>> 6. Signed tree heads (STHs) are denoted in terms of "tree size" (number
>>>>> of
>>>>> entries), but SCTs are denoted in terms of a timestamp.  Should there
>>>>> be
>>>>> a
>>>>> log client message supporting the return of the nearest STH (and thus
>>>>> tree
>>>>> size) to a given timestamp?
>>>>
>>>> I'm not sure why? Any STH (that includes that SCT) will do.
>>>
>>> Hm, it was sort of a gut feel that it might be useful, but perhaps not.
>>>
>>> S5.2. Auditor says..
>>>
>>>    A certificate accompanied by an SCT can be verified against any STH
>>>    dated after the SCT timestamp + the Maximum Merge Delay by requesting
>>>    a Merkle Audit Proof using Section 4.5.
>>>
>>> S4.5 get-proof-by-hash stipulates tree_size as an input,  but
>>> if a log auditor doesn't already have tree_size, then I suppose it first
>>> calls S4.3 get-sth, which will return a timestamp and a tree_size, which
>>> if
>>> generated max merge delay (MMD) after the SCT was gen'd, ought to be
>>> sufficient, yes?
>>
>> Yes.
>>
>>> I don't see in the spec where/how MMD is published.  Does MMD vary per
>>> log
>>> service?  The latter isn't stipulated in the spec it seems AFAICT ?
>>
>> We have not really figured out how MMD is specified. I suspect it is
>> something that will be agreed between browser vendors and logs.
>
> ok, tho specified in terms of an operational value agreed between browser
> vendors and logs is different than whatever mechanism a log service uses to
> "publish" its chosen MMD value, and log monitors/auditors will want to get
> the MMD value(s), yes?

As I said, not clear on that: seems obvious that the MMD can't just be
fetched from the log.

>>>>> 7. S3 paragraph 2 states that "TLS clients MUST reject certificates
>>>>> that
>>>>> do
>>>>> not have a valid SCT for the end-entity certificate" (i.e., hard-fail).
>>>>> Presummably this requirement is only for TLS clients participating in
>>>>> the
>>>>> CT
>>>>> experiment and that understand this protocol.
>>>>
>>>> Of course - what other way could it be? In other words, all RFCs can
>>>> only say what implementations that conform with them do.
>>>>
>>>>> This, or whatever the
>>>>> requirement actually is, should be further explained.
>>>
>>> I guess what I was getting at is that CT-conformant TLS clients should be
>>> differentiated from non-CT-conformant ones. Stipulating a name for
>>> CT-conformant TLS clients would clarify this (seems to me), e.g. "TLS-CT
>>> client" or something similar.
>>
>> I understand what you're getting at, but not why.
>
> well, its a minor item, but the "why" is that when folks come across this
> spec (eg in searching for TLS specs), and in discussions in various fora,
> that there's a name for ct-capable TLS clients, since not all tls clients
> will be so capable.

"Conforms to RFC xxxx"? "Is CT capable"? Not sure the RFC is the place
to decide what people say!

> <snip>
>>> The differences between the spec and [CrosbyWallach] doesn't seem to be
>>> that
>>> large, and so if there aren't more closely matching paper(s) to cite (?),
>>> it
>>> may be worth summarizing the differences between the spec and
>>> [CrosbyWallach] e.g. in an appendix.
>>>
>>>
>>>> "commitment" is a term of cryptographic art.
>>>
>>> so it is, but its definitions in the literature seem to vary somewhat
>>> depending on context.  IIUC, the spec uses "commitment" to refer to the
>>> hash
>>> labels of intermediate nodes ('interior nodes' in [CrosbyWallach]) as
>>> well
>>> as the root hash, yes?
>>>
>>> In S2.1.1, where it says..
>>>
>>>          We prove that the left subtree entries D[0:k] are consistent
>>>    and add a commitment to D[k:n]:
>>>
>>> ..it's not clear just what "add a commitment" means. add it (an
>>> intermediate-node hash?) to the list of hashes that the recursive
>>> algorthm
>>> is constructing?
>>>
>>> Overall, I'm finding S2.1.1 pretty difficult to parse and sort out.
>>>
>>> E.g., it isn't clear to me how/why/when the apparently boolean 3d
>>> parameter
>>> of SUBPROOF is either true or false, and whether there's an implied "if b
>>> then ... else ..."  in there somewhere.
>>
>> Its reasonably hard to define this thing rigorously, and so I'm not
>> surprised you find it hard to follow - but as I think I've said
>> before, we did try various different phrasings and did not find an
>> easier one. Suggestions welcome.
>
> ok. I suppose clarifying the use of the boolean 3d parameter of SUBPROOF is
> a place to start, tho I'm not sure of its use at this time, so don't feel
> able to suggest text :(      (i haven't grokked the code on this point
> either..)

I don't get you - the use is defined entirely by the algorithm. It
possibly doesn't help that the first step of the algorithm is buried
in text instead of having a line to itself, so I've corrected that.

> <snip>
>>>>> Suggested rephrase for this where it occurs throughout section 2..
>>>>>
>>>>>     For n > 1, let k be a number which is the largest power of two
>>>>>     such that k = 2^i, 0 <= i < n, and k < n.
>>>>
>>>> If we're going to go down that path, then it should say:
>>>>
>>>> For n > 1, let k be the largest number such that k = 2^i and k < n.
>>>>
>>>> or
>>>>
>>>> For n > 1, let k = 2^i s.t. k < n and 2k >= n.
>>>>
>>>> surely?
>>>
>>> well, yes (i prefer the former), but i think it's also important to
>>> explicitly state 0 <= i < n
>>
>> Why? Its weird! its also not generally true - e.g. n=2 and i=1.
>
> ok, what i was getting at is that in the latter statement..
>
>   For n > 1, let k = 2^i s.t. k < n and 2k >= n
>
> ..shouldn't the range of "i" also be specified? especially that it's lower
> bound is 0 <= i ?   (i haven't stared at math texts for a while and don't
> recall whether they'd leave "i" only tacitly specified..)

i is specified entirely by the text (i.e. there is only one i that
satisfies 2^i < n and 2^(i+1) >= n, for all n > 1).

> For n=2, k=1, i=0   yes?

Sorry, yes, you are correct.

>
>
> <snip>
>>>>>>    MTH(D[n]) = SHA-256(0x01 || MTH(D[0:k]) || MTH(D[k:n])),
>>>>>>
>>>>>>    where || is concatenation and D[k1:k2] denotes the length (k2 - k1)
>>>>>>    list {d(k1), d(k1+1),..., d(k2-1)}.
>>>>>
>>>>>
>>>>> The above phrase doesn't parse well and is somewhat ambiguous, here it
>>>>> is
>>>>> extracted for clarity:
>>>>>
>>>>>  "D[k1:k2] denotes the length (k2 - k1) list {d(k1), d(k1+1),...,
>>>>> d(k2-1)}"
>>>>>
>>>>>
>>>>> How about rephrasing it along the lines of this:
>>>>>
>>>>>     D[k1:k2] denotes a sublist {d(k1), d(k1+1),..., d(k2-1)}, having
>>>>>     (k2 - k1) elements, of the original input list D[n]. When (k2 - k1)
>>>>>     is 1, a leaf hash is calculated.
>>>>
>>>> We tried lots of different ways of saying this and they were all a
>>>> little messy. Yours mixes concerns and is rather verbose, so not
>>>> convinced it is actually an improvement.
>>>
>>> well, the way it's presently said in the spec is (to me) pretty darn hard
>>> to
>>> understand.
>>>
>>> which concerns are missed in the suggested reformulation?
>>
>> I said "mixes" :-)
>
> doh :)
>
>> That is, it mixes the hashing up with the definition of the list.
>> Other than that, I'm OK with the rephrasing.
>
> oh, well, perhaps just saying..
>
>      D[k1:k2] denotes a sublist {d(k1), d(k1+1),..., d(k2-1)}, having
>      (k2 - k1) elements, of the original input list D[n].
>
> ..to supplant..
>
>  "D[k1:k2] denotes the length (k2 - k1) list {d(k1), d(k1+1),..., d(k2-1)}"
>
> ?

I did something like this.

> and placing "When (k2 - k1) is 1, a leaf hash is calculated." (or something
> akin) elsewhere appropriate?  (sounds like from your various msgs you might
> have already done the equivalent)

Yes.

>
>
> HTH,
>
> =JeffH
>
>

From narten@us.ibm.com  Tue Jan 29 06:40:19 2013
Return-Path: <narten@us.ibm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C561221F8891 for <ietf@ietfa.amsl.com>; Tue, 29 Jan 2013 06:40:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.599
X-Spam-Level: 
X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
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 Ql0Js4cOYC3x for <ietf@ietfa.amsl.com>; Tue, 29 Jan 2013 06:40:18 -0800 (PST)
Received: from e9.ny.us.ibm.com (e9.ny.us.ibm.com [32.97.182.139]) by ietfa.amsl.com (Postfix) with ESMTP id AF8AE21F8487 for <ietf@ietf.org>; Tue, 29 Jan 2013 06:40:18 -0800 (PST)
Received: from /spool/local by e9.ny.us.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for <ietf@ietf.org> from <narten@us.ibm.com>; Tue, 29 Jan 2013 09:40:18 -0500
Received: from d01dlp03.pok.ibm.com (9.56.250.168) by e9.ny.us.ibm.com (192.168.1.109) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted;  Tue, 29 Jan 2013 09:40:16 -0500
Received: from d01relay02.pok.ibm.com (d01relay02.pok.ibm.com [9.56.227.234]) by d01dlp03.pok.ibm.com (Postfix) with ESMTP id 95F48C90042 for <ietf@ietf.org>; Tue, 29 Jan 2013 09:40:13 -0500 (EST)
Received: from d01av02.pok.ibm.com (d01av02.pok.ibm.com [9.56.224.216]) by d01relay02.pok.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id r0TEeD7v306410 for <ietf@ietf.org>; Tue, 29 Jan 2013 09:40:13 -0500
Received: from d01av02.pok.ibm.com (loopback [127.0.0.1]) by d01av02.pok.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP id r0TEeCj0011162 for <ietf@ietf.org>; Tue, 29 Jan 2013 12:40:13 -0200
Received: from cichlid.raleigh.ibm.com (sig-9-76-155-130.mts.ibm.com [9.76.155.130]) by d01av02.pok.ibm.com (8.14.4/8.13.1/NCO v10.0 AVin) with ESMTP id r0TEeCH1011036 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 29 Jan 2013 12:40:12 -0200
Received: from cichlid.raleigh.ibm.com (localhost.localdomain [127.0.0.1]) by cichlid.raleigh.ibm.com (8.14.5/8.12.5) with ESMTP id r0TEYwm1029033; Tue, 29 Jan 2013 09:35:01 -0500
Message-Id: <201301291435.r0TEYwm1029033@cichlid.raleigh.ibm.com>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Subject: Re: Last Call: <draft-farrell-ft-03.txt> (A Fast-Track way to RFC with Running Code) to Experimental RFC
In-reply-to: <51079D91.3070308@cs.tcd.ie>
References: <20130111151453.22161.50884.idtracker@ietfa.amsl.com> <C5E08FE080ACFD4DAE31E4BDBF944EB1133A0FB4@xmb-aln-x02.cisco.com> <51079D91.3070308@cs.tcd.ie>
Comments: In-reply-to Stephen Farrell <stephen.farrell@cs.tcd.ie> message dated "Tue, 29 Jan 2013 09:59:45 +0000."
Date: Tue, 29 Jan 2013 09:34:58 -0500
From: Thomas Narten <narten@us.ibm.com>
X-Content-Scanned: Fidelis XPS MAILER
x-cbid: 13012914-7182-0000-0000-000004C69F93
Cc: "Cullen Jennings \(fluffy\)" <fluffy@cisco.com>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 29 Jan 2013 14:40:19 -0000

Stephen Farrell <stephen.farrell@cs.tcd.ie> writes:

> Responses to Cullen below, but this is getting to the point
> where unless someone else who likes the idea wants to join
> the discussion, I'm going to conclude that we're collectively
> either unwilling or unable to consider 3933 experiments and
> regard this one as dead, which maybe means 3933 is dead-ish
> too, I dunno. (And before someone asks: no, I don't conclude
> that its just a problem with this particular experiment, and
> yes, I might be wrong there:-)

I object to this (and have come close to saying it a few times
before).

One of the things that further undermines potential support for
something (and further raises questions about intentions) is when
people raise legitmate and substantive issues with a specific
proposal, and the responses start moving away from responding to the
substance to arguments  like "Gee, can't we even do experiments anymore",
etc., etc.

This document is not getting pushback because we "collectively" are
"unwilling or unable to consider experiments". Rather, from the list
traffic, some folk have real issues with the content. Can you please
accept that and stick to the substance?

For me, as I've said before, this just isn't an experiment worth
spending time on. Too little bang for the buck, and I see serious
potential downsides. Can you please just accept that some people have
that view?  And please don't turn around with the "how will we know if
we don't try?" line of argument. There is little need to try something
as an experiment if the likely outcome seems clear.

Thomas


From adrian@olddog.co.uk  Tue Jan 29 07:06:12 2013
Return-Path: <adrian@olddog.co.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 968E721F8A00; Tue, 29 Jan 2013 07:06:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599]
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 iCpdKdV+kXnF; Tue, 29 Jan 2013 07:06:12 -0800 (PST)
Received: from asmtp3.iomartmail.com (asmtp3.iomartmail.com [62.128.201.159]) by ietfa.amsl.com (Postfix) with ESMTP id 00EEF21F8A08; Tue, 29 Jan 2013 07:06:11 -0800 (PST)
Received: from asmtp3.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp3.iomartmail.com (8.13.8/8.13.8) with ESMTP id r0TF67Da025170;  Tue, 29 Jan 2013 15:06:07 GMT
Received: from 950129200 (83-215-186-5.stjo.dyn.salzburg-online.at [83.215.186.5]) (authenticated bits=0) by asmtp3.iomartmail.com (8.13.8/8.13.8) with ESMTP id r0TF65c2025160 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 29 Jan 2013 15:06:06 GMT
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: <ietf@ietf.org>
Subject: Premature termination of IETF last call on draft-farrell-ft
Date: Tue, 29 Jan 2013 15:05:47 -0000
Message-ID: <010b01cdfe32$2a128890$7e3799b0$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: Ac3+Md1xqp5hV6gqQzKP7MVaYNdV2Q==
Content-Language: en-gb
Cc: iesg-secretary@iesg.org, iesg@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: adrian@olddog.co.uk
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 29 Jan 2013 15:06:12 -0000

Hi,

This email terminates (prematurely) the IETF last call on draft-farrell-ft.

It is clear to me that this document will not be advanced for further IESG
evaluation without considerable further work and a subsequent IETF last call.
There is no point in continuing this IETF last call.

In no way does this email stop you from discussing this document or the ideas it
contains on this mailing list.

I have moved the document into "AD Is Watching" state in the data tracker and
will work with the author to determine how he wants to process your comments and
the document.

Thanks,
Adrian



From dhc@dcrocker.net  Tue Jan 29 08:13:46 2013
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AECD921F87D7 for <ietf@ietfa.amsl.com>; Tue, 29 Jan 2013 08:13:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[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 tT8hqK8xCXX7 for <ietf@ietfa.amsl.com>; Tue, 29 Jan 2013 08:13:46 -0800 (PST)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 16B2C21F87BB for <ietf@ietf.org>; Tue, 29 Jan 2013 08:13:46 -0800 (PST)
Received: from [192.168.1.66] (76-218-9-215.lightspeed.sntcca.sbcglobal.net [76.218.9.215]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id r0TGDeQE023065 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 29 Jan 2013 08:13:41 -0800
Message-ID: <5107F531.2040304@dcrocker.net>
Date: Tue, 29 Jan 2013 08:13:37 -0800
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130107 Thunderbird/17.0.2
MIME-Version: 1.0
To: "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: Last Call: <draft-farrell-ft-03.txt> (A Fast-Track way to RFC with Running Code) to Experimental RFC
References: <20130111151453.22161.50884.idtracker@ietfa.amsl.com> <C5E08FE080ACFD4DAE31E4BDBF944EB1133A0FB4@xmb-aln-x02.cisco.com> <51079D91.3070308@cs.tcd.ie> <201301291435.r0TEYwm1029033@cichlid.raleigh.ibm.com>
In-Reply-To: <201301291435.r0TEYwm1029033@cichlid.raleigh.ibm.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Tue, 29 Jan 2013 08:13:41 -0800 (PST)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 29 Jan 2013 16:13:46 -0000

On 1/29/2013 6:34 AM, Thomas Narten wrote:
> Stephen Farrell <stephen.farrell@cs.tcd.ie> writes:
>>  I'm going to conclude that we're collectively
>> either unwilling or unable to consider 3933 experiments and
>> regard this one as dead, which maybe means 3933 is dead-ish
>> too, I dunno. (And before someone asks: no, I don't conclude
>> that its just a problem with this particular experiment, and
>> yes, I might be wrong there:-)
>
> I object to this (and have come close to saying it a few times
> before).
>
> One of the things that further undermines potential support for
> something (and further raises questions about intentions) is when
> people raise legitmate and substantive issues with a specific
> proposal, and the responses start moving away from responding to the
> substance to arguments  like "Gee, can't we even do experiments anymore",
> etc., etc.


+1

This just-terminated proposal was marked by a rather obscure and 
strikingly weak value proposition, and no apparent concern for costs of 
implementation and use.

d/

-- 
  Dave Crocker
  Brandenburg InternetWorking
  bbiw.net

From sm@resistor.net  Tue Jan 29 09:55:22 2013
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D07F321F886E for <ietf@ietfa.amsl.com>; Tue, 29 Jan 2013 09:55:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 iLvFv1hLZQFk for <ietf@ietfa.amsl.com>; Tue, 29 Jan 2013 09:55:21 -0800 (PST)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 9F17321F8868 for <ietf@ietf.org>; Tue, 29 Jan 2013 09:55:21 -0800 (PST)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r0THruri002907; Tue, 29 Jan 2013 09:53:59 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1359482041; bh=qySmniPR2kDkg4W2Ked6XAyOIdGm9gHrZc1sJr7WyfA=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=sWZn2g/8zkYlQh7Rt4g+NSwoSUeY53cBKzxuR9dbCOpjNqNcvsv7tFPrGjMyPhFIQ cquSgFDlYpb8AFPw4IJgqgujUviOmQR64OIc+GcvwNFFHkbFuANz/nrLAjymTaELW2 Fr99BLrJqg1hL5TtkZJRnfo62hglVxGb5bqdwWjQ=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1359482041; i=@resistor.net; bh=qySmniPR2kDkg4W2Ked6XAyOIdGm9gHrZc1sJr7WyfA=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=20TCtlI1AEPbh5VMANajcEr/wlVUsnvWxUaGcAGNcckTVEV17Qm9T4c89wFr75Lgp H0aqhdcAQRA8f8lUQFN5NFnlODFOBRtLyFO9DD39sS57OpD131Wjk4Vg4wme5szQAI bAhMikxSv4of8Zhk7tFrZ7QQBYgRCe7lxyRn94wg=
Message-Id: <6.2.5.6.2.20130129080837.06b33398@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Tue, 29 Jan 2013 09:49:20 -0800
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
From: SM <sm@resistor.net>
Subject: 3933 experiments (was: Last Call: <draft-farrell-ft-03.txt> (A Fast-Track way to RFC with Running Code) to Experimental RFC)
In-Reply-To: <51079D91.3070308@cs.tcd.ie>
References: <20130111151453.22161.50884.idtracker@ietfa.amsl.com> <C5E08FE080ACFD4DAE31E4BDBF944EB1133A0FB4@xmb-aln-x02.cisco.com> <51079D91.3070308@cs.tcd.ie>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 29 Jan 2013 17:55:23 -0000

Hi Stephen,
At 01:59 29-01-2013, Stephen Farrell wrote:
>Responses to Cullen below, but this is getting to the point
>where unless someone else who likes the idea wants to join
>the discussion, I'm going to conclude that we're collectively
>either unwilling or unable to consider 3933 experiments and
>regard this one as dead, which maybe means 3933 is dead-ish
>too, I dunno. (And before someone asks: no, I don't conclude
>that its just a problem with this particular experiment, and
>yes, I might be wrong there:-)

In 2004 it was written that the IETF has designed process changes 
over the last ten years in one of two ways: announcement by the IESG, 
sometimes based on informal agreements with limited community 
involvement and awareness, and formal use of the same mechanism used 
for protocol specification.

My first reaction was that IETF participants are unwilling or unable 
to consider 3933 experiments.  My second reaction was: what if 
draft-farrell-ft was an IESG statement?  Would the same outcome be 
reached?  The comments posted to this mailing list were 
addressed.  The concerns were left open.

Regards,
-sm 


From stephen.farrell@cs.tcd.ie  Tue Jan 29 10:32:35 2013
Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9ED4D21F8837 for <ietf@ietfa.amsl.com>; Tue, 29 Jan 2013 10:32:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.556
X-Spam-Level: 
X-Spam-Status: No, score=-102.556 tagged_above=-999 required=5 tests=[AWL=0.043, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 0YDDkL5njpt8 for <ietf@ietfa.amsl.com>; Tue, 29 Jan 2013 10:32:34 -0800 (PST)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) by ietfa.amsl.com (Postfix) with ESMTP id 924DA21F8528 for <ietf@ietf.org>; Tue, 29 Jan 2013 10:32:34 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id C3DABBE68; Tue, 29 Jan 2013 18:32:12 +0000 (GMT)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Rr5GKw8IAu3t; Tue, 29 Jan 2013 18:32:12 +0000 (GMT)
Received: from [IPv6:2001:770:10:203:75b2:48e:2a5f:bc82] (unknown [IPv6:2001:770:10:203:75b2:48e:2a5f:bc82]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id EDF92BE3B; Tue, 29 Jan 2013 18:32:11 +0000 (GMT)
Message-ID: <510815AD.4090304@cs.tcd.ie>
Date: Tue, 29 Jan 2013 18:32:13 +0000
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130106 Thunderbird/17.0.2
MIME-Version: 1.0
To: SM <sm@resistor.net>
Subject: Re: 3933 experiments
References: <20130111151453.22161.50884.idtracker@ietfa.amsl.com> <C5E08FE080ACFD4DAE31E4BDBF944EB1133A0FB4@xmb-aln-x02.cisco.com> <51079D91.3070308@cs.tcd.ie> <6.2.5.6.2.20130129080837.06b33398@resistor.net>
In-Reply-To: <6.2.5.6.2.20130129080837.06b33398@resistor.net>
X-Enigmail-Version: 1.5
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 29 Jan 2013 18:32:35 -0000

Hiya,

On 01/29/2013 05:49 PM, SM wrote:
> Hi Stephen,
> At 01:59 29-01-2013, Stephen Farrell wrote:
>> Responses to Cullen below, but this is getting to the point
>> where unless someone else who likes the idea wants to join
>> the discussion, I'm going to conclude that we're collectively
>> either unwilling or unable to consider 3933 experiments and
>> regard this one as dead, which maybe means 3933 is dead-ish
>> too, I dunno. (And before someone asks: no, I don't conclude
>> that its just a problem with this particular experiment, and
>> yes, I might be wrong there:-)
> 
> In 2004 it was written that the IETF has designed process changes over
> the last ten years in one of two ways: announcement by the IESG,
> sometimes based on informal agreements with limited community
> involvement and awareness, and formal use of the same mechanism used for
> protocol specification.
> 
> My first reaction was that IETF participants are unwilling or unable to
> consider 3933 experiments.  My second reaction was: what if
> draft-farrell-ft was an IESG statement?  Would the same outcome be
> reached?  The comments posted to this mailing list were addressed.  The
> concerns were left open.

I don't think that draft would ever have been suitable for
an IESG statement (maybe some bits might, but not the whole
thing) so speculating on that is probably not useful.

I also don't think it was by any means a perfect proposal,
but I do think it was good enough to try out or would have
been with the text changes discussed during LC.

It was proposed as an experiment, but I think was interpreted
as a proposed process change, at least as I read a lot (but
by no means all) of the comments. And I think it was that
kind of concern that was left open.

I'm sure that misinterpretation was partly my fault and that
some or all of the folks commenting disagree with me that their
comments were based on a misinterpretation of what was proposed.
I was also surprised by the extent to which comments focused
on near worst possible outcomes.

But in any case, that's life - I don't think the draft had
anything like rough consensus however you look at it, so
Adrian's call was correct and on we go to the next thing.
I just hope the next thing isn't more process discussion
involving me:-)

S.

> 
> Regards,
> -sm
> 
> 

From dhc@dcrocker.net  Tue Jan 29 11:11:19 2013
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6FDD421F8820 for <ietf@ietfa.amsl.com>; Tue, 29 Jan 2013 11:11:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[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 m+lZQWbvAKkm for <ietf@ietfa.amsl.com>; Tue, 29 Jan 2013 11:11:17 -0800 (PST)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id C768121F880B for <ietf@ietf.org>; Tue, 29 Jan 2013 11:11:17 -0800 (PST)
Received: from [192.168.1.66] (76-218-9-215.lightspeed.sntcca.sbcglobal.net [76.218.9.215]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id r0TJB883026319 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 29 Jan 2013 11:11:09 -0800
Message-ID: <51081EC9.7050309@dcrocker.net>
Date: Tue, 29 Jan 2013 11:11:05 -0800
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130107 Thunderbird/17.0.2
MIME-Version: 1.0
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Subject: Re: 3933 experiments
References: <20130111151453.22161.50884.idtracker@ietfa.amsl.com> <C5E08FE080ACFD4DAE31E4BDBF944EB1133A0FB4@xmb-aln-x02.cisco.com> <51079D91.3070308@cs.tcd.ie> <6.2.5.6.2.20130129080837.06b33398@resistor.net> <510815AD.4090304@cs.tcd.ie>
In-Reply-To: <510815AD.4090304@cs.tcd.ie>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Tue, 29 Jan 2013 11:11:09 -0800 (PST)
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 29 Jan 2013 19:11:19 -0000

On 1/29/2013 10:32 AM, Stephen Farrell wrote:
> It was proposed as an experiment, but I think was interpreted
> as a proposed process change,


wow.

If you don't think it was a process change, exactly what do you think 
would have been experimented on?

The label "experiment" is a qualifier for the substantive reference, not 
a replacement.  In this case, the substance was with IETF process.

You sought an experiment /with/ the process.

The statements of intended benefit were:

    Abstract:

    "have the IETF process
    explicitly consider running code, consistent with the IETF's overall
    philosophy of running code..."

and

    Introduction:

    "speed up the
    progression of certain working group documents in the latter stages
    of the process."

which is then countered and added to, by:

    "the savings in time for the end-to-end delivery
    of a proposed standard or experimental RFC may be modest, however,
    the modifications to normal IETF process will also serve as an
    indication of the importance that the IETF places in running code."

The Abstract's justification text doesn't actually describe a 
"motivation" as it claims, but rather simply describes a behavioral 
change.  It says what will be done, not why it is worth doing.

That the Introduction discounts its own, first-stated purpose, by 
finally casting the Abstract's reference in terms of "importance" adds 
to some confusion about the nature and purpose of the experiment.

In other words, you essentially characterized the experiment as:

     "Let's do something that will have little direct benefit but will 
symbolize the importance of something the IETF has already valued for.. 
ever."

This didn't make for a very compelling foundation.

And thereby makes this exercise particularly ill-suited for 
generalizations about the IETF's ability to conduct experiments.


d/
-- 
  Dave Crocker
  Brandenburg InternetWorking
  bbiw.net

From spencer@wonderhamster.org  Tue Jan 29 13:35:00 2013
Return-Path: <spencer@wonderhamster.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3789621F8816 for <ietf@ietfa.amsl.com>; Tue, 29 Jan 2013 13:35:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.699
X-Spam-Level: 
X-Spam-Status: No, score=-102.699 tagged_above=-999 required=5 tests=[AWL=-0.100, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 N62AuFFDIl7R for <ietf@ietfa.amsl.com>; Tue, 29 Jan 2013 13:34:59 -0800 (PST)
Received: from mout.perfora.net (mout.perfora.net [74.208.4.195]) by ietfa.amsl.com (Postfix) with ESMTP id 8BD4221F855A for <ietf@ietf.org>; Tue, 29 Jan 2013 13:34:59 -0800 (PST)
Received: from [192.168.1.79] (99-108-174-213.lightspeed.rcsntx.sbcglobal.net [99.108.174.213]) by mrelay.perfora.net (node=mrus2) with ESMTP (Nemesis) id 0MIuiv-1TyO5E31Cr-002MhO; Tue, 29 Jan 2013 16:34:58 -0500
Message-ID: <51084076.3090907@wonderhamster.org>
Date: Tue, 29 Jan 2013 15:34:46 -0600
From: Spencer Dawkins <spencer@wonderhamster.org>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:17.0) Gecko/20130107 Thunderbird/17.0.2
MIME-Version: 1.0
To: John C Klensin <john-ietf@jck.com>
Subject: Re: FW: Last Call: <draft-farrell-ft-03.txt> (A Fast-Track way to RFC	with Running Code) to Experimental RFC
References: <017001cdf017$c394df00$4abe9d00$@olddog.co.uk> <50FEC0B8.8060905@isi.edu> <201301222131.r0MLVK8C015116@cichlid.raleigh.ibm.com> <84D9F6D1AE454253626C8859@JcK-HP8200.jck.com>
In-Reply-To: <84D9F6D1AE454253626C8859@JcK-HP8200.jck.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Provags-ID: V02:K0:l4v+D2SVyImOB08vtAPEptOBjIOLmXM0xm++PV1wMPU JzxXEz0im+DwIhJzGVmg/l4qmT9GB1nnO+oEAr8Ii5X2hOHLLT hURP0CMLYiZCdunUyzR0CPvvBTVN2uL3YT4b/d8FHqHtr/wXL1 weCRcmay4QhfUOPj52JcFjbhb61keVUZGJkaY2atBEV311X1SU y/WwlYQx3ql0eBz3wrL/Ao2ej02ZyjXn5Hw+nCSqFx5k9AYMeH 6gaMpfXAjG4fqTGWaPaZLg1qnAwqpLBIOl+um3thMh6Qq6i2ut ZSVjf+dfc02rH/lHL7KqaAInTmK56Lepp49c7PaGgWGkwO5Q76 ph3bCbyYyWbHBxOCNikKwyPPVJTmheEL3bUnfjGm/
Cc: Thomas Narten <narten@us.ibm.com>, adrian@olddog.co.uk, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 29 Jan 2013 21:35:00 -0000

Just as a follow-up here ...

I was John's co-author on RFC 3933 (http://tools.ietf.org/html/rfc3933). 
When we were working on the draft, the problem I thought we were 
solving, was that the IESG needs to update the IETF's BCP processes from 
time to time, but (1) it was like 32 simultaneous root canals to 
actually get community consensus to modify the IETF's process BCPs 
including untried changes that might be improvements, so (2) the IESG 
was using informal IESG statements developed with much less community 
involvement than was expected for process BCP changes, in order to get 
anything done at all.

I (and, I think, John as well) saw RFC 3933 process experiments as a 
middle path between lightweight IESG decisions and full process BCP 
revisions. That's what I thought Section 2 of RFC 3933 was trying to say.

I had assumed that if the IESG clearly had discretion to do something 
under the current process BCPs, and thought it was the right thing to 
do, they would just do it, rather than set up a process experiment.

For what that's worth.

Spencer

On 1/24/2013 12:34 PM, John C Klensin wrote:
> --On Tuesday, January 22, 2013 16:31 -0500 Thomas Narten
> <narten@us.ibm.com> wrote:

>> This document seems to have a bit of missing the forest for the
>> trees. In the overall scheme of things, I don't believe the
>> draft will materially help, and is at best a distraction from
>> dealing with meaningful problems.
>>
>> The crux of the issue is that any attempt at "fast tracking" is
>> fundamentally about short-circuiting some aspect of our review
>> processes. We should only do that very carefully. In almost
>> all cases, individual judgement is needed as to when it is
>> appropriate to do that. ADs/WG chairs already have some
>> flexibility here. e.g., a WG can skip WG LC if they think its
>> ...
>
> Hi.
> First of all, I am completely in agreement with Thomas and his
> analysis.  Anything  that can reasonably and appropriately be
> done by this sort of effort can be done by discretion without
> adoption of a formal procedure and adoption of a formal
> procedure creates additional and unnecessary risks.
>
> As co-author of the process experiment model, I also object to
> its use when it is not demonstrably necessary, for example to
> give extra status and force IETF-wide use where the actions
> suggested can be carried out as a matter of normal discretion
> (see Section 5 of the document).

From barryleiba.mailing.lists@gmail.com  Tue Jan 29 18:32:21 2013
Return-Path: <barryleiba.mailing.lists@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7596521F8442 for <ietf@ietfa.amsl.com>; Tue, 29 Jan 2013 18:32:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.03
X-Spam-Level: 
X-Spam-Status: No, score=-103.03 tagged_above=-999 required=5 tests=[AWL=-0.053, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
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 3BdeESr8TAdf for <ietf@ietfa.amsl.com>; Tue, 29 Jan 2013 18:32:21 -0800 (PST)
Received: from mail-vb0-f51.google.com (mail-vb0-f51.google.com [209.85.212.51]) by ietfa.amsl.com (Postfix) with ESMTP id BBBD821F8440 for <ietf@ietf.org>; Tue, 29 Jan 2013 18:32:20 -0800 (PST)
Received: by mail-vb0-f51.google.com with SMTP id fq11so722237vbb.24 for <ietf@ietf.org>; Tue, 29 Jan 2013 18:32:20 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=E8yFLJBfKxDzLweE336CetnWISfFZTKb8AQzvvQzll4=; b=MF3nrjwteX9nfOiXaTVKtRCI9PVC3Aehdn+viNq1vX6S4JpDwFtKR/Zr2ufDm0u3Jj 2LLNnyI6w2GHcJD6tYXggeWRzzuNbM6R1vVVt2QFd6B+gvStpP1Ja15RBJNE1hDtRxMZ onrkND+tkONw3PthfANUq9tur5pGzIh+XwNRGFFXCQ4zeQIZzrZosVjYSzWGsfpmGoVp rNgG4nYzEjHURATryvZx/sgcqvqtB2mY57PW2/yLirmn6OPEQDOFZfq0jrAn9PdoWslr SFu2OlJux4vivL/oYqpTgc0ZMgdlH1Slrt6Dl1eaeDjpgTLJa8AWnGY1akgb8YoRBbev Q9pg==
MIME-Version: 1.0
X-Received: by 10.220.151.5 with SMTP id a5mr3544050vcw.22.1359513139824; Tue, 29 Jan 2013 18:32:19 -0800 (PST)
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.59.3.41 with HTTP; Tue, 29 Jan 2013 18:32:19 -0800 (PST)
In-Reply-To: <6.2.5.6.2.20130129080837.06b33398@resistor.net>
References: <20130111151453.22161.50884.idtracker@ietfa.amsl.com> <C5E08FE080ACFD4DAE31E4BDBF944EB1133A0FB4@xmb-aln-x02.cisco.com> <51079D91.3070308@cs.tcd.ie> <6.2.5.6.2.20130129080837.06b33398@resistor.net>
Date: Tue, 29 Jan 2013 21:32:19 -0500
X-Google-Sender-Auth: 7hhYKC_05_4oAEiM8rfefTjCpV0
Message-ID: <CAC4RtVCe9_B-j5QBD1y+mGT7W=NnqtLrxNRam4hZ7TmGspy=Dg@mail.gmail.com>
Subject: Re: 3933 experiments (was: Last Call: <draft-farrell-ft-03.txt> (A Fast-Track way to RFC with Running Code) to Experimental RFC)
From: Barry Leiba <barryleiba@computer.org>
To: SM <sm@resistor.net>
Content-Type: text/plain; charset=ISO-8859-1
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 30 Jan 2013 02:32:21 -0000

> IETF participants are unwilling or unable to
> consider 3933 experiments.  My second reaction was: what if draft-farrell-ft
> was an IESG statement?  Would the same outcome be reached?

When Stephen proposed his draft to the IESG, I counter-proposed an
IESG Statement that would essentially say that because implementation
experience is important, the IESG will consider it in its evaluation.
More text around that, but that's the short version.

The IESG did not consider that approach at the time, preferring to
proceed with the 3933-experiment proposal.

Barry (App AD)

From adrian@olddog.co.uk  Wed Jan 30 01:15:53 2013
Return-Path: <adrian@olddog.co.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 64D4921F86EF for <ietf@ietfa.amsl.com>; Wed, 30 Jan 2013 01:15:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599]
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 Z9ENNxAbu3gy for <ietf@ietfa.amsl.com>; Wed, 30 Jan 2013 01:15:52 -0800 (PST)
Received: from asmtp5.iomartmail.com (asmtp5.iomartmail.com [62.128.201.176]) by ietfa.amsl.com (Postfix) with ESMTP id 3493B21F86B6 for <ietf@ietf.org>; Wed, 30 Jan 2013 01:15:51 -0800 (PST)
Received: from asmtp5.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp5.iomartmail.com (8.13.8/8.13.8) with ESMTP id r0U9Fmqc005105;  Wed, 30 Jan 2013 09:15:49 GMT
Received: from 950129200 (83-215-186-5.stjo.dyn.salzburg-online.at [83.215.186.5]) (authenticated bits=0) by asmtp5.iomartmail.com (8.13.8/8.13.8) with ESMTP id r0U9FMpO004805 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Wed, 30 Jan 2013 09:15:26 GMT
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "'Spencer Dawkins'" <spencer@wonderhamster.org>, "'John C Klensin'" <john-ietf@jck.com>
Subject: When is a 3933 experiment necessary? [Was: Last Call: <draft-farrell-ft-03.txt> (A Fast-Track way to RFC	with Running Code) to Experimental RFC]
Date: Wed, 30 Jan 2013 09:15:19 -0000
Message-ID: <008501cdfeca$59a77cd0$0cf67670$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: Ac3+yfGYHdJwHjfgRaimiHk9yk0ezg==
Content-Language: en-gb
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: adrian@olddog.co.uk
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 30 Jan 2013 09:15:53 -0000

Well, is that a meta-judgment call?

I took the view that the full process expressed in draft-farrell-ft could not be
done by the IESG at their discretion. That is, that some of the steps proposed
constituted a significant variation from documented processes or
well-established behavior. Thus, it was my opinion that if such changes were to
be made they would either need to be documented direct in a BCP or run as a 3933
experiment. It was also my opinion that consensus for a BCP would be improbable
(looks like discussion on this list has upheld that view), and so *if* this was
to go ahead it would need to be as a 3933 experiment.

Turns out, however, that the community is not willing to try this experiment as
currently documented. That's OK.

I do not take quite the same negative view as Stephen, but I do agree with
Spencer that getting consensus for a process change always looks like a
formidable task. Small changes never address enough of the problem or the right
piece of the problem. Large changes are too much in one go. :-) So, it seems to
be increasingly hard to make changes to our process.  

While IESG statements remain an option, I would not like to see them regularly
used for things that are definitively a change to consensus-based process and
especially for things that change the way the community is supposed to behave.
On the other hand, IESG statements are fine for declaring how the IESG will
behave, for advising on action within existing parameters, and for emergency
action.

So, my conclusion: it would be good to have more process experiments if people
feel the process needs to change. However, it would appear that such experiments
need:
- Thorough debate on an appropriate mailing list first
   Do we need a "process experiments" mailing list?
- Very clear expression of the purpose of the experiment
   and how it will be evaluated
- Very tight scoping to a portion of the IETF or of the IETF's
   work so that the risk of the experiment simply changing
   the IETF's process by default is removed

Cheers,
Adrian

> -----Original Message-----
> From: Spencer Dawkins [mailto:spencer@wonderhamster.org]
> Sent: 29 January 2013 21:35
> To: John C Klensin
> Cc: Thomas Narten; adrian@olddog.co.uk; ietf@ietf.org
> Subject: Re: FW: Last Call: <draft-farrell-ft-03.txt> (A Fast-Track way to RFC
with
> Running Code) to Experimental RFC
> 
> Just as a follow-up here ...
> 
> I was John's co-author on RFC 3933 (http://tools.ietf.org/html/rfc3933).
> When we were working on the draft, the problem I thought we were
> solving, was that the IESG needs to update the IETF's BCP processes from
> time to time, but (1) it was like 32 simultaneous root canals to
> actually get community consensus to modify the IETF's process BCPs
> including untried changes that might be improvements, so (2) the IESG
> was using informal IESG statements developed with much less community
> involvement than was expected for process BCP changes, in order to get
> anything done at all.
> 
> I (and, I think, John as well) saw RFC 3933 process experiments as a
> middle path between lightweight IESG decisions and full process BCP
> revisions. That's what I thought Section 2 of RFC 3933 was trying to say.
> 
> I had assumed that if the IESG clearly had discretion to do something
> under the current process BCPs, and thought it was the right thing to
> do, they would just do it, rather than set up a process experiment.
> 
> For what that's worth.
> 
> Spencer
> 
> On 1/24/2013 12:34 PM, John C Klensin wrote:
> > --On Tuesday, January 22, 2013 16:31 -0500 Thomas Narten
> > <narten@us.ibm.com> wrote:
> 
> >> This document seems to have a bit of missing the forest for the
> >> trees. In the overall scheme of things, I don't believe the
> >> draft will materially help, and is at best a distraction from
> >> dealing with meaningful problems.
> >>
> >> The crux of the issue is that any attempt at "fast tracking" is
> >> fundamentally about short-circuiting some aspect of our review
> >> processes. We should only do that very carefully. In almost
> >> all cases, individual judgement is needed as to when it is
> >> appropriate to do that. ADs/WG chairs already have some
> >> flexibility here. e.g., a WG can skip WG LC if they think its
> >> ...
> >
> > Hi.
> > First of all, I am completely in agreement with Thomas and his
> > analysis.  Anything  that can reasonably and appropriately be
> > done by this sort of effort can be done by discretion without
> > adoption of a formal procedure and adoption of a formal
> > procedure creates additional and unnecessary risks.
> >
> > As co-author of the process experiment model, I also object to
> > its use when it is not demonstrably necessary, for example to
> > give extra status and force IETF-wide use where the actions
> > suggested can be carried out as a matter of normal discretion
> > (see Section 5 of the document).


From dromasca@avaya.com  Wed Jan 30 04:15:09 2013
Return-Path: <dromasca@avaya.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B759021F88B0 for <ietf@ietfa.amsl.com>; Wed, 30 Jan 2013 04:15:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.939
X-Spam-Level: 
X-Spam-Status: No, score=-102.939 tagged_above=-999 required=5 tests=[AWL=-0.340, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 FSXtO6dD7aUP for <ietf@ietfa.amsl.com>; Wed, 30 Jan 2013 04:15:08 -0800 (PST)
Received: from p-us1-iereast-outbound.us1.avaya.com (p-us1-iereast-outbound.us1.avaya.com [135.11.29.13]) by ietfa.amsl.com (Postfix) with ESMTP id 537B721F886B for <ietf@ietf.org>; Wed, 30 Jan 2013 04:15:08 -0800 (PST)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgEFAP0QA1GHCzI1/2dsb2JhbABFgmu7ZxZzgh4BAQEBAxIoLQcLDAQCAQgNBAQBAQEKFAUEBzIUCQgBAQQBDQUIDA6HbQELoVicdI0Dg1thA5JahE+EcYo7gneCJA
X-IronPort-AV: E=Sophos;i="4.84,541,1355115600"; d="scan'208";a="46556064"
Received: from unknown (HELO p-us1-erheast.us1.avaya.com) ([135.11.50.53]) by p-us1-iereast-outbound.us1.avaya.com with ESMTP; 30 Jan 2013 07:14:25 -0500
Received: from unknown (HELO AZ-FFEXHC03.global.avaya.com) ([135.64.58.13]) by p-us1-erheast-out.us1.avaya.com with ESMTP; 30 Jan 2013 07:14:54 -0500
Received: from AZ-FFEXMB04.global.avaya.com ([fe80::6db7:b0af:8480:c126]) by AZ-FFEXHC03.global.avaya.com ([135.64.58.13]) with mapi id 14.02.0328.009; Wed, 30 Jan 2013 07:15:24 -0500
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: "adrian@olddog.co.uk" <adrian@olddog.co.uk>, 'Spencer Dawkins' <spencer@wonderhamster.org>, 'John C Klensin' <john-ietf@jck.com>
Subject: RE: When is a 3933 experiment necessary? [Was: Last Call: <draft-farrell-ft-03.txt> (A Fast-Track way to RFC	with Running	Code) to Experimental RFC]
Thread-Topic: When is a 3933 experiment necessary? [Was: Last Call: <draft-farrell-ft-03.txt> (A Fast-Track way to RFC	with Running	Code) to Experimental RFC]
Thread-Index: Ac3+yfGYHdJwHjfgRaimiHk9yk0ezgAGCADA
Date: Wed, 30 Jan 2013 12:15:23 +0000
Message-ID: <9904FB1B0159DA42B0B887B7FA8119CA07A860@AZ-FFEXMB04.global.avaya.com>
References: <008501cdfeca$59a77cd0$0cf67670$@olddog.co.uk>
In-Reply-To: <008501cdfeca$59a77cd0$0cf67670$@olddog.co.uk>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [135.64.58.45]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 30 Jan 2013 12:15:09 -0000

I believe that Adrian did right in this case. This was IMO one of the situa=
tions which in Spencer's language was 'middle path between lightweight IESG=
 decisions and full process BCP revisions' and a 3933 experiment could have=
 proved it right or wrong, useful or not. The community could not reach con=
sensus to run the experiment and this is one possible outcomes when such qu=
estions are asked.=20

Same as Adrian I do not believe that this lack of consensus invalidates pro=
cess experiments. What I feel is that the key condition in the list drawn b=
y Adrian is the second:=20

> > - Very clear expression of the purpose of the experiment and how it wil=
l be evaluated

Almost in all cases when this condition was not met I noticed the discussio=
ns ran wild and became unfocussed, discussing not about the proposal to run=
 the experiment, but about that subject of the experiment and its presumed =
results before it had even been started.=20

Dan


> -----Original Message-----
> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of
> Adrian Farrel
> Sent: Wednesday, January 30, 2013 11:15 AM
> To: 'Spencer Dawkins'; 'John C Klensin'
> Cc: ietf@ietf.org
> Subject: When is a 3933 experiment necessary? [Was: Last Call: <draft-
> farrell-ft-03.txt> (A Fast-Track way to RFC with Running Code) to
> Experimental RFC]
>=20
> Well, is that a meta-judgment call?
>=20
> I took the view that the full process expressed in draft-farrell-ft
> could not be done by the IESG at their discretion. That is, that some of
> the steps proposed constituted a significant variation from documented
> processes or well-established behavior. Thus, it was my opinion that if
> such changes were to be made they would either need to be documented
> direct in a BCP or run as a 3933 experiment. It was also my opinion that
> consensus for a BCP would be improbable (looks like discussion on this
> list has upheld that view), and so *if* this was to go ahead it would
> need to be as a 3933 experiment.
>=20
> Turns out, however, that the community is not willing to try this
> experiment as currently documented. That's OK.
>=20
> I do not take quite the same negative view as Stephen, but I do agree
> with Spencer that getting consensus for a process change always looks
> like a formidable task. Small changes never address enough of the
> problem or the right piece of the problem. Large changes are too much in
> one go. :-) So, it seems to be increasingly hard to make changes to our
> process.
>=20
> While IESG statements remain an option, I would not like to see them
> regularly used for things that are definitively a change to consensus-
> based process and especially for things that change the way the
> community is supposed to behave.
> On the other hand, IESG statements are fine for declaring how the IESG
> will behave, for advising on action within existing parameters, and for
> emergency action.
>=20
> So, my conclusion: it would be good to have more process experiments if
> people feel the process needs to change. However, it would appear that
> such experiments
> need:
> - Thorough debate on an appropriate mailing list first
>    Do we need a "process experiments" mailing list?
> - Very clear expression of the purpose of the experiment
>    and how it will be evaluated
> - Very tight scoping to a portion of the IETF or of the IETF's
>    work so that the risk of the experiment simply changing
>    the IETF's process by default is removed
>=20
> Cheers,
> Adrian
>=20
> > -----Original Message-----
> > From: Spencer Dawkins [mailto:spencer@wonderhamster.org]
> > Sent: 29 January 2013 21:35
> > To: John C Klensin
> > Cc: Thomas Narten; adrian@olddog.co.uk; ietf@ietf.org
> > Subject: Re: FW: Last Call: <draft-farrell-ft-03.txt> (A Fast-Track
> > way to RFC
> with
> > Running Code) to Experimental RFC
> >
> > Just as a follow-up here ...
> >
> > I was John's co-author on RFC 3933
> (http://tools.ietf.org/html/rfc3933).
> > When we were working on the draft, the problem I thought we were
> > solving, was that the IESG needs to update the IETF's BCP processes
> > from time to time, but (1) it was like 32 simultaneous root canals to
> > actually get community consensus to modify the IETF's process BCPs
> > including untried changes that might be improvements, so (2) the IESG
> > was using informal IESG statements developed with much less community
> > involvement than was expected for process BCP changes, in order to get
> > anything done at all.
> >
> > I (and, I think, John as well) saw RFC 3933 process experiments as a
> > middle path between lightweight IESG decisions and full process BCP
> > revisions. That's what I thought Section 2 of RFC 3933 was trying to
> say.
> >
> > I had assumed that if the IESG clearly had discretion to do something
> > under the current process BCPs, and thought it was the right thing to
> > do, they would just do it, rather than set up a process experiment.
> >
> > For what that's worth.
> >
> > Spencer
> >
> > On 1/24/2013 12:34 PM, John C Klensin wrote:
> > > --On Tuesday, January 22, 2013 16:31 -0500 Thomas Narten
> > > <narten@us.ibm.com> wrote:
> >
> > >> This document seems to have a bit of missing the forest for the
> > >> trees. In the overall scheme of things, I don't believe the draft
> > >> will materially help, and is at best a distraction from dealing
> > >> with meaningful problems.
> > >>
> > >> The crux of the issue is that any attempt at "fast tracking" is
> > >> fundamentally about short-circuiting some aspect of our review
> > >> processes. We should only do that very carefully. In almost all
> > >> cases, individual judgement is needed as to when it is appropriate
> > >> to do that. ADs/WG chairs already have some flexibility here. e.g.,
> > >> a WG can skip WG LC if they think its ...
> > >
> > > Hi.
> > > First of all, I am completely in agreement with Thomas and his
> > > analysis.  Anything  that can reasonably and appropriately be done
> > > by this sort of effort can be done by discretion without adoption of
> > > a formal procedure and adoption of a formal procedure creates
> > > additional and unnecessary risks.
> > >
> > > As co-author of the process experiment model, I also object to its
> > > use when it is not demonstrably necessary, for example to give extra
> > > status and force IETF-wide use where the actions suggested can be
> > > carried out as a matter of normal discretion (see Section 5 of the
> > > document).


From sm@resistor.net  Wed Jan 30 10:19:21 2013
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B0FBB21F87D6 for <ietf@ietfa.amsl.com>; Wed, 30 Jan 2013 10:19:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 5fNY-qxdaE+V for <ietf@ietfa.amsl.com>; Wed, 30 Jan 2013 10:19:20 -0800 (PST)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 4AE1A21F87D5 for <ietf@ietf.org>; Wed, 30 Jan 2013 10:19:20 -0800 (PST)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r0UIJDAj017908; Wed, 30 Jan 2013 10:19:17 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1359569958; bh=z56nsQ/23HI2qY5mboXpUvC+VanIrDiWYRzI+rTFLL0=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=G62x5NAWVJSQ6PYxxs0BnUwuRPodPM4h7BrreNqylfozvUXqjAVjxY5rW2hwAUpZO IoJv7IfTZpHnzOYlDexVW3+zQsnSxVnApPZLsTg+ccUfcYNCRAKkNVdaLMk6Wf7y2C iKTQ9pq0yPEjExgifp6XuskmZwDUIuFwSpfon+nc=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1359569958; i=@resistor.net; bh=z56nsQ/23HI2qY5mboXpUvC+VanIrDiWYRzI+rTFLL0=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=WLWBDRwqIvKvp+7XUN+StDuk/uPnx994Uc6uCdTd3AjeSflSkuBDYVhWNeWdZuU5o jqPJcrbMSwjWOfSqla1CUJITEZHqYdT91ZDw0AZpt8es3vJ95Tkp448dyaDpFNm1kv tZx62kfZmOO1XOP1kNWnp9ulns0P+AYyxWAQXiEM=
Message-Id: <6.2.5.6.2.20130130043642.0a54e220@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Wed, 30 Jan 2013 10:15:50 -0800
To: adrian@olddog.co.uk
From: SM <sm@resistor.net>
Subject: Re: When is a 3933 experiment necessary? [Was: Last Call: <draft-farrell-ft-03.txt> (A Fast-Track way to RFC	with Running Code) to Experimental RFC]
In-Reply-To: <008501cdfeca$59a77cd0$0cf67670$@olddog.co.uk>
References: <008501cdfeca$59a77cd0$0cf67670$@olddog.co.uk>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 30 Jan 2013 18:19:21 -0000

Hi Adrian,
At 01:15 30-01-2013, Adrian Farrel wrote:
>I do not take quite the same negative view as Stephen, but I do agree with
>Spencer that getting consensus for a process change always looks like a
>formidable task. Small changes never address enough of the problem 
>or the right
>piece of the problem. Large changes are too much in one go. :-) So, 
>it seems to
>be increasingly hard to make changes to our process.

It is an unsurmountable task to change anything relating to 
process.  In a sense the process is built for incremental changes 
instead of drastic changes.

>On the other hand, IESG statements are fine for declaring how the IESG will
>behave, for advising on action within existing parameters, and for emergency
>action.

It is easier to wait for an emergency and take action.

>So, my conclusion: it would be good to have more process experiments if people
>feel the process needs to change. However, it would appear that such 
>experiments
>need:
>- Thorough debate on an appropriate mailing list first
>    Do we need a "process experiments" mailing list?
>- Very clear expression of the purpose of the experiment
>    and how it will be evaluated
>- Very tight scoping to a portion of the IETF or of the IETF's
>    work so that the risk of the experiment simply changing
>    the IETF's process by default is removed

It is good to see "process experiments" coming from IESG members.  I 
read it as meaning that those members don't expect the same old 
tricks to work forever.  "Process experiments" won't get me far 
unless I put in the effort to do the work.  I will probably sound 
cynical; it's unlikely that there will be thorough debate on an 
appropriate mailing list.  I am not against the idea of setting up a 
mailing list though.

Please do not read any of the above as implying that it won't 
work.  I cannot predict the future.  You are better placed than me to 
make the decision as you know more than me.

Regards,
-sm  


From dhc@dcrocker.net  Wed Jan 30 10:36:00 2013
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CEB1421F889C for <ietf@ietfa.amsl.com>; Wed, 30 Jan 2013 10:36:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[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 L6TuHyR7i9Qv for <ietf@ietfa.amsl.com>; Wed, 30 Jan 2013 10:36:00 -0800 (PST)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id D120921F8895 for <ietf@ietf.org>; Wed, 30 Jan 2013 10:35:59 -0800 (PST)
Received: from [192.168.1.66] (76-218-9-215.lightspeed.sntcca.sbcglobal.net [76.218.9.215]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id r0UIZvkw015075 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 30 Jan 2013 10:35:58 -0800
Message-ID: <5109680A.1040400@dcrocker.net>
Date: Wed, 30 Jan 2013 10:35:54 -0800
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130107 Thunderbird/17.0.2
MIME-Version: 1.0
To: adrian@olddog.co.uk
Subject: Re: When is a 3933 experiment necessary? [Was: Last Call: <draft-farrell-ft-03.txt> (A Fast-Track way to RFC	with Running Code) to Experimental RFC]
References: <008501cdfeca$59a77cd0$0cf67670$@olddog.co.uk>
In-Reply-To: <008501cdfeca$59a77cd0$0cf67670$@olddog.co.uk>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Wed, 30 Jan 2013 10:35:58 -0800 (PST)
Cc: 'John C Klensin' <john-ietf@jck.com>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 30 Jan 2013 18:36:00 -0000

On 1/30/2013 1:15 AM, Adrian Farrel wrote:
>     I do agree with
> Spencer that getting consensus for a process change always looks like a
> formidable task. Small changes never address enough of the problem or the right
> piece of the problem. Large changes are too much in one go. :-) So, it seems to
> be increasingly hard to make changes to our process.


I suspect it's not 'increasingly' but rather that it's always been 
extremely difficult...

Let me suggest a different possibility for the challenge in this topic:

      We are a diverse community.  Absent very, very strong consensus 
that a problem is serious enough to warrant a change, the community is 
not likely to line up automatically behind a proposal.  We will always 
have some people who prefer no change and some who offer their 
different, favorite approaches, or and some who offer a zillion tweaks. 
  In the aggregate, that makes for entropy, not consensus.

      What makes this process different from what we see in successful 
working groups?

I think there are two things:

    1. A wg has a committed core of participants who have agreed on a 
common goal.

    2. A wg process is managed.

On the average, proposals for IETF process change benefit from neither 
of these.

Hence I suggest that a proposal needs to recruit a committed core 
/before/ going public, and the discussion needs classic group 
facilitation, in terms of tracking issues, maintaining focus, and 
pursuing consensus.

d/

-- 
  Dave Crocker
  Brandenburg InternetWorking
  bbiw.net

From sm@resistor.net  Wed Jan 30 16:31:37 2013
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1C48E21F87A5; Wed, 30 Jan 2013 16:31:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 3nH6X6oKEM-8; Wed, 30 Jan 2013 16:31:34 -0800 (PST)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id C86D021F87A3; Wed, 30 Jan 2013 16:31:34 -0800 (PST)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r0V0VQqt020961; Wed, 30 Jan 2013 16:31:31 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1359592293; bh=ApSaCuDofTeRhD2RScyLcteYPs+bhvmDTtl4mvKI9xQ=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=Pzkwmh2Y9SBHIQ8N0KqNp39L8CMwaGCcwQwNx6vplLBKEaWiQsGZbGe/+4k6Liosz Ks34xImA66n/544+m1TRtvTnEuQSbykDFPz/2saBLjA/bq16sk0tp215C5c0tzyx2I B0BmSJhH3oSanfdatP5YF4VhPtUuJVbIVBdrSAXU=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1359592293; i=@resistor.net; bh=ApSaCuDofTeRhD2RScyLcteYPs+bhvmDTtl4mvKI9xQ=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=G3yREwgU8qS2H2NssuhI+cf+IpflUVeQ1UvG3Potu7+t+dred18W4N83gEBCB+fUu FqneYrqC4956VaYPUYepQeH0sIPxh8Qd5JVmWGMRM1YxNctvtSx38phTtAqZKvmb09 QzCP+H+xdmN+SVALV+bINobk7HZqN4Z/xtO/ZF9s=
Message-Id: <6.2.5.6.2.20130130143748.09bc0140@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Wed, 30 Jan 2013 16:29:30 -0800
To: iab@iab.org
From: SM <sm@resistor.net>
Subject: Re: Call for Comment: 'Privacy Considerations for Internet Protocols'
In-Reply-To: <669123F2-8F12-4C46-956D-C4A12B5363D4@iab.org>
References: <669123F2-8F12-4C46-956D-C4A12B5363D4@iab.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 31 Jan 2013 00:31:37 -0000

At 14:30 16-01-2013, IAB Chair wrote:
>This is an announcement of an IETF-wide Call for Comment on 'Privacy 
>Considerations for Internet Protocols'.
>
>The document is being considered for publication as an Informational 
>RFC within the IAB stream, and is available for inspection here:
>http://tools.ietf.org/html/draft-iab-privacy-considerations

In Section 1:

   'With regard to data, often it is a concept applied to
    "personal data," information relating to an identified or
    identifiable individual.'

I suggest rewriting the above sentence.

   "Many sets of privacy principles and privacy design frameworks have been
    developed in different forums over the years."

There is also some work in the APEC region (see 
http://publications.apec.org/publication-detail.php?pub_id=390 (payware)).

As a nit, the draft-ietf-geopriv-policy-27 reference should be RFC 6772.

I read some of the previous versions of this draft.  The Abstract 
Section describes the document as providing guidance for developing 
privacy considerations for inclusion in protocol specifications.  I 
found the draft difficult to digest.  I suggest simplifying the draft 
to make the guidance accessible to the target audience.

One of the issues nowadays is what to do about intermediaries.  If I 
am not mistaken RFC 3238 was one of the first documents to tackle 
that question from a privacy perspective.  There have been a few 
proposals to introduce intermediaries as part of the architecture (I 
am using the word is used loosely).  It is easy to argue for 
intermediaries based on use cases.  There was a case recently where 
the users only became aware that they have signed up for using an 
intermediary through the EULA.

The draft introduces the concept of secondary use (Section 
4.2.3).  Strictly speaking, it is a disclosure (Section 4.2.4).

The draft mentions consent in several places.  The authors are likely 
aware that consent was a hot topic for DNT.  It's easier to start 
with something that is easy for the average person to understand and 
build from there.  Section 7.2 could more about consent instead of 
user participation or control.

Regards,
-sm 


From abdussalambaryun@gmail.com  Thu Jan 31 03:48:29 2013
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5B07121F86D8 for <ietf@ietfa.amsl.com>; Thu, 31 Jan 2013 03:48:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.59
X-Spam-Level: 
X-Spam-Status: No, score=-3.59 tagged_above=-999 required=5 tests=[AWL=0.009,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 mV-SaxFB5cUj for <ietf@ietfa.amsl.com>; Thu, 31 Jan 2013 03:48:28 -0800 (PST)
Received: from mail-wi0-f175.google.com (mail-wi0-f175.google.com [209.85.212.175]) by ietfa.amsl.com (Postfix) with ESMTP id B092A21F86D9 for <ietf@ietf.org>; Thu, 31 Jan 2013 03:48:27 -0800 (PST)
Received: by mail-wi0-f175.google.com with SMTP id hq12so4212632wib.14 for <ietf@ietf.org>; Thu, 31 Jan 2013 03:48:26 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to:cc :content-type; bh=NbaQ5xewv1wtUsaF13fgnhkNzY/asIyxho5UI5UsyqM=; b=CCi65NpoJlt97W1BGGMH+8J+UYDPyK2fn7+TCP7D64MIRoDD4rrhhXMH5tWKS7k4TT S8IcCJiExNy7qUbBgl8NyollkR4q8ly6TX9fEe6jfC1nz/DHiCjQN+ZRuVZWkNJr9anq c0ypYG0gV57FFr3/V90yCTQgzA6WQ0T4fNu470m409vNKCp+RHBBi4E9ev2ZEWBT1bTO cVtiSN1ziyJfVMZLa/F88vn+gXk4ooDXqRxOT+Do6QfVx+KzmesaXdHBSECD+/AEuA++ 1y4JkbjoyvuuWH1PWHheuVT2yvDttWVy3jHtKnOzVM6qHuSwvEWmR7sTRJeXilmkHFOJ TKbQ==
MIME-Version: 1.0
X-Received: by 10.180.73.80 with SMTP id j16mr14433942wiv.5.1359632906862; Thu, 31 Jan 2013 03:48:26 -0800 (PST)
Received: by 10.180.14.33 with HTTP; Thu, 31 Jan 2013 03:48:26 -0800 (PST)
Date: Thu, 31 Jan 2013 12:48:26 +0100
Message-ID: <CADnDZ8-5p1qhGxQ1AOFtarumk44igorZ3EPyrAOiWurcy3-XzA@mail.gmail.com>
Subject: Re: When is a 3933 experiment necessary? [Was: Last Call: <draft-farrell-ft-03.txt> (A Fast-Track way to RFC with Running Code) to Experimental RFC]
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: dhc@dcrocker.net
Content-Type: text/plain; charset=ISO-8859-1
Cc: ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 31 Jan 2013 11:48:29 -0000

+1

AB

++++++++++++
On 1/30/2013, Dave Crocker wrote:

I suspect it's not 'increasingly' but rather that it's always been
extremely difficult...
Let me suggest a different possibility for the challenge in this topic:

We are a diverse community. Absent very, very strong consensus that a
problem is serious enough to warrant a change, the community is not
likely to line up automatically behind a proposal. We will always have
some people who prefer no change and some who offer their different,
favorite approaches, or and some who offer a zillion tweaks. In the
aggregate, that makes for entropy, not consensus.

What makes this process different from what we see in successful
working groups?
I think there are two things:

1. A wg has a committed core of participants who have agreed on a common goal.
   2. A wg process is managed.

On the average, proposals for IETF process change benefit from neither
of these.

Hence I suggest that a proposal needs to recruit a committed core
/before/ going public, and the discussion needs classic group
facilitation, in terms of tracking issues, maintaining focus, and
pursuing consensus.
d/

--
 Dave Crocker
 Brandenburg InternetWorking
 bbiw.net

From daedulus@btconnect.com  Thu Jan 31 04:14:37 2013
Return-Path: <daedulus@btconnect.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A9A8321F86C9 for <ietf@ietfa.amsl.com>; Thu, 31 Jan 2013 04:14:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.349
X-Spam-Level: 
X-Spam-Status: No, score=-5.349 tagged_above=-999 required=5 tests=[AWL=0.250,  BAYES_00=-2.599, GB_I_INVITATION=-2, RCVD_IN_DNSWL_LOW=-1]
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 BMMCvp11yX34 for <ietf@ietfa.amsl.com>; Thu, 31 Jan 2013 04:14:37 -0800 (PST)
Received: from ch1outboundpool.messaging.microsoft.com (ch1ehsobe002.messaging.microsoft.com [216.32.181.182]) by ietfa.amsl.com (Postfix) with ESMTP id E5FE721F86C5 for <ietf@ietf.org>; Thu, 31 Jan 2013 04:14:36 -0800 (PST)
Received: from mail249-ch1-R.bigfish.com (10.43.68.248) by CH1EHSOBE006.bigfish.com (10.43.70.56) with Microsoft SMTP Server id 14.1.225.23; Thu, 31 Jan 2013 12:14:35 +0000
Received: from mail249-ch1 (localhost [127.0.0.1])	by mail249-ch1-R.bigfish.com (Postfix) with ESMTP id 9B0611600176	for <ietf@ietf.org>; Thu, 31 Jan 2013 12:14:35 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.249.85; KIP:(null); UIP:(null); IPV:NLI; H:AMSPRD0710HT001.eurprd07.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: -21
X-BigFish: PS-21(zzbb2dI98dI9371I542I1432Izz1ee6h1de0h1202h1e76h1d1ah1d2ahzz1033IL8275dh8275bhz2dh2a8h5a9h668h839h947hd24hf0ah1177h1179h1288h12a5h12a9h12bdh137ah139eh13b6h1441h1504h1537h162dh1631h1758h17f1h184fh1898h18e1h1946h304l35h1155h)
Received: from mail249-ch1 (localhost.localdomain [127.0.0.1]) by mail249-ch1 (MessageSwitch) id 1359634473488649_7542; Thu, 31 Jan 2013 12:14:33 +0000 (UTC)
Received: from CH1EHSMHS007.bigfish.com (snatpool2.int.messaging.microsoft.com [10.43.68.237])	by mail249-ch1.bigfish.com (Postfix) with ESMTP id 6BC4D10C004E	for <ietf@ietf.org>; Thu, 31 Jan 2013 12:14:33 +0000 (UTC)
Received: from AMSPRD0710HT001.eurprd07.prod.outlook.com (157.56.249.85) by CH1EHSMHS007.bigfish.com (10.43.70.7) with Microsoft SMTP Server (TLS) id 14.1.225.23; Thu, 31 Jan 2013 12:14:31 +0000
Received: from DB3PRD0511HT002.eurprd05.prod.outlook.com (157.56.254.213) by pod51017.outlook.com (10.255.160.164) with Microsoft SMTP Server (TLS) id 14.16.263.1; Thu, 31 Jan 2013 12:14:27 +0000
Message-ID: <004901cdffac$1e04c7e0$4001a8c0@gateway.2wire.net>
From: t.p. <daedulus@btconnect.com>
To: t.p. <daedulus@btconnect.com>
References: <20130125213624.E984F1A495@ld9781.wdf.sap.corp><51030B76.2070401@cs.tcd.ie> <00c401cdfc80$2bcbc380$4001a8c0@gateway.2wire.net>
Subject: Reducing time to publication: was Re: FW: Last Call: <draft-farrell-ft-03.txt> (A Fast-Track way toRFCwith Running Code) to Experimental RFC
Date: Thu, 31 Jan 2013 12:04:19 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Originating-IP: [157.56.254.213]
X-OriginatorOrg: btconnect.com
Cc: ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 31 Jan 2013 12:14:37 -0000

Time to publication of an RFC can be reduced by cutting out the pauses,
which could achieved by highlighting when they occur.

This can be done by a tool which, for every active Working Group, runs
monthly and, for every draft adopted by the Working Group, records
whether or not there has been a change and posts this list as an e-mail
to the list of the Working Group.  Where a new version has been
submitted to Tools, then this new version is listed with the date of
submission.  Where the status has changed, as recorded in the tracker
(AD Review, IETF LC, Publication Approved etc), then the new status is
listed with the date of change.  Where nothing has changed, then this is
listed with the date of the last change.  Given the number of I-Ds that
some Working Groups are working on, the best sequence is alphabetic of
I-D name.

Such a list would shine a light on what is moving and what is not.  This
in turn would encourage, motivate, spur those on whom the draft is
waiting to progress it (and anyone else who could contribute).

This works.  I know it does, because something of this ilk happens on a
WG I subscribe to; I imagine the chair does it manually, or perhaps they
screen scrape, but I see it happening.

My first thought was that this would be at the option of the AD or WG
Chairs but on second thought, I think this a mistake.  Often the light
will shine on the AD or Chair but that it healthy - it is not a
criticism of them, rather an invitation for everyone to see what they
could do to move things on.

Tom Petch

----- Original Message -----
From: "t.p." <daedulus@btconnect.com>
To: "Stephen Farrell" <stephen.farrell@cs.tcd.ie>
Cc: "John C Klensin" <john-ietf@jck.com>; "Thomas Narten"
<narten@us.ibm.com>; <ietf@ietf.org>; <adrian@olddog.co.uk>
Sent: Sunday, January 27, 2013 11:19 AM
Subject: Re: FW: Last Call: <draft-farrell-ft-03.txt> (A Fast-Track way
toRFCwith Running Code) to Experimental RFC


> ----- Original Message -----
> From: "Stephen Farrell" <stephen.farrell@cs.tcd.ie>
> To: <mrex@sap.com>
> Cc: "John C Klensin" <john-ietf@jck.com>; "Thomas Narten"
> <narten@us.ibm.com>; <ietf@ietf.org>; <adrian@olddog.co.uk>
> Sent: Friday, January 25, 2013 10:47 PM
> >
> > Hi Martin,
> >
> > On 01/25/2013 09:36 PM, Martin Rex wrote:
> > > I don't know about the last time it happened, but I know about
> > > one time in Nov-2009 in the TLS WG (now rfc5746).
> >
> > I recall that and agree with the sequence of events you
> > describe, but I'm not sure that that situation is
> > relevant when considering this draft, for two reasons:
>
> Sounds a bit like 'don't confuse me with the facts, my mind is made
> up:-)'
>
> The point that Thomas made and John endorsed is that when we want to
> speed things up, our current procedures allow us to do just that.  We
do
> not need a formal process (more complications, more work).  And as
John
> pointed out, having two independent Last Call discussions, on two
> different lists, on communities that may have little overlap, is not
the
> way, IMO, to establish a clear consensus.
>
> Tom Petch
>



From john-ietf@jck.com  Thu Jan 31 06:44:32 2013
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A3ABE21F8868 for <ietf@ietfa.amsl.com>; Thu, 31 Jan 2013 06:44:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.682
X-Spam-Level: 
X-Spam-Status: No, score=-102.682 tagged_above=-999 required=5 tests=[AWL=-0.083, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 fucjzTVAx4z9 for <ietf@ietfa.amsl.com>; Thu, 31 Jan 2013 06:44:31 -0800 (PST)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id A8A6921F85B6 for <ietf@ietf.org>; Thu, 31 Jan 2013 06:44:31 -0800 (PST)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1U0vN9-0005GC-TW; Thu, 31 Jan 2013 09:44:16 -0500
Date: Thu, 31 Jan 2013 09:44:10 -0500
From: John C Klensin <john-ietf@jck.com>
To: "t.p." <daedulus@btconnect.com>
Subject: Re: Reducing time to publication: was Re: FW: Last Call:	<draft-farrell-ft-03.txt> (A Fast-Track way toRFCwith Running	Code) to Experimental RFC
Message-ID: <BF1522A80586ED2AB0D22150@JcK-HP8200.jck.com>
In-Reply-To: <004901cdffac$1e04c7e0$4001a8c0@gateway.2wire.net>
References: <20130125213624.E984F1A495@ld9781.wdf.sap.corp> <51030B76.2070401@cs.tcd.ie> <00c401cdfc80$2bcbc380$4001a8c0@gateway.2wire.net> <004901cdffac$1e04c7e0$4001a8c0@gateway.2wire.net>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Cc: ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 31 Jan 2013 14:44:32 -0000

--On Thursday, January 31, 2013 12:04 +0000 "t.p."
<daedulus@btconnect.com> wrote:

> Time to publication of an RFC can be reduced by cutting out
> the pauses, which could achieved by highlighting when they
> occur.
> 
> This can be done by a tool which, for every active Working
> Group, runs monthly and, for every draft adopted by the
> Working Group, records whether or not there has been a change
> and posts this list as an e-mail to the list of the Working
> Group.  Where a new version has been submitted to Tools, then
> this new version is listed with the date of submission.  Where
> the status has changed, as recorded in the tracker (AD Review,
> IETF LC, Publication Approved etc), then the new status is
> listed with the date of change.  Where nothing has changed,
> then this is listed with the date of the last change.
>...

Tom,

This is interesting but could also introduce a pathology in
which drafts are generated too frequently to encourage (or even
permit) healthy discussion.  If one were going to do this, also
collecting some statistics on how much (or whether) a given
draft was being discussed on a WG mailing list might be very
important.  New drafts and indications of motion like status
changes may be good clues but what really counts for measures of
progress and consensus is whether real discussion is going on. 

  john


From sm@resistor.net  Thu Jan 31 08:56:28 2013
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 776F121F855D for <ietf@ietfa.amsl.com>; Thu, 31 Jan 2013 08:56:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 lGWePWxA9Zt9 for <ietf@ietfa.amsl.com>; Thu, 31 Jan 2013 08:56:28 -0800 (PST)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 0BFDB21F8574 for <ietf@ietf.org>; Thu, 31 Jan 2013 08:56:28 -0800 (PST)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r0VGuHMq010186; Thu, 31 Jan 2013 08:56:20 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1359651382; bh=X5J1iEbAc9ulNuaizwEwqTSoXFxll9Ys8uLwy3yb2Fk=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=WFyorYJV9QjEyVl1Il8wX/Vm3RCJQb6fEtqZb2gHnxUHoIArQWXdUU52YYMjMOsKb gat7goEo0Cmco/9h15Ho/bZeTfoJDw7nL1ouCdpgnUyFon+tne0/8NgZftC1R8ltnJ dRRTNnv1m1CHU/KvEQSszL0MzYEbMHyXk47yi+/g=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1359651382; i=@resistor.net; bh=X5J1iEbAc9ulNuaizwEwqTSoXFxll9Ys8uLwy3yb2Fk=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=dgW5DSWvI1G3TtS8Tc+lZIaIW/ZkO5e7uxwEdTtgDr3RZYxV/5CUK8wX+R1b04SM2 1ztCdAry5IYh+tMssQ5oBk6oiCU72QKrlTYJcYEt/ReH9jW3Bk/LBdl2+s+W3sxfr6 Hbhb8Cjsvvdv4Q8NSCocWC739aeNtwRLYBu/FEfA=
Message-Id: <6.2.5.6.2.20130131073013.0aa87df0@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Thu, 31 Jan 2013 08:51:41 -0800
To: "t.p." <daedulus@btconnect.com>
From: SM <sm@resistor.net>
Subject: Re: Reducing time to publication: was Re: FW: Last Call: <draft-farrell-ft-03.txt> (A Fast-Track way toRFCwith Running Code) to Experimental RFC
In-Reply-To: <004901cdffac$1e04c7e0$4001a8c0@gateway.2wire.net>
References: <20130125213624.E984F1A495@ld9781.wdf.sap.corp> <51030B76.2070401@cs.tcd.ie> <00c401cdfc80$2bcbc380$4001a8c0@gateway.2wire.net> <004901cdffac$1e04c7e0$4001a8c0@gateway.2wire.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 31 Jan 2013 16:56:28 -0000

Hi Tom,
At 04:04 31-01-2013, t.p. wrote:
>Time to publication of an RFC can be reduced by cutting out the pauses,
>which could achieved by highlighting when they occur.

[snip]

>Such a list would shine a light on what is moving and what is not.  This
>in turn would encourage, motivate, spur those on whom the draft is
>waiting to progress it (and anyone else who could contribute).

There was an interesting quote from #overlyhonestmethods.  I cannot 
locate it right now as the web site is whaling out.

There is a Daily Dose web page (see http://tools.ietf.org/dailydose/ 
).  The web page provides a snapshot of what's being "published" in 
the IETF.  However, it does not provide a view of what is moving and 
what is not moving.  I don't have a view of what an area or what a 
working group is up to.

Sometimes it come as a surprise when working group participants hear 
that their working group is being shut down.  It is possible to tell 
whether a working group might be shut down.  It is possible to 
identify some of the issues which can delay publication.  The data 
for what you suggested is available from the datatracker.  The data 
to identify WG activity is also available.  I don't know how to 
assess progress though.

Regards,
-sm 


From barryleiba.mailing.lists@gmail.com  Thu Jan 31 16:25:52 2013
Return-Path: <barryleiba.mailing.lists@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C973021F8A5F for <ietf@ietfa.amsl.com>; Thu, 31 Jan 2013 16:25:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.018
X-Spam-Level: 
X-Spam-Status: No, score=-103.018 tagged_above=-999 required=5 tests=[AWL=-0.041, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
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 8IEoAsZic-ex for <ietf@ietfa.amsl.com>; Thu, 31 Jan 2013 16:25:52 -0800 (PST)
Received: from mail-ve0-f176.google.com (mail-ve0-f176.google.com [209.85.128.176]) by ietfa.amsl.com (Postfix) with ESMTP id 3CE8B21F896B for <ietf@ietf.org>; Thu, 31 Jan 2013 16:25:52 -0800 (PST)
Received: by mail-ve0-f176.google.com with SMTP id jz10so2487373veb.7 for <ietf@ietf.org>; Thu, 31 Jan 2013 16:25:51 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=+61bJ1uvljHsouoebdYgR6tY8165Ygrrp7XlZ/04uyI=; b=plYSg1aZxcDSg8Obq5llPFY6qI0G6CMLydgeSG/oWDCI15P/KOtl4hWFYSMZJ/9jcs QrejT/kmds1GQLkvb+s3Jkl9E4aUhjWC8pjjDH/njB2CEALhfzHtneM5n2jX+JBtVSAl sHEw1qBSahuhqbi544IcdOU29509xldyZbdUYzGVzAdUruZNLxwuPjD87JYihFHF7Hjb ZWsElc9s1lxrSTLAgdkX+4442FlbTmVldLsIq/s/rPdFCLCYpJLVvPtvdOnHnOpDsJkU 7fCr+gA8BDFi2vTh2F+N4AqT1IwnjlVu2u3nbYrMHuVuNl6yIK+EFH3b/o0Yus4wkIap Xq/g==
MIME-Version: 1.0
X-Received: by 10.58.106.161 with SMTP id gv1mr5676621veb.35.1359678351522; Thu, 31 Jan 2013 16:25:51 -0800 (PST)
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.59.3.41 with HTTP; Thu, 31 Jan 2013 16:25:51 -0800 (PST)
In-Reply-To: <5109680A.1040400@dcrocker.net>
References: <008501cdfeca$59a77cd0$0cf67670$@olddog.co.uk> <5109680A.1040400@dcrocker.net>
Date: Thu, 31 Jan 2013 19:25:51 -0500
X-Google-Sender-Auth: yzUquzJ9kBEPFcpYAW8GRflEsf4
Message-ID: <CAC4RtVCipnE2q-91eVJq0aEt_sr+J5DmgQQWH5qkE+QmTvoscw@mail.gmail.com>
Subject: Re: When is a 3933 experiment necessary? [Was: Last Call: <draft-farrell-ft-03.txt> (A Fast-Track way to RFC with Running Code) to Experimental RFC]
From: Barry Leiba <barryleiba@computer.org>
To: Dave Crocker <dcrocker@bbiw.net>
Content-Type: text/plain; charset=ISO-8859-1
Cc: John C Klensin <john-ietf@jck.com>, Adrian Farrel <adrian@olddog.co.uk>, IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 01 Feb 2013 00:25:52 -0000

>      We are a diverse community.  Absent very, very strong consensus that a
> problem is serious enough to warrant a change, the community is not likely
> to line up automatically behind a proposal.  We will always have some people
> who prefer no change and some who offer their different, favorite
> approaches, or and some who offer a zillion tweaks.  In the aggregate, that
> makes for entropy, not consensus.
...
>    1. A wg has a committed core of participants who have agreed on a common
> goal.
>    2. A wg process is managed.
>
> On the average, proposals for IETF process change benefit from neither of
> these.

These are good observations; I agree with them, as well as with your
suggested approach to it.

I want to make a related point (which Dave's recommendation of classic
group facilitation can cut through if we allow it to):

We often pick on every suggested change and point out every possible
flaw, with different people holding out behind different flaws, and we
get stuck there.  There seems to be some assumption, when we do this,
that our current process doesn't also have significant flaws.  But the
very reason we're trying to change something is that we *already* have
a process with flaws.

We know that no process we ever come up with will be perfect, and
agreeing to change is a question of deciding what the flaw balance is.
 We need to allow ourselves to move from one (known, "comfortable")
set of flaws to a new set, *if* we can come to a reasonable agreement
that we've improved things in a useful way.

Barry

From d3e3e3@gmail.com  Thu Jan 31 17:42:07 2013
Return-Path: <d3e3e3@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 72D2221F87D7 for <ietf@ietfa.amsl.com>; Thu, 31 Jan 2013 17:42:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.234
X-Spam-Level: 
X-Spam-Status: No, score=-103.234 tagged_above=-999 required=5 tests=[AWL=0.365, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
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 goN9aiotxV8u for <ietf@ietfa.amsl.com>; Thu, 31 Jan 2013 17:42:06 -0800 (PST)
Received: from mail-oa0-f41.google.com (mail-oa0-f41.google.com [209.85.219.41]) by ietfa.amsl.com (Postfix) with ESMTP id 547D221F8A1E for <ietf@ietf.org>; Thu, 31 Jan 2013 17:42:06 -0800 (PST)
Received: by mail-oa0-f41.google.com with SMTP id i10so3777992oag.0 for <ietf@ietf.org>; Thu, 31 Jan 2013 17:42:06 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:mime-version:in-reply-to:references:from:date:message-id :subject:to:content-type; bh=TORyvZi+4syO/PNHjDIUe4iNeIX0CN2sWZ4uoz0bXdw=; b=fa4Pyf5moVkFMfwWo76bI+FfOFl4djcE3OBoENB6AD+6dMcppc0bIggyBaNAiJv8df qeoen53OFbF7ne1hcoH6rLj33fw5TdINvVjNKaP7KJUNrXySiSUWVg1908ow3vbIJBIH UtrYsbzsTSNOr6GQ43cdaCj3xw4LSHEex3Tr4hkpwXLB/JX0YfCk5JKLB137KKGCrsDB yZxTV4jaNwjiUT6iD668WMyhIkMJNnFI7Qbgb1b+GpmqqnQP0q/cTnZsUHaSDzyD7suh K8dXr7e6woPdpZ14Ln9Z7H9DPj1gMCuRyPAtYP+cjZio45FGeWxR1C776bfp5XKv7kTg m+iQ==
X-Received: by 10.60.172.71 with SMTP id ba7mr8376731oec.50.1359682925943; Thu, 31 Jan 2013 17:42:05 -0800 (PST)
MIME-Version: 1.0
Received: by 10.76.98.168 with HTTP; Thu, 31 Jan 2013 17:41:45 -0800 (PST)
In-Reply-To: <5109680A.1040400@dcrocker.net>
References: <008501cdfeca$59a77cd0$0cf67670$@olddog.co.uk> <5109680A.1040400@dcrocker.net>
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Thu, 31 Jan 2013 20:41:45 -0500
Message-ID: <CAF4+nEET=V7EZWAUZ7gtqx8UXUe=y7Okhoe7ijaOvczyu-rsUg@mail.gmail.com>
Subject: Re: When is a 3933 experiment necessary? [Was: Last Call: <draft-farrell-ft-03.txt> (A Fast-Track way to RFC with Running Code) to Experimental RFC]
To: IETF Discussion <ietf@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 01 Feb 2013 01:42:07 -0000

On Wed, Jan 30, 2013 at 1:35 PM, Dave Crocker <dhc@dcrocker.net> wrote:
> On 1/30/2013 1:15 AM, Adrian Farrel wrote:
>>     I do agree with
>> Spencer that getting consensus for a process change always looks like a
>> formidable task. Small changes never address enough of the problem or the
>> right
>> piece of the problem. Large changes are too much in one go. :-) So, it
>> seems to
>> be increasingly hard to make changes to our process.
>
> I suspect it's not 'increasingly' but rather that it's always been extremely
> difficult...
>
> Let me suggest a different possibility for the challenge in this topic:
>
>      We are a diverse community.  Absent very, very strong consensus that a
> problem is serious enough to warrant a change, the community is not likely
> to line up automatically behind a proposal.  We will always have some people
> who prefer no change and some who offer their different, favorite
> approaches, or and some who offer a zillion tweaks.  In the aggregate, that
> makes for entropy, not consensus.

  "It ought to be remembered that there is nothing more difficult to
take in hand, more perilous to conduct, or more uncertain in its
success, than to take the lead in the introduction of a new order of
things. Because the innovator has for enemies all those who have done
well under the old conditions, and lukewarm defenders in those who may
do well under the new."
                    Niccolo Machiavelli

Donald
=============================
 Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
 155 Beaver Street, Milford, MA 01757 USA
 d3e3e3@gmail.com

>      What makes this process different from what we see in successful
> working groups?
>
> I think there are two things:
>
>    1. A wg has a committed core of participants who have agreed on a common
> goal.
>
>    2. A wg process is managed.
>
> On the average, proposals for IETF process change benefit from neither of
> these.
>
> Hence I suggest that a proposal needs to recruit a committed core /before/
> going public, and the discussion needs classic group facilitation, in terms
> of tracking issues, maintaining focus, and pursuing consensus.
>
> d/
>
> --
>  Dave Crocker
>  Brandenburg InternetWorking
>  bbiw.net

From dhc@dcrocker.net  Thu Jan 31 18:32:25 2013
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CA58921F87DF for <ietf@ietfa.amsl.com>; Thu, 31 Jan 2013 18:32:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[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 5wTvWt-x7CAh for <ietf@ietfa.amsl.com>; Thu, 31 Jan 2013 18:32:25 -0800 (PST)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 423CB21F856D for <ietf@ietf.org>; Thu, 31 Jan 2013 18:32:25 -0800 (PST)
Received: from [192.168.1.66] (76-218-9-215.lightspeed.sntcca.sbcglobal.net [76.218.9.215]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id r112WMGS029425 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 31 Jan 2013 18:32:23 -0800
Message-ID: <510B2930.20200@dcrocker.net>
Date: Thu, 31 Jan 2013 18:32:16 -0800
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130107 Thunderbird/17.0.2
MIME-Version: 1.0
To: Donald Eastlake <d3e3e3@gmail.com>
Subject: Re: When is a 3933 experiment necessary? [Was: Last Call: <draft-farrell-ft-03.txt> (A Fast-Track way to RFC with Running Code) to Experimental RFC]
References: <008501cdfeca$59a77cd0$0cf67670$@olddog.co.uk> <5109680A.1040400@dcrocker.net> <CAF4+nEET=V7EZWAUZ7gtqx8UXUe=y7Okhoe7ijaOvczyu-rsUg@mail.gmail.com>
In-Reply-To: <CAF4+nEET=V7EZWAUZ7gtqx8UXUe=y7Okhoe7ijaOvczyu-rsUg@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Thu, 31 Jan 2013 18:32:23 -0800 (PST)
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 01 Feb 2013 02:32:25 -0000

On 1/31/2013 5:41 PM, Donald Eastlake wrote:
> On Wed, Jan 30, 2013 at 1:35 PM, Dave Crocker <dhc@dcrocker.net> wrote:
>>       We are a diverse community.  Absent very, very strong consensus that a
>> problem is serious enough to warrant a change, the community is not likely
>> to line up automatically behind a proposal.  We will always have some people
>> who prefer no change and some who offer their different, favorite
>> approaches, or and some who offer a zillion tweaks.  In the aggregate, that
>> makes for entropy, not consensus.
>
>    "It ought to be remembered that there is nothing more difficult to
> take in hand, more perilous to conduct, or more uncertain in its
> success, than to take the lead in the introduction of a new order of
> things. Because the innovator has for enemies all those who have done
> well under the old conditions, and lukewarm defenders in those who may
> do well under the new."
>                      Niccolo Machiavelli



Nice.

Might be worth adding that to the Intros for all IETF process and 
structure documents...

d/
-- 
  Dave Crocker
  Brandenburg InternetWorking
  bbiw.net

From randy@psg.com  Thu Jan 31 21:14:56 2013
Return-Path: <randy@psg.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4995821F8971 for <ietf@ietfa.amsl.com>; Thu, 31 Jan 2013 21:14:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599]
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 BMvI5RLdvLnH for <ietf@ietfa.amsl.com>; Thu, 31 Jan 2013 21:14:55 -0800 (PST)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by ietfa.amsl.com (Postfix) with ESMTP id E219621F895B for <ietf@ietf.org>; Thu, 31 Jan 2013 21:14:55 -0800 (PST)
Received: from localhost ([127.0.0.1] helo=ryuu.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.80.1 (FreeBSD)) (envelope-from <randy@psg.com>) id 1U18xi-000HMD-9q; Fri, 01 Feb 2013 05:14:54 +0000
Date: Fri, 01 Feb 2013 14:14:53 +0900
Message-ID: <m28v78linm.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Barry Leiba <barryleiba@computer.org>
Subject: Re: When is a 3933 experiment necessary? [Was: Last Call:	<draft-farrell-ft-03.txt> (A Fast-Track way to RFC with Running Code)	to Experimental RFC]
In-Reply-To: <CAC4RtVCipnE2q-91eVJq0aEt_sr+J5DmgQQWH5qkE+QmTvoscw@mail.gmail.com>
References: <008501cdfeca$59a77cd0$0cf67670$@olddog.co.uk> <5109680A.1040400@dcrocker.net> <CAC4RtVCipnE2q-91eVJq0aEt_sr+J5DmgQQWH5qkE+QmTvoscw@mail.gmail.com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
Cc: IETF Disgust <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 01 Feb 2013 05:14:56 -0000

> We often pick on every suggested change and point out every possible
> flaw, with different people holding out behind different flaws, and we
> get stuck there.  There seems to be some assumption, when we do this,
> that our current process doesn't also have significant flaws.  But the
> very reason we're trying to change something is that we *already* have
> a process with flaws.
> 
> We know that no process we ever come up with will be perfect, and
> agreeing to change is a question of deciding what the flaw balance is.
> We need to allow ourselves to move from one (known, "comfortable")
> set of flaws to a new set, *if* we can come to a reasonable agreement
> that we've improved things in a useful way.

perfection is the enemy of good

and adding complexity to overcome objections is an engineer's disease

randy

From narten@us.ibm.com  Thu Jan 31 21:53:13 2013
Return-Path: <narten@us.ibm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E00C821F8840 for <ietf@ietfa.amsl.com>; Thu, 31 Jan 2013 21:53:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.599
X-Spam-Level: 
X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
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 f47qyM1iMCDk for <ietf@ietfa.amsl.com>; Thu, 31 Jan 2013 21:53:11 -0800 (PST)
Received: from e8.ny.us.ibm.com (e8.ny.us.ibm.com [32.97.182.138]) by ietfa.amsl.com (Postfix) with ESMTP id DFA8A21F8864 for <ietf@ietf.org>; Thu, 31 Jan 2013 21:53:08 -0800 (PST)
Received: from /spool/local by e8.ny.us.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for <ietf@ietf.org> from <narten@us.ibm.com>; Fri, 1 Feb 2013 00:53:07 -0500
Received: from d01dlp03.pok.ibm.com (9.56.250.168) by e8.ny.us.ibm.com (192.168.1.108) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted;  Fri, 1 Feb 2013 00:53:05 -0500
Received: from d01relay05.pok.ibm.com (d01relay05.pok.ibm.com [9.56.227.237]) by d01dlp03.pok.ibm.com (Postfix) with ESMTP id 7C139C90043 for <ietf@ietf.org>; Fri,  1 Feb 2013 00:53:04 -0500 (EST)
Received: from d01av04.pok.ibm.com (d01av04.pok.ibm.com [9.56.224.64]) by d01relay05.pok.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id r115r4to326354 for <ietf@ietf.org>; Fri, 1 Feb 2013 00:53:04 -0500
Received: from d01av04.pok.ibm.com (loopback [127.0.0.1]) by d01av04.pok.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP id r115r4fZ011535 for <ietf@ietf.org>; Fri, 1 Feb 2013 00:53:04 -0500
Received: from rotala.raleigh.ibm.com (rotala.raleigh.ibm.com [9.44.115.148]) by d01av04.pok.ibm.com (8.14.4/8.13.1/NCO v10.0 AVin) with ESMTP id r115r3nt011484 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Fri, 1 Feb 2013 00:53:04 -0500
Received: from rotala.raleigh.ibm.com (localhost.localdomain [127.0.0.1]) by rotala.raleigh.ibm.com (8.14.5/8.12.5) with ESMTP id r115r21B018451 for <ietf@ietf.org>; Fri, 1 Feb 2013 00:53:03 -0500
Received: (from narten@localhost) by rotala.raleigh.ibm.com (8.14.5/8.14.5/Submit) id r115r20i018396 for ietf@ietf.org; Fri, 1 Feb 2013 00:53:02 -0500
From: Thomas Narten <narten@us.ibm.com>
Message-Id: <201302010553.r115r20i018396@rotala.raleigh.ibm.com>
Date: Fri, 01 Feb 2013 00:53:02 -0500
To: ietf@ietf.org
Subject: Weekly posting summary for ietf@ietf.org
User-Agent: Heirloom mailx 12.5 7/5/10
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Content-Scanned: Fidelis XPS MAILER
x-cbid: 13020105-9360-0000-0000-00000FFFE6D8
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 01 Feb 2013 05:53:14 -0000

Total of 55 messages in the last 7 days.
 
script run at: Fri Feb  1 00:53:02 EST 2013
 
    Messages   |      Bytes        | Who
--------+------+--------+----------+------------------------
 14.55% |    8 | 12.99% |    66915 | stephen.farrell@cs.tcd.ie
  5.45% |    3 | 10.74% |    55297 | benl@google.com
  1.82% |    1 | 13.45% |    69278 | davids@iit.edu
  7.27% |    4 |  7.07% |    36419 | daedulus@btconnect.com
  7.27% |    4 |  5.47% |    28148 | john-ietf@jck.com
  7.27% |    4 |  5.37% |    27683 | sm@resistor.net
  7.27% |    4 |  4.99% |    25680 | dhc@dcrocker.net
  5.45% |    3 |  4.13% |    21272 | adrian@olddog.co.uk
  5.45% |    3 |  3.89% |    20035 | abdussalambaryun@gmail.com
  5.45% |    3 |  3.59% |    18484 | lear@cisco.com
  3.64% |    2 |  3.23% |    16656 | narten@us.ibm.com
  3.64% |    2 |  3.21% |    16516 | touch@isi.edu
  3.64% |    2 |  2.59% |    13323 | mrex@sap.com
  3.64% |    2 |  2.53% |    13011 | barryleiba@computer.org
  1.82% |    1 |  2.94% |    15163 | jeff.hodges@kingsmountain.com
  1.82% |    1 |  2.37% |    12197 | dromasca@avaya.com
  1.82% |    1 |  2.24% |    11534 | loa@pi.nu
  1.82% |    1 |  1.91% |     9821 | fluffy@cisco.com
  1.82% |    1 |  1.48% |     7624 | spencer@wonderhamster.org
  1.82% |    1 |  1.45% |     7473 | d3e3e3@gmail.com
  1.82% |    1 |  1.26% |     6499 | brian.e.carpenter@gmail.com
  1.82% |    1 |  1.14% |     5859 | johnl@taugh.com
  1.82% |    1 |  0.99% |     5078 | brian@innovationslab.net
  1.82% |    1 |  0.98% |     5069 | tglassey@earthlink.net
--------+------+--------+----------+------------------------
100.00% |   55 |100.00% |   515034 | Total

